F73 Screenless Band: Purchase & App Evaluation

For brands evaluating a woven, open-frame screenless band with a companion app or a separately scoped own-app project. Start with the F73 sample, then define the data your app actually needs.

Woven-strap selection and own-app data evaluation

Reviewed 13 November 2026 using the supplied F73 product pack. The values below are supplier references; the approved sample and written quotation define the delivered configuration.

Purchase itemF73 reference / decision
Supplier modelF73
Main unit dimensions44.8 × 25 × 9.8 mm; supplier reference includes the sensor module
Listed total weight14 g; verify the supplied strap configuration
Controller / heart-rate sensorAB5691 / TYHX3602
Reference battery110 mAh polymer lithium-ion
Listed companion appJoeme Fit; confirm firmware pairing and current phone compatibility
Own-app routeModel-matched package, supported fields and permitted use to be agreed before development

What should a F73 sample demonstrate?

Strap and daily wear

Confirm the open-frame buckle, adjustment range, skin contact and logo area on the actual sample. F74 shares the reference electronics; choose between them by fit and construction, not an assumed difference in sensing accuracy.

Own-app feasibility

List required live and history fields, units and timestamps. Ask for the F73-matched Android/iOS integration package and confirm pairing against the supplied firmware. A package name alone does not prove every field is available.

Background synchronization

Test pairing, reconnection after leaving phone range, time synchronization and history recovery on the intended phones. Retain sample output and the tested firmware/app versions.

Wellness outputs

Distinguish an app-displayed HRV or sleep value from an SDK-exported field. Raw PPG, a recovery score, continuous streaming and algorithm rights each need their own confirmation.

Choose the app route before quoting engineering

The supplied Joeme Fit workflow and a buyer-owned app are different routes. For an own-app project, list the required fields and obtain confirmation of a package compatible with this model and firmware. An SDK, Bluetooth document, cloud API, app source code and watch firmware are separate deliverables. Specify what your team will build and which, if any, extra engineering services are requested.

A proposed package must be checked on your sample. SDK access does not automatically include every raw sensor stream, recovery algorithm, unrestricted redistribution rights or recurring services.

From sample to pilot order

  1. Confirm F73, the configuration and the sample quantity. Provide the destination and complete recipient details for a shipping quotation.
  2. Agree sample hardware, included documents, app route and any separately quoted engineering work before payment.
  3. Record delivery, the document/package version and the actual test results. Tell Galax which required test passed or remains blocked.
  4. For a pilot or branded order, confirm the next quantity, timing, artwork, packaging and model-specific production conditions. A sample quantity is not a promise of low-MOQ custom hardware.

Is F73 different from F74 electronically?

The reviewed supplier sheets list the same AB5691 controller, TYHX3602 heart-rate sensor and 110 mAh capacity. The strap/frame presentation differs. This does not establish identical firmware, SDK behaviour or measured performance; approve the exact sample.

These are proposed acceptance checks, not completed tests. Supplier-listed wellness metrics do not establish clinical accuracy. Water-resistance, runtime, data access, document coverage and exact firmware functions should be checked for the quoted configuration.