Cover more than one manufacturer
Include the Android device families relevant to your audience instead of treating one phone as the whole platform. The Android version, manufacturer software and screen size are separate parts of a configuration. A customer report should include all three.
Prepare the right application build
Use an installable Android build that matches the release you want to test. Cloud providers may accept APK, AAB or store-based installation through different workflows. Check the required format and installation method before your session, and keep the build version in your notes.
Test transitions, not only the happy path
Review first launch, permission denial, backgrounding, return to the app and interrupted submissions. Check whether the same action behaves differently on a smaller phone or another OS version. These are useful scenarios to add to your release checklist.
Separate manual discovery from repeatable regression
Interactive testing helps you explore an unfamiliar flow. Automation helps repeat a stable set of checks across configurations. Appium and Android instrumentation frameworks are common examples, but versions, packaging and supported options depend on the provider.
Your testing checklist
- Check installation and the first launch
- Test sign-in and expired-session recovery
- Allow and deny relevant permissions
- Verify Android back navigation and keyboard behavior
- Check the critical flow after leaving and reopening the app
- Record crashes, visible errors and device configuration
A practical workflow
Prepare the build
Identify the version, required test accounts and backend environment.
Choose the Android matrix
Select manufacturer, model, OS and screen size for each planned check.
Compare one consistent journey
Repeat the same steps across the shortlist, then retest any device-specific fix.
Common questions
They share the device platform, but the workflows differ. Native or hybrid app testing requires an application build. Website testing uses a mobile browser and a URL.
Use your audience data first. Then include a second manufacturer, a smaller screen or an older supported OS when those configurations are relevant to your product.
Cloud services commonly support frameworks such as Appium or Android instrumentation. Confirm your framework, version, build format and required features with the service before planning a run.
Technical references
Official documentation for the underlying testing concepts. Available capabilities vary by provider and setup.
AWS Device Farm overviewAWS Device Farm test frameworksBrowserStack Android testing