Most business owners expect the hard part of an app to be the build. In practice, many launches stall after the build is finished, when the app reaches Google Play or the App Store and gets held up. To publish a mobile app on Google Play and the App Store without losing weeks, you need developer accounts, release builds, store listings and privacy declarations ready before you submit. This guide covers what to prepare, in what order, and where apps usually get stuck.
Set up your developer accounts first
Account verification is the step most likely to delay a launch that is otherwise ready, so start it early.
Google Play Console
Google Play needs a developer account with a one-time registration fee and identity verification. Organisation accounts ask for business details, so have your company documents ready. Decide early whose name the account sits under.
Apple Developer Program
Apple requires an annual membership to publish on the App Store. Organisation enrolment needs legal entity details and a D-U-N-S Number, which can take time to obtain. Make sure the Apple ID you use is one the business controls.
Build the release versions
Test builds and release builds are not the same. Release builds must be signed, numbered correctly and built for the stores' current requirements.
- Android: Upload a signed Android App Bundle (.aab). In Flutter, this is produced with flutter build appbundle. Use Play App Signing so Google manages the app signing key, and keep your upload key backed up.
- iOS: Produce the build with flutter build ipa on a Mac, or through a cloud build service, then upload it through Xcode or Transporter. The build appears in App Store Connect, where you can also send it to TestFlight testers.
- Version numbers: Every upload needs a higher build number than the last one, or the store will reject it.
If you are working with a team, make sure the signing keys and certificates are stored where more than one trusted person can access them. Losing a key can block future updates.
Prepare the store listing
The listing is what customers judge before they install. It also has to match what the app actually does.
- App name and a short description that says who the app is for
- A full description covering the main features, without claims the app does not deliver
- App icon and screenshots for the device sizes each store asks for
- A feature graphic for Google Play
- Category, contact email and a support page or address
- Age or content rating questionnaires, completed honestly
Get privacy and permissions right
Privacy declarations are now a common reason for delay. Both stores want the answers to match your app's real behaviour.
- Privacy policy: Publish a live, public URL. Both stores require one when the app collects personal data.
- Google Play Data safety form: Declare what data you collect, why, and whether it is shared with third parties.
- App Store privacy details: Complete the privacy questions in App Store Connect to match the same data flows.
- Permissions: Only request location, camera, contacts or notifications if the app uses them, and explain the reason in the app.
- Social sign-in: If your app offers login with third-party accounts, Apple's guidelines generally expect an equivalent option such as Sign in with Apple.
For Nigerian businesses, your data handling should also reflect the Nigeria Data Protection Act. The store forms are not a substitute for that, but they should describe what you actually do.
Give reviewers a working app
Many rejections come from reviewers not being able to test the app. If the app needs a login, provide a demo account in the review notes, with enough sample data that every main screen works. Remove placeholder text, "coming soon" screens and broken links. Test payment flows and forms on real devices, not only in an emulator, and include older Android versions in your test list.
Test with real users before public release
Testing tracks let you find problems before the public sees them. Use Google Play's internal testing track first, then closed testing with a small group. Google has required newer personal developer accounts to run a closed test with a minimum number of testers for a set period before production access, and these rules change, so check the current requirement in Play Console. On iOS, TestFlight covers beta testers. Collect crash reports and fix them before you submit.
Common reasons apps get held up
- The store listing describes features the app does not have yet
- The privacy policy is missing, hidden or does not match the data safety form
- The app crashes on the reviewer's device
- A login is required and no demo account was provided
- The version number was not increased for the new upload
- Placeholder content or unfinished screens are visible
Plan the launch after approval
Approval times vary, so do not promise customers a launch date until the app is approved. When it is, consider a staged rollout on Google Play, which releases the update to a share of users first. On iOS, you can choose phased release for automatic updates. Have a support contact ready, watch crash reports closely in the first weeks, and brief your staff on what customers will see.
Publishing is also not the end. Operating systems and store requirements change, so updates will be needed over time. Our technical support service covers bug fixes, code repairs and ongoing maintenance for apps already in the stores.
Frequently asked questions
Can I publish an iOS app without a Mac?
You need macOS with Xcode to produce and sign an iOS build directly. If you do not own a Mac, a cloud build service can produce and upload the build for you. Android builds do not have this requirement.
How long does app store approval take?
It depends on account verification, the review queue and whether the app is rejected and resubmitted. Plan a buffer in your timeline and avoid announcing a date until approval is confirmed.
Do I need separate developer accounts for each store?
Yes. Google Play and the Apple Developer Program are separate, with their own fees, verification steps and rules. Apple does not share its enrolment with Google, and the reverse is also true.
Who should own the developer accounts?
The business should own them, not a personal email belonging to one developer. Keep at least two trusted people with admin access so updates can still go out if one person leaves.
Publishing is manageable when the groundwork is done early. If you are planning a launch and want help with the build, listings or store requirements, see our mobile app development service, or send us a project brief and we will reply with next steps. You can also contact the Icoweb team directly.




