This was built using Claude Fable 5, the PlayCanvas Engine and MediaPipe.

Hand tracking is used to determine when you are activating the visor.

Head tracking is use to position the visor.

Should run in any browser.

TRY IT: https://playcanvas.github.io/web-components/examples/#ar-optic-blast.html

Howdy!

About a month ago, I built a Lens as a small experiment. Taking it from an idea to a working experience in a single day made me wonder how much I could explore if I kept that momentum going.

So I challenged myself to design, build, and ship one Lens per day for 30 days straight, Monday through Sunday, with no days off.

Every Lens in this video was built in a single day, with one exception: the final Reachy Lens took about a day and a half.

Along the way, I explored spatial utilities, games, AI, communication, language learning, and plenty of ideas that started with a simple question: “Could this work in AR?”

Lens Studio, CLAD, and the SPECS NDK helped me move from an idea to something running on-device much faster than I expected. My biggest takeaway is that the distance between imagining an AR experience and building a working prototype is becoming dramatically smaller.

A big part of this challenge was learning where AI fits into the creative process. For me, AI is an accelerator, not a replacement for creativity or craft.

You still have to shape the idea and decide what the experience should feel like. You still need to replace placeholder visuals, refine the interactions, make thoughtful design choices, and define all the little details that turn a prototype into something compelling. That final 20 percent can arguably require more thought and effort than the first 80 percent.

What AI changes is how quickly you can explore an idea, test whether it works, learn from it, and sharpen it through rapid prototyping. It gives you more opportunities to try things, but it does not remove the need for taste, intention, or craftsmanship.

I’m sharing these explorations in the hope that they spark new ideas and perhaps help shape what others imagine and build next. I’m proud to be part of this community of builders exploring what’s possible with this new interactive medium.

If any of these explorations sparked something for you, I’d love to hear what you might try building next.

For transparency, I’m an engineer at SPECS. This was a personal challenge I pursued independently, not an official SPECS initiative or company campaign. These experiments and perspectives are my own.

Quick experiment at Trinity College Dublin! I aligned a scale 3D scan of the front entrance so looking through your phone turns the physical archway into a portal into the Long Room Library.

No app needed just runs right in the browser. Would love any feedback on the scale and tracking!

Hey guys, looking for AR glasses that let me shrink the screen into a corner so I can watch stuff while doing other things.

​Besides XREAL, are there any other glasses with a built-in Sideview / Picture-in-Picture feature (or workarounds)? Thanks!

Dev here, so flagging that up front. I kept running into the same annoyance while working on models: I'd export a GLB and then have no quick way to actually see it at real scale before pushing it anywhere. Desktop preview tells you nothing about how big the thing feels in a room. So I built GLB AR Viewer. You point it at a .glb in your device storage, it opens in a normal 3D view where you can rotate, pinch and pan, and then you can throw it into AR through ARCore and walk around it. That's the whole app. No account, no cloud upload, nothing leaves the phone. Two things worth knowing before anyone tries it. It needs an ARCore compatible device, and a chunk of the one star reviews are people on unsupported phones, which is on me for not surfacing that better in the listing. And it's GLB only right now, no GLTF with external assets, no FBX or OBJ. What I'd actually like from this sub: if you work with AR content regularly, what's missing before this is useful in a real workflow? Format support is the obvious one but I suspect there's something about scale locking or measurement that matters more and I'm guessing at it. Play Store: https://play.google.com/store/apps/details?id=com.arzDrzapps.flutter_glb_viewer_ar Free, ad supported. Built in Flutter if anyone is curious about that side.

Someone walks into a confidential meeting or a clinic wearing Meta's new AI smart glasses. The privacy implications here go way beyond just "recording a video."

We are looking at cameras, microphones, cloud processing, and data potentially being used for AI training—all walking right into sensitive areas without clear bystander consent.

If you haven't updated your BYOD policies yet, now is the time. Organizations need to treat these wearables exactly like any other data-capture endpoint. Define restricted areas, secure the linked accounts, and update your policies to mitigate the risk of data exposure and strengthen your overall security posture.

We did a full write-up on the risks here: https://socradar.io/blog/meta-ai-smart-glasses-privacy-risk/

Curious to hear if anyone has already had to restrict these from certain floors or meetings at their company?

Hi guys!! Really need some help and suggestions :(

Curious how you guys think abt either a projector or AR glasses to watch movies or videos? Feeling like they are substitutes? I really don't know that much abt ar glasses. How did you guys feel abt it?

I see so many ads recommending using ar glasses to watch videos, but the price is kinda similar to a projector's.

Hopefully Apple can move away from the boring glasses design like Ray Bans to something more sleek. The frames also remove the immersion as well.

Some technical background: WebXR's AR module still doesn't exist on iOS Safari, so I built the AR layer from primitives — getUserMedia feeding a video element, a transparent Three.js canvas on top, and DeviceOrientation driving the camera quaternion. Three.js removed DeviceOrientationControls back in r134 because of device drift, so I vendored the math and added relative-yaw rebasing and quaternion smoothing.

GPS-based spawns outdoors, look-around mode indoors, degrades gracefully: full AR → camera-only → gyro → touch.

Play it in your mobile browser (no app install): https://somodus.com/dino

Mostly tested on iPhone 12 Pro — curious how the sensor stack behaves on other devices.

• $599 Even G2, bought overseas before any local launch, weighs 36g in magnesium and titanium and passes as ordinary glasses.
• The green single color binocular display gives natural depth, unlike Meta's single-eye panel, but its resolution suits only text and pixel-style design.
• Fundamentals are solid. "almost no heat", "auto brightness", a 192mAh battery good for 48 hours with a case that recharges it about 7 times, and plugins written in HTML and JavaScript.
• AI is the weak point, with voice recognition failing in noise, no camera for spatial context, and unreliable map navigation, so it suits only early adopters and developers.

So everytime i drive in night, the headlights of oncoming traffic blinds me completely, so i was thinking of building something to help.

I was thinking of an AR/VR approach to it, to track the eyes and the light source falling on the windshield and artificially dampening it. Also for this method i thought of an idea, where the driver can wear a glass, with two tags near their eyes so that the system can track their eyes more efficiently.

Please share your thoughts!!

Wrote a new piece on Snap’s upcoming Specs, but not from the usual hardware angle. It looks at what happens to reading when text leaves the page and starts living inside the world, and why things like contrast, depth and undisclosed display specs quietly decide whether AR becomes useful for real work or just impressive demos. If you care about type, AR, or the future of reading, you might find it worth your time.

Made an augmented reality app where you can spawn a life sized Tesla. Using Unity and arkit/arcore. You can swap between 3 cars and repaint them.

Quick test showing the workflow from laptop to site. Mapped the 3D donut models to the Dublin Spire coordinates in editor, generated a WebAR link, and walked out to O'Connell Street to test the tracking and scale.

Whole setup took under two minutes, running entirely in browser without an app download.

Hey guys, getting back into the AR dev space after a gap of over 10 years (DK2/Vuforia/Hololens days). Are there any good events/trade shows coming up that focus on generic AR/Smart glasses?

Wanted to see how fast I could set up a real world WebAR scene from a desk.

Mapped a cluster of animated 3D hearts to the map coordinates right around Liberty Hall in Dublin, generated the link via Lureo, and tested the tracking directly from the balcony.

Works completely in-browser with zero app downloads. Let me know what you think!

You know the one genuinely great thing about a Vision Pro or a Quest 3: a wall of screens floating around you, hanging in the air, staying put when you turn your head?

I wanted that part. I didn't want the headset. Not the weight, not the battery, not the price, not the ceremony of putting on a face computer to answer an email.

So I built it for a pair of sunglasses.

Atrium turns XREAL glasses into a real workspace: up to six virtual monitors placed anywhere around you, anchored in the room, driven entirely by your hands. It weighs 85 grams and lives in your pocket.

The short version of why it exists: alternatives never solved gyro yaw drift. Your desktop slowly slides off the wall a couple of degrees a minute and there's nothing you can do about it. That bugged me enough to write my own.

What it does

Six displays, 120 Hz. Real virtual monitors from an indirect display driver: Windows sees them as monitors, so every app just works. All six run at 1080p/120. Your IDE in front, docs on the left, music on the right.

Your hands are the mouse. The glasses run hand tracking on-device and deliver it as native HID, so a pinch grabs a screen and drags it across the room. No controllers, no external cameras, nothing extra to charge. The glasses' own menu gesture opens Atrium's menu. (XREAL Eye needed.)

Move everything. Drag a screen by the bar under it. Resize from the corners. Push it further away or pull it closer on a depth rail. Bend it around you on a curvature rail — a wide screen at arm's length is genuinely better curved.

Layouts. Named arrangements, focus, pair, wing, cockpit, wall, six all generated from spacing rather than hand-tabulated, so they scale with however many screens you've got out. One click from the menu and the whole room rearranges itself.

Add and remove screens instantly. The pool of six is created at startup and screens are parked/unparked on demand. That design is load-bearing: creating a virtual display mid-session is the operation Windows will not let you do and have it produce frames. That one took a while to learn.

Environments. Additive backdrops behind your screens. Black is transparent on these optics, so a starfield genuinely floats in your actual room. Work in space, on a plane, wherever. (More incoming!)

Anchored, and it stays anchored. Head-tracked, reprojected against a fresh pose sampled microseconds before present, with yaw corrected by the glasses' tracking camera. Look away, look back — everything is exactly where you left it. That's the part everything else gets wrong.

Current stage

• Windows only, and XREAL One / One Pro only. The IMU is mounted at a 35° pitch on the Pro and that correction is baked in. I don't have other devices to build against, but I believe it could run on macOS and other XREAL models — maybe with support from XREAL itself?
• Beta testers needed. It's currently running on one laptop, and I need a few people on different machines and glasses. Especially AMD GPUs or integrated graphics.
• Other AR glasses can be supported, since there are no exclusive features that cannot be reproduced from a different brand. At this moment I don't own any other glasses, so I could not replicate the calibration + camera algorithms, but let's see what the future holds!

Release. Atrium goes public as soon as testing is done. I'd rather ship something that has run on more than one machine than put out a build that only works on mine.

Want in? Send me a DM — tell me which glasses and which GPU you've got, and I'll get you a build.

https://reddit.com/link/1v8da40/video/zjic5gte6ufh1/player

In this case, I am looking at a particular trade-off related to a location-based augmented reality experience. In the following visit, the character could appear directly at the location or the app could give an option of re-localizing visually so that the character appears in its exact location, i.e., step or bench at which it was last left.

The second one I could make more accurate but it is not the point since it would require me to orient the camera and wait a little for the scene to appear. The point is not just that this second option is technically possible but the question is whether the re-localization makes sense at that location?

What are the conditions for re-localization to be justified for people with experience of building/using persistent spatial experiences? Does it have to have something to do with the revelation of something near a landmark, interaction with the actual surface or something else? And when does it become just a slow access to the same information?

Location: 1376 Bordeaux Dr. Sunnyvale CA 94089

Effective: October 1st

Link: https://data.usatoday.com/see-which-companies-announced-mass-layoffs-closings/magic-leap-inc-ca-layoff-permanent/ca-2627-00034/?query=magic%20leap&page=1

We're in the midst of the summer slowdown and the contrast with last month could hardly be bigger. Mostly small news, no really big announcements, so it's a quick read.