Can Your Android App Survive a Technical Code Review?
Android development roles at Indian product companies test Jetpack Compose adoption, MVVM architecture, coroutine usage, and Play Store deployment readiness. We audit your Kotlin repositories against the criteria that mobile engineering teams actually evaluate — from Activity/Fragment architecture to ProGuard configuration.
What Android Interviews Test at Entry Level
Android development has a structural hiring advantage in India: fewer bootcamps teach it, fewer students target it, and every company building mobile products (fintech, EdTech, food delivery, e-commerce) needs Android engineers. The applicant-to-opening ratio for Android roles is approximately 5:1 compared to 80:1 for full-stack web roles. The interview process tests architecture patterns (MVVM, repository pattern, dependency injection with Hilt/Koin), coroutine and Flow usage (scope management, cancellation, structured concurrency), UI implementation (Jetpack Compose adoption, Material Design, accessibility), and production readiness (ProGuard/R8, signed builds, Play Store deployment). Our audit evaluates each dimension with specific file:line references and fix recommendations.
Architecture is the dimension that separates Android portfolios. A single-Activity app with all logic in the Activity signals tutorial-level development — and every Android tutorial teaches this pattern. A multi-module app with MVVM, a repository layer abstracting data sources (Room + Retrofit), and Hilt dependency injection signals professional Android development. Our audit traces your architecture from Activity/Fragment → ViewModel → Repository → Data Source, verifying separation of concerns and testability at each layer. The most common failure: business logic in ViewModels that should be in repositories, making unit testing impossible without mocking Android framework dependencies.
Coroutine misuse is the most common runtime bug in Android portfolios. GlobalScope.launch — which every tutorial uses — creates coroutines that are not bound to any lifecycle, causing memory leaks and crashes when the Activity is destroyed. Our audit checks every coroutine launch site for proper scope binding (viewModelScope, lifecycleScope), structured concurrency patterns, and cancellation handling. A project where every coroutine is properly scoped signals production Android awareness that most entry-level candidates lack.
System Comparison
| EVALUATION CRITERIA | TYPICAL ANDROID PORTFOLIO | ANVIL ANDROID DIAGNOSTIC |
|---|---|---|
| Architecture | Single Activity. findViewById everywhere. No ViewModel. Business logic in Activity. | MVVM audit. Repository pattern verification. Hilt/Koin DI configuration check. Multi-module feasibility assessment. |
| Coroutines & Flow | GlobalScope.launch everywhere. No cancellation. Memory leaks from undisposed coroutines collecting flows. | Coroutine scope audit. viewModelScope usage verification. Structured concurrency check. Flow collection lifecycle verification. |
| UI Implementation | XML-only layouts. No Jetpack Compose. Basic Material components with default theming. | Compose adoption audit. Recomposition efficiency check. Accessibility audit (contentDescription, touch targets). Material 3 theming verification. |
| Production Readiness | Debug build only. No ProGuard/R8. Not signed. Crashlytics missing. API keys in source. | Release build configuration verification. ProGuard/R8 rules audit. Signing configuration check. Crash reporting + analytics integration verification. |
Frequently Asked Questions
Do I need Jetpack Compose experience, or is XML still acceptable?
XML is still widely used in production apps and is completely acceptable. Compose adoption is a positive signal because it indicates you are learning the framework's current paradigm, but it is not a requirement. Our audit evaluates UI implementation quality regardless of framework — XML with proper ConstraintLayout usage and Material Design adherence scores well. Compose with proper recomposition optimization scores better. Neither is penalized.
What Android-specific security checks do you run?
We check: API keys committed to source code (CRITICAL — must be removed before portfolio submission), network security configuration (cleartext traffic disabled for release builds), ProGuard/R8 obfuscation enabled, exported components in AndroidManifest.xml (activities/services/receivers that should not be exported), and WebView security configuration (JavaScript disabled for untrusted content). Each CRITICAL finding includes the specific file:line reference and fix command.
Get Your Android Portfolio Production-Reviewed
Submit your GitHub repository. Our mobile engineering team audits your Kotlin code against production Android standards — architecture, coroutines, Compose, and release readiness. Receive a diagnostic report within 24 hours.
- Expert-verified in 24 hours
- Actionable learning paths