Why another AI watch will fail like Google Glass did

Meta showed off Muse Charm this week — a chunky, screen-bearing pebble you wear on a lanyard, voice-activated, designed to let you talk to an AI agent without pulling out your phone. It looks almost exactly like the problem it won't solve.

This is the third act of a play tech has staged since 2013. Google Glass arrived with the certainty that a heads-up display would revolutionize how we see the world. Snap Spectacles launched in 2016 with the same momentum: hands-free social video, the future of sharing. Both had impressive engineering. Both had nothing a person actually wanted to do differently.

The failure wasn't technical. It was anthropological. Glass required you to look like a cyborg in public and film strangers without their obvious consent, solving a problem nobody had: I wish I could document my life hands-free without my arms. Spectacles solved: I desperately want to film from an awkward angle at eye level. These were capabilities hunting for use cases, not solutions hunting for customers. Meta's Portal and Ray-Ban Stories followed the same shape. Neither caught on because neither answered the question that matters: why would I do this instead of what I'm already doing?

Muse Charm carries the same weight. A fingerprint sensor on the side activates it. You speak. The AI responds. The pitch is frictionless access. But frictionless access to what? You already have frictionless access to an AI in your pocket. Reaching for your phone is not the frustration this solves. Waiting for an answer is not the friction this removes. Apple, Google, and Amazon have spent years understanding that wearables work when they replace an action you already perform — checking the time, paying for coffee, reading a notification. Not when they create a new ritual around a capability you didn't know you needed.

The pattern doesn't care about the company or the year. It doesn't care about how confident the CEO sounds at the keynote. Hardware fails when it's built backward: the technology first, the use case invented later to justify it. Success requires the opposite. Someone is frustrated. That frustration has a name. Then you build the device. Meta's track record suggests the company still hasn't learned which way the arrow points.