Thread by @slightlylate

Trying again: Apple's iOS store shenanigans include a subtle & unique catch-22 journalists should grok:

- when apps violate policy, Apple says "use the web"
- ...except every iOS browser is required to use Apple's engine...
- ...and it's Apple keeps it year behind

This is hidden from view because no iOS browser maker dares to submit a browser that shows a "this isn't _real_ Firefox" (e.g.) banner...because what is the user supposed to do? Buy a new phone? They also can't afford to be cut off from all the world's rich users.

But why is Apple's engine & browser years behind?

Because Apple doesn't fund the WebKit team with anything like the headcount they'd need to keep up. And let's keep in mind that this isn't down to some sort of cash crunch.

This is a choice.

The under-funding has compounding consequences:

Developers are used to Apple ignoring; most don't even bother to file bugs on WebKit:

joreteg.com/blog/project-f…

Browser makers who want to co-design new features know asking Apple is stones into a bottomless well (tho we persist).

This leads to a situation where, even when Apple catches up (e.g., Service Workers), critical follow-on features flagged by high-profile sites and partners are missing (e.g., Nav Preload).

All browsers have bugs, but late catch-up + key issues + yearly pace == massive delay.

There's a way out of this problem that doesn't require Apple to invest a reasonable amount in WebKit/Safari (tho everyone would welcome that regardless):

Allow competing browsers, the way *EVERY OTHER OS* does. Other vendors would _love_ to deliver a better web to their users.

So to recap, every time App Store shenanigans flare up, commenters should look hard at the argument that the web on iOS is some sort of alternative. You don't take my word for it, either. Go talk to developers. Do _they_ think Apple's iOS kept-web is good enough?

(typos, FML)