3 ms·
Are HTML5 web apps still viewed as wise first move into mobile app development? We're seeing companies consistently move from web to native... but generally on
by jordn 14y ago
Are HTML5 web apps still viewed as wise first move into mobile app development?
We're seeing companies consistently move from web to native... but generally only after hitting some performance barrier. Switching to native then seems to be like any other optimisation. So even if the web performance barely improves, does developing for web first still make sense (platform independence, rapid iterations etc) or should we be thinking native first?
I'd be interested in hearing whether LinkedIn and co regret going HTML5 in the first place.
- camus 14y agoif one builds an "app" , since it uses a "webview" inside a native application , it is always "native" ( except for firefox and likes os where the browser is the "os" ). Phonegap and likes use native code so one can bundle html+js into a native app. I tell my clients , instead of using a wrapper , to build a webapp directly. most of the LOB-apps require an internet connection anyway , and things like camera can be accessed from the browser now , on most mobile os. And it is easy to explain clients how to bookmark a webapp to the home screen. packaged webapps are overrated imho , in most cases a webapp makes more sense.
- jordn 14y agoNo need for the patronising scare quotes. I'm talking about whether to base your app on web technologies like HTML5 and js (regardless of delivery method - web/native webview wrapper), or to use native UI elements/memory management etc of the OS.
- pspeter3 14y agoI don't think he is trying to be condescending. He has a point that the lack of Nitro or V8 in a webview means you'll have a performance hit when you do a wrapper. HTML5 provides most of the APIs you need anyway, especially if you are on firefox OS