/
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

iOS and macOS are so fundamentally different that the whole notion of getting a cohesive UX with minimal effort by using Catalyst to port an iPad app is absurd

Jack Wellborn, “Catalyst and Cohesion”: Douglas Hill / douglashill.co : Page Up, Page Down, Home and End in Catalyst apps Nick Heer / Pixel Envy : Catalyst and Cohesion Michael Tsai : Catalyst and Cohesion  —  Jack Wellborn:  —  Developers using …

Worms and Viruses Jack Wellborn

Context & Ripple Effects

This piece lands mid-arc in a long-running argument about how far Apple should push Mac/iOS convergence. Back in 2017, [[a:925268|Daring Fireball argued the unification push should center on shared code between platforms, not on getting iOS apps to run on the Mac]] — precisely the distinction Catalyst critics are now pressing.

By late 2019 the critique has sharpened into specifics: Douglas Hill's work on Page Up/Page Down/Home/End shows Catalyst apps missing basic macOS text-navigation conventions, and Jack Wellborn, Nick Heer, and Michael Tsai converge on the view that cohesion cannot come free. What follows validates both sides — developers find Catalyst fine for simple ports but strained on complex ones (developer reports on mouse and window support), and Apple's own answer is to change the substrate rather than the framework with Apple Silicon's native iOS app support.

First-order effects

  • Developers who bet on Catalyst for iPad-to-Mac ports must absorb per-app remediation work — keyboard navigation, windowing, menu behavior — rather than shipping with minimal effort.

Second-order effects

  • Apple sidesteps the framework debate by moving convergence down the stack: Apple Silicon lets iOS apps run natively on Macs, making Catalyst one route among several rather than the strategic centerpiece.

Third-order effects

  • If the pattern holds, Mac/iOS unification settles at the architecture level while UX conventions stay platform-specific — leaving the 2017 code-sharing thesis, not app porting, as the durable model, with M1-era iOS-on-Mac quality (ranging from terrible to OK) as the cautionary evidence.

The trend: Apple's platform convergence is migrating from shared frameworks like Catalyst to shared silicon, while the software layer keeps insisting the two platforms' UX differences are real.