[agust]

Browser engines define the capabilities of web apps and websites. When they don't support APIs or have bugs, they impact negatively web software.

Apple's WebKit is renowned to be lagging behind, refusing to implement crucial features and being rigged with bugs, hence limiting the capabilities and quality of web apps, and effectively preventing them to compete with native apps.

Getting other browser engines on iOS would be beneficial for developers, businesses and end user by making mobile web apps viable.

[xcrjm]

To be fair to Apple, as a user of Safari, I mostly agree with their feature omissions. Web developers have shown near limitless capacity for abusing new platform features and Apple has provided sound explanations for why they won't implement eg. web bluetooth. On the other hand as a web developer I have definitely suffered my fair share of Safari's incompatibilities (however I find myself in these situations less and less these days).

[rgovostes]

So these web apps will prompt the user to install and configure a third-party browser engine?

[agust]

The likely outcome of alternate, capable browser engines coming to iOS will be to push Apple to invest in Safari so it can compete with them and not loose all of its market share.

Otherwise, yes it's likely web apps will prompt their user to use a browser with a capable engine on iOS if they exist. Nothing to configure, install and use.

Users will then be able to use capable web apps that take up a tenth of the storage of native apps, that are cheaper and portable across platforms — among many other benefits.