Tell me about an Android app you built or worked on. What was your role?

Note: Mobile interviews reward specifics about users and constraints. Play Store link, download numbers, or crash-free rate all make an answer concrete.

Cover:

• What the app did and its scale. Downloads, active users, and the range of devices and Android versions you supported. Supporting API 24 upwards is a very different job from targeting only recent devices.
• Your scope. Whether you owned the architecture, a feature, the network layer, or the release process. Be precise.
• The stack. Java or Kotlin, Views or Jetpack Compose, and the architecture — MVVM, MVI, or something older. Say honestly if it was a legacy codebase.
• The hard part. Strong candidates: background work surviving Doze and manufacturer battery restrictions, offline support and sync conflicts, memory or ANR problems on low-end devices, or fragmentation across OEM behaviour.
• The outcome — crash-free rate, startup time, app size, or rating before and after.