What’s the most frustrating part of tracking diabetes?
I’m building Blood Sugar Journal — a simple diabetes tracker with AI insights.
Trying to understand what actually annoys people in daily tracking.
Too many inputs?
Bad UX?
Or just not helpful enough?
Would really appreciate honest feedback.
59 views
Replies
I had made a app for tracking car expenses 10-15 years ago. And now we use at home app for tracking babies. When they slept, how much they eat, what was the output ;) .
What we usually forget is to write things down. You are in a hurry, somebody is waiting, something is more important, and a few hours later, you try to remember what was the thing that you wanted to add to the tracker. And at some point, you lose your patience. ;)
If you can think for a fast, intuitive and less intrusive way to add the data, that would be perfect. Voice to text, desktop widgets, shortcuts, images, I don't know, just throwing first thoughts here.
Blood Sugar Journal
@stoyan_minchev Absolutely agree — that’s a very real problem with any tracking app.
The hardest part is usually not the analysis, but actually capturing the data in the moment without breaking your flow.
There’s already an Apple Watch app, which helps with quicker logging, and I’m also thinking about adding things like reminders in the future, plus even faster entry points — for example, a quick action from the iPhone lock screen.
Really appreciate you sharing this. Comments like this are genuinely useful because they point to the real friction, not just features.
@dmitry_mashkin That is why we are all here. To share ideas and to help each other make better products, that satisfy peoples' needs :)
Hello Aria
The inconsistency is what gets people, I think. You do everything right and still get a weird reading, and there is no good explanation for it. That ambiguity is exhausting when you have to track it every day.
I have spoken with a few T2 diabetics using Hello Aria (our AI assistant, launching April 10th on PH) and what they found useful was not a specialized health app but just being able to message naturally about what they ate, how they felt, and then get a simple summary. Not clinical data, just patterns over time.
For your research: what is the biggest drop-off point? Is it consistency (people start then stop logging), accuracy (logs are too rough to be useful), or understanding (they log but do not know what to do with the data)?
Blood Sugar Journal
@sai_tharun_kakirala Yeah, that unpredictability is one of the worst parts.
You do everything right and still get a weird number. After a while, that just messes with your head.
And I agree about natural input, people think in events, not in forms.
From what I’m seeing, the biggest drop-off is consistency.
People start logging, but once it feels like a chore, they stop.
That’s exactly what I’m trying to reduce: less friction, more clear patterns.
From what I’ve seen, the most frustrating part is not just the number of inputs — it’s the cognitive load.
People often don’t know:
what exactly they should track
what actually matters
and how to interpret the data they’re entering
Even if the UI is clean, if users don’t clearly understand what to do and why, it quickly becomes overwhelming and they drop off.
Also, explaining why something is happening (not just showing numbers) is the key for trust — especially in health-related apps.
Blood Sugar Journal
@nadezda_sych Yeah, totally agree.
It’s not just about too many inputs — it’s the mental load behind them.
If people don’t clearly understand what to track, what matters, and why it matters, even a clean UI won’t save it.
And yes, trust comes from explanation.
Not just showing numbers, but helping people understand what may be going on.
That’s exactly the direction I’m trying to move in.