Your app is built, tested and ready for the world. Now comes the step that catches many first-time founders and businesses off guard: getting it approved and live. If you want to publish your app on the App Store and Google Play smoothly, you need the right accounts, a complete store listing, clear privacy information and an understanding of how each store’s review works. This step-by-step guide explains the process for New Zealand businesses, along with the common reasons apps get rejected and how to avoid them.
Before you start: what you need to publish your app
Preparation saves days of back-and-forth. Before submitting to either store, make sure you have:
- Developer accounts for Apple and Google, ideally registered to your organisation rather than an individual or your developer.
- A finished, stable app that has been tested on real devices, with no placeholder content or broken links.
- A privacy policy hosted on your website that explains what data you collect and why.
- Store assets: app name, icon, screenshots for the required device sizes, a short and long description and keywords.
- Support details: a support URL or email address that a real person monitors.
- Test login details for reviewers if your app requires an account.
If you are still deciding how to build your app, our guides to iOS app development and Android app development explain the options in detail.
Apple App Store vs Google Play at a glance
| Step | Apple App Store | Google Play |
|---|---|---|
| Developer account | Apple Developer Program, annual fee | Google Play Console, one-off registration fee |
| Organisation verification | D-U-N-S number required for organisations | Identity and organisation verification |
| Upload tool | Xcode or Transporter, then App Store Connect | Play Console (Android App Bundle) |
| Beta testing | TestFlight | Internal, closed and open testing tracks |
| Privacy disclosure | App Privacy “nutrition labels” | Data safety section |
| Review | Manual review of every build | Automated and manual checks |
Fees and rules change from time to time, so always check the current requirements on Apple’s and Google’s developer sites before you budget.
How to publish your app on the Apple App Store
Step 1: Enrol in the Apple Developer Program
Enrol as an organisation so the app appears under your business name. Apple requires a D-U-N-S number for organisations, which is free to obtain but can take some time to issue, so start this early. You will also need a website and the legal authority to sign agreements for your company.
Step 2: Set up the app in App Store Connect
Create a new app record with its name, bundle ID, primary language and category. Complete the agreements, tax and banking sections if your app is paid or offers in-app purchases. New Zealand businesses will need their IRD and banking details ready for this.
Step 3: Prepare your listing
Write a clear description that explains what the app does and who it is for. Upload screenshots for the required iPhone sizes (and iPad if supported), an app preview video if you have one, keywords, a support URL and a marketing URL. Complete the age rating questionnaire honestly.
Step 4: Complete App Privacy details
Apple asks you to declare the data your app and any third-party tools collect, such as contact details, location or usage data, and whether it is linked to users or used for tracking. If your app tracks users across other companies’ apps or websites, you also need to request permission using App Tracking Transparency.
Step 5: Upload a build and test with TestFlight
Your developer uploads the build from Xcode. Use TestFlight to share it with internal staff and external testers. Beta testing catches crashes and confusing flows before Apple’s reviewers, or your customers, see them.
Step 6: Submit for review and release
Add review notes, test account details and any information the reviewer needs, then submit. Many apps are reviewed within a day or two, though it can take longer. Once approved, you can release immediately, schedule a date or use a phased release that rolls out gradually.
How to publish your app on Google Play
Step 1: Create a Google Play developer account
Register an organisation account in the Play Console and complete identity verification. Google may ask for documents confirming your business details, so have them ready.
Step 2: Create the app and complete the setup tasks
The Play Console guides you through a checklist: app access instructions for reviewers, ads declaration, content rating questionnaire, target audience, news app status and the data safety form describing how you collect, share and protect user data.
Step 3: Build the store listing
Add your app name, short and full descriptions, icon, feature graphic and phone and tablet screenshots. Write naturally for people first; keyword stuffing can hurt rather than help.
Step 4: Test before production
Upload an Android App Bundle to an internal or closed testing track. Google may require newer personal developer accounts to run a closed test with a minimum number of testers before they can publish to production, so check the current rules for your account type.
Step 5: Release to production
Promote your tested release to production and submit it for review. Review can take anywhere from hours to several days. Use a staged rollout to release to a percentage of users first and watch crash reports before going to everyone.
A simple pre-launch checklist
Run through this list in the week before you submit to either store:
- Test the final build on at least a few real iPhones and Android phones, including an older or mid-range model.
- Check that every link in the app, including the privacy policy and support pages, opens correctly.
- Confirm the reviewer test account works and has sample data to explore.
- Make sure push notification and location permission prompts explain clearly why access is needed.
- Proofread your store descriptions in NZ English and check that screenshots match the current design.
- Agree who will monitor reviews and support emails during launch week.
If you built your app with a cross-platform framework, you can usually prepare both store submissions in parallel from the same codebase. Our article on native vs cross-platform apps explains how that choice affects launch and ongoing updates.
Common reasons apps get rejected
- Crashes or bugs found during review.
- Incomplete information, such as missing test logins or broken support links.
- Privacy issues, including a missing privacy policy, inaccurate data disclosures or unexplained permission requests.
- Payments rules, for example selling digital content without using the store’s in-app purchase system where it is required.
- Minimal functionality, where the app is little more than a website wrapper with no real app value.
- Misleading listings with screenshots or descriptions that do not match the app.
- Missing account deletion when users can create accounts in the app.
Rejections are not the end of the world. Read the reviewer’s notes carefully, fix the issue, reply in the review centre and resubmit.
NZ-specific considerations
Publishing from New Zealand is straightforward, but a few local points are worth noting. Your privacy policy should reflect the Privacy Act 2020, including how people can access and correct their information. If your app sells to New Zealand consumers, the Consumer Guarantees Act and Fair Trading Act still apply to your descriptions and claims. Check how GST is handled on app sales and in-app purchases with your accountant, and decide whether to release only in New Zealand first or worldwide from day one.
After launch: keeping your app healthy
Publishing is the beginning, not the end. Monitor crash reports and reviews, reply to feedback politely and ship regular updates. Both Apple and Google update their operating systems and policies every year, and apps that are not maintained can be hidden or removed. A planned maintenance arrangement, like our mobile app development support, keeps your app compliant and improving. For budgeting help, see our guide to how much it costs to build a mobile app in NZ.
Frequently asked questions
How long does it take to publish an app?
Allow a few weeks if you are starting from scratch, mainly for account verification, testing and review. Once accounts are set up, updates can often go live within a day or two.
Should the developer accounts be in my name or my developer’s?
Your organisation should own the accounts. You can invite your developer as a team member, which keeps you in control if you change providers.
Do I need a D-U-N-S number in New Zealand?
Yes, if you enrol in Apple’s program as an organisation. It is free to obtain, but allow time for it to be issued before you plan your launch.
Can I publish only in New Zealand?
Yes. Both stores let you choose which countries your app is available in, and you can expand to more markets later.
What happens if my app is rejected?
You will receive notes explaining the issue. Fix it, respond to the reviewer and resubmit. Most rejections relate to fixable issues such as missing information or bugs.
Can Wisdom Software publish the app for us?
Yes. We regularly prepare listings, manage submissions and handle reviewer feedback on behalf of our clients, while keeping the accounts in your name.
Get help to publish your app with confidence
Knowing how to publish your app on the App Store and Google Play removes a lot of launch-day stress. With accounts ready, accurate privacy details and solid testing, most apps sail through review. If you would rather hand the process to experienced hands, our team can take care of it from build to launch.
Getting ready to launch? Book a free 60-minute consultation and we will review your app, your store setup and your launch plan.