Enterprise AR: Different Requirements, Different Priorities

Magic Leap is pivoting toward enterprise, and from where I sit on the perception team, the pivot rewrites more of the requirements list than you'd guess.

In December I wrote that MR was climbing out of the trough toward productive deployment. I did not say which direction the climb went. Two months later the answer is factories, hospitals, and field service, not living rooms.

Consumer vs Enterprise

Consumer priorities:

1. Price (must be affordable)
2. Form factor (must be wearable socially)
3. Content (must have compelling experiences)
4. Ease of use (must work out of box)

Enterprise priorities:

1. Reliability (must work every time)
2. Integration (must connect to existing systems)
3. ROI (must save more than it costs)
4. Support (must have escalation path)

Almost nothing on the first list survives onto the second, and the perception work shifts accordingly.

How Reliable Is Reliable Enough?

Enterprise customers put it plainly: "If the tracking fails during a surgical procedure, that's not acceptable." Consumer tolerance runs under 1% tracking loss per hour; the enterprise requirement is under 0.01%. Two orders of magnitude.

Getting there leans on controlled environments, since enterprise can mandate good lighting and no clutter; on custom on-site calibration for specific spaces; on redundancy through multiple sensor modalities and failover paths, the staged degradation V2 fusion already carries; and on monitoring through real-time health dashboards and predictive maintenance. None of these tricks is available in a consumer living room, which is exactly why the enterprise number is reachable at all.

Integration Requirements

Enterprise systems don't exist in isolation. A deployment needs CAD integration to overlay 3D models from existing design tools, IoT integration to visualize data from sensors and machines, backend hooks into enterprise databases and workflows, and authentication through corporate identity management. For perception specifically, that translates into fiducial markers for CAD alignment, QR codes for object identification, and coordinate systems that stay consistent across visits.

Environment Considerations

Enterprise environments differ from homes, each vertical in its own way. Factories throw harsh lighting at you - bright overheads, hard shadows - plus metal surfaces that generate reflections and multi-path, scenes that never stop moving with machinery and people, and hazardous areas where you can't touch walls for mapping. Healthcare adds sterile requirements that forbid touching surfaces at all, variable procedure lighting, medical staff constantly in motion, and regulatory constraints (HIPAA, etc.). Field service means outdoor operation in sunlight and weather, variable customer sites, and connectivity you can't count on, so no assuming the cloud is there.

Each vertical needs its own perception adaptations.

Perception Customization

One size doesn't fit all, so we're building three kinds of flexibility. Environment profiles are preset configurations for common scenarios: a "clean room mode" for high-frequency lighting, an "outdoor mode" running sunlight-robust algorithms, a "dynamic mode" that adapts quickly to scene changes. Calibration tools let enterprise IT calibrate for their own spaces, with a site survey workflow, persistent map management, and quality verification. And API access goes deeper than consumer would ever allow: raw sensor access with consent, custom tracking algorithms with support, data export for analytics. The 2017 rule that third parties never get raw camera access was written for consumers, and enterprise is the first place it bends. "With consent" is carrying a lot of weight in that sentence.

Business Model Impact

Enterprise changes the perception team's day-to-day as much as the product's. Support timelines stretch to years instead of months, bug fixes become customer-specific, deployment sometimes means showing up on-site, and certification requirements (ISO, medical, etc.) enter the picture.

It's a different rhythm than consumer product development. Adjusting.