[niko001]

It might not matter to users in the sense that they ask themselves what rendering engine Chrome on iOS is using under the hood, but the effects do matter. I get a lot of support requests saying "Your [web] app is broken on my iPhone!", "Right, Safari doesn't support feature XYZ", "I'm not using Safari, I'm using Chrome", "..."

[CharlesW]

How does the developer story get better if you're required to support many web rendering engines on iOS instead of one? Or is the endgame that you'd just point people to Chrome/Blink and extend the web monoculture to Apple devices too?

[jsnell]

The endgame is that Apple is forced to actually make a working browser, rather than intentionally starve it of resources to benefit the App Store. Everyone wins.

[mynameisvlad]

That seems to be a communication problem. Instead of saying "Right, Safari doesn't support feature XYZ", say "Right, iOS doesn't support feature XYZ".

It's also technically more correct, the best kind.

[snowwrestler]

Just wait until Google has Chrome running natively on iOS and introduces nonstandard behaviors to break Safari rendering intentionally.

Then at least you’ll be able to tell all your customers that you recommend switching to Chrome for all browsing. What a great victory for browser diversity and the open web!