How to Test Apps on Real Devices Effectively
From installing your first APK to filing a report that gets accepted: a complete guide to testing mobile apps on your own device.
Setting up your device for testing
Android
Enable Developer Options: Settings → About Phone → tap Build Number 7 times
Enable USB Debugging (for ADB installs) or allow Unknown Sources (for direct APK installs)
For Unknown Sources: Settings → Security → Install Unknown Apps → allow your file manager or browser
Download the APK file from the test platform and tap to install
If blocked by Play Protect, tap 'Install Anyway': test APKs are not in the Play Store and this is expected
iOS (TestFlight)
Install TestFlight from the App Store if not already installed
Accept the TestFlight invitation link from the test platform: this opens TestFlight automatically
Tap Install in TestFlight
If using a direct IPA (enterprise distribution): tap the installation link from Safari (not Chrome) and follow the prompts
Trust the developer profile: Settings → General → VPN & Device Management → tap the developer name → Trust
Before you start testing: read the brief fully
The test brief tells you: what the app does, which flows to test, any known issues (which you should not report), test account credentials if required, and specific scenarios the developer wants checked. Missing a brief instruction is one of the most common reasons reports get rejected.
Note the exact test duration: don't start if you can't complete it
Note any flows explicitly out of scope: don't report issues in areas not being tested
Check if a test account is provided: use it, don't use your personal account
Note the minimum OS version: test on the OS version you have, not one above or below
What to test: and in what order
First launch / onboarding
Install fresh. Do not use any prior knowledge of the app. Document every step of the onboarding process and note any confusion, unclear instructions, or unexpected screens.
Core user flows
Complete every primary action the app is designed for. If it's a shopping app: browse, add to cart, checkout. If it's a productivity app: create, edit, delete, share.
Navigation and back behaviour
Test all navigation paths. Can you get back to home from every screen? Does the back button behave predictably? Are there any dead ends?
Edge case inputs
Enter empty fields where input is expected. Enter very long text. Use special characters (emoji, accents, symbols) in text fields. Try negative numbers in numeric fields.
Connectivity states
Enable airplane mode and attempt to use the app. Re-enable connectivity mid-flow. Test on a slow connection (turn off WiFi and use mobile data in a low-signal area).
Interruptions
Receive a phone call while using the app. Receive a push notification. Lock and unlock the device mid-flow. Background the app and return to it after 10+ minutes.
Performance
Note any screens that take more than 2 seconds to load. Note any animation jank or lag. Note if the device becomes warm during extended use.
Capturing evidence
Screenshots
Take a screenshot of every bug at the moment it occurs. Include the full screen: don't crop to just the bug. The context around the bug matters.
Screen recordings
For crashes, unexpected behaviour, and complex flows: record the complete sequence of steps that leads to the issue. Start recording before you begin the reproduction steps.
Device info
Record your exact device model from Settings → About. Include OS version, app version, and connection type (WiFi/LTE) in every report.
Reproduction confirmation
Before filing a bug, try to reproduce it at least twice. If it happens again, it's a real bug. If you can't reproduce it, note in your report that it occurred once but couldn't be consistently reproduced.
Ready to start testing apps?
Apply as a tester on AppTester.co. Use your existing device to earn $5–$35 per test, on your own schedule.