Mobile developer interview questions

33 questions, easy to hard. Read one, then answer it out loud: an AI interviewer follows up, hints when you're stuck and grades your answer.

Mobile interviews cover what's different about apps on phones: platforms and frameworks, the app lifecycle, offline sync, push notifications and releases.

Platforms and Frameworks

  1. A start-up with two web developers wants to launch on both iPhone and Android. Explain the trade-offs between building two native apps and using a cross-platform framework, and what you'd recommend for them.

  2. A client asks whether they could skip the app stores and ship a progressive web app instead. Explain what a progressive web app is, what it can do, and where it falls short of a native app.

  3. A designer has made one identical design for both iPhone and Android, including custom back buttons and navigation. Explain why platform conventions matter and which differences you'd respect.

  4. Explain how cross-platform frameworks get your shared code onto the screen. Compare frameworks that drive the platform's own native widgets with those that draw every pixel themselves, and the trade-offs of each.

  5. Your cross-platform app needs a feature, such as reading a health sensor, that the framework doesn't support. Explain how you'd bridge to native code and how you'd keep that bridge maintainable.

  6. Your company has a web app and is building a mobile app, and wants to share as much code as possible. Explain what can realistically be shared, what should stay platform-specific, and how you'd organise the code.

App Lifecycle

  1. A user is filling in a long form in your app, switches to their messages, and comes back an hour later to find the app restarted and the form empty. Explain the states a mobile app moves through and why this happened.

  2. Your app asks for camera, location, contacts and notification permissions all at once on first launch, and most users say no. Explain how you'd redesign when and how the app asks.

  3. Your app needs to upload large videos even if the user switches to another app. Explain the limits mobile operating systems put on background work and how you'd make the upload reliable.

  4. Deep Links
    • medium
    • Pro

    Marketing wants links in emails that open straight to a product page inside your app if installed, or the website if not. Explain how deep links work and how you'd implement and secure them.

  5. Testers report that after a phone call, your app sometimes reopens on the right screen but with blank data or a crash. Explain what process death is and how you'd design screens to restore correctly.

  6. On Android, rotating the phone in your app restarts the network request and loses what the user typed. Explain why configuration changes cause this and how you'd structure the screen so they don't.

  7. Your app stores the user's refresh token and an API key in plain local preferences. Explain the risks, how you'd store sensitive data on the device, and why some secrets should never be in the app at all.

Offline and Sync

  1. Your note-taking app shows a spinner and an error whenever the user is on the Underground. Explain what an offline-first app is and how it would change the way this app reads and saves notes.

  2. Your app needs to store user settings, a few hundred cached articles with search, and downloaded images. Explain the storage options on a phone and which you'd use for each.

  3. Your app checks whether the phone is connected to Wi-Fi before syncing, but users on hotel Wi-Fi still see failures. Explain why connectivity checks are unreliable and how you'd handle the network more robustly.

  4. A field engineer completes ten inspection reports with no signal, then reconnects. Explain how you'd design a queue of pending changes so all ten reach the server exactly once and in a sensible order.

  5. When a user likes a post, your app waits for the server before filling in the heart, which feels sluggish on mobile networks. Explain optimistic updates and how you'd implement them safely.

  6. Scrolling through your app's photo feed re-downloads images and makes the phone hot. Explain how you'd load and cache images efficiently on mobile.

  7. A user edits the same shopping list on their phone while offline and on their tablet, and both later sync. Explain the strategies for resolving conflicts and which you'd use for a shared shopping list.

Push Notifications

  1. Explain how a push notification gets from your server to a user's phone, even when your app isn't running, and what each party in the chain does.

  2. After marketing started sending three push notifications a day, many users turned notifications off or uninstalled the app. Explain how you'd design a notification strategy users don't hate.

  3. Your notification service sends to millions of stored device tokens, and many sends fail or reach people who logged out. Explain how you'd manage device tokens correctly.

  4. Your team wants to use invisible push messages to keep the app's data fresh in the background. Explain how silent or data-only notifications work and why they can't be relied on for guaranteed delivery.

  5. Product wants notifications with images and buttons like reply or mark as done. Explain how rich and actionable notifications work on mobile and what to watch out for.

  6. A news app must send a breaking-news alert to twenty million devices within a couple of minutes. Explain how you'd design the sending pipeline.

Performance and Releases

  1. Your app's feed of a thousand items stutters when scrolling. Explain what causes janky scrolling on mobile and how you'd make the list smooth.

  2. Your first app submission was rejected by the app store. Explain how app store review works, common reasons apps get rejected, and how to prepare a submission that passes.

  3. Your app takes four seconds to show its first screen on mid-range Android phones. Explain the difference between cold and warm starts, and how you'd measure and reduce startup time.

  4. Users complain your app drains their battery and uses lots of mobile data. Explain what usually causes this and how you'd fix it.

  5. Reviews mention crashes, but your team can't reproduce them. Explain how crash reporting works on mobile and how you'd use it to find and prioritise fixes.

  6. A bad release reached all users at once and you couldn't roll it back. Explain why mobile releases are harder to undo than web releases, and how you'd release more safely.

  7. Your backend team wants to change an API, but some users are still on app versions from two years ago. Explain how you'd keep old versions working and when and how you'd force users to update.

Questions about practising

How should I prepare for mobile developer interview questions?
Practise answering them out loud, not just reading them. Explaining an answer under follow-up questions is what interviews test. Work through the 33 questions here from easy to hard, and revisit the ones you struggle with.
Can I practise mobile developer interview questions with an AI?
Yes. Open any question and start a voice session: an AI interviewer asks it, follows up on your answer, gives hints when you're stuck and grades your answer with written feedback when the call ends.
Are these mobile developer interview questions free?
5 of the 33 questions are free to practise. Sign in with Google, no card needed. Pro unlocks the rest, plus practice calls to your phone.