Thank you for the detailed explanation. It confirms that a multi-scene architecture is the correct direction. I have a follow-up question to make sure we’re approaching this correctly. We’re building a native iPadOS application that uses an M5 iPad with a 43” or 55” external monitor. Our goal is for the external monitor to become an interactive workspace while the iPad continues to display a separate control interface. We understand that iPadOS controls window placement and that an application cannot automatically force a window to open full-screen or at a specific location on the external display. Our question is about what happens after the interactive window has been created. Once the application’s interactive scene/window exists on the external display, can the application fully control the layout inside that window? For example, can we programmatically size and position our own views (such as a large custom rendering view with supporting panels around it) based on the available window size, without requiring the user to manually resize or arrange our application’s internal views? In other words, we’re not trying to control the OS-managed window itself. We only want complete control over the content and layout inside our application’s window. Also, is there a recommended WWDC session, sample project, or Apple sample code that demonstrates this type of professional multi-window, external-display application? Thank you again for your guidance.