3 ms·
Your definition of "device functionality" is pretty different from mine then - consider local storage on a device. Many enterprise applications can end up stori
by king_magic 10y ago
Your definition of "device functionality" is pretty different from mine then - consider local storage on a device. Many enterprise applications can end up storing massive amounts of data on devices; that data often needs to be encrypted. Not gonna fly with a web app.
Web apps don't support push notifications on devices. Again, a hugely important example of extremely common device functionality.
Web apps require constant connectivity. Device goes into a tunnel, app quickly stops working. Or even more realistic, user drives 20km to the middle of nowhere, has no cell service, but still needs to do their job without worrying about web site connectivity.
And those are just the extremely common use cases. Again, I'm not hating on mobile-optimized web. There are many use cases where it makes perfect sense. But you really can't make a blanket statement like "So for a majority of native apps a web app makes more sense"; it's just not the case.
- palakchokshi 10y agoEnterprise applications are a different beast, especially if they are report heavy. Having said that HTML5 does have offline storage API albeit with a 5MB limit though support for it is up to the browser. HTML5 also has Notifications API[1] which can be leveraged for push notifications on mobile devices. I do not disagree that there are many use cases for using Apps especially in the Enterprise space but there are far too many consumer apps than enterprise ones so maybe I should change that statement to "a majority of native consumer apps" :) [1]https://mobiforge.com/design-development/web-push-notifications https://mobiforge.com/design-development/web-push-notificati...
- king_magic 10y agoEnterprise apps are a perfectly normal beast for mobile development, 5MB of local storage is a joke, and the notifications you're referring to are not true platform push notifications.