Meta Ray Ban Display fail: Here's why Mark Zuckerberg's demo didn't work

Playing music and controlling the volume on the Meta RayBan Display smart glasses
(Image credit: Meta)

As everyone from Tim Cook to Bill Gates will attest, live demos of new features at a launch event are fraught with potential pitfalls. Those little goblins made themselves known at Meta Connect, when Mark Zuckerberg tried to demonstrate two features of the new Meta Ray-Ban Display smart glasses, only to have both fail.

While Zuckerberg blamed the issue at the time on the building's Wi-Fi, the reason was something else entirely. Andrew Bosworth, Meta’s chief technology officer, took to an Instagram Story the day after to explain the reason.

A screenshot of Meta's AMA on Instagram

(Image credit: Meta / Instagram)

The first problem occurred when Zuckerberg had a chef use Meta AI and the Ray-Ban Display's camera to look at the ingredients and suggest a recipe. Meta AI first failed to respond, and then jumped around, seemingly ignoring the chef's commands.

“When the chef said ‘hey Meta, start Live AI,’ it started every single Meta Ray-Ban’s Live AI in the building, and there was a lot of people in the building” Bosworth said in the Instagram AMA. “Obviously, in rehearsal, we didn't have as many people in the building."

"The second thing is, we had routed Live AI traffic to our dev server in theory to isolate it, but we had done it for everyone in that building on those access points, which included all of those headsets. We DDoS’d ourselves, basically.”

"And, it didn't happen in rehearsal because we hadn't had as many people with the glasses in the building."

The second error came when Zuckerberg tried to take a WhatsApp video call from Bosworth. Despite Bosworth repeatedly calling Zuckerberg on the Ray-Ban Displays — the incoming call tone was clearly heard by everyone in attendance — Zuckerberg could not answer the call.

"The video call issue was quite a bit more obscure," Bosworth said in the AMA. "A never-before-seen bug. The display had gone to sleep at the very instant the notification had come in that a call was coming in."

Even when Mark woke the display back up, we didn't show the answer notification to him. We never ran into that bug before. That was the first time we'd ever seen it; it's fixed now, and that's a terrible place for that bug to show up."

To his credit, Zuckerberg was able to quickly pivot and make light of both errors, but it serves as a reminder that when you're trying something new on stage for the first time, anything can happen.

Follow Tom's Guide on Google News and add us as a preferred source to get our up-to-date news, analysis, and reviews in your feeds. Make sure to click the Follow button!

More from Tom's Guide

TOPICS
Mike Prospero
U.S. Editor-in-Chief, Tom's Guide

Michael A. Prospero is the U.S. Editor-in-Chief for Tom’s Guide. He oversees all evergreen content and oversees the Homes, Smart Home, and Fitness/Wearables categories for the site. In his spare time, he also tests out the latest drones, electric scooters, and smart home gadgets, such as video doorbells. Before his tenure at Tom's Guide, he was the Reviews Editor for Laptop Magazine, a reporter at Fast Company, the Times of Trenton, and, many eons back, an intern at George magazine. He received his undergraduate degree from Boston College, where he worked on the campus newspaper The Heights, and then attended the Columbia University school of Journalism. When he’s not testing out the latest running watch, electric scooter, or skiing or training for a marathon, he’s probably using the latest sous vide machine, smoker, or pizza oven, to the delight — or chagrin — of his family.

You must confirm your public display name before commenting

Please logout and then login again, you will then be prompted to enter your display name.