Re:Current state of AV1 codec playback support – Oct '22
by Jasper_ on Friday October 21, 2022 @12:45AM
(#33284607)
Yes, they have banned alternative engines.
https://developer.apple.com/app-store/review/guidelines/#2.5...
> Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript.
Re:Current state of AV1 codec playback support – Oct '22
by enkrs on Friday October 21, 2022 @03:06AM
(#33285336)
Which is the reason why I choose iOS: I trust Apple to implement the integrations in the WebView for best battery life. To get new OS features in the browser right away. Would Google Chrome implement picture-in-picture on the iPhone if they were running their own engine?
I use Firefox on iOS for the password and tab sync integration, and am supper happy that it’s using the WebKit framework. I care about the iOS experience more than some video codec support.
Re:Current state of AV1 codec playback support – Oct '22
by vetinari on Friday October 21, 2022 @04:04AM
(#33285680)
If the other browsers could implement their engines, you would still have the option not to install them.
Since they can not do it, you don't have that option.
Re:Current state of AV1 codec playback support – Oct '22
by alwillis on Friday October 21, 2022 @04:29PM
(#33292690)
If the other browsers could implement their engines, you would still have the option not to install them.
So it’s okay for user who (in theory) installed a 3rd party browser on iOS to have a worse experience and potentially make themselves vulnerable to malware? That’s exactly what Apple doesn’t want.
Re:Current state of AV1 codec playback support – Oct '22
by paulryanrogers on Friday October 21, 2022 @09:11PM
(#33294696)
Or potentially offer a more secure browser than Safari
It's just that they don't allow JIT code execution for security reasons which is needed for a comparatively performant engine.