Droplet came to QuidVista with a product that had already gone through five years of research and development, involved over 100 healthcare professionals, and addressed a genuinely serious health problem. The challenge wasn’t the hardware — it was making the experience of using it simple enough for the people who needed it most.
The Problem Droplet Solves
290,000 people are admitted to hospital in the UK every year suffering from dehydration. Over 200 die from it. The people most at risk are older adults — not because they don’t drink, but because the sensation of thirst diminishes with age, meaning the body’s natural warning system stops working reliably long before dehydration becomes critical.
Droplet’s answer to this is elegantly practical: an intelligent capsule built into the base of ceramic mugs and glass tumblers that measures fluid consumption in real time, connects to cloud servers, and automatically compares actual intake against personalised daily targets. When someone isn’t drinking enough, the system knows — and it alerts them, and the people looking after them, before the situation becomes a health event.
The hardware works. The data model is sound. What Droplet needed was a mobile app that could bring all of that together in a way that a 78-year-old with no particular interest in technology could actually use — and that their adult children, checking in from hundreds of miles away, could rely on.
The Challenge: Designing for the Real User
Most software is designed by people in their twenties and thirties for people who are broadly similar to themselves. Droplet’s primary users are older adults who may have limited smartphone experience, reduced dexterity, and low tolerance for friction. Their secondary users are family members and professional caregivers who need clarity and confidence at a glance — not dashboards that require interpretation.
Getting this wrong would mean an expensive, well-engineered IoT device sitting unused in a cupboard because the app was too confusing to set up. Getting it right meant thinking carefully about every step: from the moment someone opens the app for the first time, through pairing their Droplet device, to the moment a daughter in another city checks whether her mother has been drinking enough today.
What We Built
Onboarding that earns trust from the first screen
The onboarding journey was the most critical piece of work. We designed a step-by-step flow that guides users through device pairing, personalisation of hydration targets, and caregiver connection — with clear language, large touch targets, and no assumption of prior technical knowledge. Each screen does one thing. Progress is visible. There is no point at which a user is left wondering what to do next.
We tested and iterated the onboarding flow specifically with the target demographic, not just with people who were already comfortable with technology. That process shaped the final design significantly — the instincts of a confident smartphone user are frequently wrong when the audience is different.
Real-time hydration monitoring
The app surfaces drinking data in simple graphic form — a clear, readable view of how much has been consumed against the day’s target, updated in real time as the Droplet device registers intake. The design prioritises at-a-glance comprehension over information density. The most important thing — are they drinking enough? — is always the first thing you see.
Configurable reminders
Users and caregivers can set visual and verbal reminder intervals at 20, 40, or 60 minutes, giving flexibility for different levels of need. The night-time illumination feature of the hardware integrates with the app’s alerting logic, so reminders are contextual rather than disruptive.
Remote caregiver access
Family members and professional caregivers can monitor hydration status from anywhere in the world through the same app. We built the permission and sharing model to be straightforward to set up — because a feature that takes three steps to configure will frequently not get configured at all.
Why This Kind of Project Matters
Building for non-technical audiences is a discipline in its own right. The tendency in software development is to add capability — more features, more data, more options. Building for older adults requires the opposite instinct: ruthless simplification, constant questioning of whether each element earns its place, and a genuine commitment to testing with real users rather than assuming.
The Droplet app is a good example of what happens when engineering rigour meets thoughtful product design. The underlying platform is technically sophisticated — IoT device management, real-time data sync, cloud infrastructure, caregiver access controls. None of that complexity is visible to the person holding the mug. That invisibility is the point.
290,000 hospital admissions a year is a problem that technology can help solve. But only if the technology actually gets used.