Google unveils Depth API in ARCore to enable AR depth maps and occlusion, available in its Scene Viewer dev tool and used in Houzz app and Google's AR in Search
no special sensors needed! 😎😎 Sign up to be a collaborator for the new Depth API in #ARCore. https://twitter.com/... @googledevs : Deep dive into the future of AR! 📸🌍 Introducing the ARCore Depth API. Learn how you can use this new technology to create a depth map using a single RGB camera, improve occlusion, build greater AR experiences, and more! Read the blog → https://developers.googleblog.com/ ... https://twitter.com/... Glenn Gabe / @glenngabe : Occlusion can really help e-commerce retailers by placing objects naturally in your surroundings -> Google shows off stunning new AR updates coming to web and mobile apps soon The Houzz app with occlusion is available today: https://www.theverge.com/... https://twitter.com/...
Context & Ripple Effects
This announcement extends a pattern Google had already established with ARCore: extracting sensor-grade capability from ordinary phone cameras. The Augmented Faces API overlaid front-camera effects months earlier without any depth sensor, and Cloud Anchors had opened multi-user AR back in ARCore 1.2. The Depth API pushes further — inferring per-pixel depth from a single RGB feed, which is why it works on the existing Android fleet rather than only depth-equipped flagships.
What makes the launch notable is distribution rather than the algorithm alone: it ships inside Scene Viewer, is live in the Houzz home-furnishing app, and powers AR results in Google Search itself — putting occluded, physically plausible product placement in front of shoppers before the SDK was even broadly released. The related coverage shows the trajectory held: general availability followed within six months (the API reached all Android and Unity developers), and raw depth fidelity kept improving into 2021.
First-order effects
- Android developers gain realistic occlusion through Scene Viewer without requiring a depth sensor, immediately widening the pool of eligible devices for AR experiences.
- Houzz and Google's own AR in Search get better product placement now — furniture and goods render behind real-world surfaces instead of floating over them, which Glenn Gabe flagged as a direct win for e-commerce retailers.
Second-order effects
- Retailers using AR try-on or place-in-room features face a rising baseline: once occlusion is free on commodity phones, depth-less AR looks broken by comparison.
- Because the capability arrives as an API rather than new hardware, adoption pressure shifts to ARKit-class rivals and depth-sensor vendors, whose hardware moats erode when a software path matches the effect.
Third-order effects
- If the software-inference approach keeps closing the gap with dedicated sensors, AR capability stratifies less by device tier and more by who controls the perception stack — favoring platform owners like Google that ship it at OS scale.
- The same single-camera depth foundation underpins later mapping work such as immersive view in Maps, pointing toward ambient computing experiences that model physical space continuously from commodity cameras.
The trend: Smartphone AR is shifting from specialized depth hardware toward software-inferred perception on ordinary RGB cameras, letting platform owners like Google upgrade the entire installed base at once.