Why a Water Tracking App Needed to Be Reimagined for the Wrist, Not Shrunk Onto It

We worked on a water tracking product that lived on a phone, and it worked well there. The native app was tactile and engaging, with enough room on screen for logging a drink to feel like a small physical act rather than a form entry. Then the client asked for an Apple Watch component, and the first plan on the table was the obvious one, which was to take what already existed and make it smaller.

A watch app built by shrinking a phone app always feels like something has been taken away.

That plan did not survive contact with the device. We had to rethink the navigation and rethink how we were handling the interactions, because the things that made the phone version pleasant were the things the watch had no room for. We never matched the fluidity of the phone experience, and we stopped trying to. What we did manage was a set of features that genuinely belonged on a wrist.

So this is an account of how that decision got made, what we kept, what we dropped, and what the watch work ended up teaching us about the phone app we thought was already finished. Some of it applies to any product heading for a smaller device, whether that is a skincare routine tracker, a hotel check-in flow or a supplements reminder.

What the Phone App Was Actually Good At

The phone version of the water tracker earned its engagement through movement and space. A large screen gives you room for things to animate, for a tap to feel like it produced a result, and for a day's progress to be readable at a glance while still being pretty. People used it because logging a glass of water felt like a small satisfying moment rather than admin.

That quality matters more than it sounds. In a meditation app teardown we ran, the soft gradients and the breathing animation were slowing people down behaviourally before they had read a single word of copy. The interface and the way the interface works was doing the calming, not the text describing calm. Strong behavioural design shows up as something the product does, and doing it needs room.

Why space was the hidden feature

On the water app, the screen size was carrying a share of the emotional work. There was space for a generous target to feel achievable, space for progress to be shown in a way that felt kind, and space for a mistake to be undone without a menu. None of that was listed in the brief as a feature. All of it mattered.

Which meant the watch brief was about finding a different way to produce the same feeling with almost none of the room.

The Wrist Is a Different Context, Not a Smaller Screen

A phone gets held, with both hands free and attention already given. A watch gets raised, usually mid-something, often with one hand busy and the other wearing the device. The screen on the smaller Apple Watch is roughly 32 mm by 35 mm according to Nielsen Norman Group, 2015, and the time people spend looking at it is measured in seconds.

Context changes what the user is capable of. Somebody filling a glass at the kitchen tap has wet hands, three seconds of patience and no interest in a settings screen. Somebody at a desk between meetings has a bit more, but not much.

Designing for who actually turns up

In the meditation teardown we flagged a classic failure, which was designing for the ideal user rather than the actual one arriving at the product. That app assumed everyone opening it was rational and calm, when a large number of them were anxious and opening it precisely because they needed help. Nobody really opens a meditation app the first time because they are already calm and curious.

The watch version of that mistake is assuming a user who is sitting still and paying attention. The real one is walking, cooking, or halfway out of the door. So we designed for a person with one hand, three seconds and a mild sense of guilt about their water intake.

Deciding What Survives the Move

The useful question is what each feature asks of the person using it. Features that ask for attention, comparison or thought belong on the phone. Features that ask for one movement belong on the wrist. We sorted everything on the water app that way, and the sorting did most of the app UX design work before anyone opened a design tool.

Choosing the wrong surface is a real cost, and we have argued against a device before. When we worked on a surveying app for performance coaches, we recommended against asking the audience to download a native app, because that was a step too far for what was a simple touch point.

Pick the surface that matches the size of the moment, then design for that moment only.

Instead the presenter creates the survey in the native app, a QR code appears on screen, and anyone scanning it lands on a fully branded mobile responsive page. Far more people finished the survey, because the barrier matched the size of the ask.

Designing Around a Single Moment of Input

The water app on the wrist came down to one job, which was logging a drink. Everything else was support. Once we accepted that, the design got much simpler, because we were no longer protecting a feature set and could spend the whole screen on one action.

Decisions are the thing to watch. In the meditation teardown, the app asked people to pick a goal before they had done anything in the product, and asking someone to choose in that state of mind adds a decision, and decision is friction, which increases anxiety rather than giving relief. A watch has even less tolerance for that. Every choice you put in front of someone at the sink is a chance for them to give up.

Count the decisions in your watch flow, then remove every one that could be made on the phone, inferred from past behaviour, or set to a sensible default.

Celebrating the small log

On a fitness product we redesigned, we framed everything around personal pace and celebrated turning up at all, because two minutes a day beats zero. The same framing carried into the water app on the wrist. One glass logged while making tea is a win, and the interface says so, because people who feel they are behind stop logging altogether.

Rebuilding Navigation When There Is Nowhere to Navigate

On the phone, the water app had the usual structure of sections and screens that people moved between. On the watch, that structure had nowhere to live. We flattened it, so the main job sits on the first screen and the two or three supporting things sit one level away, reachable without hunting.

Chrome is expensive at this size. Nielsen Norman Group point out that a navigation bar in the Stocks watch app uses up 16% of available pixels that would have served the primary content better. On a screen that small, a tab bar is a tax on the thing people came for.

Using what the device already gives you

The crown, the side swipe and the long press are all movements people already know. Building custom controls on a wrist wastes the one advantage you have, which is a user who has already learned the platform. We leaned on the native patterns and spent our design effort on the logging moment instead.

Before adding a menu to a watch screen, ask whether the same choice could be handled by the crown, a swipe, or simply by remembering what the person did last time.

What we ended up with was less like an app and more like a single control with a bit of context around it.

Complications, Glances and the Interfaces You Never Open

The best watch experience often involves no app at all. A complication on the face showing how much water you have had today does more for the habit than a beautifully built screen nobody opens, because it removes the step where someone has to remember and then go looking.

We redesigned an accident reporting app for a vehicle manufacturer on exactly this principle. We looked at the accelerometer of the device, and if we detected movement followed by a sudden stop, the app preemptively asked whether the person had been in an accident. That unburdens people of the process of finding a reporting button while shaken and distracted. The rest of the flow worked the same way, with voice memos for witness statements and visual diagrams showing which photo angles to take, so it became a step-by-step visual process instead of something you had to remember during trauma.

The product comes to you

A complication is a quieter version of the same idea. The product shows up where attention already is, which on a watch is the face. For the water tracker, that meant progress visible on a glance, with the app itself reserved for the moments when someone actually wanted to act.

Design the complication first, then design the app. If the complication alone is useful, the app has a much easier job.

Notifications That Prompt Without Nagging

A reminder on a wrist is physical. It taps you. That makes the timing question far more serious than it is on a phone, where a notification can sit unread in a list and cost nobody anything.

On the concierge app we built for a high-end property development, the notifications landed well because of when they arrived. The notification wasn't seen as "here's something wrong" or "here's something I need to worry about", it was seen more as "I'm going to get my next bit of helpful information", because it came at the right time and for the right context.

Timing decides whether a prompt reads as someone helping you or someone checking up on you.

That difference is the whole game for a tracking product. A water reminder at 11am when you have logged nothing since waking is useful. The same reminder arriving four minutes after you logged a glass is the app telling you it has not been paying attention, and people switch those off within a week.

So we tied prompts to behaviour rather than to the clock alone, and kept the number low. A wrist tap that gets ignored still costs you, because the next one gets trusted a little less.

Accepting a Less Fluid Experience

We did not reproduce the feel of the phone app on the watch, and saying so out loud early in the project was the most useful thing we did. The animation, the gesture and the sense of a satisfying tactile moment were tied to screen size. Chasing them on a 32 millimetre screen would have burned the budget for a worse result.

Constraints cost money whether you accept them or not. On an alcohol buying and selling platform we worked on, we were forced to embed web elements instead of building a proper API layer, and that added about a twenty percent uplift in work over the entire length of the project. The client wanted to keep the budget the same, so we dropped features towards the end to compensate.

Spend the compromise deliberately

Watch work has the same shape. You have a fixed amount of effort and a device that will not do what the phone does, so the choice is whether you spend that effort on one thing done properly or five things done thinly. We picked logging, made it good, and let the rest stay on the phone where it already worked.

Nobody complained about the missing charts. They would have complained about a slow log.

How This Changed the Phone App Too

Stripping the water app back to one action exposed how much the phone version had been carrying out of habit. Once we had seen the job described in a single screen, several things on the phone looked like they were there because there was room for them, which is a poor reason for a feature to exist.

So the phone app got simpler. The logging action moved up, the setup questions got shorter, and a couple of screens that existed to display data nobody acted on came out. The watch work functioned as an audit we had not asked for.

Clarity travels back

On another fitness product we worked on, we had to take people through a few orientation questions, and one of the key changes we made was simply framing how long it would take. Not a technical thing at all, just telling people what to expect, and suddenly they went into it in a much more prepared way. Early abandonment dropped.

Small clarifications like that are forced on you by a watch, because there is no space to be vague. Then you bring them home and find the phone app needed them as well. That is the pattern we now expect from this kind of work, and we plan for it rather than treating it as a bonus.

A Checklist for Taking Any Product to the Watch

This is the order we work in now, whether the product is a water tracker, a hotel app or a fitness membership. The sequence matters, because the early steps stop you building the wrong thing beautifully.

1. Write down the single job the wrist version exists to do, in one sentence.
2. Describe the person's real context at that moment, including what their hands are doing.
3. Sort every existing feature by whether it asks for one movement or for thought.
4. Design the complication or glance first, then the app behind it.
5. Count the decisions left in the flow and remove the ones the phone can handle.
6. Decide what fluidity you are giving up, and say so to the client before the build starts.

Run step six as a conversation with whoever holds the budget. A compromise agreed in week one is a design decision, and the same compromise discovered in week nine is a problem.

The checklist takes an afternoon. On the water project, the equivalent thinking saved us from building a shrunken phone app that would have been quietly uninstalled.

Conclusion

The water tracking app taught us something we now apply to every small-screen brief, which is that the device changes the person, and the person changes the design. A wrist gets three seconds, one hand and divided attention. Everything that works there is built for those conditions from the start.

What we kept on the watch was small. One action, done properly, supported by a glance that needed no opening. What we gave up was the tactile pleasure the phone screen made possible, and giving it up on purpose was cheaper and better than chasing it. The phone app improved as a result, because designing for severe constraints shows you which parts of a product were being carried by available space rather than by genuine usefulness.

Any lifestyle product can go through this. A skincare routine, a coffee subscription, a gym membership, a pet feeding schedule. The question is the same each time, which is what single moment deserves to live on someone's wrist, and whether you are prepared to leave everything else behind.

If you are weighing up a watch version of your product, or wondering whether the moment you have in mind is worth the build, we are happy to think it through with you. Let's talk about your wearable experience.

Frequently Asked Questions