Skip to content

Want to contribute?

GlassesResearch is being built for everyone interested in AI eyeglasses, smart eyewear, wearable computing, open hardware, reverse engineering, accessibility, privacy, and user-controlled ecosystems.

You do not need to be a professional developer or researcher to help.

If you own a device, found a manual, captured a Bluetooth packet, tested a feature, preserved an APK, photographed hardware, discovered a supplier, corrected a model name, or simply noticed that something on this site is wrong or incomplete, you can contribute.

Help build the smart-glasses knowledge base you wish already existed.

What the community means here

The community is not limited to people already using this repository. It includes people wherever smart-glasses knowledge is being created or discussed:

  • device owners and early adopters;
  • developers, makers, and reverse engineers;
  • accessibility users and advocates;
  • researchers, journalists, archivists, and repairers;
  • people in vendor forums, Discord servers, Reddit communities, GitHub projects, Matrix rooms, mailing lists, and specialist groups;
  • anyone comparing, modifying, preserving, documenting, or questioning smart eyewear.

GlassesResearch intends to meet people where they already are, invite them to participate, and preserve what they have learned with clear attribution.

Ways to contribute

Contributions can be tiny or substantial. Useful examples include:

Report or correct a model

  • Add a missing model to The List.
  • Correct a model name, manufacturer, release date, feature, or status.
  • Identify rebadged, white-label, regional, discontinued, or historical devices.
  • Supply reliable links to manufacturer pages, manuals, reviews, regulatory filings, or archived listings.

Share hands-on findings

  • Fit, comfort, battery-life, display, audio, camera, microphone, or prescription-lens observations.
  • Setup, pairing, reset, recovery, repair, and troubleshooting procedures.
  • Photos of packaging, ports, controls, boards, lenses, labels, or accessories.
  • Reproducible test results and the exact firmware, app, phone, and operating-system versions used.

Preserve technical artifacts

  • Manuals, SDKs, sample code, protocol documentation, firmware references, APK metadata, release notes, and software dependencies.
  • BLE services, characteristics, packet captures, command sequences, and observed device states.
  • Teardowns, board markings, chip identifications, optical measurements, and manufacturing clues.
  • Links to community projects before they disappear.

Do not upload proprietary material unless you have the right to redistribute it. When redistribution is uncertain, contribute metadata, checksums, archive references, lawful public links, and preservation notes instead.

Improve the knowledge base

  • Fix a typo, broken link, unclear sentence, or navigation problem.
  • Add citations or stronger primary sources.
  • Separate verified facts from community reports or inference.
  • Improve tables, glossaries, model cross-links, comparisons, FAQs, and buying guidance.
  • Translate or summarize non-English public documentation while retaining the original source.

Contribute without using Git

You may open a GitHub issue and describe what you found. A maintainer can help place it correctly.

Include as much of the following as practical:

  1. Device manufacturer and exact model.
  2. What you observed or found.
  3. Whether it is hands-on, externally reported, or inferred.
  4. Source links, photographs, files, dates, versions, and reproduction steps.
  5. How you would like to be credited.

How evidence is labeled

GlassesResearch distinguishes among:

  • Hands-on verified: directly observed and documented by a contributor.
  • Primary-source documented: supported by a manufacturer, regulator, standards body, repository, manual, filing, or other original source.
  • Community reported: reported by one or more identifiable community sources but not yet independently reproduced.
  • Inferred: a reasoned conclusion based on available evidence, explicitly labeled as inference.
  • Unknown or disputed: evidence is incomplete, contradictory, or unresolved.

A contribution does not need to be fully verified before submission. It does need to be honestly labeled.

A practical contribution workflow

Easiest route: open an issue

Use an issue for:

  • a new model or source;
  • a correction;
  • a question requiring investigation;
  • a community report;
  • a preservation lead;
  • a proposed feature or research project.

Direct route: submit a pull request

  1. Fork the repository.
  2. Create a focused branch.
  3. Make one coherent change.
  4. Cite sources and label evidence appropriately.
  5. Open a pull request explaining what changed, why it matters, and how it was verified.

Small pull requests are welcome. A one-line correction with a reliable source is valuable.

Outreach: meet the community where it is

GlassesResearch contributors are encouraged to share relevant pages and invitations in communities where they already participate, including:

  • general smart-glasses and augmented-reality communities;
  • communities centered on XREAL, Ray-Ban Meta, Even Realities, Brilliant Labs, VITURE, Rokid, Halliday, Solos, Vuzix, Google Glass, and other manufacturers or models;
  • reverse-engineering, hardware-hacking, repair, firmware, Android, Bluetooth, optics, accessibility, privacy, and open-source communities;
  • relevant GitHub repositories, issue trackers, forums, Discord servers, Reddit communities, Matrix rooms, mailing lists, and local maker groups.

Outreach should be respectful and useful rather than promotional. A good invitation explains:

  • what information is being preserved;
  • why that community's knowledge matters;
  • how contributors will be credited;
  • that unverified reports are welcome when clearly labeled;
  • that the project is vendor-independent and does not exist to market products.

Reusable invitation

We are building GlassesResearch, an independent, vendor-neutral knowledge base for AI eyeglasses and smart eyewear. If your community has hands-on findings, manuals, firmware history, BLE research, setup notes, repairs, teardowns, software projects, archived links, or model knowledge, we would like to preserve and credit it. Contributions can be as small as a correction or as large as a technical dossier. Evidence is labeled clearly as verified, primary-source, community-reported, inferred, or unresolved.

Contributor recognition

Contributors should receive visible credit whenever they want it and whenever licensing, privacy, and safety permit.

Recognition may include:

  • attribution within the relevant page or evidence record;
  • a contributor name or handle in commit and pull-request history;
  • inclusion in a future contributor hall;
  • links to the contributor's public project, research, or profile;
  • acknowledgment for artifact preservation, testing, translation, photography, code, investigation, or correction work.

Anonymous and pseudonymous contributions are also welcome.

Preservation promise

GlassesResearch exists partly because valuable knowledge disappears.

Manufacturers remove manuals. Apps vanish. SDKs are abandoned. Forums close. Product pages are rewritten. Community discoveries become trapped in old chats, private drives, dead links, and forgotten repositories.

Our principle is:

Archive first. Organize second. Verify continuously. Attribute always.

Whenever legally and ethically possible, the project will preserve references, metadata, context, checksums, citations, historical records, and public artifacts so future researchers do not have to rediscover the same information.

The goal is not to collect files indiscriminately. The goal is to preserve knowledge responsibly.

Community standards

Contributions should be:

  • honest about certainty and provenance;
  • respectful toward other contributors and communities;
  • free of harassment, doxxing, credential theft, malicious code, or unsafe instructions;
  • careful with personal information and device-owner privacy;
  • properly attributed and compatible with copyright and licensing requirements;
  • focused on documentation, research, interoperability, preservation, repair, accessibility, and user control.

Vendor criticism is allowed. Unsupported accusations are not evidence.

What happens after you contribute

A submission may be:

  • merged directly;
  • edited for structure, sourcing, or evidence labels;
  • placed in a research backlog pending verification;
  • linked from a model chapter or resource catalog;
  • preserved as a community report;
  • declined when it creates legal, privacy, safety, or evidentiary problems.

Questions and incomplete leads are welcome. This is a research institution under construction, not a finished encyclopedia.

Start here

Own glasses? Know something? Found something? Preserve it with us.