# Mobile Developer Interviews: iOS and Android Prep
Mobile interviews look a lot like general software interviews, with extra focus on platform knowledge, app lifecycle, and building for unreliable devices and networks.
## Platform fundamentals
**iOS:** Swift value versus reference types, optionals, ARC and retain cycles (and how `weak` and `unowned` break them), the view controller lifecycle, SwiftUI state management, and Grand Central Dispatch or Swift concurrency.
**Android:** Kotlin null safety, coroutines and structured concurrency, the activity and fragment lifecycle, configuration changes, ViewModel and LiveData or Flow, and Jetpack Compose basics.
If the role is cross-platform, expect questions on React Native or Flutter and when native code is still the better choice.
## Architecture
Be ready to explain MVVM, MVI, or a clean architecture setup you have used, and why. Interviewers like candidates who can say what problem the pattern solved, not just name it.
## Practical coding rounds
Typical tasks:
- Build a list screen that loads data from an API with pagination, loading, and error states.
- Cache results so the app works offline.
- Debounce a search field.
- Fix a memory leak or a crash in provided code.
## Mobile system design
"Design an offline-first notes app" or "design a photo feed." Cover local storage, sync and conflict resolution, image caching, battery and data usage, background work limits, push notifications, and how you would roll out a change safely with feature flags and staged releases.
## Quality and performance
Talk about measuring startup time, avoiding work on the main thread, crash reporting, unit and UI testing, and accessibility (dynamic type, screen readers, contrast).
## Show a shipped app
If you have an app in a store, be ready to discuss a real bug, a performance problem you solved, and a review that changed your roadmap.
## Practice explaining your choices
Narrating trade-offs is half the interview. Rehearse with a friend or a tool like [Linkjob AI](https://www.linkjob.ai/) so your explanations stay short and clear.
Read 23 times, last 9 hours ago