# 30 mobile developer interview questions, and what a good answer shows

> Thirty mobile developer interview questions for iOS and Android roles on the app lifecycle, architecture, networking, performance and releases, each with what a strong answer covers.

Source: https://hintvo.com/blog/mobile-developer-interview-questions | Last updated: November 20, 2026 | Reviewed: 2026-11-20

Mobile interviews test whether you can build an app that survives bad networks, old devices and a system that may close it at any moment, and ship it without breaking the version people already have. Below are 30 common questions for iOS and Android roles, each with what a good answer shows.

## Platform basics

- **Walk me through an app's lifecycle on iOS or Android.** A good answer names the states from launch to background to terminated, what to save and when, and that the system can close a background app without warning.
- **What happens when the system closes your app in the background?** A good answer saves drafts and navigation state as the user goes, and restores them quickly on the next launch.
- **How do you keep the main thread free?** A good answer moves network, disk and heavy work to background threads, returns to the main thread only to update the interface, and knows how to spot dropped frames.
- **When should an app ask for a permission?** A good answer asks in context, when the feature needs it, explains why first, handles a refusal gracefully and never blocks the whole app on it.
- **How does a push notification reach a device?** A good answer explains that the app registers with the platform's push service for a token, the server sends through that service, and tokens change and must be refreshed.
- **Which differences between iOS and Android change your design?** A good answer covers navigation patterns, background limits, the range of devices and OS versions, and store review.

## Architecture and state

- **How do you structure an app so it stays testable?** A good answer separates the interface from the logic, injects dependencies and keeps side effects at the edges.
- **Where should app state live?** A good answer keeps screen state in view models, shared state in a repository or store, persisted state in a local database, and one source of truth for each.
- **How do you handle deep links?** A good answer maps routes to screens, validates parameters, and handles a signed-out user or content that no longer exists.
- **Native or cross-platform?** A good answer weighs native code for platform features and performance against one shared codebase, and decides by the team's skills and what the app needs.
- **How do you design an app that works offline?** A good answer makes the local database the source of truth, queues writes, syncs with clear rules for conflicts, and shows what has not synced yet.
- **How do you change behavior without shipping a new version?** A good answer uses remote configuration and [feature flags](https://hintvo.com/blog/feature-flags-in-plain-words), with safe defaults when the fetch fails.

## Networking and data

- **How do you make network calls reliable on a bad connection?** A good answer sets timeouts, retries safe requests with backoff, makes writes idempotent, caches responses and shows clear loading and error states. See [retries and backoff](https://hintvo.com/blog/retries-and-backoff-in-plain-words).
- **How do you protect data stored on the device?** A good answer keeps secrets in the Keychain or Keystore, never stores tokens in plain preferences, encrypts sensitive files and assumes some devices are rooted.
- **What is certificate pinning, and what does it cost?** A good answer explains trusting only known certificates to stop interception, and the risk of locking users out when a certificate changes, which needs a backup pin and a plan.
- **How do you change an API when old app versions are still installed?** A good answer keeps the API backward compatible, versions it, sets a minimum supported version and has a forced-update path for emergencies.
- **How would you load images in a long scrolling list?** A good answer resizes images to the displayed size, uses memory and disk caches, cancels requests for rows that scrolled away and shows placeholders.

## Performance and quality

- **Startup is slow. How do you make it faster?** A good answer measures a cold start, delays work the first screen does not need, initializes lazily and trims what loads at launch.
- **How do you find a memory leak?** A good answer uses the platform profiler, looks for reference cycles or leaked contexts, and fixes the reference that keeps objects alive.
- **How do you keep scrolling smooth?** A good answer reuses cells, keeps binding light, computes layout ahead of time and decodes images off the main thread.
- **How do you test a mobile app?** A good answer uses unit tests for logic, UI tests for the key flows, real devices and older OS versions, and crash reporting in production.
- **A crash hits one percent of users on one device model. How do you investigate?** A good answer filters crash reports by device and OS, reproduces it on that model, and ships the fix with a staged rollout.
- **How do you release a risky change?** A good answer uses a phased store rollout, feature flags, a watch on the crash-free rate and a quick way to switch the feature off.
- **How do you keep the app's download size down?** A good answer compresses assets, removes unused resources and libraries, and uses the platform's app bundles and on-demand resources.

## Accessibility and product

- **How do you make a mobile screen accessible?** A good answer adds labels for VoiceOver and TalkBack, supports larger text sizes, checks contrast and touch target size, and tests with the screen reader on.
- **How do you decide what to track with analytics?** A good answer starts from the questions the team needs answered, keeps a small event plan, respects privacy and consent, and removes events nobody uses.

## Behavioral, for mobile roles

- **Tell me about a release that went wrong.** A good answer covers what happened, how it was noticed, how they limited the damage and what changed in the release process.
- **Tell me about supporting an old OS version.** A good answer explains the cost, how the decision was made and how they kept the code clean while supporting it.
- **The store rejected your app close to a deadline. What do you do?** A good answer reads the cited guideline, fixes the issue or appeals with evidence, and tells people the new date early.
- **Which app do you admire, and what would you borrow from it?** A good answer names specific details, such as an interaction, its speed or its first-run experience, and explains why they work.

## How to practice these

1. Pick the five questions you would find hardest, not the ones you already know.
2. Answer each one out loud in about two minutes, and record yourself if you can.
3. Compare your answer with the note: did it cover what a good answer shows?
4. For every question, write down one real example from your own work that you could use.

For interviewers: the notes work as a scoring guide. Decide before the interview what a strong answer covers, and score the evidence you heard, not the confidence it was said with. See [how to run a fair technical interview](https://hintvo.com/blog/run-a-fair-technical-interview).

More roles and the questions every engineer gets: [interview questions by role](https://hintvo.com/blog/software-engineer-interview-questions-by-role).

> **Where Hintvo fits:** a practice interview asks questions out loud, gives you a score out of 5 and a stronger version of each answer, and on coding questions you can ask for a hint, the approach or the full solution. Practice interviews need a pack of hours. Use Hintvo only where AI help is allowed. Check the rules of your company, school or interviewer first, and respect a no.

## Related

- [How to explain a past project in an interview](https://hintvo.com/blog/explain-a-past-project-in-an-interview.md): How do I explain a past project clearly in a job interview?
- ["Tell me about the hardest bug you fixed": how to tell a debugging story](https://hintvo.com/blog/hardest-bug-you-have-fixed.md): How do I answer "tell me about the hardest bug you have fixed"?
- [200 software engineer interview questions by role, and what good answers show](https://hintvo.com/blog/software-engineer-interview-questions-by-role.md): What interview questions do software engineers get for each role, and what makes a good answer?
