{"id":36250,"date":"2022-06-16T15:38:47","date_gmt":"2022-06-16T19:38:47","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=36250"},"modified":"2022-11-30T10:39:22","modified_gmt":"2022-11-30T15:39:22","slug":"tvos-16-announced","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/06\/16\/tvos-16-announced\/","title":{"rendered":"tvOS 16 Announced"},"content":{"rendered":"

José Adorno<\/a>:<\/p>\n

\n

The company talked during the WWDC 2022 keynote all about iOS 16, iPadOS 16, macOS 13 Ventura, and watchOS 9, but not a single word about tvOS 16.<\/p>\n

[…]<\/p>\n

While other operating systems have their own preview page, Apple TV’s software doesn’t. This is what we could find thanks to the release notes, developers, and more.<\/p>\n<\/blockquote>\n\n

Joe Rosensteel<\/a>:<\/p>\n

\n

[This] year’s WWDC announcements regarding tvOS lack any meaningful changes, and more importantly, communicate nothing about where the platform is going.<\/p>\n

[…]<\/p>\n

Digging deeper in to the WWDC videos on Apple’s site there’s a 24 minute-long session<\/a> about designing video interfaces. It’s for iOS and iPadOS, not for tvOS. The tvOS playing experience is only referenced to explain where the title and subtitle elements came from[…] Metadata being exposed for title and subtitle is fine, but season and episode number have to be encoded into those strings by the developer, there’s nothing in the player that pulls that from a sidecar or metadata file, or any design opinion from Apple over how to format such information for consistency.<\/p>\n

[…]<\/p>\n

The thing that I’ve found that’s the most exciting? Developers can proactively restore an in-app purchase<\/a>. This was a complaint I had when setting up my Apple TV 4K<\/a> last year, where none of the in-app purchases, and subscriptions, migrated over. That that<\/em> is what I’m most<\/em> excited about either means I’m very boring or the list of features is very boring.<\/p>\n

[…]<\/p>\n

What company, and what developer, is going to argue in favor of ripping out the custom players they’ve spent years building for something that doesn’t help their own interests? There isn’t even a reason for consumers to ask for AVPlayerView<\/code>, because it might be a more consistent player if it was implemented everywhere, but it isn’t a better<\/em> player. The benefit of implementing AVPlayerKit is mainly for Apple, not for anyone else.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n