News for hackers. Stuff that matters.
Re:Unraveling HTML5 vs. Native by Zigurd on Tuesday April 30, 2013 @07:09PM (#5635473)
I think the "functionality" axis doesn't work. One could argue some high-value enterprise Web apps are more "functional" than Facebook Home, but that does nothing to capture why it is appropriate for the Web app to be implemented that way and why it is preposterous to suggest Facebook should be done in HTML5.

The importance of power consumption, fine-grained interactivity, the need to fit non-browser concepts in user experience such as AppWidget in Android, the desirability of sync vs. CRUD-over-IP etc. are among the decision points for choosing one or more client implementation approaches.

Then there is the fact that most high-value apps do not have a single answer for implementation approach, and that these high value apps were not born that way. When Facebook turned away from making mobile Web apps, they did not also start making native desktop clients.

This is how I would boil it down: Is your app valuable enough to be worth spending enough on a mobile client implementation than can do things a Web interface cannot do? That is, for a minimum viable product, you probably need to do almost everything your Web interface does, but in order to really justify the effort, you should, at least, have a road map to some place where the mobile app exceeds what the Web app can do. This might be as simple as notifications and an AppWidget. But preferably it's something app-specific.

There are no comments on this comment yet.