3 ms·
In theory this kind of "controlled" backwards compatibility break is good, it lets old apps work whilst encouraging developers to keep up with platform changes.
by nvm0n2 3y ago
In theory this kind of "controlled" backwards compatibility break is good, it lets old apps work whilst encouraging developers to keep up with platform changes. In practice it has the nasty side effect of preventing the scaling of the software industry, and with it, industrial society. Therefore Google should drop this policy and allow old programs to be distributed forever.
With near perfect backwards compatibility, the amount of software that society can consume is in effect unlimited. The number of software developers is finite, but the amount of software they can create isn't: only the growth rate is finite. Thus society can benefit from an ever-expanding library of programs which increases overall wealth. Indeed, tool creation is the only way to increase wealth in countries with a flat or falling population (productivity * population = gdp, more or less). In this mode, software is like knowledge. It accumulates and compounds.
With imperfect backwards compatibility you are forced to engage in continuous maintenance of all existing software. Suddenly there is now a fixed limit on how much software society can have, it's a function of how many maintenance developers there are. You can literally reach a limit where things can slide backwards. Problems can become un-automated. In this mode, software is more like oil. It can run out.
Google want to force continuous maintenance because the Android team justify their existence with constant change, and if a platform is full of unmaintained apps then it will feel old and tired compared to a platform full of apps that have the freshest new looks and features. But that often doesn't matter, especially for non-consumer or specialized software used only by a small number of people (but for high leverage impact). Because Google and Apple are unapologetically consumer focused cultures, they care far more about things like how apps look and stuff that's irrelevant in business contexts (consumer privacy).
- gmiller123456 3y agoThis is not about backwards compatability. Google is preventing users from installing apps that are 100% compatible with their phone.
- nvm0n2 3y agoYes, exactly. It is a "controlled" break. The OS is capable of being backwards incompatible but store policies create an equivalent of it being not backwards compatible.
- danpalmer 3y agoGoogle is preventing new users from installing the app for the first time, on a device that is substantially newer than the app they are installing. Anyone who has already "purchased" (may be free) the app will still be able to access it, and anyone on an older device can still access it. I the simplification of this that you specified is ok as a summary, but the devil is in the details, and the details here do make this policy much less impactful than your summary suggests. Policy: https://support.google.com/googleplay/android-developer/answer/11917020?hl=en-GB#:~:text=Existing%20Google%20Play,the%20app%20supports https://support.google.com/googleplay/android-developer/answ....