WearEars
GitHub (opens in a new tab)中文

03 / DEVELOPERS

A place for the next device.

WearEars separates the interface, drivers and transport. The shared contract carries common operations, while each driver owns its protocol.

Read the driver contract (Chinese) (opens in a new tab)

SYSTEM DESIGN

Follow a control through four layers.

Open a layer to read its role and inspect the source.

  1. InteractionWatch app & tiles

    The watch app and tiles expose controls. The connection controller coordinates queries, requested modes and device reports.

    View source (opens in a new tab)
  2. Unified contractTwsClient

    TwsClient defines the interface for connection, battery queries and mode changes. Drivers declare available operations through capability flags.

    View source (opens in a new tab)
  3. Driver selectionDriverRegistry

    The registry selects a candidate driver from device information and keeps brand protocols separate from the interface.

    View source (opens in a new tab)
  4. CommunicationRFCOMM / GATT

    Drivers parse device frames and perform implemented protocol operations. The standard path reads aggregate battery when the system provides it.

    View source (opens in a new tab)

CONTRIBUTE

Contribute a driver

Join the project discussion (opens in a new tab)
  1. 01

    Document the evidence

    Record the model, firmware, transport and command sources. Mark verified frames and fields that need investigation.

  2. 02

    Implement the shared contract

    Keep frame parsing, device operations and capability declarations in the driver. Register its matching rules in DriverRegistry.

  3. 03

    Record verification separately

    Keep offline frame checks and hardware results distinct, with capability boundaries per model.

Planned

Developer SDK and documentation site

Current integration resources are the source, driver contract and protocol records. A packaged SDK and dedicated documentation site are on the roadmap.