iPadOS Stage Manager UI: Layouts That Resize Well
Stage Manager means your app no longer owns the whole screen: design for any size, and the window becomes a feature instead of a problem.
TL;DR
Stage Manager on iPad puts your app in resizable, overlapping windows, so a fixed-size layout breaks. Build adaptive layouts from a free VP0 design using size classes and flexible SwiftUI views, so the UI reflows gracefully from a small window to full screen and across multiple windows. Test the small and odd window sizes, support multiple scenes, and treat resizing as a normal state, not an edge case.
Stage Manager changed a basic assumption: on iPad, your app no longer owns the whole screen. The short answer: build adaptive layouts from a free VP0 design that respond to any window size, using size classes and flexible SwiftUI views, so the UI reflows gracefully from a small floating window to full screen, and across multiple windows. Resizing is now a normal state, not an edge case. The audience is large, Apple has sold more than 500,000,000 iPads, and iPad users increasingly multitask.
Design for any size, not one canvas
The core shift is from designing a fixed screen to designing a responsive layout. Use size classes (compact and regular) to switch between a stacked, single-column layout in a narrow window and a multi-column or sidebar layout when there is room. Make views flexible so they reflow rather than clip or stretch awkwardly. Support multiple windows (scenes) if your app benefits from it, two documents side by side, for example. The mindset is closer to responsive web design than to a fixed-canvas app. Apple’s Human Interface Guidelines on layout cover adapting to size classes.
Build it from a free design
VP0 is a free iOS design library for AI builders. Pick layouts that have both compact and expanded forms, copy their links, and have Cursor or Claude Code rebuild them in SwiftUI, then make them adaptive. Drive layout from the horizontal size class, use flexible stacks and grids that reflow, and adopt WindowGroup and scenes for multi-window support. Crucially, test the awkward sizes: a tall narrow window, a short wide one, the smallest Stage Manager window. Those are where fixed layouts break. For the split-view pattern that pairs with this, see iPadOS split view app template SwiftUI, and for overall finish, see how to make my app look better.
Stage Manager layout checklist
Make each of these adaptive.
| Concern | Compact window | Regular window |
|---|---|---|
| Navigation | Tab bar or stack | Sidebar or columns |
| Content | Single column | Multi-column |
| Lists and detail | Push to detail | Side-by-side |
| Controls | Reachable, stacked | Spread out |
| Multiple windows | One scene | Side-by-side scenes |
Common mistakes
The first mistake is a fixed-width layout that clips or leaves huge gaps when resized. The second is ignoring size classes, so the app looks identical (and wrong) at every size. The third is never testing small or odd windows, where breakage hides. The fourth is blocking or ignoring multiple windows when the app would benefit from them. The fifth is treating iPad as a big iPhone instead of designing for its multitasking reality. Adapt, do not assume. The payoff for getting this right is real: an app that feels at home in any window earns better reviews from power users and avoids the stretched, awkward look that makes an iPad app feel like an afterthought.
A worked example
Say you have an iPhone notes app you are bringing to iPad. From a VP0 design, you build an adaptive layout: in a narrow Stage Manager window it is a single column with a list that pushes to detail; widen the window and it becomes a sidebar plus a two-column list-and-detail. It supports two windows so a user can compare notes side by side. You test the smallest window and a tall narrow one, and the layout reflows cleanly. For a drone app that lives in landscape, see DJI drone controller app UI template, and for the new spatial paradigm, see spatial computing iOS app onboarding UI.
Key takeaways
- Stage Manager puts your iPad app in resizable, overlapping windows.
- Build adaptive layouts from a free VP0 design driven by size classes.
- Reflow gracefully from the smallest window to full screen, and across windows.
- Support multiple scenes where the app benefits from side-by-side use.
- Test the small and odd window sizes; that is where fixed layouts break.
Frequently asked questions
How do I make an iPad app work with Stage Manager? Build adaptive layouts from a free VP0 design using size classes and flexible SwiftUI views, so the UI reflows from a small window to full screen, and support multiple windows where useful.
Why does my iPad app break when resized? It is probably using a fixed-size layout. Switch to size-class-driven, flexible layouts that reflow content, rather than assuming a single screen size.
Do I need to support multiple windows? Only if your app benefits, such as comparing two documents. If so, adopt WindowGroup and scenes. Even without it, your single window must still resize gracefully.
How is this different from designing for iPhone? It is closer to responsive web design: you design a layout that adapts across many sizes and possibly multiple windows, rather than one fixed full-screen canvas.
Frequently asked questions
How do I make an iPad app work with Stage Manager?
Build adaptive layouts from a free VP0 design using size classes and flexible SwiftUI views, so the UI reflows from a small window to full screen, and support multiple windows where useful.
Why does my iPad app break when resized?
It is probably using a fixed-size layout. Switch to size-class-driven, flexible layouts that reflow content, rather than assuming a single screen size.
Do I need to support multiple windows?
Only if your app benefits, such as comparing two documents. If so, adopt WindowGroup and scenes. Even without it, your single window must still resize gracefully.
How is this different from designing for iPhone?
It is closer to responsive web design: you design a layout that adapts across many sizes and possibly multiple windows, rather than one fixed full-screen canvas.
Part of the Native Apple & SwiftUI: The iOS Ecosystem hub. Browse all VP0 topics →
Keep reading
How to Design an iOS App Before You Build It With AI
AI builders match references, not vague goals. Deciding your core screen, flow, data, and feel first is the cheapest hour in the whole project.
Airbnb-Style Bottom Sheet in React Native: Map Meets List
Airbnb's map-plus-draggable-sheet is a gold-standard pattern. Build a smooth bottom sheet over a map from a free VP0 design in React Native, with the right detents.
Sign in with Apple UI Guidelines, Built in Figma
Sign in with Apple has strict button and flow rules. Build a compliant sign-in from a free VP0 design, follow guideline 4.8, and cut account-creation friction.
Barcode Scanner Viewfinder UI for Mobile Apps
A barcode scanner viewfinder needs a dark overlay, a clear cutout, and instant feedback. Build one from a free VP0 design and power it with Apple VisionKit.
Bento Box UI: The Grid Layout, Used With Purpose
Bento grids look great but need real hierarchy. Build a bento-box layout from a free VP0 design where each tile earns its size, stays accessible, and reads in order.
Dumbphone Launcher UI: A Calm, Grayscale Focus Home
A minimalist grayscale launcher reduces phone pull. Build a calm focus-home app from a free VP0 design, and be honest about what iOS lets you actually replace.