The service that also provides H264 versions of its content, you mean? Which is the point I already made.
> How do you know what's in the users interest? [...] If battery really is a concern (assuming it is)
Well, Apple is heavy-handed with its users. They make a lot of assumptions about what is best for them, and this is one of them.
> don't watch lengthy videos (1-2 hours) on an iOS device.
I suspect Netflix would disagree with you.
Netflix on an iPhone? Probably not. At least not holding it in your hand for 2 hours.
Do you have data to support this or are you just assuming that your personal tastes are universal? I see quite a few people watching videos on phones or tablets – ever see parents loading up their kid’s iPad before a flight?
With 80% on a "big" device.
I also watch videos, but "video" is not a movie or series. Video sounds more like 15 min. max and/or not "cinematic".
Obviously. But that's not how Apple works. You do things their way, or you get an Android phone/Windows laptop. They make the choices for users, and judging by market share a very solid number of people are very content with that arrangement.
Contrary to your point about not watching on iOS, I, and everyone I know, watch all content on an iOS device, both in the living room and on the go.
There is certainly a segment of the market that is using misc devices or “casting” to USB sticks plugged into TVs, but the 4K TV owning cord cutters I know tend to also own iPhones and use Apple TVs.
We saw this shift happen even more when iOS (and TvOS) gained SSO across apps with the “TV” app as indexer, and another bump when Amazon Prime released.
If you watch in the living room (on TV) you are not watching it on the iOS device. By that I mean the screen of the iOS device. Being in the living room, watching on TV, means you have no battery issue. Watching on your device means literally that, watching it on your device with your devices' screen. Not some casting or streaming to other displays.
If we ignore YouTube, which Google controls to their own benefit, what’s the percentage of WebM/VP9 versus H264/H265?
H264 is used in other places in the electronics industry. That’s one of the reasons Apple picked it. Isn’t it the format most digital cameras record video in?
WebM/VP9 is used by... Google. And Wikipedia (who won’t use something with patent licensing). Is there anything else big?
Basically everyone else uses H264 like Apple since it was the designated successor to MPEG2.
In this case, Apple went with the industry standard. Google is the odd man out.
So why should Apple have to bend to Google’s whim here and implement WebM/VP9?
Why shouldn’t Google just fix their site?
No, browsers and hardware manufacturers have implemented VP9 because it has better licensing terms than H.264 and especially better than HEVC. HEVC was released at around the same time as VP9 and yet today VP9 has double the installed base of HEVC: https://ngcodec.com/news/2017/10/21/why-we-are-supporting-vp...
> In this case, Apple went with the industry standard.
No. When it comes to the web the industry standard is royalty-free formats and protocols: https://www.w3.org/Consortium/Patent-Policy-20170801/
Video formats which require a patent licensing fee (like H.264 and HEVC) have been an anomaly.
> Why shouldn’t Google just fix their site?
Because VP9 outperforms H.264: https://medium.com/netflix-techblog/more-efficient-mobile-en...
VP9 just works better: https://youtube-eng.googleblog.com/2015/04/vp9-faster-better...
This isn’t like Mozilla, who only makes a web browser.
Apple will be adding support for AV1. Like VP9, AV1 is royalty-free. The Alliance for Open Media has been so effective (even before AV1's release) and HEVC's licensing has been so terrible that MPEG is starting to question whether it can survive as an organization:
http://blog.chiariglione.org/a-crisis-the-causes-and-a-solut...
Royalty-free video formats are simply a better way to go.
WebM was released in 2010. VP9 is from ‘12/‘13.
H264 was already the web video standard when WebM/VP9 came along.
I take issue with Google trying to force everyone over to their format and removing support for higher resolution H264. They crippled what used to work for me to push their agenda. And because it’s license free I’m supposed to be good with it.
This is exactly the kind of stuff people used to get pissed at MS or Apple for.
But it’s Google, and people love Chrome. So this is good and Apple is the one not going with the ‘standard’ that ‘everyone else’ is using.
And, yes, it was not Google's finest hour, especially when they strung Mozilla promising to disable H.264 in Chrome but never actually shipping it (remember https://brendaneich.com/2012/03/video-mobile-and-the-open-we...).
How do you know what's in the users interest? A choice between "Video playing" vs. "Video not playing" is pretty obvious to me. (And I am a user too)
If battery really is a concern (assuming it is), just make it an option not to play videos if they require software decoding.
Besides that, users usually (an assumption I made, just as you did) don't watch lengthy videos (1-2 hours) on an iOS device.