News for hackers. Stuff that matters.
Re:Unraveling HTML5 vs. Native by brandon_wirtz on Tuesday April 30, 2013 @11:46AM (#5632849)
We make an app written as HTML5 CSS3. We made this decision because with limited dev resources it allowed us to write once deploy many. That is powerful. Our app required more testing than a native app, and less.

With a native app if you write your code for Version X of the OS you can be 99% certain that Version X.1, X+1, and X+1.3 are all going to treat it the same. With HTML5 "fixes" to the renderer can mean that what was working will stop working. Or stop looking like it used to.

With an HTML5 app you should be able to write once and deploy many, but Mobile Safari, and Mobile Chrome, that do the renderings on IOS and Android don't handle all JS and CSS quite the same. So you may have slight differences. Much less than you would have with ObjectiveC vs Java, but differences none the less.

PhoneGap makes much of the stuff you want to do with the hardware easier, but not perfect. If you want to send a Text, or make a call or access the contacts you will have to at least touch a plugin, if not write some native code. Most of the time you can just clip a snippet from someone else, but if you want to do anything awe inspiring you will have to still get your hands dirty with native code.

http://tldrstuff.com shows what we were able to do with a single UI Core across Windows Phone 8, Android, and IOS.

We hit all of the platforms, and had less code to change, but our app doesn't "Feel" native. We don't have a UI that looks integrated with the OS, but we have concistency across platforms. Was our decision "right"? Hard to say. We spent less resources which was a major driving factor so I say yes. Did it keep us from being Wavii or Summly? I hope not. But it is hard to say. I don't know if we traded dev resources for glory, or if we saved money we will want and need to be bigger than either.

Re:Unraveling HTML5 vs. Native by SkyMarshal on Tuesday April 30, 2013 @01:07PM (#5633432)
Thanks for the interesting postmortem. I've been thinking along the same lines recently - HTML5 + app packager for teams with limited development resources, multiple parallel native apps for teams that handle it. Or native if you have some specific requirement that can only be met by native.

Fwiw, the Flat/Tiled/Metro design motiff seems to taking off enough that it's a satisfactory cross-device substitute for native.

Summly used it too; as such, yours doesn't look significantly different theirs, other than their use of transparency in places.

Maybe it was their mention of their use of genetic algorithms in their well-done launch video [1], and having a 15yr old founder, that did it for them. Of the Three T's they nailed two - team and technology. Attention, interest, and Traction were sure to follow.

[1]: http://vimeo.com/52014691