Certain products are born because of an absence of similar solutions in the market, while others are created because of the gaps that exist in the available products.

Design Thinking Approach: In this framework, you start with understanding the users, their issues and then identify the possible solutions for the user group. This framework ends with creating a prototype and testing the solution in the market to check the market fit.

New Product Development Framework: This is a more commonly accepted approach where you begin with your product ideas and validate them in the market to check for the fit. Once it's validated, you build a prototype, plan your entire production and post-production, and work on the costing before actual development.

As is true with most technology selections, there’s no one-size-fits-all answer when it comes to the type of mobile app to develop. There are numerous web app best practices to consider, not all of which are technical. Who is your target audience? Are they more likely to prefer a mobile web or a native app? What’s the difference between native and hybrid apps? What development resources do you have and which mobile technologies are they most familiar with? What is the licensing and sales model that you’re envisioning for your product?

And beyond the old web apps versus native apps question, a hybrid mobile app may be the right answer for you, depending on your requirements and resource constraints. Hybrid apps, like native apps, run on the device itself (as opposed to inside a browser) but are written with web technologies (HTML5, CSS, and JavaScript) and typically underpinned by a hybrid app framework. More specifically, hybrid apps run inside a native container and leverage the device’s browser engine (but not the browser) to render the HTML and process the JavaScript locally. A web-to-native abstraction layer enables access to device capabilities that are not accessible in mobile web applications, such as the accelerometer, camera, and local storage.