Magic Leap says it will add multi-user chat rooms with custom avatars in November, support for two controllers by early next year, city-wide AR layers, and more
Context & Ripple Effects
Magic Leap spent 2018 building out the developer stack around its first headset: an SDK previewed through a creator portal back in March, then the Magic Leap One Creator Edition shipping over the summer on Nvidia silicon with AT&T as sole US carrier. This roadmap update is the next beat — turning a single-user dev kit into something with shared spaces, custom avatars, two-controller input, and city-scale AR layers.
The multi-user push matters because it targets the same shared-hologram territory Microsoft would later stake out with Mesh avatars in Teams, and because Magic Leap's consumer-era feature cadence ultimately gave way to an enterprise pivot around Magic Leap 2 — and eventually to talks over licensing its IP and manufacturing capacity to Meta.
First-order effects
- Creators holding the AT&T-distributed Magic Leap One get a concrete feature calendar — multi-user chat rooms with custom avatars in November, dual-controller support by early next year — instead of waiting on unspecified SDK promises dating back to 2015.
Second-order effects
- Shared avatar spaces put Magic Leap head-to-head with Microsoft's mixed-reality collaboration play before Mesh even reached Teams, forcing both to compete on persistent multi-user experiences rather than lone-wearer demos.
Third-order effects
- If the pattern holds, consumer-facing AR platforms consolidate around whoever can fund shared-infrastructure features at scale — which is the trajectory that pushed Magic Leap from headset maker toward licensing its optics IP to larger players like Meta.
The trend: Augmented reality is shifting from single-user developer kits toward shared, persistent spatial layers — a race whose capital demands reshaped Magic Leap from consumer hardware company into an enterprise and IP supplier.