With thousands of unique Android device models on the market, relying on a single phone to test your app's UI is a recipe for disaster. The rise of foldable phones, expanding tablet adoption, and Chrome OS means your app layout must be truly adaptive.
If your app crashes or looks broken on a Samsung Galaxy Z Fold or a Pixel Tablet, users will simply uninstall it, tanking your metrics.
In this guide, we'll cover the essential strategies and tools you need to test your Android apps across various screen sizes and foldables effectively.
1. Master the Resizable Emulator in Android Studio
Before you even distribute your app to real testers, you should be catching layout bugs locally. The Resizable Emulator in Android Studio allows you to hot-swap between a standard phone, a foldable, a tablet, and a desktop layout without restarting the device.
What to test for:
- Do your layouts transition gracefully when the emulator is resized?
- Does your app correctly handle the
onConfigurationChangedevent? - Are you using Window Size Classes (Compact, Medium, Expanded) to drive your layout decisions rather than hardcoding pixel widths?
2. Testing Foldable Postures with Jetpack WindowManager
Foldable devices introduce entirely new states, known as "postures." A device could be flat, half-folded like a laptop (Tabletop posture), or held like a book (Book posture).
To test how your app responds to these physical changes, you need the Jetpack WindowManager library.
- Automated Testing: Use the
androidx.window:window-testingartifact. It includes theWindowLayoutInfoPublisherRule, which allows you to push fake folding features and postures to your UI tests without needing physical foldable hardware. - The Espresso Device API: You can use this API in your instrumented tests to simulate folding and unfolding, ensuring your app preserves state correctly during these complex configuration changes.
[!WARNING] One of the most common crashes on foldables occurs because developers fail to save UI state during the rapid configuration change that happens when a device is unfolded. Ensure you are using
ViewModelandsavedInstanceStatecorrectly!
3. Real-Device Testing is Non-Negotiable
While emulators and automated tests are great for catching obvious layout breaks, they cannot replicate the physical feel of interacting with a foldable or tablet.
How does the hinge feel when interacting with your UI? Is the thumb-reach comfortable on a 10-inch tablet? Does your app drain the battery excessively when using the larger inner screen of a foldable device? These are questions only real humans using real devices can answer.
Furthermore, Google Play explicitly requires a 14-day closed testing period with 20 real users for new personal developer accounts. If your app is aimed at a broad audience, your test pool must include diverse devices.
4. Get Access to a Fleet of Devices with 12-App Tester
Acquiring a test fleet of the latest foldables and tablets is incredibly expensive for indie developers and small studios.
Instead of buying a $1,800 foldable just for testing, you can use 12-App Tester.
Our platform connects you with a diverse pool of real Android users possessing a wide array of devices—from budget smartphones to the latest flagship foldables and tablets.
When you run a QA campaign with us, our testers will:
- Install your app on their actual physical devices.
- Test your layouts in different orientations and postures.
- Provide detailed screenshots and bug reports of any UI inconsistencies.
- Help you easily pass the Google Play 14-day testing requirement.
Don't let a poorly scaling UI lead to negative reviews. Read our guide on why your app might be rejected for more insights, and secure your device testing strategy with 12-App Tester today!