Starting right with a mobile-optimized MVP

Starting right with a mobile-optimized MVP

Kwang Wei No Comment
Commentary

Before you develop your solution across different operating platforms, its probably a good practice to validate your concept with an MVP (minimal viable product). This is where you will be able to gather more insights to how well your product performs through actual interactions with your users.

“When the product is finally released, customers don’t like the product, the startup fails – going down with it countless costly work hours and perhaps financial resources invested in full-scale development.”

Startups often begin with an idea for a product that they think people want , in part, fueled by their passion and hence personal biases. They spend months, sometimes years, perfecting that product without ever shipping or showing it to their first perspective customer. When they perform poorly in customer acquisition, it is often because they never spoke to prospective customers and lacked insights to execute the concept effectively.

When the product is finally released, customers don’t like the product, the startup fails – going down with it countless costly work hours and perhaps financial resources invested in full-scale development.

 

Apple or Android first? Its not about the device.

Consider using web applications to reach out to both groups of customers. Modern web applications are responsive, cross-platform and are able to deliver functionalities used to be only available on native solutions such as  real-time communications and push notifications. Rather than deciding on which device to serve, focus on the functionalities and the user experience.

With frameworks such as Ionic and PhoneGap, it is indeed possible to publish ‘wrapped up’ web apps on app stores. Disregarding that, a vanilla web app can be added to homescreen via “Add to homescreen” prompt. This may also imply a less obtrusive workflow as compared with the native applications when it comes to user acquisition. Downloading a native app often requires a higher level of conviction of the value it offers before it happens, as compared to simply accessing a web app from a referral link.

Well- developed web apps perform well across multiple platforms. Designed to be responsive, they would work smoothly across different OS and screen sizes. The pros and cons between web app and native development has been pretty well documented on various articles. Beyond costly development for 2 separate platforms; for the purpose of MVP, allowing users to experience your service before committing to a download should be an important consideration.

Product developer at Sol59. Specializes in user experience and processes- particularly in the field of traditional retail businesses.


Let us know if there's something we can help you with.

I would like to learn more