Apple letting the new iPad Pro run macOS would require major tradeoffs and touch on a Mac would lead to “a lot of flakey software that doesn't really work”
It is not unusual for customers to want the best of all worlds. It is why Detroit invented convertibles and el caminos. But the idea of a “dual boot” device is just nuts. It is guaranteed the only reality is it is running the wrong OS all the time for whatever you want to do....
Context & Ripple Effects
The iPad Pro’s laptop-replacement ambitions have long run into interface limits: an earlier assessment found iOS on iPad Pro lacked precise pointer input, even as its multitasking improved. Later coverage of resizable app windows in iPadOS 16 showed Apple pursuing more desktop-like workflows within iPadOS rather than merging the platforms.
This analysis matters because it frames the boundary as a software-quality and interaction-model problem, not merely a matter of putting similar hardware on both product lines.
First-order effects
- The argument pushes back on expectations that the new iPad Pro should dual-boot macOS, emphasizing that macOS touch support could compromise reliability and usability.
- It reinforces Apple’s existing product distinction: iPad Pro remains centered on iPadOS, while Mac retains the desktop operating environment.
Second-order effects
- Demand for advanced iPad workflows is more likely to focus on iPadOS multitasking, files, and input behavior than on a full macOS port; the prior call for a keyboard-and-trackpad “pro” mode illustrates that pressure.
- Developers avoid an immediate requirement to adapt Mac software for touch-first interaction, but the split preserves separate expectations for iPad and Mac app design.
Third-order effects
- If Apple continues narrowing workflow gaps through iPadOS rather than OS convergence, the industry’s 2-in-1 competition will remain centered on interface design and app ecosystems, not simply shared chips or form factors.
- The durable tradeoff is segmentation versus convergence: a unified device can reduce platform boundaries, but may also weaken the clear interaction assumptions that make software dependable.
The trend: Tablet platforms are adding desktop-style productivity features while preserving distinct operating systems and interaction models.