Why we are suing Apple for better HTML5 support in iOS

Post by paulcole » Fri, Oct 07, 2016, 2:02 PM UTC

Svenskunganka wrote: post #96

kbart wrote: post #73

Earlier quoted context omitted.

"Apple is blocking HTML 5 somewhat and there is almost nothing we can do about it." Sure we can! Vote with your wallet and don't buy Apple's products. Or at least write a complaint to one of their support centers..

The problem is that this approach is perfectly fine when it comes to us programmers or more technical people, but for "normal" users this approach won't work, simply because they don't know the possibilities an up-to-standards iOS Safari would bring. There's a saying; "What you don't know can't hurt you", and that can be applied for these users - whom make up the majority of iOS device users - since they don't know w…

Post by fenomas » Fri, Oct 07, 2016, 2:05 PM UTC

namaemuta wrote: post #147

gcp wrote: post #101

Earlier quoted context omitted.

If you mean the Android store, then no. You can for example find the "real" Firefox on the Google Play store. (The one on the Apple store is a Safari skin which has the problems the article points out)

Sorry, I didn't express myself correctly. I meant this chrome app[1] in the apple store. I was wondering if people with iPhones can at least install a different browser to take advantage of those features. But if you say that it's just a skin they are pretty much trapped there. [1] https://itunes.apple.com/us/app/google-chrome-fast-secure/id...

Post by cageface » Fri, Oct 07, 2016, 2:09 PM UTC

coldtea wrote: post #104

kyriakos wrote: post #81

Many of the HTML5 technologies Apple is steering clear from make the Web more App like meaning they become a threat to their dominance with the App Store on their own platform. The longer they take to adopt them the longer they can benefit from the exclusiveness and control over iOS app ecosystem. I don't think sueing them will get them anywhere but it might be a push to get them understand that users are aware of th…

From ordinary users, nobody cares about the web platform on mobile. Native apps are faster, with better integration to platform APIs and features, lighter on battery, and consistent (even if a large part of an app is just a webview in a native app shell). And for developers, they can actually be monetized and attract paying users, unlike mobile browser-based apps. Safari on mobile is pretty up to date as mobile techn…

Post by madeofpalk » Fri, Oct 07, 2016, 2:12 PM UTC

zajd wrote: post #162

madeofpalk wrote: post #148

Earlier quoted context omitted.

> You can definitely build a slider natively... Nope http://caniuse.com/#search=snap

You don't need snap to build a slider natively. Also interestingly snap is NOT supported when Safari is rendering stuff in a different app, only when you're actually in the Safari App.

Post by madeofpalk » Fri, Oct 07, 2016, 2:14 PM UTC

sgtpepper43 wrote: post #157

madeofpalk wrote: post #148

Earlier quoted context omitted.

> You can definitely build a slider natively... Nope http://caniuse.com/#search=snap

"Build natively" means to create it yourself in vanilla JavaScript, like this http://meandmax.github.io/lory/ . What's the use of a native element that only one browser has when you need cross browser support anyway?