Why we are suing Apple for better HTML5 support in iOS

Re:Why we are suing Apple for better HTML5 support in iOS by onion2k on Friday October 07, 2016 @08:51AM (#12660218)

Speed is an important metric, but only up to a point. Once a browser renders a page faster than a user can interact with it any further improvement has very little impact. Any phone released in the past year or two meets that criteria for a well constructed page (obviously a badly written site is always going to perform badly, even on the best hardware.)

So, while it may be true that an Android phone is 5x slower than a new iPhone, that doesn't make a difference to the end user. They see the website working well on both devices. At that point it starts being about features, so iOS's lack of support for WebRTC, Beacons, Gamepads, Fetch, etc means the experience is worse. Not that Android supports everything, but if you compare iOS Safari to Chrome on Android[1] it's very clear that Safari is behind, even if it's faster.

[1] http://caniuse.com/#compare=ios_saf+10,and_chr+51

[ Parent | on HN ]

Re:Why we are suing Apple for better HTML5 support in iOS by madeofpalk on Friday October 07, 2016 @08:59AM (#12660261)

As pages get more and more complex (say, because they have new fancy HTML5 APIs) that performance actually begins to matter, right?

I'm a web developer and I don't feel like iOS Safari is holding me back in producing the types of web experiences that myself or my clients are looking for. They're not asking for HTML5 Gamepad support. Instead, they just want an image carousel - Chrome doesn't support that but Safari does http://caniuse.com/#search=snap.

[ Parent | on HN ]