This is a great example of the power of HTML5 and excites me about the future of it.
I'm a web and iOS developer and I'm starting a consumer facing app and here's my release priority:
1) Web app for desktop, tablet, and mobile using responsive web design
Pro: Every device in the world can reach my app. Since I'm trying to gain exposure, I want everyone to be able to experience what the app has to offer no matter their device or OS.
Con: Currently, users don't expect to interact with my app in this way. They want to go to the App Store and download an app. They also want to use something that they are used to on their specific platform. (To counter this (and for other reasons), the plan is to label the app as beta, so users know what they're getting themselves into and what to expect.)
2) Native App for tablets and smartphones
Pro: Performance, distribution, and native controls. Also, mobile users will use my app differently than desktop users so they deserve their own design and features.
Con: Resources in time and stress managing several code bases.
3) Native App for desktop
Pro: Performance, distribution, and native controls. Also, desktop users will use my app differently than mobile users to they deserve their own design and features.
Con: Resources in time and stress managing several code bases.
Existing case in point - Trello. They started with a responsive web app, they made a great native mobile app, and I expect them to release an awesome desktop app soon.
If you have the time to validate a different approach using Html5 and mixing Native OpenGL, you can see it by download a Android Apk in https://github.com/Srid68/Priya.InfoList (Early Alpha)
I'm a web and iOS developer and I'm starting a consumer facing app and here's my release priority:
1) Web app for desktop, tablet, and mobile using responsive web design
Pro: Every device in the world can reach my app. Since I'm trying to gain exposure, I want everyone to be able to experience what the app has to offer no matter their device or OS.
Con: Currently, users don't expect to interact with my app in this way. They want to go to the App Store and download an app. They also want to use something that they are used to on their specific platform. (To counter this (and for other reasons), the plan is to label the app as beta, so users know what they're getting themselves into and what to expect.)
2) Native App for tablets and smartphones
Pro: Performance, distribution, and native controls. Also, mobile users will use my app differently than desktop users so they deserve their own design and features.
Con: Resources in time and stress managing several code bases.
3) Native App for desktop
Pro: Performance, distribution, and native controls. Also, desktop users will use my app differently than mobile users to they deserve their own design and features.
Con: Resources in time and stress managing several code bases.
Existing case in point - Trello. They started with a responsive web app, they made a great native mobile app, and I expect them to release an awesome desktop app soon.