MatrixBeginner3-5 min reference
Mobile Device Matrix
You can't test every device, so a device matrix is about choosing a small set that covers the variation that matters — OS version, screen size, and market share — and defending the choice with data. This sheet is the method and a starter matrix; for execution at scale see the device-cloud tools linked below.
The axes that matter
| Axis | Why it varies behaviour |
|---|---|
| OS version | APIs, permissions, default behaviours change per release |
| Screen size / density | Layout, tap targets, reflow |
| Form factor | Phone, tablet, foldable, notch/Dynamic Island |
| Vendor skin (Android) | Samsung/Xiaomi tweaks differ from stock |
| Hardware tier | Low-end RAM/CPU exposes perf + memory bugs |
A starter matrix
| Tier | iOS | Android |
|---|---|---|
| Latest | Newest iPhone, current iOS | Recent Pixel, current Android |
| Mainstream | iPhone from ~2–3 yrs ago | Popular Samsung mid-range |
| Minimum supported | Oldest iOS you support | Oldest Android API you support |
| Edge | Small (SE) + large (Pro Max), one tablet | One low-end device, one foldable/tablet |
How to choose
- Start from your analytics — real device/OS distribution.
- Cover min + current OS, plus the most popular version in between.
- Span smallest and largest screens you support.
- Include at least one low-end device for performance.
- Refresh quarterly — the market moves.
Common mistakes
- Testing only the newest flagship the team owns.
- Ignoring the minimum supported OS (where deprecations bite).
- No low-end device, so jank and OOM crashes ship.
- Emulators/simulators only — they miss real GPU, sensors, and network behaviour.
- A static matrix that's never refreshed against current usage.
// Related resources