Deciding on whether to develop a web or native app is the most important decision you'll make once the app has been approved to be developed by your users or customer. In some cases, this is something already decided by the user or customer because they already have something in mind. On the other hand, if you're building an app for public consumption, you and your team will have to make the decision. No matter what, it can sometimes be a difficult decision, so it's important you understand the factors. Here are some of the deciding factors:
That's just a taste of the kinds of question that you need to carefully evaluate. Another important wrinkle in this decision is that sometimes you find you have to combine both web and native. As a developer, I have had to write an app for a large utility that needed to integrate into their enterprise asset system, which used a web app frontend but also required native performance due the volume of the data and the speed at which users drove down the road.
There are no easy answers here. You will need to carefully evaluate your alternatives and make the best decision. Don't be surprised if you start down one path and realize that the other path was more appropriate. If the answer isn't obvious, hire a consultant, review other apps (both native and web), determine the cost, get everyone involved, conduct a proof of concept, and most importantly, be prepared to learn and keep an open mind.
3.15.235.188