/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Apple's new iPadOS includes mouse support for iPads as an accessibility setting

the mouse cursor is locked to the iPad screen. It also doesn't map right-click to the new context menus in iOS 13, but it does do scroll wheel Steve Troughton-Smith / @stroughtonsmith : I think this is my most popular tweet — ever. Apple, if you think you're gonna get away with hiding iPad mouse support in AssistiveTouch and only half-supporting it, you're kidding yourselves 😂 Make it official, and do it properly. APIs too https://twitter.com/... Sean Hollister / @starfire2258 : am imagining steve jobs spinning in his grave rn https://twitter.com/...

The Verge Tom Warren

Context & Ripple Effects

This is the quiet first move in what became Apple's slow-motion reversal on the iPad-as-a-computer question: mouse support shipped not as a feature but buried in AssistiveTouch, with the cursor locked to the screen and right-click unmapped to iOS 13 context menus. Developer Steve Troughton-Smith immediately called it half-supported and demanded official APIs — and he was right about where this was heading. Within months, leaked code pointed to Smart Keyboards with built-in trackpads and proper right-click, and Apple followed through with iWork adding trackpad and mouse support in iPadOS 13.4.

First-order effects

  • Users who need or want a pointer gain one today, but only through AssistiveTouch — no public API, cursor pinned to the display edges, scroll wheel works while context-menu right-click does not.
  • Developers building for iPad get nothing to integrate against yet, putting pressure on Apple to either formalize pointer support or leave a gap between what the OS can do and what apps can target.

Second-order effects

  • The criticism forces Apple's hand: within ten months the accessibility hack becomes a designed feature — a translucent, momentum-driven cursor that changes form by context (Wired's review of the 13.4 cursor) plus first-party app support in iWork.
  • Hardware follows software: the leaked trackpad-equipped Smart Keyboard line gives Apple a premium accessory upsell tied directly to the pointer, pulling iPad pricing and positioning closer to laptop territory.

Third-order effects

  • Once the pointer exists, multitasking has to grow around it — the arc runs from this hidden setting through Craig Federighi's framing of the cursor as a paradigm change, to Stage Manager in iPadOS 16, to the Mac-like resizable windows and Files/Preview apps of iPadOS 26 — a structural convergence of iPadOS toward desktop-computing paradigms.
  • The episode establishes a pattern: Apple piloting major platform capabilities inside accessibility settings first, letting usage and developer reaction decide whether they graduate into official features — with accessibility users effectively serving as the vanguard for everyone.

The trend: Major interface capabilities increasingly debut as accessibility features before becoming platform-defining ones, and the iPad is converging on Mac-class input and windowing one release at a time.