Sources: Apple plans to let developers port their iPad apps to Mac using a new SDK that will be released as early as June at WWDC
- This year, it will be easier to turn iPad apps into Mac apps — App merger initiative comes as Apple plans its own Mac chips
Context & Ripple Effects
This SDK is the concrete step in an arc Bloomberg first reported in December 2017, when sources described Apple's plan to combine iPhone, iPad, and Mac apps into one unified catalog. In June 2018 Apple publicly denied a full merger but confirmed it was building tooling to ease porting for 2019 — this report names that tooling: an SDK shipping as early as WWDC in June.
The strategic stakes go beyond developer convenience: per Bloomberg's framing, the app-merger initiative lands alongside Apple's plans for its own Mac chips, which would eventually let Macs run iOS apps natively on shared architecture.
First-order effects
- iPad developers gain a supported path to the Mac App Store with one codebase, immediately expanding their addressable market from iPad owners to every Mac user without a ground-up rewrite.
Second-order effects
- Mac users get a much larger native app catalog, pressuring incumbent Mac software vendors whose paid desktop titles now compete against cheap or free ports of iPad apps.
- The SDK de-risks Apple's silicon bet: once apps are portable across platforms, the planned shift away from Intel toward Arm-based Mac processors has a ready software library waiting on day one.
Third-order effects
- If the pattern holds through the chip transition — where Apple-designed Macs natively run iOS apps via shared architecture — the Mac and iOS ecosystems converge around a single developer target, with Apple controlling both the SDK and the silicon that defines what 'native' means.
The trend: Apple is dissolving the boundary between its mobile and desktop platforms by pairing a shared app SDK with its own processors, making one codebase and one architecture the default for all its devices.