Let’s imagine you are designing a wearable device. The core constraints of wearables are size and energy. It must be small enough to carry, yet provide enough functionality to send data. Think of the wristwatch. A watch cannot be so heavy that it feels like an extra limb, yet so flimsy that it flatlines when inverted, wet, or cold. The evolution of the wristwatch created designs where movement itself powers the “motion.” The device becomes an extension of “you.”
Energy scarcity as a constraint
This isn’t just “use less power.” Energy availability fundamentally changes architecture. Wearables need intelligent connectivity patterns; when to sync, when to go dormant, when to offload data to computers/phone/cloud. Industrial IoT plugs in, wearables must make every milliamp count. This shapes your data strategy.
Haptics
With a phone, your interaction zone is bounded by the screen. With a wearable in motion, the interaction zone is your body and immediate gestures. The device has to distinguish between your incidental movements (swinging your arm while walking) and intentional gestures. You normally can’t communicate complexity through vibration alone. But, wearable nodes could capture complexity as sensors, and let the network handle the data management side of things.
No nuance, no rich information. Wearables have to be ruthlessly constrained in their information density. They tell you things, they monitor, but they don’t do complex things without trial and a lot of error.
Your “phone” is a perfect example; the “modern” phone is a miniaturized, highly evolved, computer. The battery and screen are maxed out. It’s not a phone, it is a portable computer that has a phone application. Consider how the walkie-talkie has evolved only slightly in the same time frame as your mobile device.
Multi-device mobility
A wearable rarely works alone. It’s often part of an ecosystem (phone, cloud, other wearables, potentially smart home or ops center). It needs to intelligently negotiate which device does what computation, where data lives, and how devices hand off responsibility, all while the user moves through different ranges and connectivity contexts (WiFi → cellular → Bluetooth range).
Lightness
“Lightness” is not a descriptor of bulk or weight. It has a particular valence. A wearable that requires user training, switching modes, calibration or decision choices misses the point. 1980s “multi-function” fashion watches had many functions that were never used and an instruction booklet the size of your arm. When something has weight. You’re constantly aware of it. It’s a tool you use, not something you wear.
Psychological form
It seems strange to discuss the idea of psychological safety in the context of design, but there is an element of this. Not “military -grade durability,” …more like: Can I trust this in the moment? That mental overhead vanishes once you’ve touched it, held it, used it. The first interaction should reveal function. Behavior should be predictable (not surprising). It should adapt to you, not require you to adapt to it, implicit feedback loops not explicit settings.
