hunzaboy
My motivation wasn't really to replace existing apps. I built it because this is the workflow I actually needed.
For example, my mother is 70 and isn't comfortable using apps. Someone else usually has to help her take the reading, and I need to keep track of the data for her. I wanted something where whoever is helping can simply open her phone, enter the reading, and have everything relevant in one place — readings, meals/photos, medication, notes and A1C.
There are definitely more sophisticated solutions out there, but they aren't always practical or available for everyone. In some places, CGMs and connected meters aren't covered by insurance, aren't readily available, or simply aren't realistic to use.
So SugarTrack is deliberately boring: no Bluetooth, no USB, no account, no cloud, no subscription. Just a simple log that stays on the phone.
It solves my particular problem, and I figured there are probably other people with a similar situation.
My focus is a bit different though. I’m trying to make the experience as simple and frictionless as possible, especially for non-technical amd old people.
The problem I wanted to solve starts when the readings change. A doctor may ask, “What did you eat around that time?” With this app you can save a photo of the meal alongside the blood sugar reading, notes and medication.
So the goal is less about storing the number and more about keeping the context around the number and making that context easy to share with the doctor.
https://dev.to/hunzaboy/how-to-create-a-clean-bulletproof-em...
Its just how it is currently due to limitation from email renderers and clients.
Emails can be clean and simple but still in HTML. :)