What we build with it
Android is a target for everything mobile we build, and treating it as "the other platform" is how products end up broken on it. It has its own rules: background execution limits that kill work you assumed would finish, a permission model that changes meaningfully between versions, manufacturer-specific battery optimisation, and a device range wide enough that performance assumptions from a flagship do not hold.
The platform work itself is written in Kotlin behind platform channels and built with Gradle — foreground services, notification channels, NFC and hardware access, install-referrer plumbing, and vendor SDKs that ship Android-only.
Where it fits
Under every Flutter app in our portfolio, all of which are live on Google Play. It is also where white-label work gets interesting: many branded apps from one codebase means many application IDs, signing identities and store listings, generated rather than maintained by hand.
When we recommend it
It is not really a recommendation — if you are building a mobile product outside the US, Android is likely the majority of your users, and treating it as secondary is a business decision rather than a technical one.
Where we would push back is on fully native Android for a product that also needs iOS, unless something specific forces it. And on ignoring the low end: the cheapest device in your analytics is the one that decides your reviews.
