Earlier quoted context omitted.
Depends on how you look at it. While the hardware might keep functioning and current software might keep running, some devs also deprecate their software. I have an old 6S+ that I keep software that I don't want to install on my actual device. Slack informed me that it will no longer function after a date set later this year. Other apps have already stopped working on it because the devs do not want to deal with it.…
> TL;DR sometimes it's not Apple, it's the app devs that deprecate them. Are the app devs deprecating just because their support matrix is too big, or because current SDKs will no longer build apps compatible with those devices? I think the later case is less common on the Android side of the fence, but Apple is not great about keeping old versions of the dev tools functional, and you end up needing to keep elderly M…
On Android it’s less of an issue because the SDK ships separately from the system, but there are often still substantial behavioral differences between system versions under the same SDK that can be a real pain in the rear, especially when it comes to permissions-related issues. This why it’s common for Android apps to have odd bugs or behave strangely on ancient versions of Android — while it’s easy for the dev to produce a build technically runs on a wide range of versions, properly testing against all those permutations of versions and manufacturer skins is practically speaking impossible unless you’re a sizable company that keeps a lab full of devices with CI rigged up to test against them all.