Phone-only Android app broken on tablets and foldables?
Short answer: Many business apps were built for phones held upright, with the manifest locking them to portrait or a fixed aspect ratio. When an app targets Android 16, Android ignores those restrictions on tablets, the inner screens of large foldables and desktop-style windows, so the app is shown full-screen and resizable whatever the manifest says. Layouts designed for a narrow phone can end up stretched, with giant buttons, lines of text running across the whole screen, or state lost on rotation. The lasting fix is to adapt layouts to the available window size; a temporary opt-out exists while you do.
What changed in Android 16
Android's documentation explains that Android 16 (API level 36) overrides app restrictions for screen orientation, aspect ratio and resizability on devices whose smallest width is 600dp or more. That covers tablets, the inner displays of large foldables, and desktop windowing on any form factor. On those displays, apps targeting API level 36 are resizable and can enter multi-window mode.
The documentation lists what's ignored there, including portrait and landscape values of screenOrientation, resizeableActivity, minAspectRatio, maxAspectRatio and orientation requests from code. Its own illustration shows an app that used to be letterboxed, with black bars at the sides, now running full screen.
Phones aren't affected. The documented exceptions include displays smaller than 600dp (most phones, flip phones and foldables' outer screens), games identified through the app category flag, and cases where the user has chosen the app's default behaviour in the device's aspect ratio settings.
Why "it looked fine before" stops being true
Before, a portrait-only app on a tablet appeared in a phone-shaped window. It wasn't pretty, but the layout held. Now the same screens fill a wide window, and common problems appear:
- buttons and form fields stretched across the screen,
- text lines too long to read comfortably,
- images scaled up and blurry,
- bottom navigation spread so widely it's hard to use,
- forms or checkout flows losing what was entered when the device rotates or folds.
The last one is the most damaging for a business app, because it loses orders and bookings.
The temporary opt-out
Android documents an opt-out: declare android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY as a property on a specific activity, or on the whole application. It restores the old behaviour while you work on proper layouts. Treat it as breathing room, not a solution, and check Android's documentation for how long it remains available in later releases.
Adapt layouts to window size, not device type
Android's guidance is to use window size classes: breakpoints that group the space available to your app into compact, medium, expanded, large and extra-large widths, with height classified separately. The width breakpoints are 600dp, 840dp, 1200dp and 1600dp.
The documentation stresses that size classes are explicitly not determined by the physical device, and aren't meant for "is this a tablet?" logic. A tablet in split-screen may give your app a compact width; a foldable may change size class when opened. Base layout decisions on the current window size.
Practical changes for typical business apps:
- Constrain content width. Centre forms and reading content with a maximum width instead of letting them stretch.
- Use two panes where it helps. A list of orders or appointments on the left with details on the right works well at expanded widths.
- Adapt navigation. A bottom bar on compact widths can become a navigation rail on wider windows.
- Use grids for catalogues. Product or menu items can show in more columns as width grows.
- Provide suitable image sizes so photos stay sharp.
Don't lose state on resize
When a window changes size, folds, unfolds or rotates, Android may recreate the screen. Make sure form input, scroll position and checkout progress survive that change by keeping state in the right place rather than only in view objects. Test this specifically on the screens where people type or pay. A customer who unfolds their phone halfway through a booking should still see what they entered, not a blank form and a reason to give up.
Testing without a drawer full of devices
Use Android Studio's emulators for tablets, foldables and resizable windows, and try split-screen mode. Check each key flow: sign-in, browsing, booking or ordering, payment and account settings. Rotate and resize in the middle of each flow. If you can, test on at least one real tablet or foldable your customers use, and ask a few regular customers who own one to try a test build before release.
Check the rest of the experience
Large screens also change smaller details. Check that dialogs and bottom sheets don't stretch edge to edge, that keyboard and mouse input work on tablets used with a keyboard, and that screenshots in your store listing show the improved layouts once they're ready.
Planning the work
- Turn on the opt-out if large-screen layouts are badly broken today.
- List screens by importance and fix the critical flows first.
- Introduce window size classes and a maximum content width across the app.
- Add two-pane layouts where they clearly help.
- Remove the opt-out once the main flows work well.
An illustrative example
A dry-cleaning business in Chicago has a pickup-booking app designed only for phones. After an update targeting Android 16, customers with tablets report a stretched booking form and lost details when the screen rotates. The developer adds the opt-out to buy time, then constrains the booking form's width, switches the order history to a list-detail layout at expanded widths, and fixes state handling so the booking survives rotation. The opt-out is removed in the following release.
FAQ
Does this affect my app if I don't target Android 16?
These overrides apply to apps targeting API level 36. Google Play's target requirements mean most apps will get there.
Will phone users notice any change?
No. Displays below 600dp smallest width are excluded.
Can I just keep portrait mode on tablets?
Only temporarily, through the documented opt-out.
Is this only about tablets?
No. Large foldables and desktop windowing are included too.
If your Android app needs to work properly on tablets and foldables, tell us which screens matter most.