Android apps rarely break because of one big bug.
They fail quietly — after SDK upgrades, background execution limits, OEM behavior changes, or dependency updates.
Over the last year, I ran into multiple real production issues such as:
- Background work silently stopping
- Lifecycle-related leaks with Kotlin Flow
- Target SDK upgrades changing runtime behavior
- Notifications failing without crashes on newer Android versions
- CI builds breaking due to unmanaged dependencies
- OEM-specific power management issues
This is not a rant — it’s a practical production post-mortem, written from an engineering and architecture perspective, with up-to-date fixes and real code examples.
👉 Read the full article on Medium:
https://medium.com/@vaibhav.shakya786/things-that-broke-my-android-app-last-year-and-how-i-fixed-them-420c2c37de27
Top comments (0)