hunzaboy

SugarTrack is intentionally just a simple log. It doesn't try to replace the glucometer, connect over Bluetooth/USB, or automatically import readings.

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.

This looks really interesting. Thanks for sharing. I’ve already found some really good ideas here for the next version.

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.

True.

Unfortunately, that’s not really an option for my target audience. In remote areas, the issue isn't only the cost. Its availability, access to the devices, internet connectivity, and the expertise needed to set them up can all be barriers. A basic glucometer and a phone are much more realistic.

My use case is a bit different. I’m not trying to replace the meter or its history.

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.

Hello Hacker News,

I’m sharing a small app I built: *SugarTrack*.

I know it’s the age of AI, but I still think there’s value in taking the time to solve simple, practical problems—especially when those problems affect people who aren’t technical.

I built SugarTrack because I was tired of managing blood sugar readings using paper forms and notebooks for someone close to me. We were taking photos of readings, keeping Excel sheets, and writing notes in different places. It worked, but it was messy and difficult to maintain.

I wanted something much simpler: a digital notebook that stays on the phone.

A lot of existing apps require an account, a subscription, or an internet connection. I didn’t need any of that. I just wanted to record readings and have the information available when needed.

*SugarTrack is a free Android app with:*

* No account or login * No internet connection required * No analytics or tracking * Local SQLite storage * Blood sugar readings and notes * Meal photos * Medication tracking * A1C tracking * Graphs for viewing trends * Daily reminders * PDF and CSV export for sharing with a doctor

There’s also a practical reason I wanted this to work offline. In many developing countries, people often have to manage and record their health information themselves, without the connected glucose-monitoring devices and ecosystems that are more common in wealthier countries. A simple offline-first tool can therefore be much more useful than an app built around subscriptions and cloud accounts.

SugarTrack *does not measure blood sugar*. You still use your own glucometer—the app is simply a place to keep and understand your readings.

It’s Android-only for now.

I’d genuinely love feedback from anyone who has had to track blood sugar for themselves or a family member. *What would make a simple app like this actually useful in your day-to-day life?*

How to balance text in HTML without JS. CSS text balance is available now in Canary. Learn and Get Excited!

Fix the Reaction Button UI in Google Meet

Yes, it is for a new template tutorial. Also i am a big Starwars fan :)

https://dev.to/hunzaboy/how-to-create-a-clean-bulletproof-em...

No Registration is required. Just copy and paste directly from the email preview page.

Yes. HTML version are free/MIT but MJML source codes are not for free.

Already fixed that typo. Seems like I need a better spelling plugin ;)

I am glad you found these useful :)

HTML emails have to be coded like this. For best possible results we have to use table layouts and inline css because email clients are tricky and doesn't use latest css properties. So to keep them compatible with all kinds of email clients, the elements have to have inline css. Otherwise it is not even possible to have a decent HTML email which will render correctly on all email clients.

Its just how it is currently due to limitation from email renderers and clients.

I agree with that. However even using little HTML or lots of HTML should make any difference. The email clients are going to treat it the same.

Emails can be clean and simple but still in HTML. :)