App testing before launch is the best way to avoid bad first reviews, rejection by Apple or Google and angry customers. An app runs on hundreds of types of phone, with different screens, versions and settings. What works perfectly on the developer's phone can crash on a customer's.
So testing isn't a formality at the end, but a regular part of the build. In this article you'll learn which types of test there are, how a beta test works and which points you can check yourself before your app goes live.
Why app testing before launch matters so much
With a website you can often fix a bug within a few minutes. An app is different. A new version first has to go through Apple's and Google's review again, and then users still have to install the update. So a bug stays visible for longer.
On top of that, a first impression is hard to repair. People who run into a bug the first time they open the app often delete it straight away and sometimes leave a low rating. Those reviews stay in the store and put new users off.
Which types of app testing are there?
A good test round has several parts. Each catches a different kind of problem:
- Functional testing: does every button and screen do what it should? From logging in to paying.
- Device testing: does the app work on old and new phones, small and large screens, iPhone and Android?
- User testing: do real users understand what to do without explanation?
- Performance testing: does the app start quickly, stay smooth with lots of data and not drain the battery?
- Security testing: is data properly protected, and can nobody access someone else's information?
- Accessibility testing: does the app work with larger text, screen readers and enough contrast?
- Automated tests: small pieces of code that check whether parts keep working after every change.
Which phones should you test on?
You can't test on every phone in existence. But you can make a smart selection:
- At least one recent and one somewhat older iPhone.
- A few Android phones from different brands, because manufacturers often customise Android.
- A small screen and a large screen.
- The oldest version of iOS and Android you want to support.
- A tablet if needed, if your app also has to work on one.
Also look at your own target group. Do your customers mainly use iPhones, or budget Android phones? That's where you focus. Besides real devices, developers also use simulators: software that mimics a phone on the computer. Handy for quick testing, but no substitute for a real phone in your hand.
A beta test with real users
Before your app is available to everyone, you can first give it to a small group. That's called a beta test. Apple and Google offer their own tools for this:
- Apple's TestFlight: you invite testers by email or link, and they install the test version on their iPhone.
- Testing tracks in Google Play: you first open the app to an internal or closed group of testers before it goes public.
Choose testers who resemble your real users. Colleagues know the app too well and don't get stuck anywhere. Ask a few loyal customers or staff from the shop floor. Give them a few concrete tasks, such as 'book an appointment for next week', and then ask what they found difficult.
Checklist: how to test your app before launch
Go through these points, or have your developer show you they've been tested:
- Installing, opening and registering works from a clean phone.
- Logging in, logging out and forgotten password all work.
- All main routes work from start to finish, such as ordering, booking or sending a form.
- Payments work, including a failed or cancelled payment.
- The app keeps working properly without internet or with a poor connection.
- What happens if someone refuses permission for the camera, location or notifications?
- A phone call or notification during use doesn't break the app.
- The app works with larger text and in dark mode.
- Push notifications arrive and open the right screen.
- Texts have been checked for errors, in every language you offer.
- The privacy policy can be reached from the app and matches what the app does.
- Crash reporting is switched on, so you see errors after launch.
Reporting and fixing bugs
You'll find bugs while testing. That's exactly the point. Make it easy for your developer by reporting them well:
- What did you do, step by step?
- What did you expect, and what happened?
- On which phone and which version of iOS or Android?
- A screenshot or short screen recording.
Then agree together which bugs need fixing before launch and which can wait. A small cosmetic issue doesn't need to hold up the launch. A bug in payments or login does.
Launch calmly and keep testing afterwards
Even after thorough testing, it's wise to launch calmly. Both Apple and Google let you roll out an update gradually to a share of users. If something goes wrong, it only affects a small group. Read more about publishing in getting your app into the App Store.
Testing doesn't stop after launch. Every update and every new version of iOS or Android needs a fresh check. That's part of app maintenance and updates. For websites we have a similar list in testing before go-live.
App testing and launch with Violexa
At Violexa we test throughout the build, not just at the end. You regularly get a test version on your own phone, and before launch we go through a fixed checklist together. Then we guide the submission to Apple and Google. Read more about how we build apps under websites and apps.
A custom project starts from €1,799 excl. VAT (€2,177 incl. VAT). Larger apps get a fixed price in writing up front.
Is your app nearly ready, or are you unsure whether it's been tested well enough? Book a free quickscan. In 30 minutes, online or at your location, we take a look with you. Afterwards you get short written advice with a price indication, with no obligation.
Frequently asked questions
How do you test an app before it's in the App Store?
With Apple you use TestFlight. You invite testers, who install the test version on their iPhone without the app being public. With Google Play you can first put the app in an internal or closed test group.
How many testers do you need for an app?
For a user test, a handful of people will already find most of the big problems. Choose testers who resemble your real users. For a broader beta test, a larger group helps you find bugs on different phones.
How long does app testing before launch take?
That depends on the size of the app. Testing ideally happens throughout the build. For the final test round and a beta test with real users, allow a few weeks, including time to fix the bugs you find.
What happens if Apple or Google rejects my app?
You get a message with the reason. It's often about missing privacy information, a crash or unclear features. Once it's fixed, you submit the app again. Testing well in advance reduces the chance of rejection.
