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.
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.
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.
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.
"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.
Once Android starts shipping with Chrome stock things will be different.
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.
This just captures features, speed is an order of magnitude.
H.264 support is not an HTML5 feature, by the way.
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.
I work on Pocket Island, at wooga.
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
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.