Ensuring Mobile App Compatibility with New Devices
After the release of a new iPhone model with a changed form factor and Dynamic Island, users started complaining: the status bar overlaps content, buttons go under the Home Indicator, the camera covers part of the interface. The app didn't break—it just didn't know about the new Safe Area insets. Our mobile development team, with 8 years of experience, regularly encounters such problems. Over 5 years, we have conducted compatibility audits for more than 100 mobile apps. We guarantee that after adaptation, the app will display correctly on any form factor.
What Breaks When a New Device Launches?
Safe Area and Dynamic Island. On iOS, Safe Area insets depend on the model. Hardcoded offsets—UIEdgeInsets(top: 44, left: 0, bottom: 34, right: 0)—are already incorrect for several iPhone generations. The right solution: use view.safeAreaInsets or safeAreaLayoutGuide in Auto Layout. In SwiftUI—.ignoresSafeArea() with explicit edge specification, not globally. For more details, see the Apple Human Interface Guidelines.
Display cutout on Android. Since Android 9, there's the DisplayCutout API. Devices with a camera cutout (Pixel, Samsung A-series, Xiaomi) require setting LAYOUT_IN_DISPLAY_CUTOUT_MODE_SHORT_EDGES. If the app uses NEVER, content will be clipped. All modes are described on Android Developers.
Changing aspect ratio. Modern flagships have aspect ratios of 19.5:9 and 20:9. If the layout is designed for 16:9 with fixed heights, black bars appear. On Android, test using <activity android:maxAspectRatio>—if not specified, the OS may enable letterbox.
Foldable and large screens. When unfolding a foldable device, the app receives a configuration change. If the Activity does not handle configChanges, it gets recreated with state loss. Jetpack WindowManager FoldingFeature allows adapting the layout.
| Problem | Cause | Solution |
|---|---|---|
| Content is overlapped by cutout | Hardcoded offsets | Use safeAreaLayoutGuide / view.safeAreaInsets |
| Black bars on 20:9 screens | Layout for 16:9 | Set maxAspectRatio and adaptive design |
| State loss when unfolding | Unhandled configChanges |
onConfigurationChanged or WindowManager |
Which Devices Are at Risk?
The greatest risks occur with the release of:
- iPhones with Dynamic Island (iOS 16+),
- Foldable smartphones (Samsung Galaxy Z Fold, Pixel Fold),
- Tablets and phablets (iPad Pro, Samsung Tab),
- Devices with non-standard aspect ratios (20:9, 21:9).
For each type, we have prepared a checklist of checks. For example, for foldable devices, it is necessary to check both portrait and landscape orientations, as well as folded and unfolded screen states.
| Device Type | Key Check | Release Frequency |
|---|---|---|
| iPhone with Dynamic Island | Safe Area insets for each edge | Annually |
| Foldable | State preservation during fold/unfold | 2-3 times a year |
| Android with cutout | DisplayCutout and layout with SHORT_EDGES |
Quarterly |
How We Do It
For example, in an Android project, we discovered that the Activity did not handle configChanges, causing the app to recreate with form data loss when unfolding a Galaxy Fold. We added FoldingFeature from Jetpack WindowManager and adapted the layout for both states. The result—stable operation on all foldable devices. Using Jetpack WindowManager is 2x faster and simpler than manual onConfigurationChanged handling.
The work process includes:
- Analysis of new devices and their specifics (safe area, cutout, foldable).
- Audit of current code: search for hardcoded offsets, frame-based layout, deprecated APIs.
- Fixing layout using modern constraints and system insets.
- Testing on simulators and real devices (Firebase Test Lab, BrowserStack).
- Regression testing of core functionality.
Example code for Safe Area on iOS
override func viewSafeAreaInsetsDidChange() { super.viewSafeAreaInsetsDidChange() // use actual insets let top = view.safeAreaInsets.top let bottom = view.safeAreaInsets.bottom // update layout } Quick Compatibility Check
Use a simulator of the new device (Xcode Simulator for iOS, Android Emulator with the appropriate AVD). For iOS, check traitCollection.horizontalSizeClass and verticalSizeClass. For Android—WindowMetricsCalculator.computeCurrentWindowMetrics(activity) instead of the deprecated Display.getSize(). Then run UI tests on a cloud service—this takes 1–2 hours. Comparison of approaches: simulator gives 70% reliability, real device—100%, but cloud service (Firebase Test Lab) covers 90% at a lower cost.
Why This Matters for Business
80% of negative reviews in the first days after a new device launch are related to display issues. User loss due to app malfunction can reach 15%. Timely adaptation not only preserves the audience but also boosts app store ratings. A preliminary audit can save up to 70% of the budget that would be needed for fixes after release.
What's Included in the Work
- Documentation with a list of changed files and rationale.
- Adaptation to the latest OS version and new APIs.
- Recommendations for supporting future devices.
- Access to test reports on a real device park (200+ devices).
- 30-day warranty on fixes.
Timelines and Cost
A compatibility audit for new devices and fixing critical bugs takes from 2 to 5 days, depending on code volume. If the app was originally written without Auto Layout / ConstraintLayout (legacy frame-based code), significant refactoring may be required. The cost is calculated individually.
Contact us for a consultation—our certified engineers will ensure correct operation on all modern devices. Order a compatibility audit to avoid losing users and negative reviews.