| This is a frustratingly incorrect comment. > but new features are part of libraries and included in versions 5+ years old easily No. No they don't if you're not being completely disingenuous. Jetpack AppCompat style libraries backport app functionality that older Apple devices will get via OS updates in a strictly saner way than having to rely on a backport of a TextView... OS-level functionality does not get backported and of course cannot come from library changes. - Some people who don't know better try to imply that iOS tying things like the mail app to the OS means that Android should be excused... Android does the same thing. Gmail is not the Android built-in mail app, just like on iOS Gmail is an additional app that's shipped by Google. This is the Android Email app and it hasn't been updated in 3 years: https://android.googlesource.com/platform/packages/apps/Emai... Headline features like Assistant changes, privacy and permissions, and system UI overhauls don't end up on your old device either. - Android's update strategy has resulted in a hellscape where Google is forced to recommend supporting a 6 year old version of their OS (that doesn't get security updates anymore!) by default. Missing nice-to-have features doesn't make iOS's approach any less infinitely better than the Android mess. What you're doing is like bragging that your neighbor's filet mignon is a little undercooked while you chow down on dog food. |
This is critically important, though. Look at Compose vs SwiftUI for example–Compose works really well, and even in beta was more stable than SwiftUI, which is nearly impossible to support on iOS 13 devices without massive kludges.
> OS-level functionality does not get backported and of course cannot come from library changes.
This is true, though not super relevant IMO. What OS functionality are folks missing on Android due to being behind? Security updates are the important bit, and most devices still get those for years.
> Gmail is not the Android built-in mail app, just like on iOS Gmail is an additional app that's shipped by Google.
The built-in app isn't updated because Google moved away from that model entirely. Why even bring it up? It's irrelevant.
> Headline features like Assistant changes, privacy and permissions, and system UI overhauls don't end up on your old device either.
Assistant receives updates via the Play Store: https://play.google.com/store/apps/details?id=com.google.and...
Good point regarding privacy & permissions, apps also need to use newer SDK versions to support those IIRC.
The UI overhaul is a weird thing to be concerned about on Android. If you care that much you will install your own launcher. And apps that care will ship the updated UI, one of the advantages of them just being libraries. I guess the notification pane won't update, but is that a huge deal? I'd guess for most folks the answer is no.
> Android's update strategy has resulted in a hellscape where Google is forced to recommend supporting a 6 year old version of their OS
It isn't perfect, but far better than supporting SwiftUI on iOS 13, for example
> What you're doing is like bragging that your neighbor's filet mignon is a little undercooked while you chow down on dog food.
Honestly this is just rude imo, no
To be clear, I think there are pros and cons to both approaches. I think somewhere in the middle would be better, but generally prefer the way Android approaches putting new APIs into older apps.