For a decade, a phone app on a tablet was allowed to look like a phone app: a narrow column with black bars on both sides. Google has ended that arrangement, and the reason is money.
The Audience Moved
Google's May 2026 update counts "over 580 million large screen devices in the hands of users" and reports that "multi-device users spend 9x more on average than phone only users." Its developer guidance says Play "ranks apps and games optimized for large screens higher than unoptimized apps," and that apps below the bar "display a warning on the app details page" (Google). An app that ignores large screens is choosing lower placement, a warning label, and less of its highest-spending cohort.
The Platform Stopped Asking
Android 16 made the shift mandatory on a schedule. For apps targeting API level 36, "orientation, resizability, and aspect ratio restrictions no longer apply on displays with smallest width >= 600dp" (Android 16 behavior changes). A temporary opt-out exists, and Google has published its end: Android 17 removes it, and Play will require API level 37 "in August 2027" (Google, February 2026). That is the whole runway.
What the Work Actually Is
The expensive mistake is to treat this as a bespoke tablet redesign. Google has already packaged the answer into three canonical layouts (list-detail, supporting pane and feed), and most app screens are one of them. The engineering discipline is to size layouts by available window space rather than by device type, because a foldable, a split-screen tablet and a desktop window all change the space without changing the device.
The quality bar is graded. Google's large-screen tiers start at "Adaptive ready", where the app "runs full screen (or full window in multi-window mode) on all devices, but app layout might not be ideal," and rise to layouts designed for each device class.
A Portfolio Decision
For product leaders, the sequence matters more than the ambition: remove the orientation locks, adopt adaptive navigation, move the most-used flow to list-detail, and make sure user state survives a fold or resize. Google's own case study shows the upside: FlipaClip "saw 54% growth in tablet users in the four months after they optimized their app to be adaptive" (Google).
-Rocky
#AdaptiveApps #Android16 #ProductStrategy #EngineeringDreams #StrategiaX
Originally published on ANDROID-ARCHITECT, the Android engineering blog of Strategia-X.