Prisoners of Google Android development (solutional.ee)

Article summary

The article describes a case study of an Android app release that caused production crashes due to a small API-level update, resulting in Google Play delays and limited rollback options. The author had to update the app's target SDK version to meet Google's requirements, but the update introduced a critical bug that affected Android 13 devices. The author struggled to get the update approved and rolled out, highlighting the challenges of working with Google Play's review process. The experience led the author to prefer open web platforms for development.

Main themes

• Android app development
• Google Play review process
• API changes and compatibility
• Legacy application maintenance
• Open web platforms
• Developer control and autonomy
• Testing and regression testing
• Google's policies and priorities

What commenters say

• Google's review process can be slow and unresponsive, causing frustration for developers trying to fix critical bugs.
• Developers should prioritize thorough testing and regression testing to avoid similar issues.
• Google's API changes and requirements can be breaking and difficult to work with, especially for legacy applications.
• The web is not a completely independent alternative, as Google and Apple still exert significant control over web standards and browsers.
• Rolling back updates is not always possible, especially when Google's policies restrict the use of older API targets.
• Developers should be aware of the potential costs and maintenance work involved in hosting and maintaining their own infrastructure.
• Google's emphasis on user privacy and security can lead to breaking changes and difficulties for developers who do not prioritize these aspects.
• The use of third-party frameworks and libraries can add complexity and compatibility issues, and developers should be prepared to adapt to changes and updates.