App Store and Play Store Publishing Interview Questions for Mobile App Development
25 App Store and Play Store Publishing questions with answers for mobile app development roles — 7 easy, 12 medium, 6 hard.
About App Store and Play Store Publishing
Shipping an app means mastering both stores. Learn signing, versioning, Play Console and App Store Connect, testing tracks and TestFlight, privacy declarations, review guidelines, staged rollouts, forced updates, over-the-air updates with EAS, fastlane automation and store optimisation. These questions show whether you can own releases end to end, which employers value highly.
Sheet progressStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
✓ 3 questions free • Unlock the rest in seconds
01
What are the steps to publish an app on the Play Store?
Create a Play Console developer account, create the app and fill in store listing details, screenshots, privacy policy, content rating, data safety and target audience forms. Build a signed release App Bundle with a unique application ID and increasing versionCode, and use Play App Signing. Upload to internal or closed testing first, then promote to production with a staged rollout. New personal accounts must complete a closed test with testers before production access.
02
What are the steps to publish an iOS app on the App Store?
Enrol in the developer program, create an App ID and the app record in App Store Connect, and set up signing with certificates and provisioning profiles, often managed automatically by Xcode or EAS. Archive the release build with an incremented build number, upload it, and test through TestFlight. Complete metadata, screenshots, privacy nutrition labels and age rating, then submit for review. After approval, release manually, automatically or in phased release.
03
What are versionName, versionCode and build numbers?
On Android, versionName is the user-visible version like 2.3.1 and versionCode is an integer that must increase with every upload. On iOS, CFBundleShortVersionString is the marketing version and CFBundleVersion is the build number, which must be unique per version upload. In Flutter, the pubspec version 2.3.1+45 sets both; in Expo, version and the platform build numbers are set in app config and can auto-increment with EAS.
TestFlight distributes iOS beta builds to internal testers on your team and external testers, up to 10,000, after a light beta review. Play Console offers internal testing for quick distribution to up to 100 testers, closed testing for selected groups, and open testing for anyone to join. Using these tracks catches device-specific bugs and gathers feedback before production, and staged rollouts then limit risk further.
05
Write a release checklist for a mobile app update.
1. Bump version name and build number on both platforms.
2. Run full automated tests and smoke tests on release builds.
3. Verify signing, obfuscation and debug symbol upload.
4. Check new permissions and update store privacy declarations.
5. Update release notes and screenshots if UI changed.
6. Upload to internal track and TestFlight; QA sign-off.
7. Submit for review with reviewer notes and demo account.
8. Start staged rollout at 5 to 10 percent.
9. Monitor crashes, ANRs, reviews and key metrics.
10. Expand rollout or halt and hotfix.
06
Tell me about an app you published and what you learned from real users.
Situation: I published a notes app with a friend and got about 2,000 installs. Task: improve ratings stuck at 3.6. Action: I read every review, found users disliked losing notes when switching phones, added cloud backup and a clear onboarding screen, and fixed two crashes from Crashlytics. Result: rating rose to 4.4 in two months. I learned to prioritise what users actually complain about over features I assumed they wanted.
07
Why are you interested in this mobile developer role at our company?
Connect your skills to the role honestly. For example: your app serves millions of users in tier 2 and tier 3 cities, and I have focused on performance for budget phones and slow networks in my projects. I have shipped two cross-platform apps to both stores, and I want to work where release quality and user experience matter at scale. I also like that your team uses Flutter, which I enjoy and want to master.
08
What is app signing and why must you protect the keys?
Signing proves the app comes from you and that updates are from the same developer. On Android, you sign uploads with an upload key and Play App Signing re-signs with the app signing key held by the store; a lost upload key can be reset, but losing a self-managed app key meant you could never update the app. On iOS, signing uses certificates and provisioning profiles. Store keys in a secure vault and CI secrets, never in the repository.
09
What are over-the-air updates and what are their limits?
Over-the-air updates push new JavaScript bundles and assets to React Native apps without a store release, using services like EAS Update. They fix bugs quickly but can only change JavaScript and assets, not native code, permissions or SDK versions, which need a new build. Store policies allow them only if the app's core purpose does not change. Use runtime versions to ensure updates match compatible native builds, and roll out gradually.
10
What are privacy declarations required by the app stores?
The Play Store requires a data safety form describing what data is collected, shared, encrypted and deletable, plus a privacy policy link and account deletion option for apps with accounts. The iOS App Store requires privacy nutrition labels, a privacy manifest file for the app and listed third-party SDKs describing data use and required reason APIs, and App Tracking Transparency permission before tracking users across apps.
11
How do you build a release version of a Flutter app for both stores?
App Store Optimisation improves an app's visibility and conversion in store search. Key factors are the app title, subtitle or short description, keywords, long description, screenshots, preview videos, ratings and reviews. Developers influence it by keeping app size small, crash rates low and performance high, since store algorithms consider quality signals, by adding in-app review prompts at good moments, and by supporting localisation for regional languages.
14
How do you force users to update when an old version has a critical bug?
Keep a minimum supported version in remote config or an API endpoint, check it at startup and show a blocking update screen linking to the store. On Android, use the Play In-App Updates API with the immediate flow for critical updates and flexible flow for normal ones. Keep the backend compatible with older versions for a defined period, and use forced updates sparingly because they frustrate users.
15
Your iOS app was rejected for guideline 5.1.1 about data collection. What do you do?
Read the reviewer's message in App Store Connect carefully. Guideline 5.1.1 issues often involve requesting permissions without clear purpose strings, requiring sign-up for features that do not need an account, or missing account deletion. Fix the specific problem, for example improving usage description text or adding in-app account deletion, and reply in Resolution Center explaining the changes. Ask for clarification if the rejection is unclear.
16
Store review is delaying your launch date. How do you plan releases to avoid this?
Submit builds early, a few days before the planned date, and use manual release so you can publish the approved build at launch time. Ship the code behind a remote feature flag so the feature can be enabled on launch day without a new review. Keep a pre-approved build ready, follow store guidelines closely and include clear review notes and demo login details for reviewers.
17
A user reports that they cannot find your app in the store on their old phone. Why could this happen?
The app may not be available for their device because the minimum OS version is higher than theirs, the device lacks a required hardware feature declared in the manifest, the app is not released in their country, or the device architecture is excluded. Check the device catalogue in Play Console and the deployment target on iOS. Decide whether supporting that segment is worth lowering requirements.
18
How do you communicate a delayed release to stakeholders?
I inform them as soon as I know, not on the release day. I explain the reason briefly, such as a store rejection or critical bug, the impact, the new estimated date, and what we are doing to avoid repeating it. I offer options, like releasing other features first. Regular short updates until release keep trust, and I note learnings in the release retrospective.
19
How do you handle account deletion requirements in mobile apps?
Both major stores require apps that let users create accounts to also let them delete their account from within the app, and the Play Store also requires a web link for deletion requests. Implement a clear settings option, confirm the action, call a backend endpoint that deletes or anonymises user data according to retention rules, revoke tokens, clear local data and sign the user out. Document what is retained for legal reasons.
20
The Play Store flagged your app because a third-party SDK collects data not declared in the data safety form. How do you handle it?
Identify the SDK and what it collects using its documentation and the Play SDK Index. Update the data safety form to declare that data accurately, or configure the SDK to stop collecting it, or replace it if its behaviour is unacceptable. Update the privacy policy too. Then submit a new build if code changed. Keep an inventory of SDKs and their data practices to avoid future surprises.
21
A critical bug reaches production in a React Native app. How do you fix it quickly?
If the bug is in JavaScript, fix it, test on a preview channel, and publish an over-the-air update to production with a staged rollout, keeping it compatible with the current runtime version. If it needs native changes, build a hotfix release, submit it, and request expedited review on iOS if justified. Meanwhile disable the feature with a remote config flag if possible, and halt the store rollout.
22
Your company wants to publish the same app for five white-label clients. How do you manage builds and store listings?
Keep one codebase and create a configuration per client with app ID, name, icons, colours, API base URL and feature flags, using Android flavours and iOS targets or schemes, or dynamic Expo app config. Automate builds for each client in CI with fastlane or EAS. Each client usually needs its own store account or listing, so document signing keys and access per client and automate metadata uploads.
23
An over-the-air update crashed the app for users on an older native build. What went wrong and how do you prevent it?
The update probably used a native module or API that the older binary did not have, so JavaScript called missing native code. Prevent this by setting runtime versions tied to native code fingerprints, so updates only reach compatible builds. Roll out updates gradually, monitor crashes per update ID, and keep a rollback by republishing the previous update. Test updates on the oldest supported build before release.
24
How would you plan a staged rollout for a major redesign?
Release to internal testers and beta users first and collect feedback. Then roll out to 5 percent of production users, monitoring crash-free rate, ANRs, key conversion metrics and reviews for a few days, before moving to 20, 50 and 100 percent. Keep the redesign behind a remote flag to switch back without a release. Define rollback criteria in advance and communicate the plan to support teams.
25
How do you automate store submissions with fastlane?
fastlane defines lanes in a Fastfile, such as beta and release. A lane can increment build numbers, build the app with gradle or gym, sign with match, which stores iOS certificates encrypted in a private repository, upload to TestFlight with pilot or Play testing tracks with supply, and upload metadata and screenshots. Running lanes from CI makes releases repeatable and removes manual steps on a developer's machine.
Frequently asked questions
How important is App Store and Play Store Publishing in Mobile App Development interviews?
Shipping an app means mastering both stores. Learn signing, versioning, Play Console and App Store Connect, testing tracks and TestFlight, privacy declarations, review guidelines, staged rollouts, forced updates, over-the-air updates with EAS, fastlane automation and store optimisation. These questions show whether you can own releases end to end, which employers value highly.
How should I use the App Store and Play Store Publishing sheet?
Go top to bottom — easy to hard. Answer before opening each answer, tick what you solved and save misses to Last-Minute Revision.