Google: Difference between revisions
SinexTitan (talk | contribs) m the Google Pixel page exists on the wiki so the link now directs there instead of Wikipedia |
→Controversies: Added a subsection regarding API level requirements for Google Play apps to appear in the Play Store |
||
Line 38: | Line 38: | ||
{{Main|Google asserts the right to seize your phone during a repair}} | {{Main|Google asserts the right to seize your phone during a repair}} | ||
Google's Service & Repair Program terms explicitly state that any device containing non-Google-authorized parts "will not be returned" to the customer. | Google's Service & Repair Program terms explicitly state that any device containing non-Google-authorized parts "will not be returned" to the customer. | ||
=== Target API level requirements for Google Play apps === | |||
Google's policy of requiring apps for Android to target recent API levels to appear in the Play Store<ref>{{Cite web |date=August 31 2024 |title=Policy Center |url=https://support.google.com/googleplay/android-developer/answer/11926878?hl=en |access-date=May 9, 2025 |website=Play Console Help}}</ref> creates a continuous cycle of maintenance and redevelopment that can be especially burdensome for smaller developers, indie creators, and consumers. | |||
The requirement for apps to target newer APIs each year serves some legitimate security and feature purposes. However, it also effectively functions as a form of forced obsolescence. Even perfectly functional apps that don't need technical updates must be regularly reworked just to remain visible on the Play Store. | |||
This creates several issues: | |||
* Development resources must be allocated to updating apps rather than creating new features | |||
* Smaller teams and individual developers are placed at a disadvantage attempting to keep up with the constant update cycle | |||
* Legacy apps that are no longer actively maintained disappear, even if they're still useful | |||
* The cost of maintaining apps increases, potentially making some projects financially nonviable | |||
* Losing access to previously purchased apps when upgrading devices | |||
* Users being unable to reinstall older apps that worked perfectly well for their needs | |||
* Facing unexpected costs to replace functionality they've already paid for | |||
* Dealing with the frustration of discovering favorite apps have disappeared | |||
While Google argues this approach improves the Android ecosystem's security and functionality, it does place a significant burden on developers and can lead to the premature "death" of otherwise functional applications. | |||
This creates a troubling disconnect in digital ownership. Consumers reasonably expect that when they purchase an app, they should maintain access to it across their devices over time. Instead, they discover their digital purchases can effectively vanish due to policy decisions beyond their control. | |||
==Anti-consumer legal cases== | ==Anti-consumer legal cases== |