Mobile App Compatibility Testing Across Devices

Testing Mobile App Compatibility Across Devices

A designer created a mockup for an iPhone 14 Pro with a 6.1'' screen and Dynamic Island. The developer tested on the same device. After release, it turned out that on the Samsung Galaxy A03 with a 720×1600 display, the "Confirm" button was cut off because the layout relied on safe areas that don't exist on older Samsung devices. On the iPad Mini, the bottom navigation took up a third of the screen—nobody tested the tablet. In our practice, such stories are common. We help identify issues before release: we build a device matrix, test on emulators, cloud farms, and physical devices, and deliver a report with recommendations. Contact us for a preliminary assessment of your project.

Devices are too diverse. There is no one-size-fits-all solution—only methodical testing. We conduct it using a combination of emulators, cloud farms (BrowserStack, Firebase Test Lab), and physical devices. This saves time and money by preventing costly bugs in production.

Why Devices Differ and How It Affects Your App

Devices differ not only in screen size. Here's what actually impacts app behavior.

Screen Resolution and Pixel Density

ldpi (120 dpi), mdpi (160), hdpi (240), xhdpi (320), xxhdpi (480), xxxhdpi (640). Icons without adapted variants for density look blurry or oversized. On a Redmi with 720p and a Samsung with 1080p, the same physical diagonal means different density, different dp→px conversions.

Aspect Ratio

The standard 16:9 (720×1280) is outdated. Current ratios: 20:9 (Samsung S-series), 19.5:9 (iPhone), 21:9 (Sony Xperia), and foldable devices with variable ratios. Layouts that hardcode element heights break on non-standard proportions.

Safe Area and Notches

Dynamic Island (iPhone 14 Pro+), notch-hole (Samsung), punch-hole camera (most modern Android). On Android, WindowInsets and displayCutout must be handled. Without cutout handling, content goes under the camera. Apple recommends following safe area insets Apple Human Interface Guidelines.

Hardware Performance

Qualcomm Snapdragon 8 Gen 3 in a flagship vs. MediaTek Helio G85 in a budget device—different performance levels. Animations at 120 fps smooth on flagships stutter on mid-range devices. Complex Compose layouts with multiple recompositions will suffer.

Hardware Features

No NFC, barometer, LiDAR, or Face ID. Without checking PackageManager.hasSystemFeature(), attempting to use missing hardware causes a crash or silent failure.

Our Approach to Compatibility Testing

We start by analyzing your target audience and device statistics, then build a test matrix. After that, we run checks on emulators, cloud farms, and physical devices. You receive a report with an incompatibility matrix, screenshots, and recommendations. Order testing today—we'll prepare a detailed test plan.

Device Matrix

We build the matrix based on analytics (Firebase, Mixpanel by device_model), general market statistics, and business requirements:

Minimum matrix for most projects: 5–7 devices. More can be tested via BrowserStack or Firebase Test Lab (real devices without purchasing). Testing on a cloud farm is 5x faster than buying and maintaining your own device park.

Testing Environment Comparison

What We Deliver

1. Target audience and device statistics analysis
2. Device matrix construction (5–7+ models)
3. Testing on emulators (Android Emulator, iOS Simulator)
4. Testing on cloud farm (BrowserStack, Firebase Test Lab)
5. Manual testing on physical devices (if needed)
6. Report with incompatibility matrix, screenshots, and recommendations
7. Consultation on fixing found issues

Testing Adaptive Layouts

On Android, use WindowSizeClass from Jetpack Compose:

val windowSizeClass = calculateWindowSizeClass(this) when (windowSizeClass.widthSizeClass) { WindowWidthSizeClass.Compact -> PhoneLayout() // < 600dp WindowWidthSizeClass.Medium -> TabletLayout() // 600–840dp WindowWidthSizeClass.Expanded -> DesktopLayout() // > 840dp } 

Test all three classes: Compact (phone portrait), Medium (tablet portrait or phone landscape), Expanded (tablet landscape).

On iOS, use horizontalSizeClass in SwiftUI:

@Environment(\.horizontalSizeClass) var sizeClass var body: some View { if sizeClass == .compact { VStack { ... } } else { HStack { ... } // iPad, landscape iPhone Plus } } 

Special Cases: Foldable Devices

Samsung Galaxy Z Fold has two modes: folded (compact, 22:9) and unfolded (large screen, ~4:3). The app must correctly transition between modes without losing state. onConfigurationChanged is called upon unfolding/folding. If the Activity is recreated, all unsaved form data is lost. We check: focus in TextField is preserved, scroll position is restored, modal dialogs do not "jump".

Checking Hardware Features

// Android: check before use val hasBluetooth = packageManager.hasSystemFeature(PackageManager.FEATURE_BLUETOOTH) val hasNfc = packageManager.hasSystemFeature(PackageManager.FEATURE_NFC) val hasCamera = packageManager.hasSystemFeature(PackageManager.FEATURE_CAMERA_ANY) 

If a feature is unavailable, we hide the UI element or show an explanation. No crashes, no disabled button.

Experience and Guarantees

Our team—certified engineers with 10+ years in mobile development. We have tested over 40 projects of varying complexity—from startups to enterprise solutions. We guarantee testing quality: you receive a comprehensive report with real problems and concrete fix solutions.

Timelines

2–3 days for device matrix construction based on analytics, testing on priority devices (emulators + cloud farm), and a report with an incompatibility matrix and screenshots. For expanded coverage (foldables, tablets, specific regions), the timeline extends to 5–7 days. Pricing is individual—contact us for a consultation to assess your project.