The iPad conundrum

Why the iPad’s origins stand in the way of its future.

The Wrong Starting Point

What is an iPad?

The original iPad keynote from 2010 is revealing. Jobs made the argument for a new category of device between the smartphone and the laptop. One that would be better at browsing, reading, watching, playing and communicating. The emphasis was not on productivity but immediacy. The iPad was meant to feel less like operating a computer and more like interacting directly with whatever was on the screen.

Yet as the iPad became more powerful, it has gradually returned to many of the conventions its original vision seemed intent on escaping.

Over the past decade, nearly every major advance in iPadOS has involved adding back something traditionally associated with desktop computing. Keyboards and keyboard shortcuts. Multi-window applications. Trackpads. External displays and storage. More sophisticated file and window management.

This creates a curious contradiction.

If the iPad’s defining characteristic is touch, why then has its evolution involved accommodating everything that isn’t?

The predictable answer is that users eventually want to do more with their devices. Fair enough. But that answer raises a more interesting question.

When users ask for keyboard shortcuts, windowing systems and external display support, are they rejecting the idea of a tablet? Or are they simply expressing a different and additional intention for the same device?

The distinction matters.

An iPad being held in the hand and an iPad sitting on a desk attached to a keyboard, trackpad and external display are physically the same computer. Yet they are being used in fundamentally different ways.

People who seek to run the iPad as their primary computer quickly run into its limitations. The inevitable refrain is simply to put macOS on the iPad and be done with it.

Yet that conclusion never feels quite right.

The real issue is not whether the iPad should run macOS. It is whether a computer’s interface should be determined by its hardware or by the context in which it is being used.

Others have asked the question and arrived at solutions from different directions.

Microsoft experimented with Continuum, where a phone could present a desktop-style environment when connected to a display and peripherals. As did Motorola with Webtop. Canonical continues to pursue a comparable vision with Ubuntu Touch. None of these efforts were commercially successful, but all were built around the same premise: one computer, multiple modes.

Within Apple’s ecosystem, Federico Viticci’s MacPad project explored a variation of the idea. By combining an iPad with Mac hardware, he created a Frankendevice that could move between touch-first and desktop-style computing as circumstances demanded.

Speaking of context, the Magic Keyboard is a useful touchstone that provides telling evidence.

Attach an iPad to a Magic Keyboard and the user is no longer interacting with a tablet in the conventional sense. They are sitting at a desk, typing, pointing with a trackpad and often working across external displays and storage devices.

In practical terms, they are using a laptop.

To iPadOS, the shift in context does not appear significant. Other than a few additional capabilities that are made available, the OS remains committed to assumptions established when the device was a handheld pane of glass.

Imagine a different approach.

Dock the iPad to a Magic Keyboard and a desktop environment appears. Window management expands. Applications gain access to richer workflows. External displays become first-class citizens.

Remove the keyboard and the desktop environment recedes. The interface simplifies itself for touch. The device becomes a tablet again.

Docking reveals intention. As does undocking. The OS ought to respond accordingly.

The argument is compelling, more so because it no longer needs to be speculative.

The processors used in modern iPads and Macs are closely related. The performance gap continues to narrow. Many applications already exist on both platforms.

The convergence of Apple’s hardware and software invites a different question. Why should the future be defined by either macOS or iPadOS? Both operating systems were designed around assumptions that predate the devices Apple now ships.

A future device may well be a shape-shifter, spending part of its day in a pocket (perhaps powering a VR headset), part of it in the hand (as a communicator), then docked at a desk (desktop mode), or later connected to a television (as a streamer or gaming console). Its physical form now is secondary. What matters more is the role it is performing at the moment.

In the past, a phone, tablet and desktop computer had fundamentally different performance envelopes determined by their hardware capabilities. A phone processor couldn’t realistically run desktop workloads. Battery life, thermals, memory and storage imposed hard limits.

Today, Apple ships a laptop powered by the same A18 Pro architecture used in the iPhone. The MacBook Neo launched in March 2026 is positioned as a mainstream Mac running full macOS, despite using what would traditionally have been considered a “phone chip.”

That would be one way of saying they put macOS on a phone. But that would be missing the point.

The point is, constraints have weakened.

An M-series iPad isn’t incapable of running professional software because it lacks processing power. It often possesses more computational capability than desktops from only a few years ago. Likewise, modern processors can scale from extremely low-power mobile use to demanding desktop workloads while remaining remarkably efficient.

That changes the nature of the problem.

Hardware can be whatever they need to be, if the software will let them.

Rather than conforming to a fixed, predefined role, the OS can now truly adapt to the one it finds itself in.

Perhaps the debate has been framed incorrectly all along. Not whether macOS should come to the iPad, because of the limitations of iPadOS, but whether either operating system represents the end state Apple should be working toward.