Screenless Recovery Band: App and Bluetooth Integration Review

For brands and app developers evaluating the Galax F73 screenless-band direction. Start with a confirmed field list, sample and written integration scope. F73 remains an evaluation-stage project direction; this page does not publish a finished product specification or a validated recovery algorithm.

F73 hardware reference · OEM and app routes · Sample checklist

What is available to discuss

The existing F73 project guide describes Bluetooth data exchange and protocol integration as evaluation topics. Confirm the exact sample configuration, supported protocol fields and engineering deliverables with Galax. A phrase such as “open protocol” does not establish access to all raw sensor data or proprietary scores.

DecisionRecord for the selected sampleEvidence needed before commitment
Sensor and data scopeRequested fields, units, timestamps and data-quality flagsConfirmed field list and de-identified sample output
Real-time / history accessSampling interval, history depth and clock behaviorProtocol review and sample-read demonstration
App connectionPairing, reconnection, background sync and phone permissionsResults on the intended iOS/Android versions
Algorithm rightsWhich scores are supplied, calculated in an app, licensed or excludedWritten deliverables and permitted use
Battery targetIntended sensing, reporting and sync profileMeasured runtime with documented conditions
Commercial routeSample, hardware, app/UI, engineering and cloud/service scopeSeparate MOQ, setup/NRE, recurring charges if any and support terms

Keep reference facts and measured results separate

HRV repeatability, sleep-stage consistency and recovery-score performance are not established by the existence of a sensor or a protocol field. Do not position the sample as a medical diagnostic device or present a battery target as measured runtime. The exact protocol and production specification should be agreed before development or volume purchasing.

A practical evaluation sequence

  1. Describe the target user and app functions.
  2. Confirm the selected hardware, firmware and fields with Galax.
  3. Read sample data into a test app or controlled development environment.
  4. Record data-format, reconnection, permission and update behavior.
  5. Evaluate any wellness metrics against an agreed reference method and retain the conditions and results.
  6. Agree the engineering, software rights, commercial scope and sample acceptance before production.

App and service responsibilities

Identify who operates the app and cloud, owns accounts and data, maintains compatibility, supplies updates and supports end users. Confirm consent, retention and deletion requirements for the actual service. Subscription-free operation is not assumed.

Galax can discuss model feasibility before quantity or every detail is decided. Review the order and document scope or start with the existing buyer resources.

Compare five screenless-band models

Galax now has five supplier-reference models to discuss for OEM and wholesale sourcing. F73 and F74 share reference electronics with different strap/frame presentations; F76 uses a smaller reference main unit; F360 and F370 use a different controller/sensor combination and a 200 mAh reference battery. This is a hardware comparison, not a measured performance ranking.

ModelMain unit (mm)BatteryController / HR sensorStarting point
F7344.8 × 25 × 9.8 mm110 mAhAB5691 / TYHX3602Open-frame woven strap
F7444.8 × 25 × 9.8 mm110 mAhAB5691 / TYHX3602Full-frame woven strap
F7637.2 × 18.9 × 8.7 mm75 mAhAB5691 / TYHX3602Compact main unit
F37044.5 × 25 × 10 mm200 mAh7013A6 / GH3228Metal-accent design; supplier-listed ECG configuration
F36044.5 × 25 × 10 mm200 mAh7013A6 / GH3228Decorative faceplate; supplier-listed ECG configuration

Supplier specification references reviewed 11 November 2026. Dimensions include the sensor module. Confirm the exact sample, BOM and firmware before quoting or comparing runtime, data access, water resistance or document coverage. F76 supplier sheets contain an inconsistent F75 header; the pack and model field identify F76, so confirm the order model against the approved sample.

F73 screenless band: hardware reference for OEM buyers

For a private-label fitness band or an own-app wearable project, F73 is a starting model to review with Galax. The supplier’s F73 English specification provides the reference details below; the approved sample and written order specification define the delivered configuration.

Reference itemSupplier specificationConfirm on your sample
Model and formF73 screenless smart bracelet; woven-fabric strapStrap finish, fit, color and logo location
Main unit dimensions44.8 × 25 mm; stated thickness 9.8 mm including sensor moduleApproved drawing and finished sample dimensions
Electronics referenceAB5691 controller; STK8321_W motion sensor; TYHX3602 heart-rate sensorQuoted BOM and firmware version; substitution approval
Battery and charging3.7 V, 110 mAh; magnetic charging cableRuntime under your sensing/sync profile, charge test and charger compatibility
Companion app referenceJoeme FitExact app build, supported phones, languages and pairing with the selected firmware

Source: supplier F73 English specification, reviewed 11 November 2026. These are reference specifications, not Galax laboratory measurements. Battery-life claims, Bluetooth version, water-resistance documentation and certifications require configuration-specific confirmation.

Identify the referenced app through its official listings: Joeme Fit on Google Play and Joeme Fit on the App Store. A store listing does not establish SDK availability, protocol rights or compatibility with every F73 firmware version.

F74 sample appearance: manufacturer footage

See the F74 frame, woven strap and physical handling in supplier-provided footage. The finish shown is a sample reference; confirm the appearance and branding area against your approved sample.

Manufacturer sample footage, five-second silent excerpt. This illustrates appearance and strap handling; it is not a completed accuracy, runtime or protocol-integration test.

Continue with the F74 product reference or compare all five screenless models. For your own app, request the exact field list, authorized protocol / SDK access and a sample-read demonstration before development.

Choose the screenless-band OEM route

Private-label hardware with an existing app

Start with the selected sample and supplied companion app. Confirm available strap colors, logo and packaging options, model-specific MOQ and app/service terms. Hardware branding and app branding are separate deliverables.

Your own app with Bluetooth integration

Request the field list, sample output, protocol or SDK access terms, history-sync behavior and supported firmware. Validate a small data-read demonstration before committing to an app build.

Custom firmware, app or algorithm project

Define sensor access, recording intervals, firmware changes, score ownership and update responsibilities. Confirm feasibility, engineering fees, development milestones and acceptance criteria before quoting volume production.

MOQ, lead time, development cost and recurring software fees depend on the chosen route. Ask for separate sample, hardware, customization and service line items rather than assuming one price covers every layer.

HRV, sleep and recovery data: what to request

Heart-rate readings, beat-to-beat intervals, an HRV summary and a recovery score are different deliverables. Ask which are produced by the selected firmware, which can be exported and which are calculated by the app. Raw optical data is a separate request. A displayed wellness metric does not establish access to its input data or algorithm.

  • Data contract: field names, units, timestamps, sampling intervals, quality flags, history depth and sample output.
  • Phone behavior: pairing, reconnection, background sync, permissions, offline storage and firmware updates on the intended phones.
  • Algorithm and service rights: score definitions, permitted use, licensing, cloud dependencies, account ownership, exports and deletion.
  • Acceptance: repeatability method, actual runtime profile, agreed pass criteria and a dated result record.

The terms “recovery band” and “screenless fitness tracker” describe a project direction. A validated recovery algorithm, unrestricted raw data and medical performance are not included by implication.

Start a sample or quotation review

Tell Galax your target market, intended use and whether you want the referenced app or your own app. An estimated quantity is helpful but is not required to start a feasibility discussion. Use the blank checklist to keep the hardware, protocol and commercial decisions together.

For model-specific supporting files, see the document and sample confirmation guide. Document availability and applicability must be checked against the exact hardware and destination market.

Screenless-band supporting documents: model lists and scope

Supplier-provided documents are available below for model review. The RED verifications name Shenzhen jumei Technology Co., Ltd as applicant and manufacturer, list multiple models, and identify F107 as the test model. Galax is the sourcing contact; these documents are not issued to Galax.

Product referencesRED documentRoHS documentWhat to confirm
F73, F74, F76CQASZ20230901719E
Issued 7 October 2023; test model F107
NAP23030304C02E
Report NAP2303030402E; issued 27 September 2023
Exact radio, PCB, firmware, strap/materials and production version against the listed family and full reports
F360, F370CQASZ20240400586E
Issued 12 April 2024; test model F107
NAP23030304C04E
Report NAP2303030404E; issued 3 April 2024
Exact hardware and shipment configuration, complete report scope and applicable destination-market requirements

The model names above appear in the documents’ model lists. A listed family model is not the same as an independent test of every production variant. The RED verifications describe conditions for CE marking, including completion of the EU Declaration of Conformity and compliance with applicable directives. The RoHS verifications apply to submitted samples and should be read with the full reports.

These files do not establish medical accuracy, measured runtime, access to raw HRV/ECG data, SDK licensing or completed app integration. They do not establish certification for a children’s 4G watch. For an order, request the applicable complete reports, declaration, labeling and a match to the approved sample.

Ask Galax to confirm the selected model documents · Review app / protocol requirements