5 Exciting New Wearable Technologies

The number of wearable connected devices more than doubled between 2016 and 2019, growing from 325 million to 722 million, according to Statista. That trajectory has not slowed. Over a billion connected wearable devices are already in use globally, and forecasts from ElectroIQ suggest no ceiling in sight. What is changing is the ambition behind the devices. Wearables are moving from novelty to necessity, from counting steps to monitoring heart arrhythmias, from contactless payments to tracking a sleeping infant's oxygen levels.

Wearables demand a fundamentally different design logic, where every pixel and every second of attention carries real weight.

For brands and product teams, this creates a design problem that standard UX thinking does not fully solve. A wearable sits on the body. It interrupts the wearer at moments of physical activity, stress, or rest. The screen, where there is one, is often a fraction of the size of a phone. The interaction window is measured in seconds, not minutes. Getting the experience right requires a fundamentally different set of design decisions, and getting it wrong means the device ends up in a drawer.

This article covers five categories of wearable technology that are genuinely changing behaviour right now, and then goes deeper into the design and brand challenges that make wearables harder to get right than they first appear.

Smartwatches and Health Monitoring Bands

Smartwatches now hold a 43% share of the wearable device market, and nearly one in two people wear one regularly, according to a ValuePenguin survey. That dominance comes from continuous, passive health data collection: heart rate, blood oxygen, sleep cycles, stress indicators, and, increasingly, ECG readings that can flag atrial fibrillation before the wearer notices anything is wrong.

Health monitoring bands sit alongside smartwatches as a slightly simpler category. Devices like Fitbit and Whoop strip out the smart features and focus purely on biometric data. The appeal is focus: less to manage, more to learn from the body. For users recovering from illness, managing chronic conditions, or simply trying to sleep better, a dedicated health band with a week-long battery life and no notifications is often the more useful tool.

The design constraint that defines the category

We worked on a water tracking app that was originally phone-only, and a client later asked us to add an Apple Watch component. The native phone app was tactile and engaging, built to take advantage of a large screen. The Apple Watch offered very limited real estate. We had to rethink the entire navigation pattern and interaction model. We could not replicate the phone experience on the wrist, but we did build something that worked within the watch's own logic. The lesson was direct: watch design is a discipline in its own right, not a smaller version of mobile design.

Smart Glasses and Heads-Up Displays

Smart glasses have had a difficult decade. Google Glass launched in 2013 and was pulled from consumer sale within two years, largely because the social dynamics of wearing a camera on your face were never resolved. Since then the category has matured quietly. Meta Ray-Bans now sell in volume. Apple Vision Pro has redefined what heads-up computing can mean, even at its current price point. Industrial smart glasses from companies like Vuzix are standard equipment in warehouses and surgical theatres where hands-free access to information genuinely changes what workers can do.

Where the real design tension sits

For consumer smart glasses, the tension between capability and social acceptability has not fully resolved. People will wear technology on their face if it looks like eyewear, not if it looks like technology. That constraint drives every design decision, from the form factor of the frame to the brightness of any heads-up display overlay. The display must be readable in direct sunlight without overwhelming the wearer's field of vision. Notifications must surface and dismiss quickly enough that looking at them does not make the wearer appear absent from the conversation they are having. These are problems phones do not have, because you put a phone away when you are done.

For enterprise use, the priorities shift. A surgeon viewing imaging data during a procedure needs absolute reliability and zero lag. A warehouse operative picking stock needs large, legible text at a glance. Both groups need a device that works through a full shift without overheating or dying.

Wearable Payment and Transaction Devices

Contactless payment rings, wristbands, and embedded chip cards have been available for several years, but adoption has accelerated as NFC infrastructure has spread. The appeal is simple: for a short run, a music festival, or a day at the beach, carrying a phone creates friction that a payment ring eliminates entirely. Theme parks and sporting venues have adopted wristband-based cashless payment systems at scale, partly because they speed up transactions and partly because they create a closed-loop spending environment that suits the venue's economics.

We worked on a currency exchange product that was originally designed to let people transfer leftover foreign currency to each other at an agreed rate, bypassing bank fees entirely. Partway through the project, we found that both legal regulations and Apple's App Store policies prohibited direct peer-to-peer payment transfers of this kind. The product had to pivot to a location-based, in-person exchange model where users physically met to hand currency over. Apple then raised concerns about money laundering, and we had to impose a limit of approximately €100 to €150 on any single transaction to satisfy those requirements.

That experience reflects a broader truth about wearable payment products. The regulatory environment around money movement is not an afterthought. It shapes what the product can be, and teams that discover those constraints late pay a heavy price in rework and lost direction.

Before designing any payment or transaction flow for a wearable product, map the regulatory requirements for your target market first. App store policies, financial services law, and anti-money-laundering rules can each impose constraints that fundamentally change the user journey.

Smart Clothing and Biometric Textiles

Smart clothing embeds sensors directly into fabric. A running shirt tracks breathing patterns and muscle fatigue. A sports bra monitors heart rate without a chest strap. Compression socks measure circulation. The advantage over wrist-based devices is placement: a garment worn against the torso or leg can capture data that a watch cannot, with greater accuracy and without requiring a separate device to be charged and managed.

The design challenges here are material rather than digital. The electronics must survive repeated washing, stretching, and sweat. The connection between the textile sensors and any processing unit must be robust enough for athletic use. Battery life is constrained by what can be woven into clothing without adding weight or bulk. And the companion app still has to present that data in a way that is actually useful to the wearer, not just technically impressive.

Where biometric textiles are growing fastest

Professional sport is the lead adopter. Football clubs, cycling teams, and rugby squads use biometric garments to monitor player load and recovery in real time, catching signs of overtraining before injury occurs. That data then feeds into decisions about squad selection, training intensity, and rest protocols. The consumer market is following, particularly in endurance sport, where serious amateur runners and cyclists are willing to pay a premium for accuracy and granularity. Rehabilitation is a third area of growth, with post-surgical recovery garments that track movement and alert physiotherapists to compensation patterns the patient may not notice themselves.

Baby and Child Monitoring Wearables

Baby monitors have existed for decades, but the current generation is a different product. Wearable sock monitors like Owlet track a sleeping infant's heart rate and blood oxygen continuously. Smart camera systems with AI-powered movement detection can distinguish between a baby shifting position and one in distress. The emotional stakes are high, and the design of these products has to reflect that. A parent reading a night-time alert needs to understand immediately whether the reading is within range or requires action, under conditions of severe sleep deprivation, in the dark, in under five seconds.

We worked on a baby monitor product where the client was building both the physical hardware, including cameras and sensors, and the companion app. The integration turned out to be far more complex than originally anticipated. Rather than relying on off-the-shelf Bluetooth protocols, we had to formally define a software-hardware contract that specified exactly how the app would communicate with the device: turning things on and off, retrieving sensor data, and accessing camera feeds, all in a format the app could actually consume.

On the baby monitor project, we defined the contract between software and hardware before a single line of production code was written.

To test that integration without access to real hardware, we built a prototype that ran a web server from the device. This let us connect to it, inspect its internals, verify that settings applied through the app were correctly reflected in the device, and simulate the full communication loop between app and hardware. The work was spread across a consortium of teams in the UK, Europe, and further afield, and keeping every team aligned on capabilities and requirements across those distributed groups was one of the harder project management challenges we faced.

If you are building a wearable product that combines physical hardware with a companion app, define the data contract between them before either team writes production code. Ambiguity about data formats, update frequency, and error states becomes extremely expensive to resolve once both sides have built against different assumptions.

Why Wearables Break Conventional Brand Design

Brand design for wearables presents problems that brand design for screens does not. On a website or a phone app, a brand has generous space to express itself: full-colour photography, motion, type at multiple sizes, copy that explains and reassures. On a smartwatch face, you have roughly 32mm by 35mm of screen, and the user will glance at it for two seconds before returning to whatever they were doing. That two-second window has to carry the core of the brand experience, or the device becomes anonymous.

The standard brand toolkit simply does not transfer. A logo that reads well at 200 pixels wide becomes illegible at 40 pixels. A typeface chosen for its elegance at 16pt body copy becomes unreadable at the sizes a watch demands. Colour palettes designed for light mode on a phone screen can look completely different on an AMOLED watch display at low brightness. Every brand asset has to be rethought for the constraints of the form, not adapted from what already exists.

The added complexity of hardware identity

For brands building their own wearable hardware, the challenge is deeper still. The physical device is part of the brand. Its weight, materials, finish, and the feel of its band all communicate something about what the brand believes and who it is for. A fitness tracker built from aircraft-grade aluminium communicates differently from one built from polycarbonate, even if the software inside is identical. Getting that hardware-software brand coherence right requires the design team to be involved from the earliest stages of product development, not brought in once the device is manufactured.

Designing for Glanceability and Micro-Moments

The concept of glanceability is central to good wearable UX. A glanceable interface delivers its primary message within the first one to two seconds of a user looking at the screen, without requiring any interaction. Most wearable interactions are of this type. The user raises their wrist, reads the time, notes the heart rate or the step count or the next navigation instruction, and lowers their wrist. The interaction has ended before it felt like it started.

Designing for that pattern requires ruthless prioritisation. Nielsen Norman Group observed that a navigation bar in the Stocks watch app wastes 16% of available pixels that would have been better used for primary content. On a screen that small, 16% is not a rounding error. Every element that is not the primary piece of information is competing against it, and competition on a watch screen almost always hurts comprehension.

Touch targets and interaction limits

Touch targets on a watch face present their own constraint. Nielsen Norman Group recommends a minimum touch target of 1cm by 1cm to ensure reliable, quick interaction. On a 32mm screen, fitting three or four tappable areas at that size leaves almost no room for anything else. This is why the most successful watch interfaces rely heavily on gestures, digital crowns, and physical buttons rather than on-screen taps. The interaction model has to be designed around the device's physical controls, not retrofitted to them after the screen layout is finished.

When designing a watch companion app, audit your primary user task and ask whether it can be completed with a single glance and no tap at all. If it cannot, ask whether it can be completed with one tap. Every additional interaction required is a point at which the user will abandon the wearable and reach for their phone instead.

The Hardware, Software Contract Brands Must Get Right

The most underestimated challenge in wearable product development is the relationship between the physical device and the software that talks to it. Teams that come from a pure software background often assume that the hardware will expose a clean, well-documented API, and that connecting the app is a matter of integration rather than negotiation. That assumption is frequently wrong.

On the baby monitor project we described earlier, the gap between what the hardware team thought the app needed and what the app team actually needed only became clear once we sat down and defined it formally. The document we produced specified every data type, every command, every error state, and every timing constraint in a format both teams could work to. It was not glamorous work, but it was the thing that allowed the project to move forward without constant back-and-forth between teams in different countries.

When we had no access to the physical test devices, we built our own internal version of the monitor to test against, running a web server from the device that let us inspect its internals and verify that app commands were being reflected correctly in the device's state. That kind of bridging work sits between software and hardware and belongs to neither team by default. Someone has to own it explicitly, or it falls through the gap.

• Define the data contract before either side writes production code.
• Specify error states and edge cases, not just the happy path.
• Build a hardware simulator if real devices are unavailable.
• Assign clear ownership to integration work that spans both teams.
• Test the full communication loop end-to-end before assuming it works.

The broader point applies to any wearable product that involves a physical device and a companion app. The gap between what two teams each believe the contract to be is almost always larger than either team realises at the start. Making it explicit, in writing, with agreed formats and error handling, is the work that prevents the most expensive kinds of late-stage rework.

Conclusion

Wearables are not a single category with a single design playbook. A baby monitor app, a payment ring, a smart running shirt, and a heads-up display each present their own set of constraints, and the right answer for one is often the wrong answer for another. What they share is the demand for a fundamentally different approach to design, one that starts from the physical reality of the device and the genuinely brief moments of attention users will give it.

The brands that will build lasting products in this space are the ones that treat the hardware-software relationship as a design problem from day one, that define the contract between teams before either side builds, and that resist the temptation to adapt their existing digital brand assets rather than rethinking them for a new form factor.

Nearly half of wearable device users discontinue use within six months, according to Canhoto and Arp 2017 and Peng et al. 2021. That is a design and experience problem, and it is entirely solvable with the right thinking applied at the right stage.

If you are building a wearable product or adding a wearable component to an existing digital experience, the time to think about these questions is before the hardware is specified, not after the prototype is built. Let's talk about your wearable product.

Frequently Asked Questions