F360 Screenless Band: Purchase & App Evaluation
For teams evaluating a screenless band with a supplier-listed ECG configuration. Verify the electrode workflow and actual data output on F360 before planning an app feature or production order.
ECG-listed configuration and data export review
Reviewed 13 November 2026 using the supplied F360 product pack. The values below are supplier references; the approved sample and written quotation define the delivered configuration.
| Purchase item | F360 reference / decision |
|---|---|
| Supplier model | F360 |
| Main unit dimensions | 44.5 × 25 × 10 mm; supplier reference includes the sensor module |
| Listed total weight | 25 g; verify the supplied strap configuration |
| Controller / heart-rate sensor | 7013A6 / GH3228 |
| Reference battery | 200 mAh polymer lithium-ion |
| Listed companion app | Joeme Fit; confirm firmware pairing and current phone compatibility |
| Own-app route | Model-matched package, supported fields and permitted use to be agreed before development |
What should a F360 sample demonstrate?
ECG recording workflow
Confirm that the selected sample implements the supplier-listed ECG function, identify the electrodes and record how a user starts and completes a reading. A feature name is not proof of an exported waveform.
Exported data
Request the actual record format, units, timestamps, sampling details and any supported quality flags. Distinguish an app result, a PDF/image and a waveform accessible to the buyer app.
Platform-specific integration
F360 uses a 7013A6/GH3228 reference rather than the F73/F74 AB5691/TYHX3602 combination. Verify the package and firmware together; do not assume F73 code or data fields work unchanged.
Wear, sync and battery
Check the faceplate/strap finish, contact, reconnection and historical records. Measure runtime with the planned reading and sync schedule; 200 mAh is a capacity reference, not a runtime test.
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
- Confirm F360, the configuration and the sample quantity. Provide the destination and complete recipient details for a shipping quotation.
- Agree sample hardware, included documents, app route and any separately quoted engineering work before payment.
- Record delivery, the document/package version and the actual test results. Tell Galax which required test passed or remains blocked.
- 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.
Does the ECG listing establish diagnostic performance?
No. It is a supplier feature reference, not clinical validation or medical-device authorization. Confirm the exact sample function, data access and intended-use documents before making an ECG-related product claim.
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.
