Mobile and Cross-Platform Testing
Users do not experience your application on a standardized viewport. They experience it on a cracked iPhone SE held sideways on a bus, a foldable Samsung in half-open mode, a ten-year-old Android tablet with a custom ROM, and a 4K desktop monitor. Your testing strategy must account for all of them.
Why Cross-Platform Testing Is a Data Problem
The "it works on my machine" fallacy is exponentially worse on mobile. With 24,000+ unique Android device models, 200+ common screen resolutions, and network conditions varying 100x between best and worst, exhaustive testing is impossible. The answer is not "test everything" -- it is "test the right things on the right devices."
This chapter covers how to build a data-driven device matrix, test responsive layouts and PWAs, automate native mobile testing with Appium, manage cross-browser complexity, and handle emerging platforms like voice interfaces and on-device ML.
Topics Covered
1. Device Strategy — 01-device-strategy/
- Fragmentation Reality — Understanding the scale of device fragmentation in 2026
- Device Coverage Matrix — Building a data-driven, tiered device selection strategy
2. Responsive and PWA Testing — 02-responsive-and-pwa/
- Responsive Testing — Viewport breakpoints, AI agent responsive testing, and layout stability
- PWA Testing — Service workers, offline behavior, push notifications, and install prompts
3. Native Mobile — 03-native-mobile/
- Appium Fundamentals — Architecture, test patterns, and AI-native evolution
- Cloud Device Farms — BrowserStack, Sauce Labs, AWS Device Farm, and Firebase Test Lab
4. Cross-Browser — 04-cross-browser/
- Browser Testing Strategy — Three-tier approach to cross-browser coverage
- What Varies Between Browsers — Where to focus cross-browser testing effort
5. Emerging Platforms — 05-emerging-platforms/
- Voice and Camera — Testing voice interfaces and camera-based features
- On-Device ML — Testing ML models running on mobile devices
- Mobile Accessibility — VoiceOver, TalkBack, touch targets, dynamic type, and interview talking points
Prerequisites
Familiarity with web testing fundamentals (Playwright or Cypress). For the native mobile sections, a basic understanding of iOS or Android development concepts is helpful but not required. Cloud device farm sections assume no prior experience with any specific vendor.