Is Your Idea Worth Trying? MVP, PoC and More

We can choose from a couple of different approaches when it comes to testing a mobile app before we dive into full business mode.

Which is short for “proof of concept”. It should answer the question: Is this idea viable?

Usually, it is developed as an internal project to validate the main functions of an app and determine if the production process should start at all. It gives all the project participants fast clarification if the concept is worth pursuing.  It’s also the cheapest and safest way to test it beforehand.

It doesn’t mean that if PoC analysis results in a negative outcome, we should drop the idea. It actually can help it evolve, so the product can be more profitable for the owner and useful for their clients.

MVP stands for “minimum viable product”, while MVVVP is “minimal viable valuable validating product”.

MVP is a minimal form of an app that can be launched so we can collect feedback from the users. It should have core features and basic design so people who use it can focus on its functionalities. The main focus of MVP is proving value proposition.

MVVVP is just an extended concept of MVP, formed by Guy Kawasaki. Besides economic worth, MVVVP should also determine if the product changes the lives of its users and if the idea corresponds with the brand’s philosophy. Although it is not a well-known term, keeping in mind the rules of MVVVP can make MVP even more reliable.

We recognize them because prototypes are well known from industries other than IT. Car manufacturers and other companies that create physical objects use prototypes to showcase new models of their products.

In the digital world, prototypes are the same thing. Their main goal is to test whether an app works properly. It’s the first chance to go through the actual app and see how it works. A prototype can be designed every step of the way to the final result. It allows seeing how the product will work and what else is there to be changed.

At iteo, we usually create prototypes based on UX product workshop results we achieved with a client. We prepare low-fi views and if there’s a need for more – an Invision App prototype. Usually, they are a part of functionalities, including user-flows like login process or adding to cart process.

Ideally – all of them. As you can see, PoC, MVP and a prototype have slightly different objectives but their purpose is similar – to see if the idea is worth trying. They are useful tools to polish the app on every stage of production. This way we can be sure that our product will fulfill all business requirements we assumed at the beginning.

Also, you probably already noticed that each of these methods can be useful at different times. PoC will be perfect at the beginning before the development process starts. MVP is great to communicate with future clients and users of the app. Collecting feedback is crucial to understand how our product can serve its customers. And a prototype can be useful in every step of the way – some do it towards the end of the project. At iteo, we prefer to make it early, so we can give the client an idea of how their product will actually work.

Why should I even do it?

Each of those methods will give you comprehensive feedback and an idea of what you should do next. If you wonder why is that important, the simplest and most important reason is to save time and money.

You will lower the usage of your resources because the team won’t waste it on developing an app that has flaws or is not viable. Also, if the value of your product will be proved beforehand, your business will have an opportunity to gain as much as possible out of it. You won’t lose money and clients thanks to a failed idea.