App Resizability and Multi-Window Support
Article Summary
Miguel Montemayor from Android drops a major compatibility requirement: the developer opt-out for resizability is gone in Android 17. If your app still assumes portrait-only or fixed aspect ratios, you've got work to do before August 2027.
Google is removing the safety net introduced in Android 16. Apps targeting API level 37 must support all orientations and window sizes on large screens (600dp+), with no manifest opt-outs allowed. This affects tablets, foldables, desktop windowing, and multi-window scenarios across the entire Android ecosystem.
Key Takeaways
- Manifest attributes like screenOrientation and resizeableActivity are ignored on large screens
- Camera preview issues are the most common failure mode when apps go adaptive
- CameraX and CameraViewfinder libraries handle orientation transformations automatically
- Stretched UI and inaccessible buttons plague apps that assumed fixed dimensions
- August 2027 deadline: Google Play requires API level 37 targeting for new apps
Android 17 mandates full resizability support for large screen devices with no developer opt-out, forcing apps to handle dynamic window sizes and orientations by August 2027.
About This Article
Apps targeting Android 17 often have camera preview issues on landscape foldables or in multi-window mode. The previews stretch, rotate unexpectedly, or get cropped because developers assume the camera sensor and device orientation always match up the same way.
Google recommends Jetpack CameraX's PreviewView, which handles sensor orientation, device rotation, and aspect ratio scaling automatically. If you're using Camera2, use CameraViewfinder instead. It works back to API level 21 and applies the necessary transformations without extra work.
Starting in August 2027, Google Play will require all new apps and updates to target API level 37. This makes adaptive resizability mandatory for distribution. The developer opt-out that existed in Android 16 will no longer be available.