Apple Glasses and the Developer Bet Nobody's

The part of the Apple Glasses story that the consumer tech press keeps glossing over isn't the design philosophy or the price point. It's this: somewhere right now, a small team is two years into building an app for Ray-Ban Meta frames. Another team shipped an integration for Brilliant Labs' Aria. A solo developer is maintaining an open-source project that pipes notifications into Even Realities' G2s. These people are making platform bets — and Apple's entry, whenever it actually arrives, will restructure every one of those bets without asking their permission.

That's the story I want to pull on. The consumer framing — will regular people wear these? — is fine as far as it goes. But I cover who gets to build things, and on whose terms, and what happens when a dominant platform shows up late to a space where smaller builders have already done the hard work of figuring out what the category even is.

Mark Gurman's latest reporting, covered by 9to5Mac's Fernando, puts Apple Glasses in late 2027 with a rumored price range of $200 to $600 — framing that comes from a leak, not a locked spec sheet, so hold it loosely. The more substantive signal in Gurman's reporting isn't the price. It's the product philosophy: Apple apparently wants to build glasses that are glasses first, with technology as a secondary layer rather than the whole pitch.

Fernando draws the comparison explicitly: "They wanted to position themselves as glasses first that just so happened to be a tech item versus trying to be a tech item that so happened to be glasses, which is I think the mistake that's happening with the Meta glasses right now."

He's right about the diagnosis. Whether Apple executes on it is a different question.

The Apple Watch Analogy Holds, But Not the Way You Think

The Apple Watch comparison is everywhere in Apple Glasses coverage, and it's genuinely instructive — though usually for the wrong reasons. Fernando notes that the Apple Watch is "the best-selling watch of all time" — a claim that's been repeated widely enough in industry coverage to feel like established fact, but which originates from Apple's own marketing and has been amplified through enthusiast media rather than independently audited against comprehensive global watch sales data. It's probably true. But probably-true isn't the same as verified.

What's more interesting to me about the Apple Watch parallel is what it says about developer relationships, not consumer adoption. When watchOS launched in 2015, the developer story was a mess. Third-party apps were slow, constrained, and ran on the phone rather than the watch itself. Apple controlled the SDK tightly. The watch that users actually wanted to build apps for — the watch with native apps, real performance, genuine capability — arrived with watchOS 2, a year later.

That's not a failure story. It's actually Apple's standard playbook for new platforms: ship something with enough first-party integration to be compelling, keep the SDK constrained at launch to maintain the experience, then open it up incrementally as the platform matures. The gold Edition Apple Watch, priced at up to approximately $17,000 at launch, wasn't just a luxury flex — it was a signal to the fashion world that Apple was serious about the object. The developer relations side of that launch was considerably less glamorous.

If Apple Glasses follow the same arc, the first SDK won't be where the interesting building happens. The interesting building will happen when Apple decides — on its own timeline, for its own reasons — to open the aperture.

Privacy as Platform Governance

The privacy dimension of smart glasses has gotten more urgent since Harvard students AnhPhu Nguyen and Caine Ardayfio demonstrated in October 2024 that Ray-Ban Meta frames could be used to identify strangers in public by piping the camera feed into a facial recognition pipeline. That demo wasn't about Ray-Ban doing anything wrong — Meta's frames were just cameras on a face, pointed at a crowd. The issue was architectural: always-on cameras on your face represent a fundamentally different privacy surface than a camera in your pocket.

Fernando makes the point about Even Realities' G2s that their microphone only activates on explicit prompt, and there's no camera at all. "They don't have any cameras on them," he says. "There's no speakers on them."

What he's describing isn't just a feature set — it's a governance choice baked into the hardware. No camera means no accidental surveillance. No always-on microphone means no passive data capture. Those decisions constrain what the device can do, but they also constrain what can go wrong.

Apple's reported approach suggests similar restraint: an iPhone companion device that delivers notifications, maps, Siri prompts — an extension of what's already in your pocket, not a new surveillance node. That framing is more trustworthy than Meta's for reasons that have nothing to do with brand reputation and everything to do with business model. Apple sells hardware. Meta sells attention and data. Those incentives shape what gets built into the platform at the architectural level, well before any privacy policy gets written.

For developers, this governance structure matters enormously. Building on Meta's platform means operating inside a data economy where your app's users are also Meta's product. Building on Apple's platform means operating inside a hardware economy with a 30% toll booth but considerably cleaner data handling norms. Neither is free. They're just different kinds of unfree.

The People Who Already Shipped

Here's what doesn't get said in the consumer coverage: the wearables developer community that exists right now is small, scrappy, and has been doing genuine work to figure out what smart glasses can actually be useful for. Brilliant Labs shipped Aria as an explicitly open platform — open hardware designs, open SDK, a deliberate bet against the walled garden model. The Even Realities G2 community is building notification integrations and teleprompter workflows with tools that are, by smart glasses standards, relatively accessible.

These developers aren't waiting for Apple. They're already here. And when Apple enters, a significant portion of the developer talent that's been building for open or semi-open platforms will face the familiar calculation: do you go where the users are, or do you stay where you can actually control what you've built?

Apple is very good at winning that calculation. The App Store's track record on this is not ambiguous. The developers who built the early smartwatch ecosystem — Pebble's community, the independent watchface developers, the people who figured out what notification-on-wrist even meant before Apple shipped watchOS — largely migrated to Apple's platform when the user base followed. Some of them thrived. Some of them found that Apple had shipped a first-party version of their app as a default feature.

That's not malice. It's just how dominant platforms work. The open experiments get acquired, abandoned, or outcompeted. The canonical developer tools become Apple's canonical developer tools. And the governance structures that the smaller platforms built — the open SDKs, the community ownership models, the deliberate architectural restraint — get replaced by whatever Apple decides to ship with the first version of glassOS, or whatever they end up calling it.

What I Actually Think

The "glasses first" philosophy is smart product thinking and I don't want to undersell it. Fernando's point about the Even Realities G2 — that it succeeded at CES 2025 precisely because it looked like eyewear rather than a prop from a cyberpunk film — captures something real about what the category needs to become mainstream. Apple applying that philosophy at scale, backed by their industrial design capability and retail distribution, could genuinely normalize smart glasses in a way that nothing else has.

But "glasses first" almost certainly means "Apple's glasses first" — meaning the developer ecosystem will be shaped around Apple's priorities, Apple's SDK release schedule, Apple's decisions about what third parties are allowed to build. That's not new. It's how Apple has always run platforms. The question worth sitting with is whether the wearables space — which has more genuine open-platform experimentation happening right now than almost any other hardware category — will retain any of that openness once Apple's installed base arrives.

My read, based on watching Apple manage developer relationships at platform launches for years: the first generation will be tightly controlled, first-party-focused, and described as "curated for quality." The second or third generation will open up more. By then, the developers who built the interesting open stuff will have either moved in, sold out, or burned out.

That last one, I'm told, is more common than the press releases suggest.

Dev Kapoor is Buzzrag's open source and developer communities correspondent.