Skip to content

GlassesResearch

Independent research into AI eyeglasses, smart eyewear, and open, user-controlled ecosystems.

Knowledge over marketing. Evidence over speculation. Openness over lock-in.

The repository I wish I had when I began.

Start here

Mission

GlassesResearch is a digital research institution dedicated to preserving, understanding, and advancing the global smart-glasses ecosystem. It makes scattered information easier to find, verify, preserve, compare, and build upon. It covers potentially hundreds of models across hardware, BLE behavior, firmware, SDKs and apps, optics, retail variants, reverse engineering, manufacturing intelligence, community resources, and user-controlled AI integrations. The W610 is the current hands-on reference device, not the repository boundary.

Principles

  • Document before modifying. Preserve original behavior, evidence, and sources.
  • Verify claims. Separate confirmed findings from hypotheses and open questions.
  • Attribute sources. Credit vendors, researchers, community posts, and archived materials.
  • Prefer user control. Explore local-first and vendor-independent integrations.
  • Avoid needless rediscovery. Record repeatable procedures and prior results.
  • Preserve corrections. Mark disproven claims and retain the reasoning trail.
  • Archive first when knowledge is at risk. Organization can improve later; a vanished source cannot.
  • No orphan knowledge. Give recurring entities one canonical home and link back to it.
  • No empty merges. New structure must provide immediate value.
  • Measure preserved knowledge, not page count. Infrastructure exists to serve evidence and discovery.

Institutional collections

GlassesResearch organizes existing and future work into interconnected collections:

  • global device database and model dossiers;
  • manufacturer, ODM, rebrand, and product-family history;
  • firmware, SDK, API, application, BLE, and protocol research;
  • hardware, optics, display, audio, sensor, repair, and prescription resources;
  • AI capability and integration research;
  • papers, patents, standards, and historical timelines;
  • community, developer, and preservation directories;
  • comparison tools, indexes, glossary entities, and a knowledge graph.

See docs/INSTITUTIONAL_COLLECTIONS.md for the canonical collection map.

Model chapters

Each glasses model receives its own self-contained research dossier under models/. Device-specific hardware, BLE research, firmware, applications, manufacturing intelligence, diagnostics, diagrams, schematics, evidence, resources, questions, chronology, genealogy, and research history remain together inside that model's hierarchy.

Registry and current hands-on model

Shared entities and repository-wide methods remain in canonical locations such as the glossary and project documentation.

Repository map

Evidence workflow

Visual evidence should be preserved alongside written observations rather than treated as decoration. Each photo set should have a dated folder and a short index describing what each image shows, where it came from, and whether it is original evidence or a third-party source.

Recommended naming pattern:

images/YYYY-MM-DD-topic/

Model-specific evidence should normally be stored inside the appropriate model chapter, such as:

models/W610/evidence/photos/YYYY-MM-DD-topic/

See images/README.md for naming, provenance, privacy, and cataloging guidance.

Current status

This repository is actively converting investigations into useful, cross-linked knowledge across the smart-glasses ecosystem. The W610 chapter is the current hands-on reference implementation; the model registry provides the growth path for devices not yet physically available to maintainers.

Contributing

Contributions should clearly distinguish observed facts, sourced claims, interpretations, hypotheses, and disproven claims. Include reproduction steps whenever possible and follow the founding charter, evidence standard, repository laws, preservation program, and investigation workflow.

Research only hardware and software you are authorized to inspect. Do not publish credentials, personal data, proprietary secrets, unlawfully distributed files, or material whose distribution is prohibited.