Wearables compress every hard problem in embedded engineering into the smallest possible space. The device must be tiny, run for days, survive sweat and impact, sense a moving human body accurately, connect to a phone reliably, and feel comfortable enough that someone chooses to keep wearing it.
Any one of those is manageable. Together they conflict — a bigger battery means a bulkier device, more sensing means more power, better sealing means harder assembly — and wearable development is largely the discipline of resolving those conflicts in the right order.
This guide covers the constraints that define wearable products, the sensing realities teams underestimate, and how to sequence development so the trade-offs are made deliberately.
The Four Forces That Shape Every Wearable
Size dictates the battery, and the battery dictates everything
Industrial design usually fixes the enclosure early, which fixes the cell, which fixes the energy budget before any firmware exists. Working the other way — establishing the energy budget first and letting it inform the enclosure — avoids the common outcome of a beautiful device that lasts a day.
The human body is a hostile RF environment
Tissue is mostly water, which absorbs 2.4 GHz energy efficiently. An antenna that performs well on a bench can lose much of its range once the device is against skin, and orientation changes as the wearer moves.
Antenna design and placement must be validated on a body or a suitable phantom, never only in free space.
Motion corrupts physiological sensing
Optical heart rate works by measuring tiny light changes through skin. Movement shifts the sensor, changes contact pressure, and introduces artefacts far larger than the signal itself. This is why wrist-worn heart rate is accurate at rest and unreliable during vigorous activity.
Robust designs use an accelerometer alongside the optical sensor so motion can be identified and compensated for, or so readings can be flagged as unreliable rather than reported as fact.
Comfort decides whether data exists at all
A wearable that irritates skin, snags, or feels heavy gets left in a drawer. Weight, strap material, edge radius, and heat all determine adherence — and a device nobody wears produces no data regardless of how good its sensing is.
In wearables, comfort is not a design preference. It is a data collection requirement.
Technical Decisions That Define the Product
| Decision | Typical answer | Why |
|---|---|---|
| Connectivity | Bluetooth Low Energy | Phone compatibility and low power; everything else is a niche choice |
| Processor | BLE SoC such as nRF52 class | Integrated radio saves space and power |
| Battery | Small Li-Po, sometimes coin cell | Shape constrained by enclosure; charging adds a port or coil |
| Charging | Pogo pins or wireless | Avoids a connector opening that must be sealed |
| Sealing | IP67 minimum, IP68 preferred | Sweat, rain, handwashing, and occasional immersion |
| Sensing | Accelerometer plus the specific modality | Motion context is needed to interpret almost everything else |
| Data strategy | Process on-device, sync summaries | Streaming raw sensor data destroys battery life |
That last row is the one most often reconsidered late. Classifying activity or detecting an event on the device and syncing a summary is dramatically cheaper than streaming — the same reasoning behind TinyML on constrained hardware.
When a Wearable Becomes a Medical Device
This distinction changes cost, timeline, and risk more than any technical choice, and it hinges on claims rather than on hardware.
- Wellness positioning — “track your activity”, “monitor your sleep patterns”. Minimal regulatory burden.
- Medical positioning — “detects atrial fibrillation”, “measures blood oxygen for diagnosis”. Requires clinical validation and regulatory clearance.
Two devices with identical sensors can sit on opposite sides of this line purely because of how they are marketed. Decide the positioning before development starts, because clinical-grade validation is not something that can be added at the end.
Sequencing Wearable Development
Frequently Asked Questions
Conclusion
Wearable development is an exercise in resolving conflicts: size against battery, sensing against power, sealing against serviceability, and capability against comfort. The order in which those are resolved determines whether the product works.
Prove the sensing on real people first, build the energy budget before choosing the cell, validate antennas on a body, capture motion context alongside every other signal, and run long wear trials. The devices that succeed are usually the ones that did less, but did it reliably enough that people kept wearing them.
Many wearables are heading into clinical use. What that involves, from remote patient monitoring to FDA cybersecurity requirements, is covered in IoT in healthcare.