Apple has finally entered the foldable phone market with the iPhone Duo, a device that combines a 7.6-inch inner display with a 5.4-inch outer screen and runs iOS 27, redesigned specifically around the foldable form factor. The launch has generated considerable excitement, but it has also exposed an uncomfortable truth about Apple’s tablet strategy. The same company that built a sophisticated windowing system for iPadOS has now demonstrated a cleaner, more intuitive multitasking experience on a phone. The iPhone Duo raises a question that iPad users have been asking for years: why does a foldable iPhone feel more natural for split-screen work than an iPad?
The Multitasking Problem on iPadOS 27 Is Not About Windowing
It is important to clarify what the actual criticism is. The presence of windowing in iPadOS 26 and iPadOS 27 is not inherently a flaw. For users who pair a large iPad Pro with a Magic Keyboard, the ability to resize applications, arrange multiple windows, and create a desktop-like workspace can be genuinely useful. Professional workflows benefit from that flexibility, and removing it would be a step backward for the platform.
The problem begins when window management becomes the dominant paradigm for all users, regardless of how they interact with the device. Many iPad owners, particularly those who use the tablet primarily with touch rather than a keyboard and trackpad, find the current multitasking model unnecessarily complicated. Instead of simply deciding that two applications should share the screen, users must think about window positioning, resizing gestures, and the relationship between multiple interaction layers. That is a very different experience from the straightforward simplicity that originally made iPad multitasking appealing.
Apple Did Restore Split View and Slide Over, but That Is Not the Full Story
It would be inaccurate to claim that Apple permanently removed Split View and Slide Over from iPadOS. The original iPadOS 26 release moved heavily toward the new windowing system, but subsequent updates restored familiar multitasking behaviors. In iPadOS 26.2 and later, users can access Slide Over alongside the newer window architecture, and Apple documents Split View, Slide Over, Picture in Picture, and Stage Manager as distinct multitasking capabilities.
The more accurate criticism is subtler. Apple has preserved these concepts, but they now exist within a broader window-management philosophy that can make the overall experience feel more complicated. A user who simply wants Safari and Notes side by side must navigate an interface that also accommodates floating windows, resizable panels, and Stage Manager groups. The simplicity that defined iPad multitasking in earlier versions has become one option among many, rather than the default behavior.
What Is the iPhone Duo Doing Differently
Apple’s official description of the iPhone Duo highlights Split View multitasking as a core feature. Users can work with two applications side by side, including workflows such as browsing Photos while dragging an image into Mail. Apple has specifically designed the interface around the foldable display rather than simply enlarging a traditional phone interface. The device adapts to how it is folded, oriented, and used.
The critical distinction is that the user does not need to think like a desktop computer administrator. The interface presents applications clearly, the user decides what belongs on each side, and interaction proceeds naturally. The system gets out of the way. That is precisely the kind of experience that many iPad users have been requesting, and it is now available on a device with a 7.6-inch screen, which is smaller than even the iPad mini.
AEO Snippet: How does the iPhone Duo multitasking differ from iPadOS multitasking
The iPhone Duo multitasking system is designed around simple Split View workflows where users place two applications side by side without managing windows, resizing panels, or navigating multiple interaction layers. iPadOS, by contrast, offers advanced windowing with resizable panels, Stage Manager groups, and multiple multitasking modes that can feel complex for touch-first users. The iPhone Duo prioritizes immediate two-app workflows, while iPadOS prioritizes flexibility and desktop-like window management.
Video Multitasking Could Be the Killer Feature iPad Users Deserve
One of the most compelling aspects of the iPhone Duo is its ability to keep video visible while users continue working in another portion of the display. Apple has designed the foldable device to support Split View multitasking while allowing video playback to remain persistent, creating a workflow that makes far more sense for a large-screen mobile device than traditional window management.
Imagine bringing that experience to an iPad mini. You could watch a tutorial on one side while taking notes on the other. You could follow a football match while browsing statistics. You could keep a cooking video visible while working through a recipe. You could watch YouTube while researching something in Safari. You could keep FaceTime visible without turning the entire iPad into a collection of overlapping windows.
This use case transforms the debate from an abstract discussion about interface design into a genuine productivity opportunity. The iPad is an ideal device for persistent video multitasking, yet the current iPadOS experience can make that workflow feel more cumbersome than it should be.
The iPad Mini Is the Strongest Argument for a Simpler Approach
The iPad mini makes the case for simplified multitasking more convincingly than any other Apple device. The smaller iPad is not designed to replace a MacBook. It is a compact tablet built for reading, browsing, note-taking, entertainment, gaming, communication, and lightweight productivity. On a device of that size, a full desktop-style windowing environment can feel disproportionate to the hardware’s physical dimensions.
Two-app split-screen workflows, by contrast, are perfectly suited to the iPad mini. The screen is large enough to make side-by-side applications genuinely useful, but small enough that managing multiple resizable windows becomes visually cramped. A dedicated multitasking mode that prioritizes simplicity and touch interaction would transform the iPad mini into a device that feels purpose-built rather than compromised.
Apple has demonstrated with the iPhone Duo that it understands how to create a compact interface that adapts to different screen configurations. The same philosophy could give the iPad mini a multitasking experience that feels natural rather than imposed.
Why the Magic Keyboard Should Not Define iPadOS Multitasking
A significant portion of the argument for maintaining iPadOS windowing as the primary multitasking model depends on the assumption that users are working with a keyboard and trackpad. That assumption does not reflect how many people actually use their iPads. A considerable number of iPad owners do not have a Magic Keyboard, and many do not want one.
The iPad is fundamentally a touch-first device. Its operating system should not make touch users feel as though they are operating an undersized desktop computer. A keyboard can make window management easier, but it should not be required to make multitasking feel intuitive. This distinction is becoming increasingly important as Apple continues to blur the line between iPhone, iPad, and Mac capabilities. Each device should honor its primary interaction method.
Apple Should Offer Choice Rather Than Impose a Single Philosophy
The strongest path forward for iPadOS is not to abandon windowing. Professional users who rely on multiple resizable windows should retain that functionality, and Apple should continue refining it. The iPad has become powerful enough to support workflows that were previously limited to laptops and desktops, and that capability should not be diminished.
Instead, Apple should offer a choice. Casual users could access a simple multitasking mode for quick two-app workflows. Professionals could use advanced windowing for complex projects. Everyone could move between these experiences without needing to understand the underlying window architecture. The operating system should accommodate both scenarios rather than forcing users to adapt to a single interaction philosophy.
Saved App Pairs Could Reshape iPadOS Productivity
One of the most promising concepts that the iPhone Duo implicitly supports is the idea of saved application pairs. People often perform the same combinations repeatedly: Safari and Notes, Mail and Calendar, Files and Pages, YouTube and Messages, Photos and Mail, research apps alongside a writing application. Instead of rebuilding these layouts every time, iPadOS could remember them and restore them instantly.
Apple already understands this concept at a system level. The iPhone Duo software demonstrates that multitasking can be designed around recurring combinations rather than simply leaving users with a collection of independent windows. Saved app pairs would eliminate repetitive setup and turn multitasking into an immediate, context-aware experience. This feature would be particularly valuable on the iPad, where users frequently return to the same workflows throughout the day.
Why the iPad Pro and iPad Mini Should Not Share the Same Multitasking Model
A 13-inch iPad Pro with a Magic Keyboard is a fundamentally different device from an iPad mini held in one hand. The screen size, input method, usage context, and user expectations all differ substantially. Yet iPadOS currently applies the same multitasking architecture across both devices, with only minor adjustments for screen real estate.
The iPhone Duo proves that Apple can design software specifically around a device’s physical characteristics. The company should apply that same principle to the iPad lineup. A 13-inch iPad Pro could retain advanced windowing because the screen size makes it genuinely useful. An iPad mini could default to a simplified split-screen mode because that better matches how people actually use the device. An iPad Air could sit somewhere in between, offering both options with intelligent defaults based on whether a keyboard is attached.
iPadOS 27 Has an Opportunity to Learn From iPhone Duo
The launch of the iPhone Duo gives Apple a reference point for designing multitasking around the user rather than around traditional desktop conventions. The company now has a real-world example of a multitasking interface created specifically for a nontraditional display, and the approach has proven both functional and intuitive.
Apple could use the iPhone Duo as a laboratory. What worked in that interface? What felt natural? Which gestures were unnecessary? Which workflows became easier? Which features translated well to touch? The answers to those questions could directly inform future iPadOS releases, particularly for devices like the iPad mini where simplicity matters most.
The Real Lesson Is Not About Foldables Versus Tablets
The iPhone Duo is not inherently better than the iPad as a productivity device. The iPad remains a fundamentally different product with a larger canvas, more powerful hardware configurations, and a broader ecosystem of accessories and applications. The lesson from the iPhone Duo is that screen size alone does not determine productivity. Software determines how useful that screen becomes.
A badly designed large display can feel restrictive. A well-designed smaller display can feel incredibly powerful. The iPhone Duo appears to understand that distinction, and the iPad needs to benefit from the same thinking.
What the Ideal iPad Multitasking Future Looks Like
The best future for iPad multitasking does not force users to choose between simplicity and power. It provides both. Casual users could split two applications with a simple gesture and minimal interface overhead. More advanced users could create multiple windows and arrange them as needed. Professionals could use Stage Manager and external display support. Everyone could use Picture in Picture without friction.
Users who repeatedly perform the same tasks could save application combinations for instant access. Video could remain visible during multitasking by default, with intelligent placement that does not interfere with active work. The operating system would adapt its interface based on screen size, input method, and usage context, rather than applying a one-size-fits-all approach.
That vision would transform iPadOS multitasking from something users have to learn into something they naturally understand. The technology already exists across Split View, Slide Over, Picture in Picture, and Stage Manager. What is missing is a more coherent user experience that ties these capabilities together without requiring users to navigate multiple interaction paradigms.
The iPhone Duo Raises the Bar for What Users Expect
Once users experience a cleaner multitasking system on the iPhone Duo, they may reasonably ask why their iPad cannot work the same way. The Duo provides a compelling example of where Apple’s interface philosophy can go when the company designs software specifically around hardware capabilities. The foldable form factor forced Apple to think differently about multitasking, and the result is an experience that many iPad users would welcome on their own devices.
Apple does not need to copy the iPhone Duo interface wholesale onto the iPad. The devices serve different purposes and have different design constraints. But the company should transfer the interaction principles that work: simplicity by default, power on demand, and an interface that adapts to the user rather than requiring the user to adapt to it.
The question is no longer whether Apple knows how to build better multitasking. The iPhone Duo suggests that Apple already does. The real question is whether the company will finally give iPad users the same level of simplicity, flexibility, and intelligence that it has now demonstrated on a foldable phone.
