Device Fragmentation

A banking app passes every test on the team’s three test phones: a new iPhone, a new Pixel and a new Galaxy. Two days after release, support tickets pile up: “The Confirm button is missing on my phone.” “The app crashes when I open my statements.” “I never get the payment notification.”

All three complaints come from devices the team never tested: an iPhone SE with its short screen, a cheap Android phone with 2 GB of RAM, and a Xiaomi phone whose battery saver freezes apps in the background. That’s device fragmentation, and it’s one of the main reasons mobile testing is harder than it looks.

What is fragmentation?

FragmentationFragmentationThe huge variety of device models, screen sizes and OS versions an app must support.Open in glossary → means your app runs on a huge variety of devices that differ in many ways at once:

Dimension	Examples	Why it matters
Screen size & shape	4.7″ iPhone SE, 6.7″ phones, tablets, foldables, notches and punch-holes	Layouts overflow, get cut off or look stretched
Pixel density	160 to 640+ dpi on Android, @2x and @3x on iPhone	Blurry images, wrong sizes if the app uses pixels instead of dp/pt
OS version	iOS 17–26, Android 11–16 at the same time	Different permissions, APIs and behaviors
Manufacturer skin	Samsung One UI, Xiaomi HyperOS, OPPO ColorOS, stock Pixel	Different fonts, settings, battery savers, sharing and permission screens
Hardware power	2 GB to 16 GB RAM, budget vs flagship chips	Slow screens, memory crashes, the app killed in the background
Form factor	Phones, tablets, foldables (folded and unfolded), Chromebooks	Layout must adapt when the screen changes size at runtime
Other hardware	Cameras, sensors, NFC, fingerprint vs face unlock	Features that only fail on some devices
User settings	Font size, display size, dark mode, language, battery saver	The same phone behaves differently for different people

Android has tens of thousands of device models from hundreds of makers. Apple only sells a few dozen iPhone and iPad models, but even there you still have small and large screens, older and newer iOS versions, and iPad multitasking.

Why it matters

• Your users don’t own your test phones. Teams usually test on new, expensive devices. Many users have older, cheaper or smaller ones.
• Device-specific bugs are hard to reproduce. “It works on my phone” is the start of the conversation, not the end. Without the device details, developers can’t fix the bug.
• Bad reviews are public. An app that crashes on a popular budget phone gets one-star reviews from all of its owners.
• You can’t test everything. That’s the real lesson: you need a smart, small set of devices that represents your users. It’s a form of compatibility testingCompatibility testingChecking the product works across different devices, OS versions, browsers and screen sizes.Open in glossary →.

How teams choose a device matrix

A device matrix is the list of devices (and OS versions) you test on. Here’s how good teams build one:

A typical starter matrix looks like this:

Slot	Example	Covers
Newest iPhone	The latest iPhone on the latest iOS	New iOS behaviors
Oldest supported iPhone	iPhone XR on iOS 17	Old iOS, older hardware
Small iPhone	iPhone SE	Short 4.7″ screen
Popular Samsung	Galaxy A-series	Biggest share, One UI
Low-end Android	2–3 GB RAM phone on an older Android	Performance, memory, old OS
Other maker	Xiaomi or OPPO	Aggressive battery savers, different skin
Stock Android	Pixel on the latest Android	Newest Android features first
Large screen	Foldable or tablet	Adaptive layouts, resizing

Build your device matrix

Now it’s your turn. Pick devices from the (example) analytics below. Try to cover the risks without blowing the time budget.

🧩 Build your device matrix

You test a food-delivery app. Analytics show these models (example data). Pick the devices for your regression run and watch the feedback.

Suggest a matrix Clear

DeviceScreenRAMUsers

• Samsung Galaxy A15Android 14 · One UI · 6.5″ · 4 GB6.5″384×8544 GB11%
• ✓iPhone 16iOS 26 · 6.1″ · 8 GB6.1″393×8528 GB9%
• ✓Samsung Galaxy S24Android 16 · One UI · 6.2″ · 8 GB6.2″384×8328 GB8%
• iPhone 13iOS 18 · 6.1″ · 4 GB6.1″390×8444 GB7%
• Xiaomi Redmi Note 13Android 14 · HyperOS · 6.67″ · 6 GB6.67″393×8736 GB7%
• Samsung Galaxy A12Android 11 · One UI · 6.5″ · 3 GB6.5″360×8003 GB5%
• iPhone 15 Pro MaxiOS 26 · 6.7″ · 8 GB6.7″430×9328 GB5%
• Google Pixel 8Android 16 · Pixel (stock) · 6.2″ · 8 GB6.2″412×9158 GB4%
• iPhone SE (3rd gen)iOS 26 · 4.7″ · 4 GB4.7″375×6674 GB4%
• Moto E13Android 13 · Android Go · 6.5″ · 2 GB6.5″360×8002 GB3%
• iPad (10th gen)iPadOS 26 · 10.9″ · 4 GB10.9″820×11804 GB3%
• iPhone XRiOS 17 · 6.1″ · 3 GB6.1″414×8963 GB2%
• Galaxy Tab A9Android 15 · One UI · 8.7″ · 4 GB8.7″600×9604 GB2%
• Galaxy Z Fold6 (unfolded)Android 16 · One UI · 7.6″ · 12 GB7.6″673×84112 GB1%

Screen sizes are approximate logical sizes (pt on iOS, dp on Android). The remaining 29% of users are spread over hundreds of other models.

Users

17%

Devices

2

Time

1.2 h

One regression pass takes about 35 min per device. Your team has 6 h per release.

OS range

iOS: 26 – 26 (supported 17–26)

Android: 16 – 16 (supported 11–16)

Coverage checks 2/8

• Both platforms
• Oldest supported OS (iOS 17, Android 11)Old OS versions are where crashes and missing APIs hide. Add the iPhone XR and the Galaxy A12.
• Newest OS (iOS 26, Android 16)
• A small screenSmall or short screens (iPhone SE, 360 dp Androids) are where buttons get cut off.
• A low-end device (≤ 3 GB RAM)Cheap phones expose slow screens, memory crashes and the app being killed in the background.
• A tablet or foldableLarge and changing screens break stretched images and fixed layouts.
• More than one Android manufacturerSamsung, Xiaomi and Google phones behave differently (battery savers, fonts, permissions).
• At least 45% of users on these exact modelsStart from your analytics: the most popular models give the most value per device.

Screen sizes, to scale

Galaxy S24

iPhone 16

Real devices, emulators and cloud device farms

You have three ways to get a device in front of you. Good teams mix all three. (For a deeper look at the first option, see Simulators and emulators.)

	Emulators & simulators	Real devices	Cloud device farms
What it is	Software on your computer: Android emulatorEmulatorSoftware that imitates a real device's hardware and OS on your computer, like the Android Emulator.Open in glossary →, Xcode iOS simulatorSimulatorSoftware that imitates a device's behavior on your computer, like Apple's iOS Simulator.Open in glossary →	Physical phones on your desk	Real (and virtual) devices in a data center, used over the internet
Good for	Fast checks, many OS versions and screen sizes, early development	Real performance, camera, sensors, gestures, push, battery, OEM skins	Many models you don’t own, automated runs at scale
Weak at	Performance, real hardware, OEM skins (emulators run stock Android)	Cost, maintenance, limited number of models	Latency, cost per minute, some hardware (e.g. NFC) is hard to test remotely
Cost	Free	Buying and replacing phones	Subscription or per-minute pricing

Popular cloud options:

• BrowserStack gives you real iOS and Android devices in the browser. App Live is for manual, interactive testing; App Automate runs automated test scripts.
• Firebase Test Lab (Google) runs automated tests on physical and virtual devices: instrumentation tests and the automatic Robo crawler for Android, and XCTest for iOS. You get videos, screenshots and logs, but it isn’t meant for manual tapping.
• AWS Device Farm offers real Android and iOS devices for both automated test runs and remote access sessions where you interact with a device manually.

Bugs that only happen on some devices

#	Bug	What you see	Typical severity
1	Content cut off on small screens	The main button is below the screen edge and the screen doesn’t scroll	High
2	Overlap with large fonts	Text runs under prices, icons or other text at 130–200% font size	Medium
3	Stretched or blurry images	Photos distorted on tablets and unfolded foldables, blurry on high-density screens	Low–Medium
4	Layout breaks on fold/unfold (see Orientation and screen sizes)	The screen resets, loses input, or keeps the phone layout on the big screen	Medium–High
5	Low-memory crashesCrashWhen an app suddenly closes or stops working because of an unhandled error.Open in glossary →	App crashes on 2–3 GB phones when loading images, maps or the camera	High
6	Background work killed by OEM battery savers	No notifications, stale order status, uploads stop (Xiaomi, OPPO, Samsung “sleeping apps”)	High
7	Camera differences	Wrong orientation, black preview or crash when scanning a card on some models	High
8	Notch / cutout overlap	Header or buttons hidden behind the camera cutout; see safe areaSafe areaThe part of the screen not covered by the notch, Dynamic Island, rounded corners or home indicator.Open in glossary →	Medium
9	OS-version-only bugs	A feature works on Android 15 but crashes on Android 11 (missing API)	High
10	OEM font or setting differences	A maker’s system font is wider, so labels truncate only on that brand	Low–Medium

Find the bug

This food-delivery product screen looks fine on the default iPhone 16. But it has five bugs that only appear on certain devices or settings. Switch device profiles, change the font size, tap around, and lock the phone for ten minutes to see what happens to the order status.

🐞 Bug hunt: Device profile lab

This demo has 5 hidden bugs. Explore it like a tester, then check your findings.

Found0/5

9:41

Pizza Place

Order #4821 · Preparingjust now

Margherita pizza, wood-fired with extra basil

€18.90

San Marzano tomatoes, fior di latte, fresh basil and olive oil.

SML

Extras

Extra basil+€0.50Extra mozzarella+€1.50Chili oil+€0.80 See all photos (24)Add to order · €18.90

Device profile

Restart app

DeviceiPhone 16 · 393×852 ptiPhone SE (3rd gen) · 375×667 ptPixel 8 · 412×915 dpMoto E13 · 360×800 dp · 2 GB RAMXiaomi Redmi Note 13 · HyperOSGalaxy Z Fold · unfolded · ≈673×841 dpiPad (10th gen) · 820×1180 pt

Font size (system setting)

100%130%200%

Lock phone for 10 minutes

Apple · 8 GB RAM · shown at 63% scale

1. 1

   Hint: Switch to the iPhone SE.

   Small screen: the "Add to order" button is cut off

   On the short 667 pt screen the button sits below the bottom edge, and the screen doesn’t scroll, so users can’t order at all. The content area uses a fixed height with clipping instead of scrolling. It gets worse with larger fonts on other phones too. Expected: the screen scrolls, or the main button is pinned to the bottom.

   Reveal answer✓ I found this
2. 2

   Hint: Set the font size to 200% on any device.

   Large font: product name overlaps the description

   The name area has a fixed height that fits two lines at the default text size. With bigger text the name needs more lines and spills over the description below, so both become unreadable. Expected: text containers grow with the content at every font size.

   Reveal answer✓ I found this
3. 3

   Hint: Pick the unfolded Galaxy Z Fold or the iPad.

   Foldable / tablet: the photo is stretched

   The round pizza becomes a wide oval. The image has a fixed height and stretches to the full width without keeping its aspect ratio. Expected: the image keeps its proportions (crop or letterbox), and large screens get a layout made for them.

   Reveal answer✓ I found this
4. 4

   Hint: On the Moto E13 (2 GB RAM), open the photos.

   Low-end device: "See all photos" crashes the app

   The app shows “FoodNow keeps stopping” and restarts, losing the selected size and extras. It loads all 24 full-size images at once, which runs out of memory on a 2 GB phone. The same tap works on every other device. Expected: images load as small thumbnails and the gallery works on the lowest supported device.

   Reveal answer✓ I found this
5. 5

   Hint: Lock the phone for 10 minutes on the Xiaomi, then compare with the Pixel.

   Xiaomi: no order notification and a stale status after locking

   On other phones a “Your rider picked up your order” notification arrives and the status changes to On the way. On the Xiaomi profile nothing arrives and the status stays Preparing · 10 min ago, because HyperOS’s battery saver froze the app in the background. Expected: status updates arrive via push notifications, and the app refreshes when it returns to the foreground.

   Reveal answer✓ I found this

Tools and how-to

AndroidiOSCloud

• Android Studio › Device Manager: create virtual devices for different screen sizes, densities and Android versions, including foldable, tablet and Resizable profiles.
• Change size and density on a real phone with adbadbAndroid Debug Bridge: a command-line tool for installing apps, reading logs and controlling Android devices.Open in glossary →: adb shell wm size 720x1280 and adb shell wm density 320. Undo with adb shell wm size reset and adb shell wm density reset.
• Font and display size: Settings › Display. Combine the largest font with the largest display size for the worst case.
• Low memory: test on a real low-end phone. In Developer options, Don’t keep activities helps you find state-loss bugs.
• Battery savers: keep the maker’s default battery settings, lock the phone for a while, and watch for missing notifications.

• Xcode Simulator: install simulators for the smallest (iPhone SE) and largest iPhones and an iPad. Add older iOS runtimes in Xcode › Settings › Components.
• Larger Text: Settings › Accessibility › Display & Text Size › Larger Text, with Larger Accessibility Sizes turned on.
• Display Zoom: Settings › Display & Brightness › Display Zoom makes the UI bigger, similar to a smaller screen.
• Real devices: keep at least one old, supported iPhone around. The simulator won’t show real memory limits or performance.

• BrowserStack App Live: upload your build (or install from TestFlight / Play), pick a real device and test manually in the browser.
• Firebase Test Lab: upload an APK/AAB and run a Robo test across a list of devices to catch crashes and layout issues automatically; or run your team’s instrumentation or XCTest suites.
• AWS Device Farm: run automated tests across a device pool, or start a remote access session to use a real device manually.
• Always record the exact device model and OS version from the farm in your bug report.

Example test cases

Checklist

Device fragmentation checklist

0 of 13 checked

Copy

• The device matrix is based on real analytics or market data, and reviewed regularly
• The matrix covers both the oldest supported and the newest OS on iOS and Android
• At least one small screen (iPhone SE or 360 dp Android) is in the matrix
• At least one low-end Android (2–3 GB RAM) is in the matrix
• A tablet or foldable is tested if the app supports large screens
• More than one Android manufacturer is covered (Samsung plus another skin)
• Main buttons are reachable on short screens; every screen can scroll when needed
• No text clipping or overlap at the largest font and display size
• Images keep their proportions on wide screens and look sharp on high-density screens
• Fold/unfold and rotation keep the user’s input and adapt the layout
• Background features (notifications, tracking, uploads) work with OEM battery savers on default settings
• Important bugs are confirmed on a real device, not only an emulator or simulator
• Every device bug report includes model, OS version, font/display settings and app build

Check your understanding

Quick quiz

0/5 answered · 0 correct

1. 1.What is device fragmentation?

   AWhen an app crashes into piecesBThe wide variety of devices, screens, OS versions and manufacturer skins an app must supportCSplitting a release into phasesDA bug in the device storage

2. 2.You can test on only six devices. Which set is the BEST choice?

   ASix of the newest flagship phonesBSix iPhones, because iOS users spend moreCNewest iPhone, small iPhone, popular Samsung, low-end Android, another Android maker, and a foldable or tabletDSix emulators with the same Android version

3. 3.Order notifications never arrive on a Xiaomi phone but work on a Pixel. What is a likely cause?

   AXiaomi phones cannot show notificationsBThe manufacturer’s battery saver stopped the app in the backgroundCThe Pixel has a bigger screenDDark mode is on

4. 4.Which statement about Firebase Test Lab is TRUE?

   AIt is only for iOSBIt runs automated tests (like Robo or instrumentation tests) on devices in Google’s data centersCIt replaces the need for any real deviceDIt is a manual testing app you install on your phone

5. 5.Why should important bugs be confirmed on a real device?

   AEmulators are illegal for testingBReal devices have real performance, memory limits, hardware and manufacturer skins that emulators and simulators don’t reproduceCReal devices are always fasterDBug trackers only accept real-device bugs

Key takeaways

• Fragmentation = many screen sizes, densities, OS versions, manufacturer skins, hardware levels and form factors at once.
• You can’t test every device. Build a device matrix from analytics: popular models plus the extremes (small screen, low-end, oldest and newest OS, another maker, tablet or foldable).
• Mix tools: emulators and simulators for speed, real devices for truth, and cloud device farms (BrowserStack, Firebase Test Lab, AWS Device Farm) for reach.
• Classic device-only bugs: cut-off buttons on small screens, overlap with large fonts, stretched images on big screens, low-memory crashes, and background work killed by battery savers.
• Every device bug report needs the model, OS version, settings and build. Without them, nobody can reproduce it.