News for hackers. Stuff that matters.
Re:HTML5 is not ready by kunle on Thursday June 21, 2012 @05:40PM (#4144345)
One tough thing for HTML5 is that the platforms that the community want to write for (iOS & Android) have no intrinsic incentive to actually support it (other than lip service). A world where HTML5 is dominant for the most profitable tier of games or apps is a world where the best developers dont have to write in iOS & Android (where Apple and Google respectively make their money), so given that, what's their incentive to make sure HTML5 reaches feature/performance parity with their native platforms?
Re:HTML5 is not ready by Peaker on Thursday June 21, 2012 @06:31PM (#4144507)
Apple is claiming that the app store is break-even. That it benefits them only indirectly by making iOS a more attractive choice.

If that is true, and HTML5 worked better with iOS than with Android, that would work well within that strategy.

I think perhaps there are other reasons for poor HTML5 support on the mobile platforms.

Re:HTML5 is not ready by cageface on Thursday June 21, 2012 @08:46PM (#4144894)
iOS has by far the best support for HTML5 of any mobile platform. If Apple felt threatened by HTML5 I'd expect to see a lot more evidence of sabotage.
Re:HTML5 is not ready by kunle on Friday June 22, 2012 @12:56AM (#4145472)
Not claiming that iOS support for HTML5 is bad, just that I find it hard to believe that Apple will ever invest as much in HTMl5 as it does in native, and by extension, that Apple will ever make sure HTML5 is at feature parity to native.

At some stage and for some subset of use cases (I think particularly with apps like news media for example) it will matter less and less, but for anything that is intensive, I just dont see an argument for why HTML5 will ever function at parity.

Re:HTML5 is not ready by cageface on Friday June 22, 2012 @02:13AM (#4145670)
To be honest I'm a little puzzled by Apple's efforts with Mobile Safari. It would seem to be much more in their interests to make it suck.

By best guess is that Apple doesn't really care about the native app market that much per se and they'll do whatever it takes to sell their hardware.

Re:HTML5 is not ready by DeepDuh on Friday June 22, 2012 @05:18AM (#4146053)
I think you got it exactly right. Of course they want to keep having the best native App catalogue, but for those devs who DO decide to go the mobile web app route they don't want to block their users from using it on iOS devices, since this would lower their satisfaction with iOS.

Conversely, they don't support flash because of the poor / non existant mobile hardware support which leads to bad performance and -again- unsatisfied users. With this move they want to force developers to use either html5 or native apps.

You can say lots of things about their app store policies, but their html5 adoption strategy is pretty rock solid and it's good we have a giant of Apple's calibre behind this in order to nudge the ecosystem in that direction.

Re:HTML5 is not ready by novalis on Friday June 22, 2012 @11:24AM (#4147139)
With their lack of mobile flash plugin support, Apple just made flash executable wrapped apps to be profitable through the app store, I wouldn't go about categorizing Apple's calibre on profit related decisions.

"but for those devs who DO decide to go the mobile web app route they don't want to block their users from using it on iOS devices, since this would lower their satisfaction with iOS." Establishing that they did block a plugin on the browser is a first step. The rest is simply a side effect of js being supported on the browser combined with the flash cold cut, is there some extra benevolance we should thank Apple for when their Canvas implementation is afflicted by the same trouble a flash vm would run into inside a safari mobile browser ?

Also devs go the web app route way in ways apple has no voice in or control over, as much as they try. As it should be. Let us not forget such amazing experiments as the introduction of the quicktime plugin and how that opened the door for things like flash shockwave itself, and we all know how well that went.

Revisionisn and a good nanny brand delivered narrative won't make safari mobile canvas any more apt, sadly. Or a commercial brand any less profit seeking. As it should.

Re:HTML5 is not ready by MatthewPhillips on Thursday June 21, 2012 @10:37PM (#4145145)
What are you basing this on? At minimum Chrome and Firefox have better html5 support, as they have near parity with their desktop counterparts. I don't have the numbers but I'd guess Opera Mobile has better html5 compatibility as well.
Re:HTML5 is not ready by cageface on Thursday June 21, 2012 @10:40PM (#4145148)
I'm talking about the browser shipping with the system, which is what 99% of the people using the device are going to use and where web apps are going to live or die.

Once Android starts shipping with Chrome stock things will be different.

Re:HTML5 is not ready by MatthewPhillips on Thursday June 21, 2012 @10:45PM (#4145159)
I really doubt it has significantly better html5 support than the Android browser, if it's even better at all. But goal posts moving aside, your point was that Safari is somehow evidence that html is important to Apple, when viewed in the context of the entire industry it's above average. Lots of companies are doing good things with html in mobile, even Rim.
Re:HTML5 is not ready by cageface on Thursday June 21, 2012 @11:22PM (#4145227)
Mobile Safari is head & shoulders better than the stock Android browser, which is really a piece of shit. This is abundantly documented all over the web. Just ask the Sencha guys how much fun they've had trying to get acceptable performance out of Android.

Judging the companies by the browser they put in front of users, Apple cares more about HTML5 than anybody else. Like I said, if Google can get mobile Chrome out there I'll revise my assessment.

Re:HTML5 is not ready by paulirish on Friday June 22, 2012 @01:20AM (#4145538)
The difference is enormous between Android Browser and Chrome: http://beta.html5test.com/compare/browser/android40/chromemo...

This just captures features, speed is an order of magnitude.

Re:HTML5 is not ready by MatthewPhillips on Friday June 22, 2012 @01:42PM (#4147796)
We were comparing Mobile Safari to Android.

H.264 support is not an HTML5 feature, by the way.

Re:HTML5 is not ready by zmmmmm on Thursday June 21, 2012 @07:49PM (#4144720)
> it benefits them only indirectly by making iOS a more attractive choice

Since you agree it benefits them - and your use of the word "only" is deceptive here; having the best app catalog is no marginal thing, it is an enormous benefit, often cited as the primary reason Android tablets have struggled and why WP7 failed - why don't you think that benefit - which exists primarily because HTML5 still sucks for mobile apps - incentivises them not to improve browsers?

It would be trivial for both Google and Apple to remove a large number of the barriers to HTML5 apps replacing native apps. But they don't, and it's been long enough that time is not an excuse.

Re:HTML5 is not ready by ThomPete on Thursday June 21, 2012 @06:42PM (#4144542)
Apple don't want the app store to be anything but break even. They have it because it's a way to make money where it really matters which is the hardware.
Re:HTML5 is not ready by hdragomir on Thursday June 21, 2012 @06:57PM (#4144583)
wooga chose to focus on iOS because of the less fragmentation.

I work on Pocket Island, at wooga.

Re:HTML5 is not ready by greggman on Thursday June 21, 2012 @09:05PM (#4144948)
You can cross develop though

Either Native -> HTML5 with things like Mandreel (http://www.mandreel.com/)

or

HTML5 to Native with things like cocoon.js (http://ludei.com/tech/cocoonjs)

Even many "native" apps just embed the native browser as a widget. Development is often much faster that way and they can fall back to native APIs for those few features HTML5 doesn't give them access too

Re:HTML5 is not ready by flatline3 on Thursday June 21, 2012 @09:57PM (#4145065)
> Even many "native" apps just embed the native browser as a widget.

They sacrifice UX doing so.

> Development is often much faster that way ...

It's faster for their existing web team, which is what this is really about.

Re:HTML5 is not ready by greggman on Tuesday June 26, 2012 @09:10PM (#4165020)
I'm not sure that's true. I think there are some fairly popular mobile apps using a webview. The facebook app? Honestly I don't know if that's true but their mobile website has almost the exact same UX. There's a few subtle differences but maybe those come from some glue around a webview and not all brand new code.
Re:HTML5 is not ready by MatthewPhillips on Thursday June 21, 2012 @06:32PM (#4144509)
A similar, but less conspiracy-y explanation is that there is essentially no browser competition in mobile so there is no motivation to improve like on desktop. Hence, the two major OS vendors update their browsers yearly.
Re:HTML5 is not ready by josephcooney on Thursday June 21, 2012 @09:12PM (#4144961)
How much do google really make from Android?
Re:HTML5 is not ready by hdragomir on Friday June 22, 2012 @08:33AM (#4146484)
A fraction of what AppStore revenue is -- even though they have more market share. :-(