--- title: "Android Developer | Mobile Development Team | Azendo" description: "Assign an Android Developer to your roadmap under one monthly agreement, working from Thailand with an Azendo service delivery manager accountable for delivery." url: "https://azendo.co/services/mobile-development/android-developer/" --- [← Mobile development](https://azendo.co/services/mobile-development/) # Android Developer assigned to your roadmap. An Android Developer builds and maintains your Android app across the device and OS spread that makes Android testing genuinely harder than iOS. Assigned under one service agreement with a minimum monthly capacity in hours, run by a service delivery manager in Chiang Mai, Thailand — five hours ahead of Northern Europe. [Contact us](https://azendo.co/get-in-touch/) [See pricing](https://azendo.co/pricing/) Part of our service line [Mobile development](https://azendo.co/services/mobile-development/) This role is delivered as part of our mobile development services. Take the role on its own, or the whole discipline as one delivery team. ## What an Android Developer does on a mobile development team. Skills and scope are agreed before delivery starts, so the first sprint is productive rather than a ramp-up month. The work runs to the same backlog, the same repositories and the same definition of done as your own team's. ### Android Developer skills and technology we assign for * [Kotlin](https://azendo.co/skills/kotlin/) * [Java](https://azendo.co/skills/java/) * [Jetpack Compose](https://azendo.co/skills/jetpack-compose/) * [Android Studio](https://azendo.co/skills/android-studio/) * [Coroutines](https://azendo.co/skills/coroutines/) * [Room](https://azendo.co/skills/room/) * [Hilt](https://azendo.co/skills/hilt/) * [Retrofit](https://azendo.co/skills/retrofit/) * [Espresso](https://azendo.co/skills/espresso/) * [Play Console](https://azendo.co/skills/play-console/) * Feature development in Kotlin, working in your existing architecture rather than imposing a new one. * Jetpack Compose migration from legacy View-based screens, done incrementally. * Play Store releases, staged rollouts and the device fragmentation testing that has to go with them. * ProGuard and R8 configuration, where a wrong rule ships a crash that only appears in release builds. * Maintaining build variants and flavours where the app ships in multiple configurations. ## Seniority levels we assign. Junior through principal. Mid-level covers most feature work on an established app. Seniority is one of the inputs in [how the monthly fee is built](https://azendo.co/pricing/). ## When an Android Developer is the right assignment. Frequently assigned in a pair with an iOS Developer where feature parity matters. On an ongoing roadmap this role is most often assigned alongside an iOS Developer or a React Native Developer. All 4 roles in this service line can sit on the same agreement, and capacity moves between them at the monthly cycle rather than requiring a new contract. At Azendo this sits inside [mobile development](https://azendo.co/services/mobile-development/), on the same agreement as the rest of the team. 160 h Typical monthly capacity for this role Fixed Monthly price, unaffected by leave or holidays 4–6 weeks From signed scope to delivery starting Monthly Cycle to raise or lower committed hours ## Other roles in mobile development. [iOS Developer Mobile development role](https://azendo.co/services/mobile-development/ios-developer/)[React Native Developer Mobile development role](https://azendo.co/services/mobile-development/react-native-developer/)[Flutter Developer Mobile development role](https://azendo.co/services/mobile-development/flutter-developer/) The same delivery team, on your product, month after month. Chiang Mai and Bangkok, Thailand — five hours ahead of Northern Europe ## Questions about assigning an Android Developer. How do you handle device fragmentation testing? Through a device matrix agreed at scoping, using real hardware for the top devices in your analytics and emulation below that. Can the developer work on a Compose migration? Yes, and incrementally. Full rewrites of working Android apps rarely justify their cost. ## Add Android developer capacity to your roadmap. Tell us the scope and the stack. We come back with the profile, the capacity and what the first month looks like, or you can [talk to a service delivery manager](https://azendo.co/get-in-touch/) first. [Contact us](https://azendo.co/get-in-touch/) [How it works](https://azendo.co/how-it-works/) ## Assign a Android Developer to your roadmap.