For AV1 this is true, but we don't really need to postulate about whether or not Apple plays games to suppress open codecs, they do it constantly. Like when they finally eventually added support for Opus, but not Ogg containers, so you had to stuff Opus in a CAF that only Safari can support. Opus is also now supported in WebM, but you still can't just decode Ogg Opus, and there is still no sensible audio-only Opus container supported in Safari right now.

Apple devices have had accelerated VP9 devices for literally years, which didn't stop them from simply not supporting VP9 during that time period, despite no reason (i.e. battery life) and despite that it has been patent unencumbered for that entire period.

And so much for battery life... If you are on a Wikimedia website on an iPad, it will use open codecs no matter what, and if you are on an Apple device, you might just get a software decoder in WebAssembly instead, if you're not on a new enough OS.

> Opus is also now supported in WebM, but you still can't just decode Ogg Opus

Apparently Ogg Opus and Ogg Vorbis has been supported since 18.4 (Mar 2025)[1]

I think it would be great to see more adoption of Opus in podcasting personally.

[1]: https://developer.apple.com/documentation/safari-release-not...

It's really hard to keep up with Apple's support for open codecs: it's always bad, and it always improves one minor step per year at best. Evidently, I'm behind on it, because I've mostly given up on trying to make software I work on work well with Apple devices by this point. (I can't tell you exactly what's wrong, but I've noticed I still can't get most WebMs to load in Safari on my M1-based iPad... some of them do, some of them do not.)

Apple is hopefully noticing that while major publishers can be swayed by this sort of behavior, lack of support for open codecs and open formats is going to make the iPhone and iPad web experience much worse for people who veer outside of the mainstream for a bit.

Perfect. Apple can implement efficient decode in current/next gen devices then enable support in iOS Safari/WKWebView to chew up battery life of older devices. It's more defensible than Batterygate[0]. For current transition, Liquid Glass might be enough extra load.

[0] https://en.wikipedia.org/wiki/Batterygate

If that were the only reason, Apple wouldn't have waited until the M3 chip to include an ASIC for AV1. Other chip manufacturers had AV1 support significantly earlier.