Ray-Ban Meta Audio and Gen 3 Expand the Wearable AI Portfolio

Meta’s September 23 glasses announcement is a portfolio decision: should wearable AI be one general-purpose device or several products with different trade-offs?

In its Connect announcement, Meta introduced Ray-Ban Meta Audio, Ray-Ban Meta (Gen 3), new Meta Glasses styles and Muse access on AI glasses. Meta says the audio model weighs 43 grams, offers up to 12 hours on one charge and up to 48 additional hours from its case, and starts at $349 for preorders shipping October 13. Meta says Gen 3 starts at $449, reaches up to nine hours of battery life, adds a customizable action button and includes a 12-megapixel camera with 3K video.

Those specifications describe distinct choices. Audio-only glasses emphasize listening, calls and assistant access. Gen 3 adds capture and a longer list of camera features at a higher starting price. Muse adds a personal-agent layer across the glasses family. The right comparison is therefore the daily task a person wants to support, not a single score for the portfolio.

The limits are equally important. Battery figures are vendor specifications, not independent real-world measurements. The announcement does not establish how long those features last under a specific mix of calls, recording and AI use, nor does it resolve regional availability for every capability.

My recommendation is to map the purchase to the moments that matter: listening, hands-free capture, assistant interaction or all three. Teams should also consider the visibility of recording, fit and the management of personal data. More models create choice, but they also create a clearer need to compare boundaries.

Meta is betting that regular hardware variations and software updates can grow an AI-glasses category. This release supplies a wider set of options and prices. Whether it changes daily behavior will depend on comfort, battery performance and the usefulness of Muse in actual routines—evidence that the announcement alone does not yet provide.

One useful follow-up is to separate the announcement from the decision it enables. What evidence would make this relevant for your team?

A practical comparison should include the surrounding workflow, not just the headline metric. Which constraint would you measure first?

The stated limits matter here. Which missing detail would you want verified before relying on this change?