One checklist
Everyone executes against the same named targets; defects reference a profile ID.
← Back to use cases
SEO Page
Android device profiles
Profiles name the combination of device characteristics you care about—API level, manufacturer tier, screen class, and more—so every run targets the same thing. They underpin compatibility testing, regression, and device simulation without arguing about which phone is “reference”.
What belongs in a profile
- Android version / API level and security patch expectations.
- Screen size, density, and locale defaults.
- Performance class (RAM, CPU) when it affects your app.
- Optional network or account fixtures used during the test.
Why teams adopt them
Parallel shards
Map shards to profiles instead of random emulator images.
Faster triage
Reproduce customer issues by matching the closest profile, not guessing settings.
How Device Changer fits
Device Changer is built around consistent, shareable environments for Android validation—ideal when profiles must match between QA and engineering.
Interface screenshots
FAQ
How many profiles do we need?
Start with three to five that mirror analytics buckets; expand when you see repeated escapes outside those buckets.
Are profiles a replacement for real devices?
No—they prioritise and document what you test; physical coverage still closes hardware gaps.