Google's Ara team on why they ditched swappable core components like CPUs and radios to focus on differentiated modules like cameras, batteries, and glucometers
Next year, Google will sell a smartphone with interchangeable parts. Swap in different ones to give the phone new abilities.
Context & Ripple Effects
By May 2016, Project Ara had already been through one slip — Google pushed its pilot test into 2016 after originally aiming earlier — and days before this piece it had spun Ara out of the ATAP skunkworks into a standalone business unit with developer hardware slated for Q4. The design pivot reported here is the tell: swappable CPUs and radios are off the table, and modules are narrowed to cameras, batteries, and specialty hardware like glucometers.
That narrowing is what makes the later arc legible: by September, sources reported Google had scrapped the Ara phone entirely, leaving licensing-to-partners as the only path to market. Abandoning the core-component swap was effectively the moment the full modular-phone thesis died — once the processor and radio are fixed, 'Ara' becomes an accessory port, not a rebuildable computer.
First-order effects
- Module developers heading into the Q4 2016 dev-kit shipment must now design against a fixed compute and radio base, so the addressable market shrinks to peripherals where differentiation is real — imaging, power, health sensors like the glucometer.
- Google's own roadmap changes shape: with core components locked, the 2017 consumer phone competes on module variety rather than upgradeability, undercutting the original pitch that buyers could refresh the phone's brain without replacing the shell.
Second-order effects
- Partner and supplier attention shifts toward niche module makers — medical-sensor and camera specialists gain a potential distribution channel through Ara's marketplace, while commodity silicon vendors lose the hypothetical second sales channel a swap-market would have opened.
- Once the core is fixed, the economics converge on ordinary smartphones, which pressures Google toward the partner-licensing route sources later described rather than carrying first-party hardware costs for a differentiated-only device.
Third-order effects
- If the pattern holds, modular phones retreat from a consumer-replaceable-computer vision to an accessory-ecosystem play — and when even that fails to clear the bar, the technology survives only as licensed IP inside partners' devices, as the September reports suggested.
- The broader structural lesson for hardware platforms: interchangeability at the core (CPU, radio) collides with integration economics, so modularity efforts that survive tend to do so at the periphery, not the motherboard.
The trend: Modular smartphone ambitions are collapsing inward — from swappable core components to differentiated peripheral modules to licensed technology — as integration economics beat user-upgradeable hardware.