Google now inviting developers to buy Glass
Now that Google has offered a preview of Glass' SDK and opened the Mirror API to all developers, it has a strong incentive to get its eyewear in the hands of app writers. Accordingly, the crew in Mountain View is now inviting developers …
Context & Ripple Effects
Google has spent November dismantling its own scarcity model for Glass. The sign-up list it opened on November 12 funneled would-be buyers into a waitlist, then came a sneak peek of the Glass SDK on November 19, and on November 25 the Mirror API opened to all developers whether or not they owned the hardware. With the toolchain now broadly available, the remaining bottleneck is physical units — hence this invitation for developers to simply buy their way in.
The move matters because Glass' value proposition is only as good as its app catalog, and until now the people best positioned to write those apps were locked out by the same invite system gating consumers. The story also travelled unusually widely for a developer-access change — pickups at TechCrunch, Mashable, VentureBeat, SlashGear, 9to5Google and Marketing Land all landed the same day — suggesting the press read it as a signal about how quickly the Explorer program is scaling toward general release.
First-order effects
- Developers no longer need to win an Explorer spot or borrow hardware to build for Glass — anyone with the money and a developer account can now get a unit to code against.
- Google's waitlist loses its gatekeeping function for this cohort, converting the Explorer program from curated invitees into a self-selecting buyer pool of app writers.
Second-order effects
- An expanding base of developer-owned units feeds the app ecosystem that makes the device more attractive to the general consumers still stuck behind the sign-up list, tightening the loop between SDK access, hardware sales and catalog depth.
- Rival wearable platforms now face a competitor whose developer kit, cloud API and hardware channel are all open simultaneously — matching that requires opening their own pipelines rather than drip-feeding access.
Third-order effects
- If this staged sequence — waitlist, SDK preview, open API, developer hardware sales — holds, it points to wearables launching as developer-platform plays first, with consumer availability timed to catalog maturity rather than manufacturing readiness.
The trend: Consumer hardware launches are increasingly sequenced around developer access first, with Google using Glass to run the playbook in public one unlock at a time.