I'm not sure if that page is up to date. Firefox for Android and Chrome for Android both seem to support AVIF according to my tests. I'm not sure what "Android browser" means here, but it's been a while since I've seen the built-in browser engines not running on some recent version of Chromium as a base.
I don't expect Apple to ever implement AVIF. They have bought into HEIF as the new version of JPEG through licenses and hardware decoding and they're not exactly known of implementing open standards next to their own.
Encoding WEBP and AVIF and using the <picture> element on web pages should solve the bandwidth problem without depending on outdated browsers or lacking browser manufacturers. AVIF is better than WEBP in many cases, but WEBP is also better than JPEG or PNG in many places the older formats are still used.
I can't get AVIF images to open in the latest Chrome on Android, pages with fallbacks use the fallback as well. My guess is it'll be enabled when AV1 is (which should be soonish now that devices with hardware AV1 decode are starting to be shipped in volume).
Apple added AV1 hardware decode support to the A14 so I wouldn't rule it out in the future.
> I'm not sure what "Android browser" means here, but it's been a while since I've seen the built-in browser engines not running on some recent version of Chromium as a base.
Looks like it's the pre-Android 5, non-Chromium, AOSP browser ?
I don't expect Apple to ever implement AVIF. They have bought into HEIF as the new version of JPEG through licenses and hardware decoding and they're not exactly known of implementing open standards next to their own.
Encoding WEBP and AVIF and using the <picture> element on web pages should solve the bandwidth problem without depending on outdated browsers or lacking browser manufacturers. AVIF is better than WEBP in many cases, but WEBP is also better than JPEG or PNG in many places the older formats are still used.