Why I built SymptomTap

Start with the moment, not the journal

I started SymptomTap with a small question: how little work could it take to record a symptom? Not to explain it, diagnose it or turn it into a detailed diary entry. Just to note what happened while it was still the thing I wanted to record. That distinction became the starting point for the app.

A simple action can grow surprisingly complicated inside software. Open an app, find the right screen, choose a category, fill in a form, decide whether a note is required. Each individual step can sound reasonable. Put them together and the original task starts to feel bigger than it needs to be. I wanted to work in the other direction.

Make the short version useful

My aim is for logging to take a few seconds. The symptoms someone uses most should be close, rather than hidden behind a new search every time. A quick entry should be useful on its own. More detail can have a place without becoming the price of making any entry at all.

This is a product choice, not a claim that I have measured how everyone behaves. My working assumption is simply that fewer steps make an action easier to fit into a day. If recording something feels like opening a complicated journal, it is no longer the small action I set out to build.

There is a practical limit to reducing steps, though. A button still needs a clear meaning. I do not want a short interaction to become an ambiguous one. The question is not just whether an action is fast, but whether someone can understand what they are recording without stopping to decode the interface.

Leave room for different kinds of entries

Not everything fits a single point in time. Sometimes the useful thing to record is a moment. Sometimes it is how long an episode lasts. And sometimes the moment has already passed before there is a chance to make an entry. SymptomTap is built around instant, timed and retrospective entries for that reason.

I also do not want a fixed list to decide what someone is allowed to record. Choosing personal symptoms and triggers is part of the idea. The app should provide a structure for observations, rather than make people translate every observation into the closest label I happened to choose for them.

Sometimes the phone can stay in a pocket

Apple Watch became important because the shortest interaction may be the one that does not start with taking out a phone. Recording from the wrist gives the app a different job: keep the next action obvious, keep the interaction brief, and then let the person get back to what they were doing.

I do not see the Watch as a smaller place to squeeze every iPhone screen. The phone has room for more detail. The wrist is where I want the quick action to stay quick. Thinking about those two roles separately helps me decide what belongs on each device, instead of duplicating everything by default.

A small tool with a clear boundary

SymptomTap is for recording observations, not for diagnosis or treatment decisions. Making an entry easier does not turn the app into a source of medical advice. That boundary matters to the product as much as the buttons do, and I want it to remain clear wherever I describe the app.

The idea I keep coming back to is modest: remove enough friction that recording something remains a small task. The product page is where I keep current availability and screenshots; this note is about the reason behind the work. I am building around that brief, rather than trying to make a journal that does everything.