Comments for InterfaceThis

Comment on Is HTML5 Ready for Prime Time vs. Native? (Mobile App Development) by PhoneGap – A Device Independent Platform « TMK Mobile

PhoneGap – A Device Independent Platform « TMK Mobile — Tue, 31 Jan 2012 15:54:40 +0000

[...] post short, there is a good comparison on the pros and codes of native vs. web technologies here: http://interfacethis.com/2011/is-html5-ready-for-prime-time-vs-native/ and many other comparisons that you can find on the Internet. But you will appreciate the [...]

Comment on One Year Later: Is HTML5 Ready for Prime Time vs. Native? No. by stationstops

stationstops — Fri, 27 Jan 2012 23:02:40 +0000

I actually recommend developing in HTML5 now. It keeps the overhead of iOS off the table so you can focus on the actual value of the application. If when you’re done you want to do it in native, you really haven’t wasted much time and you can deploy, beta, A/B test your product on multiple platforms easily while you work on your iOS version – which will be better for you having done the exercise.

You look at Zite, which is HTML5, how fast they went from zero to $10M CNN buyout by focusing on value, aggregation algorithms, and simple interface – vs Flipboard, which is basically a poor RSS reader wrapped in cool Ken Burns effects.

Another example is Path – very sexy, but they were too busy making it sexy to think about why anyone would use it for more than a month before realizing its basically a Facebook also-ran that substitutes photo filters for friends.

Comment on One Year Later: Is HTML5 Ready for Prime Time vs. Native? No. by andybriggs

andybriggs — Thu, 26 Jan 2012 21:35:32 +0000

I’m planning a slightly more complex app than Pints, and was leaning strongly towards PhoneGap with one of these frameworks. Thankfully I decided to research them a bit more thoroughly before committing, as it sounds like I would have ended up having to abandon my efforts and switch to native to get the necessary performance.

Thanks for taking the time to share your experiences, and best of luck for your new venture!

Andy

Comment on One Year Later: Is HTML5 Ready for Prime Time vs. Native? No. by andybriggs

andybriggs — Thu, 26 Jan 2012 21:33:44 +0000

Thanks for taking the time to share your experiences, and best of luck for your new venture!

Andy

Comment on Comparing Mobile Web (HTML5) Frameworks: Sencha Touch, jQuery Mobile, jQTouch, Titanium by tecsined

tecsined — Wed, 18 Jan 2012 22:27:11 +0000

Thank you for this article. I think is really good. I am trying to choose between Sencha and Kendo UI. I haven’t found any good comparison on internet. Could somebody with experience in these tools help me?

Thanks

Comment on One Year Later: Is HTML5 Ready for Prime Time vs. Native? No. by davidGREE1

davidGREE1 — Sun, 08 Jan 2012 13:44:24 +0000

Love your point of view, as I can see it the evidence points to the fact that HTML5 isn’t ready to replace native apps.

You can see the uncompleted compatibility of HTML5 with mobile and tablets in the following chart:

http://blog.magicsoftware.com/2011/12/html5-vs-native-future-of-enterprise.html

Comment on One Year Later: Is HTML5 Ready for Prime Time vs. Native? No. by Ben Wilson

Ben Wilson — Sat, 07 Jan 2012 16:19:40 +0000

You make some excellent points, but I disagree with the “one time” learning curve conclusion. It comes down to slick/specialized ui vs multiplatform for most projects, with a few exceptions like hardware use. Learning multiple, completely different, nonstandard SDKs vs HTML5 standards with [single nonstandard framework] makes it a [popular mobile OS count] learning curve. If you’re only targeting a single OS and don’t mind being subject to that company’s whims (only slightly OT), then it makes sense, but targeting multiple OSs creates a whole slew of additional “curves”. Native will “look and feel” better for many years IMO. If that’s the primary concern, then there’s not anything you can do.

Comment on Is HTML5 Ready for Prime Time vs. Native? (Mobile App Development) by One Year Later: Is HTML5 Ready for Prime Time vs. Native? No. « InterfaceThis - Dave Feldman rants about product design

Fri, 06 Jan 2012 23:32:51 +0000

[...] Touch, jQuery Mobile, jQTouch, and Titanium Mobile. Setting aside differences among frameworks, I tackled the question of native vs. web and gave a nuanced answer, even a hesitant yes. A year later I’ve abandoned HTML5 and begun [...]

Comment on One Year Later: Is HTML5 Ready for Prime Time vs. Native? No. by dfeldman

dfeldman — Fri, 06 Jan 2012 23:30:30 +0000

@Adrian_D_Jones Thanks for the comments and link. I agree it’s not black and white, and yet…Pints is not a complicated app at all. It’s basically just a set of hierarchical list views. And even so, I found myself struggling to debug it and to create a polished, native-like experience in HTML5. And the debug/tool issue is an important (and non-obvious) one given that part of my reason for trying HTML5 in the first place was speed to market.

SproutCore does look pretty cool. I worry about betting on it a bit, though, given that the team that created it was acquired by Facebook.

Comment on One Year Later: Is HTML5 Ready for Prime Time vs. Native? No. by Adrian_D_Jones

Adrian_D_Jones — Fri, 06 Jan 2012 23:21:05 +0000

Great post. At the end of your article you admit that it’s still nuanced, but your stance is still pretty weighted towards native. I’m not sure it’s that black and white, and HTML5 is getting more compelling every day. I think it depends more on what you want your app to do. If you are building a fancy graphics intensive game, then yes, you should go native. But a simpler app? Maybe web technologies will do you fine, and you can still wrap it in PhoneGap if you want to get it in an app store. Here’s an article that breaks down the pros and cons for native, web and hybrid apps: http://appnovation.com/natives-are-restless. There’s also mention of an HTML5 framework called SproutCore which is an alternative to Sencha and JQuery Mobile.