#developingourprototype

A minimum viable product, or MVP, is a product with enough features to entice new customers and validate a product concept early in the product development cycle. To put it another way, this is the process of creating a simplified product to test your hypothesis. In industries like software and IT, the MVP can help a company or startup get user feedback as soon as possible so that it can iterate and improve the product.

Furthermore, it allows businesses to cut costs and risks many times over and, with the right approach, come up with a viable business idea, as opposed to the previous methodology, in which companies create a product, launch it, and then discover that it is not a viable product. What a waste of time and money! MVP enables a company to collect as much validated learning about customers with the least amount of effort.

Developing NavigaTour’s Prototype

Mr. Ronald mentioned in his discussion that it is best to create the wireframe as a group, which we considered, but I was in charge of the layout of our application as NavigaTour's engineer. I chose a med-fidelity wireframe with Canva, which included a more accurate layout of the application. We ensured that our application has the combination of the following features in such a way that its core features solved at least one problem effectively and kept us competitive; while also including exciting features that solved a problem – something unique to our target customers. We then demonstrated our prototype to friends and family and received some positive feedbacks. 

A few people mentioned how much they liked the idea of catering to everyone, including people with disabilities and those who are visually impaired. Some expressed concern about mall updates, speculating on the possibility of shop relocations within the mall. “Do you think you'll be able to update it right away?” This question raises an intriguing point, which is why we set up a separate account for management so that we can easily update the application. A few people also mentioned that they wished the color palette was a little friendlier, and I couldn't agree with them more. I actually had trouble deciding on a color for the application. I thought it would be great to stick with our brand color, but our respondents said they preferred a more user-friendly palette.

This process aided our application in the following ways: we were able to test our product hypothesis with limited resources, we received valuable feedback without hiring or wasting engineering hours, we were able to get the product to our customers, and we established required abilities in crafting our application.