upvote
Is this just for Type 1 or would type 2 work well also? Seems like it would?
reply
All types. The sugar dashboard allows import of data from different glucose apps, so its goal is to allow you visualize and analyze your data. I hope to integrate with cgms directly if I get some that allow it, and also source from Health connect. Sharing with specific people eg doctor is also a big ask that I'm working on. The other WIP tools will be fore general health, not just diabetes, like carb counting from a photo via AI
reply
Also recently diagnosed and just open sourced how I'm using AI to count carbs + get insulin doses [1]. Biggest issues I've seen to starting a legit business is not having sanctioned access to real-time blood sugar values (the APIs are all one hour behind), and dealing with the FDA. Love the idea of more tech-enabled diabetes management, good luck!

[1] https://github.com/kennedyjustin/BolusGPT

reply
Love this! Thank you for sharing! My backend is also in Go so this is a godsend. Will see how I can incorporate and let you know if I do!

> not having sanctioned access to real-time blood sugar values (the APIs are all one hour behind)

Ah, I didn't know this. One of the prospective tools I had in mind was real time alerting in case of drastic drops eg ping doctor or relative. I think will have to be limited to the apps/tools that do support realtime.

reply
Technically there is unsanctioned access (someone reverse engineered the real-time APIs [1] which I ported to Go). I think the FDA does not want easy access to real-time values so that folks can't easily recommend insulin dosing without oversight. I am personally of the opinion that it is our right to have programmatic access to the real-time data and do with it what we please.

Would love to get in touch to hear more about your long-term vision for the project!

[1] https://github.com/gagebenne/pydexcom

reply
That's so cool! Nice work!! Are you happy to share how you built and host it? How long has it taken you to get it to this point?
reply
Thanks! I started out with a Nextjs full stack on Vercel, with db on Turso but ended up with a React frontend (next on vercel) and Go backend (selfhosted on vps).

Decided to port the backend to Go + postgres (on a Hetzner VPS), and retain the frontend on Nextjs - A lighter weight client, moving most of the compute to the backend API. Few reasons for the port: I've had a lot more success/stability with Go backends, Turso pulled multi-tenant dbs which is what I mostly wanted them for, Nextjs is getting too hard for me.

Go backend is just the std lib (1.22+ server with the nice routing) - I mostly write all the lines in this

Frontend is textbook modern react: React19,next15,tailwind4 - AI mostly writes the code in the frontend (Cursor + Cline + sequentialthinking + context7 + my own custom "memory bank" process of breaking down tasks). AI is really, really good at this. I wrote this https://image-assets.etelej.com/ in literally 2 days 2 weekends ago with less than 10% of code being mine (mostly infra + hono APIs)

reply