Android 17 might finally fix the app problem holding Android tablets and foldabales back

Google says there are now more than 500 million active Android devices outside the slab phone category, including foldables, tablets, ChromeOS devices, cars, and AR glasses.

That kind of range only works if apps can properly adapt to different screen sizes and orientations. Otherwise, Android's hardware diversity remains a weakness.

Android 17 seems to be taking that problem more seriously . Large screens are now considered first-class, and the days of wasting pixel real estate with stretched-out phone UIs are finally numbered.

Tablet and foldable fans, huzzah. This is the milestone we've been waiting for.

Android 17 removes the escape hatch for fixed-size apps

Google asked nicely for a long time. It encouraged developers to build responsive layouts and published resources to help them get there. Up through Android 15, an app's manifest was still the final word.

If a developer set android:resizeableActivity="false"and android:screenOrientation="portrait", Android honored those flags and the app stayed locked in portrait mode.

Android 16 is the first move toward adaptive layouts. On screens wider than 600dpi, including tablets and foldables, the system can ignore those manifest flags and force apps to resize and adapt to the larger display.

Even so, Android 16 still gives developers an escape hatch through the temporary opt-out flag .

Android 17 is expected to go further. Responsive design is set to become a rule that developers won't be able to work around.

When an app targets API 37, the operating system overrides legacy manifest tags. The application must run in the full available window, whether the developer wrote the code to support it or not.

This rule is not universal. Apps categorized as android:appCategory="game"can still lock orientation if needed.

Android also keeps honoring user-set aspect ratios over system settings. On phones smaller than 600dp wide, behavior stays the same.

Google's 500 million device problem is an app problem

Google is finally drawing a line because the market has changed. We are not talking about a few niche products anymore.

Look at foldables like the Samsung Galaxy Z series or the Google Pixel 10 Pro Fold . Although still small, they are now part of the mainstream Android market.

You open an app on the smaller display, unfold the device, and expect it to continue naturally on the larger screen.

If it crashes or stays locked in place, the hardware stops feeling premium right away.

Android is also moving toward a more mature desktop-style experience.

Android 16 brought major desktop windowing work , and Android 17 continues that direction with Bubbles and desktop-mode refinements.

With the new Bubbles system , users can drag nearly any app into a floating window, place it on the taskbar, and use apps side by side.

You cannot build a desktop experience around apps that refuse to resize. An app locked in portrait mode turns into a dead weight in any multitasking setup.

Android 17 gives developers overdue homework

This mandate does not solve everything overnight. OS-level forced resizing is not the same thing as thoughtful UI design .

When Android 17 overrides a portrait lock and stretches an app never meant to render horizontally, it may look bizarre.

I'm talking about Buttons ballooning to comical sizes, text lines running endlessly from edge to edge, and other issues that degrade readability.

Independent developers often do a good job adapting. What concerns me more is corporate apps and legacy platforms. Those apps often run on old XML codebases that have been dragged down by years of technical debt.

Portrait lock was their safety net to avoid the harder work of managing the state correctly. All of this leaves devs with some overdue work.

Responsive design is now part of the job. Apps need to work in portrait and landscape, handle every size in between, use layouts that resize gracefully, and move away from hardcoded widths.

The next Android app problem is the long tail of legacy software

At this point, the hardware is not the problem anymore . The silicon is good enough. Now the software layer has to do its part and make that experience stable.

There is one caveat. API 37 only changes apps that are built for API 37. Abandoned apps sitting on the Play Store will still be boxed in and awkward on modern screens.

Android continues to honor their legacy status until Google's deprecation rules finally phase them out.

Apps that fail to keep up with target API requirements slowly lose their place in the store and then lose access to users on new Android releases.