I was discussing with Steven about the prototype implementation and few things I wanted to clarify of what the prototype means.
A Prototype is something which is a “Throw Away” work. Don’t get me wrong, It’s a fully workable solution but with limitations and thinks like that. With the prototype, one doesn’t worry about how it’s implemented, what technology, backend, API’s if any etc. meaning, what the end users care about is to have a feel about the working application. Let’s say, we are dealing with the Mobile App implementation, say if I’m the end user, I want to see whether or not the App can be developed as per the Spec. How feasible it’s to develop a working solution that can be visualized so later it can be finalized for real development.
Wireframe vs Prototype vs Mockups
There’s often a confusion for peoples to understand these aspects. Please take a look into - https://designmodo.com/wireframing-prototyping-mockuping/
Why Prototyping Quickly?
You might wonder why hurrying and quickly developing a prototype. As most of you are aware about the software development life cycle, it involves lots of brainstorming, analysis, building a proper high level and low level implementation specs, technology decisions, finalize software and hardware requirements etc. Then come up with a backend database design, Services or API’s if any depending on the design. There’s a significant work involved in producing a fully fledged workable solution. It equates to the timelines and cost of development. That’s exactly why it’s recommended to build a fully workable, quick, easy to showcase and throwaway applications that can be demonstrated to the end user.
Why Prototyping Is a ThrowAway Work?
Most of the Prototypes are developed in a quick fashion without the backend meaning mostly coded with Mock data etc. These prototypes are coded without a proper design and choosing appropriate technology etc. Throwaway doesn’t mean you cannot reuse portion of it but overall a Prototype App is not meant to be used in a real world like any other production apps.
There are several advantages in prototyping the App.
Prototypes is usually developed in a quick fashion so the end users doesn’t have to wait for months or year
Prototypes is used to demonstrate a workable solution.
Getting an early feedback is really important. With the prototype, it’s possible at the early stage
Prototyping helps in understanding the development estimates of the real app
Steven Reubenstone Shalini Sundari Please review and let me know your feedbacks.