Apple's platform unification push should center on making it easier for devs to share code between Mac and iOS apps, not on getting iOS apps to run on the Mac
@daringfireball, http://daringfireball.net/... Thanks: @cremnob
Context & Ripple Effects
A week after [[a:925031|Bloomberg reported Apple plans to combine iPhone, iPad, and Mac apps in a push toward platform unification]], John Gruber stakes out the contrarian position: the goal should be easier code-sharing between platforms, not shipping iOS apps onto the Mac as-is. The distinction matters because it separates developer ergonomics from product surface area.
The debate doesn't stay theoretical for long — by mid-2018 Apple publicly denies a merger but confirms a porting effort slated for 2019, and Federighi frames hardware as staying distinct even as software converges. Two and a half years on, Apple silicon Macs run iOS apps natively through the Mac App Store, making this piece the earliest articulation of the fork in the road Apple actually took.
First-order effects
- Developers planning Mac versions of their apps in 2018 must weigh two paths Apple is signaling simultaneously: shared codebases via improved frameworks versus direct ports of existing iOS binaries.
Second-order effects
- If iOS apps land on the Mac wholesale, Mac-native developers compete against a flood of touch-first ports, pressuring them to justify premium pricing — while Apple's own framing that some iOS apps 'would be great on the Mac' sets which categories get absorbed first.
Third-order effects
- The endpoint visible in the corpus is one architecture under both platforms: once Macs run iOS apps natively, the Mac App Store inherits the iOS catalog, and 'Mac developer' and 'iOS developer' collapse into a single audience targeting Apple's silicon.
The trend: Apple is converging macOS and iOS around a shared codebase and shared silicon, with the open question being whether apps themselves — not just development tools — become portable across both.