Product design

Mobile

Wearables

Designing the app experience for a smart ring

The Virtusan Ring tracks sleep, heart rate and steps. I assumed it would show data in real time, but it synced every four minutes, so I redesigned the app around a passive device and improved it with user feedback over a year.

Role

Lead UX/UI Designer

Timeline

2024 to 2025

Platform

iOS and Android app

Team

Backend, frontend, PM, graphic designer & me

The product

The Virtusan Ring is a smart wearable that works with the Virtusan app, a wellness app that offers science-backed protocols for sleep, focus, exercise and stress. It’s built for health-focused people aged 20 to 40 who care about longevity and are early adopters of wearable tech. My job was the app side: the interface and how the ring fits into the user’s day.

The problem: designing for a device that didn’t exist yet.

I started designing before we had the ring. Talks with manufacturers were still going on, so we made an assumption: it would work like an Apple Watch and show data in real time.

It didn’t. The ring synced once every four minutes. That changed the product from something users watch to something that quietly records, and the app had to become a place to review data, not follow it live.

Design 1.0: ship fast, learn from users

Getting the ring to market had taken about four months of back and forth with the supplier: fixing sensors, working through a faulty API. The decision was to release a first version of the interface as quickly as possible and let users test it.

That meant no time to test the wireframes. I designed from experience and had no real feedback between the wireframes and the release. The experience held up, but the interface lacked polish.

Once users had the ring, four issues came up, some from feedback and some I spotted myself:

No clear way to move to the next step.

Graphs were too basic.

The info popup used too much space and was useless after the first read.

The key data points on the main, uneditable screen weren’t prioritised.

Design 2.0: three decisions

With real feedback and more time, I reworked the widgets.

A daily steps graph instead of weekly.

The weekly graph didn’t match the rest of the page, which showed daily numbers. Aligning them made the widget easier to read at a glance.

A way to go deeper.

I added a chevron and a short view of how much of the daily goal was done, so users can see progress and explore without leaving the main screen. The info icon moved to a subpage, and the redundant “steps” label was removed.

Show what the ring is doing.

Because data arrives every few minutes, I added a battery indicator to the ring status button and a “last updated” message. That way a number that seems stale doesn’t look like a bug.

I added more graphs and brought the whole flow in line with the brand guidelines.

Outcome

The app launched to users with the ring. I don’t have usage numbers to share, but the second version answered the specific problems the first version’s users found.

What I took from it

Two things I’d do differently: confirm how the hardware behaves before designing around it, and put even a rough prototype in front of a few users before launch. Most of the learning here came after release, which is expensive.