Quick answer: Before launch, test the app on real iPhone and Android devices against a written checklist built from your project brief. Cover the full customer journey (browse, cart, checkout, order status), account and notification flows, poor-network behaviour and store-listing details. Record every issue, agree what must be fixed before release, and sign off in writing.
Acceptance testing is the buyer's final check that the app does what was agreed. Developers test their own work, but you know your customers and your business rules. This guide is general information to help you plan that check, not a substitute for your own contract or professional advice.
Before you start
- Use the agreed scope. Test against the written brief or quote. Our guide to writing a project brief explains how to make that document testable.
- Use a test build, not the public store. Ask for a test build you can install on your own phones, and a test version of your store with sample products.
- Test on real devices. Use at least one iPhone and one Android phone, ideally one older model and one recent model. Emulators miss problems with cameras, push notifications and slow connections.
- Name one tester who keeps the issue list. Scattered feedback is hard to act on.
The acceptance checklist
| Area | What to check |
|---|---|
| Browsing | Categories, product pages, images, search and filters load correctly and match your store data |
| Cart and checkout | Add, remove and change quantities; apply coupons; complete an order with each payment method you offer using test mode |
| Accounts | Sign up, log in, reset password, edit profile, log out |
| Orders | Order appears in your store admin, status changes show in the app, customer receives the expected emails |
| Notifications | Push notifications arrive, open the right screen and can be switched off |
| Branding and content | Name, logo, colours, languages, legal pages and contact details are correct |
| Connectivity | Behaviour on slow Wi-Fi, mobile data and when the connection drops mid-checkout |
| Devices | Different screen sizes, rotation if supported, text size settings |
| Marketplace roles | If you run a marketplace, test as customer, vendor and admin separately |
How to run the test
- Walk the main journey first. Place a complete test order from install to order confirmation. If this fails, stop and report it before testing the details.
- Then try unusual behaviour. Enter wrong passwords, leave the cart for a day, press the back button during payment and switch apps mid-checkout.
- Ask someone unfamiliar with the project to try it. A new person finds confusing steps you no longer notice.
- Log every issue the same way. Note the device, operating system version, steps to repeat, what you expected and what happened, with a screenshot or screen recording.
Sort issues by severity
- Blocker: customers cannot complete an order or log in, or the app crashes. Fix before launch.
- Major: a feature works incorrectly but there is a workaround. Agree whether it is fixed before or soon after launch.
- Minor: cosmetic or low-impact. Schedule for a later update.
Agree these categories with your developer in advance, so that "ready to launch" has the same meaning for both sides.
Check the store listing and accounts
Launch is more than the app itself. Confirm the app name, description, screenshots, privacy policy link and support contact are ready, and that the Apple and Google developer accounts are in your name. Review the platform guidelines for each store before submission, because review requirements can change.
Sign-off and what comes after
When blockers are fixed, confirm it in writing: which version was tested, which issues remain open and who accepts them. Then plan the handover, including source code and accounts, as described in who owns the source code when you hire an app developer. After release, keep updates going using our mobile app maintenance checklist.
Next step
If you are preparing an app project, read what to prepare before customizing your mobile app. To discuss testing and launch support for your project, see our app customization service or request a quote.
Frequently asked questions
How do you test an app before launch?
Test a build on real iPhone and Android devices against a written checklist from your brief. Cover browsing, cart, checkout, accounts, orders, notifications and weak-network behaviour. Log each issue with device, steps and screenshots, rank them as blocker, major or minor, fix blockers, then sign off in writing.