Cross-device testing

tldr: Cross-device testing verifies your app works across phones, tablets, foldables, and wearables. Real device coverage is essential, but you do not need a 30-device lab. Focused selection plus cloud device farms covers most teams.


Why emulators are not enough

Emulators are great for early development. They miss:

  • Real performance characteristics (CPU, GPU, memory pressure).
  • Real network conditions (cellular, varying signal).
  • Hardware-specific bugs (camera, GPS, biometrics).
  • Manufacturer-specific OS variations (Samsung's One UI, Xiaomi's MIUI).

For final-stage testing, real devices are not optional.


How to pick devices

Three criteria.

Market share. Cover the top devices used by your real users. Check your analytics.

OS version coverage. Latest, latest-1, and the oldest version you support.

Form factor diversity. Small phone, large phone, tablet, foldable. Each has layout implications.

A pragmatic starter set: 5 to 8 devices covering the above. Expand based on the bugs you find.


Cloud device farms

For teams without a device lab, cloud farms provide real devices on demand.

Major options:

  • BrowserStack App Live and App Automate.
  • Sauce Labs Real Device Cloud.
  • AWS Device Farm.
  • Firebase Test Lab.
  • Kobiton.

All provide programmatic access for automated tests, plus interactive sessions for manual testing.


Foldables and unusual form factors

Foldables (Samsung Galaxy Z Fold, Pixel Fold) introduce new testing concerns.

  • App should handle fold/unfold transitions cleanly.
  • Layout should work in both folded and unfolded states.
  • Multi-window scenarios on the unfolded screen.

Most apps fail one of these. Test explicitly if you support foldables.

Wearables (Apple Watch, Wear OS) are nearly a separate platform. Test only if you ship to them.


Web vs native cross-device

For web apps, "cross-device" usually means viewport size, browser, and touch vs mouse. Real device coverage is less critical than for native.

For native apps, real devices matter for everything from layout to performance to specific OS APIs.


How AI testing fits

Bug0 handles cross-browser and viewport coverage for web apps natively: same flow, different viewports, run in parallel. For native mobile, pair with platform-specific testing tools and cloud device farms.


FAQs

How many devices do I need?

5 to 8 is enough for most teams. More if you serve developing markets with high device fragmentation.

Should I buy real devices or use cloud farms?

Buy a small set for daily development. Cloud farms for CI and broader coverage.

How often should cross-device tests run?

Critical paths on every PR. Full device matrix nightly or pre-release.

How does Bug0 handle cross-device testing?

Bug0 runs web tests across browsers and viewports automatically. For native, integrate with mobile-specific tools.

Ship every deploy with confidence.

Bug0 gives you a dedicated AI QA engineer that tests every critical flow, on every PR, with zero test code to maintain. 200+ engineering teams already made the switch.

From $2,500/mo. Full coverage in 7 days.

Go on vacation. Bug0 never sleeps. - Your AI QA engineer runs 24/7

Go on vacation.
Bug0 never sleeps.

Your AI QA engineer runs 24/7 — on every commit, every deploy, every schedule. Full coverage while you're off the grid.