Mobile App QA Testing Checklist Before Launch

The pre-launch test table

Test the business flow first

Start with the action that makes the product valuable. For ecommerce, it is browsing, cart, checkout and order status. For a booking app, it is service choice, available time, confirmation, reminder and reschedule. For an online school, it is lesson access, progress, payment and content playback.

Do not start with button colors. Start with the path that would create a refund, support ticket, store rejection or lost customer if it failed.

Devices, networks and permissions

A mobile app can behave differently across devices. Android back navigation, screen cutouts, keyboard behavior, permission dialogs, low-memory states, push handling and background behavior can vary. iOS has its own release, permission and layout patterns.

For an MVP, choose a practical device set: one recent iPhone, one older supported iPhone, one mid-range Android, one older Android and any special device your audience uses. Automated services help, but manual checks reveal hesitation, confusing copy and small interaction problems.

Store testing tracks and timing

Apple TestFlight lets teams invite internal and external testers before publishing. It should be a calendar item, not a last evening task. Google Play supports internal, closed and open testing tracks.

Some new Google Play personal developer accounts must run a closed test with at least 12 opted-in testers for at least 14 consecutive days before production access. If this applies to the account, it changes the launch schedule.

Analytics and crash reporting

Before launch, check that important events fire correctly: sign_up, purchase, booking_created, payment_failed, subscription_started, onboarding_completed and consultation_click when relevant. Use the event plan from mobile app analytics setup.

Crash reporting is also launch quality. The team should know if a crash happens on a specific device, app version or screen. Do not collect sensitive data in logs; combine this with the security checklist.

How testing changes cost

At Appfyl, MVP projects usually sit around 15,000-25,000 USD. Solid medium products often sit around 25,000-55,000 USD. Large products with several roles, payments, privacy-sensitive data, admin workflows or broad launch testing can reach 55,000-115,000 USD.

Testing effort grows with roles, payment states, integrations, supported devices, languages, offline behavior and store requirements. For broader planning, read mobile app maintenance cost, app redesign and modernization and mobile app backend development.

How Appfyl uses this

Appfyl ties testing to product risk. We identify the core business flow, the roles that touch it, the data that must be protected, the analytics events that prove it works and the devices that matter for the audience.

For booking and delivery products, we test schedule changes, push notifications, failed payments and support actions. For fintech and healthcare products, we test permissions, private data, account recovery and logs. For education products, we test content access, playback, progress and subscription states.

Want to see how Appfyl turns scope into shipped products? View Appfyl cases.

Next step

Before launch, write your top five "must not fail" scenarios. Then add them to the Appfyl feature brief quiz or your project brief.

Questions people ask