Interview with Apple's SVP of software engineering Craig Federighi on porting iOS apps to Mac, how the hardware will remain distinct, and more
NEAR THE END of yesterday's WWDC keynote, Craig Federighi, Apple's senior vice president of software engineering, acknowledged that people …
Context & Ripple Effects
Two years ago, Federighi was part of the trio telling journalists the Mac's job was to stay Mac-like, with iOS and macOS kept deliberately distinct. By late 2017, commentators were pushing back that Apple's unification effort should mean easier code-sharing between platforms, not literally running iOS apps on the Mac — the position staked out in Daring Fireball's argument about shared code over merged apps.
This interview is Apple threading that needle: at WWDC 2018, Federighi confirms iOS apps are coming to the Mac as a porting path, while insisting the hardware itself stays separate. The through-line runs forward to Apple later making iOS apps run natively on Macs with its own chips, which turned this framework-level bridge into a shared-architecture guarantee.
First-order effects
- Mac users gain access to iOS apps through a porting route Apple now officially endorses, without Apple merging the two operating systems.
- Developers face an immediate choice: invest in bringing their iOS apps to the Mac via the new framework or keep the platforms separate.
Second-order effects
- Apps built for touch arrive on a mouse-and-trackpad platform, forcing developers to adapt interaction models rather than simply recompile — the friction Daring Fireball warned about.
- A successful porting path extends the iOS App Store's gravitational pull toward the Mac, pressuring Mac-only developers to compete with a much larger catalog.
Third-order effects
- If the pattern holds, Apple converges its software ecosystem — one app catalog spanning both platforms — while keeping hardware categories distinct, a structure later cemented when Apple-designed chips let Macs run iOS apps natively.
- Platform boundaries shift from being defined by hardware to being defined by input model and windowing conventions, the distinction Federighi still defends years later in the iPadOS windowing work.
The trend: Apple is converging its app ecosystems across iPhone and Mac while keeping the devices themselves distinct, moving from 'separate platforms' toward a shared architecture under one developer surface.