John

Posted on Apr 10

I Built a Free Hydration Tracker with No Signup: Here’s What I Learned

#typescript #webdev #showdev #react

I recently built Drink Daily, a hydration tracking web app designed to be free, simple to use, and available without registration.

🔗 Live app: https://drink-daily.vercel.app/en

This is one of the projects I’m most proud of so far, not just because it works, but because it reflects the kind of products I like building: practical, lightweight, and polished enough to feel good to use.

Why I built it

A lot of small health-related apps create friction too early.

You open the app and immediately hit:

a sign-up wall,
limited functionality,
too much clutter,
or an interface that feels more like a form than a product.

I wanted to build something different:

useful from the first visit
no registration required
clear and focused
pleasant to interact with
good enough to feel like a real product, not just a demo

Hydration tracking felt like a good fit for that kind of experience.

What Drink Daily is

Drink Daily is a free hydration tracking app that helps users keep track of daily water intake without forcing account creation.

The goal was to keep the experience:

frictionless,
fast,
understandable,
and easy to return to.

Instead of overcomplicating the idea, I focused on making the core experience feel smooth and intentional.

What I wanted to get right

When I started building it, I cared about more than “just making it work.”

I wanted the app to feel:

1. Simple

The app should be easy to understand immediately.

2. Lightweight

No unnecessary barriers, no bloated flows, no forced registration.

3. Polished

I enjoy building interfaces that feel refined, so I paid attention to layout, spacing, clarity, and the overall experience.

4. Actually usable

Even for a small app, I wanted it to feel like something people could genuinely use — not just click through once.

What I learned while building it

Building Drink Daily taught me a lot about the difference between having features and creating a good experience.

A few things stood out:

Product decisions matter as much as technical ones

It’s easy to keep adding features, but choosing what not to add is just as important.

Small UX details make a huge difference

Spacing, hierarchy, naming, and flow can completely change how “finished” a project feels.

Friction shows up fast in simple apps

When the app itself is simple, every unnecessary step becomes more noticeable.

Public projects feel different

Building something you’re willing to show publicly makes you think more carefully about quality, clarity, and polish.

What I’d improve next

Like most projects, this one still has room to grow.

Some things I’d like to improve or expand over time:

deeper progress insights
more personalized tracking options
more refinement in the user flow
additional quality-of-life improvements
continued UI/UX polishing

I also want to keep improving how I present and document my public work.

Why I’m sharing it

I’m currently growing my public developer profile and becoming more active in open source and build-in-public style sharing.

This project felt like a good first thing to share because it reflects what I enjoy most:
building practical web apps with a strong focus on clean UI, smooth UX, and modern frontend development.

If you try the app, I’d genuinely appreciate any feedback:

What feels good?
What feels unclear?
What would you improve?

DEV Community