Device fragmentation
Device fragmentation is the spread of a product's users across many combinations of device, operating system version, screen size, pixel density and hardware capability, such that no single configuration represents more than a small share of them. It is the reason a page that works on the team's own phones still fails for users, and it is what cross-device testing exists to cope with.
The longer version
Fragmentation has several axes at once. Manufacturers ship different screens, memory and processors; operating system versions stay in use for years after release because devices stop receiving updates; manufacturers modify the browser or the system web view; and the same operating system version runs on a flagship and on a budget device with a fraction of the memory. Each combination can change how a page lays out, how fast it runs and which web features exist. The user base is spread thinly across all of it, so the most common combination is still a minority.
Browser fragmentation is the neighbouring idea and is narrower: the spread across rendering engines and their versions, which cross-browser testing covers. Device fragmentation includes that and adds the hardware and the operating system, which decide performance, input and viewport. The two are often lumped together as compatibility, but the remedies differ. A browser gap is usually a missing feature with a known fallback; a device gap is often a page that is too heavy for the memory or too wide for the screen, and the fix is in the product, not a polyfill.
Teams underestimate it because their own devices are recent and fast. A page tested on current flagships ships, and support tickets arrive from a two-generation-old device with a system web view that lacks one API, or from a budget phone where the page is killed for memory. The reports name symptoms, not configurations, so the first job is finding out what device it was. The other failure is the opposite: attempting to support everything, which makes the matrix unrunnable and the supported claim meaningless.
The working answer is a supported set: a test matrix drawn from analytics that names the devices, operating system versions and viewports the product commits to, with a documented floor below which behaviour is best effort. Reports from outside the set are a signal to revisit the matrix rather than defects to fix one by one.
Common questions
What is the difference between device fragmentation and browser fragmentation?
Browser fragmentation is the spread across rendering engines and versions and is addressed by cross-browser testing and feature fallbacks. Device fragmentation adds hardware and operating system variation: screen sizes, pixel densities, memory, processor speed and system web views. A browser gap usually has a polyfill; a device gap usually means the page itself is too heavy or too wide.
Does device fragmentation affect web apps or only native apps?
Both are affected. A native app meets fragmentation through operating system versions and hardware directly. A web page meets it through the browser or system web view each device ships, which decides which web features exist, plus the screen size, pixel density and memory that decide how the page lays out and whether it survives. A page tested in one recent browser has not been tested against the fragmentation its users bring.
Why does a page work on the team's phones but fail for users?
The team's phones are usually recent, fast and updated, which places them in a small and unrepresentative corner of the user base. Users carry older operating system versions, budget hardware with less memory and manufacturer-modified browsers. A page that is heavy or assumes a recent API works in the office and fails on the devices most people hold.
How do teams deal with device fragmentation?
By bounding it rather than covering it: a supported set drawn from analytics, a documented floor below which behaviour is best effort, real devices in hand for the classes that carry most sessions, and emulators for the rest. Pages are built to degrade rather than to assume, so a missing API or a small screen removes a feature instead of breaking the page.
Is device fragmentation worse on Android than on iOS?
Android fragmentation is wider because many manufacturers ship their own hardware, screens and system web views, and operating system updates reach devices unevenly or never. iOS is narrower, with one manufacturer and updates that most devices take quickly, but it still varies by screen size, device generation and the operating system versions that older hardware is stuck on.
Bug reports that arrive ready to triage.
Collect replay, console, network and browser context with the Free plan.