> we're talking about the system browser engine, which is made by the same people who make iOS and is shipped as a core part of iOS
The Apple employees who work on WebKit, Safari's open source browser engine, or even those who make Safari from WebKit are not the same Apple employees who work on iOS's file system or Photos.app or anything else found on an iPhone when you first take it out of the box.
Still, it is odd that iOS 16, including Safari, has added support for AVIF but HEIF still doesn't work in Safari.
I don't know why you're arguing, it sounds like we agree. Apple makes the product iOS, it's weird that one part of iOS (the camera/photos system) is completely incompatible with another part (the browser). You'd have expected them to add HEIF support to their browser, delay shipping HEIF until it's supported in their browser, or automatically convert from HEIF to a format that's supported by their browser.
Your argumentative tone would've made sense if my criticism was directed at the Safari team for not implementing HEIF support. But my criticism is towards Apple for failing to make a cohesive product.
It's probably because the two teams don't have a common direct report until they get to an SVP who has hundreds of issues and conflicts on their plate.
> Still, it is odd that iOS 16, including Safari, has added support for AVIF but HEIF still doesn't work in Safari.
Exactly. Safari had the motivation/resources to add AVIF support, but not HEIF. So it seems like Apple chose to back the wrong horse (HEIC) at first and is now pivoting to AVIF
The Apple employees who work on WebKit, Safari's open source browser engine, or even those who make Safari from WebKit are not the same Apple employees who work on iOS's file system or Photos.app or anything else found on an iPhone when you first take it out of the box.
Still, it is odd that iOS 16, including Safari, has added support for AVIF but HEIF still doesn't work in Safari.