Mobile developer interview questions for remote roles
Remote mobile interviews focus on how your app behaves in the real world: on slow networks, cheap phones, old app versions and strict store reviews. Expect framework questions for React Native or Flutter, a practical task, and questions about releases.
These are questions we see in interviews for remote cross-platform roles open to Nigerian developers.
Updated October 2026 by the WorkRemote careers team
On this page
About the role and your experience
Openers that check you understand the job and have done the work.
Why did you choose React Native (or Flutter) over native development?
Why they ask
They want to know you understand the trade-offs, not just the framework you happened to learn.
How to answer
One codebase for two platforms, faster delivery and shared skills with the web (for React Native) or highly consistent UI (for Flutter). Be honest about the costs: native features sometimes need platform code, and debugging spans several layers.
Why mobile, and why this company?
Why they ask
They want genuine interest in their product.
How to answer
Download and use their app before the interview. Mention something specific you liked and one thing you would improve, kindly.
Technical questions
What you know and how you'd do the work, often with a live task or test.
How do you make a long list scroll smoothly?
Why they ask
List performance is the most common mobile performance problem.
How to answer
Use a virtualised list (FlatList or FlashList in React Native, ListView.builder in Flutter) so only visible rows render. Give rows stable keys, keep row components light and memoised, size images to what is displayed, and avoid inline functions that force re-renders. Test on a low-end Android phone with a release build, not a debug build.
In Flutter, what is the difference between a StatelessWidget and a StatefulWidget?
Why they ask
A basic Flutter check that leads into state management.
How to answer
A StatelessWidget is described entirely by its configuration and rebuilds only when its parent passes new values. A StatefulWidget has a State object that persists across rebuilds; calling setState marks it dirty so Flutter rebuilds it. For shared or app-wide state you move beyond setState to Riverpod, Bloc or Provider.
How would you build an app that works offline and syncs later?
Why they ask
Offline support is vital for users on unstable networks, including in Nigeria.
How to answer
Store data locally (SQLite, WatermelonDB, Drift or MMKV), show cached data first, queue user actions with unique IDs, and replay them when the connection returns. Make server endpoints idempotent so retries do not duplicate records, and decide how to handle conflicts, such as last-write-wins or asking the user.
Show a sample answerHide the sample answer
For a field sales app in Kano, reps recorded orders in places with no signal. I stored orders in SQLite with a client-generated UUID and a status of pending, and a background task synced them when the network came back. The API ignored duplicate UUIDs, so retries were safe. Lost orders stopped completely.
How do you store an access token securely on the device?
Why they ask
Security mistakes in mobile apps are common and costly.
How to answer
Use the iOS Keychain and Android Keystore-backed storage through expo-secure-store, react-native-keychain or flutter_secure_storage, not plain AsyncStorage or SharedPreferences. Keep access tokens short-lived with a refresh token, and clear them on logout.
How do push notifications work on Android and iOS?
Why they ask
Almost every product app uses them and setup is fiddly.
How to answer
The app asks for permission, gets a device token from Firebase Cloud Messaging (Android, and often iOS through FCM) or Apple Push Notification service, and sends it to your backend. The backend sends messages through FCM or APNs. Handle token refresh, notification taps that deep link to a screen, and Android 13's runtime permission for notifications.
How do you handle API changes when users are on old app versions?
Why they ask
Unlike the web, you cannot force everyone to update instantly.
How to answer
Keep APIs backwards-compatible (add fields, do not remove or rename them), version endpoints when you must break things, send the app version in a header, and add a minimum-supported-version check that shows an update screen when needed.
What are over-the-air updates, and what are the limits?
Why they ask
Teams using Expo or similar tools ship JavaScript fixes without a store release.
How to answer
With EAS Update (or similar), you can push JavaScript and asset changes to installed apps without store review. You cannot change native code that way, and store rules still apply, so you should not use updates to change an app's main purpose. Use staged rollouts and keep the ability to roll back.
Your app's size has grown to 120MB. How do you reduce it?
Why they ask
App size affects downloads, especially where data is expensive.
How to answer
Measure first with the store's size reports. Then compress and resize images, remove unused libraries and fonts, use Android App Bundles so users download only what their device needs, enable code shrinking (R8) on Android, and load large assets on demand.
How do you test a mobile app?
Why they ask
Mobile bugs are expensive because fixes wait on store review.
How to answer
Unit tests for logic, component or widget tests for UI, a few end-to-end flows with Maestro or Detox, and manual testing on real devices, including a low-end Android and an older iPhone. Use TestFlight and Play testing tracks for beta releases.
Behavioural questions
Past situations. Answer with a real example: what happened, what you did, what changed.
Tell me about an app you shipped and something you would do differently.
Why they ask
Shows real experience and the ability to reflect.
How to answer
Give the store link, your role, users or downloads, one technical decision you are proud of and one you would change. Be specific.
How do you work with designers who only design for iPhone?
Why they ask
Platform differences cause friction on many teams.
How to answer
Raise Android-specific needs early (back button behaviour, different system fonts, smaller screens), suggest small adjustments, and agree what should look identical and what should feel native on each platform.
Situational questions
Hypotheticals about problems you'd meet in the job.
Apple rejected your build the night before launch. What do you do?
Why they ask
Store rejections happen to everyone; they want calm problem-solving.
How to answer
Read the guideline cited, decide whether to fix the app or explain through Resolution Center, reply clearly with screenshots, and tell the team the realistic new date straight away. If it is a misunderstanding, a polite, specific reply is often enough.
Show a sample answerHide the sample answer
We were rejected under guideline 5.1.1 because sign-up asked for a date of birth with no explanation. I added a line explaining it was required for KYC, updated the privacy details in App Store Connect and replied in Resolution Center. It was approved the next day, and I told the product manager the launch would slip by one day before she asked.
A crash only happens on some Android devices. How do you investigate?
Why they ask
Device fragmentation is a daily reality on Android.
How to answer
Check Crashlytics or Sentry for the device models, OS versions and stack trace, look for patterns (memory, a specific manufacturer's customisation, an OS version), reproduce on a matching device or Firebase Test Lab, then fix and monitor the crash rate after release.
Remote work questions
How you'll work from Nigeria with a team elsewhere: hours, power, internet, communication.
How do you test on iOS if you do not own a Mac?
Why they ask
Interviewers know many Nigerian developers lack Macs and want an honest answer.
How to answer
Be honest about your setup: Expo cloud builds, TestFlight on an iPhone you have access to, or a Mac you use. Show you have a plan if the job needs more, such as buying a used MacBook once hired.
How do you keep releases on schedule when your team is in another time zone?
Why they ask
Releases involve QA, product sign-off and store review across time zones.
How to answer
Agree a release calendar, submit builds early in your day so reviews progress overnight in the US, share TestFlight and Play testing links with notes on what to test, and post release status updates in one channel.
Remote interview tips
Install the company's app before any interview and try its main flow. Interviewers notice when you have, and it gives you a real example to discuss.
Have your own app installed on your phone, ready to show on camera or via screen mirroring. Keep a short screen recording as backup in case the live demo fails on a weak connection.
If they ask you to build a feature live, use the framework you are strongest in, and say how you would test it on both platforms.
Questions people ask
What is a typical mobile developer take-home test?
Usually a two- or three-screen app that fetches data from a public API, with a list, a detail screen, search and some caching. Expect four to eight hours. Reviewers check structure, state management, error handling and tests.
Will I be asked native Android or iOS questions in a React Native interview?
Often a few, such as permissions, app lifecycle or how a native module works. Senior roles go deeper.
Do mobile interviews include algorithms?
Some do, especially at larger US companies. Startups more often focus on practical app-building tasks.
Updated October 2026 by the WorkRemote careers team
Interview questions for roles close to mobile developer
- Android Developer
An Android developer builds native apps for Android phones and tablets, today mostly in Kotlin with Jetpack Compose. It is one of the cheapest software careers to start from Nigeria (no Mac needed, $25 once to publish on Google Play), and remote companies hire Nigerian Android developers, usually at mid-level and above.
- iOS Developer
An iOS developer builds native apps for iPhone and iPad in Swift, mostly with SwiftUI and some UIKit. You can do it remotely from Nigeria, but it costs more to start than Android: you need a Mac for Xcode, ideally an iPhone, and $99 a year to publish on the App Store.
- Frontend Developer
A frontend developer builds the part of a website or web app people see and click, mostly with HTML, CSS, JavaScript or TypeScript and React. It is one of the most common remote tech jobs open to Nigerians, but it is also the most crowded, so you need polished, fast, accessible work to get noticed.
- Full Stack Developer
A full stack developer builds both the user interface and the server side of a product, often React or Next.js on the front and Node.js, Python, Laravel or Rails behind it with a SQL database. Startups hiring remotely like full stack developers because one person can ship a whole feature, and many Nigerians land remote work this way after a few years at an agency or startup.