A wearable session is a glance-duration.. You look at something on a one and a half inch screen for two seconds or less while wandering around your kitchen and expect all the context, what happened and what to do next, to be there on the screen before your eyes lift off again. This is the design reality for any engagement on wearables today.

According to Stormotion’s 2025 data on fitness apps, 28% of users return on day one, but only 8.48% on day thirty, so there is value to be mined from retention, and wearables comprise a growing part of that retargeting. More than 60% of patients in the US own a wearable health device already.

A watch screen will contain one primary and one supporting data point. Add a third and none of them have any chance of getting noticed at all.

A modal is a UI element that appears over another screen to request some form of engagement, usually with a dismiss button to go back. In wearable device design, you have neither the space nor the time for such an element.

What you can do is an always-on complication for passive data consumption and a Short Look and Long Look pattern, as pioneered by the Apple Watch, for those rare moments when the user actually wants to engage in an interruption that they might have forgotten about by the time their wrist unfurls. Note that neither of these options is suitable for critical or time-sensitive information, which means those alerts have to behave like notifications.

A phone app has to earn every session by the skin of its teeth through some hero content or campaign. On a wearable, the data is already there whether you look or not (anticipating what the user needs before they ask) in the form of the user’s vitals and their aggregates, like heart rate variability, step count, and sleep score.

This changes the retention design equation from “how do I get the user to engage” to “what passive data do I want to surface when the user engages.”

If you miss a streak on your phone it’s because you chose not to engage. On a wearable it’s just as likely that the battery ran out overnight and you didn’t know it. Any penalty for a broken streak should therefore be designed with forgiveness baked in, because otherwise, the user is likely to give up entirely on the next day rather than re-engage with the product. The best streak management systems like Fittr and HealthifyMe recognize this and let you freeze your streak instead of breaking it, and that should be the default in any wearable retention design.

The full article details the three-part interruption system responsible for deciding between an in-watch engagement and a push to the phone, and how to design around the handoff to avoid the dreaded white screen of death when coming from a notification.

Build, validate, and export a clean sitemap.xml file straight in your browser. No signup, with support for Astro, WordPress, Shopify, and doc sites. The validator side flags duplicate URLs, bad changefreq values, and malformed XML before you submit to Search Console.

Try the sitemap generator → Sitemap Generator