Flux Tech Logo

I Wanted to Help My Dad Feel Good — So I Built a Free 3D Glucose Tracker

by ayoubFikraGo Published:





There is a specific kind of helplessness that has nothing to do with weakness. It is the helplessness of watching someone you love sit at the kitchen table every morning, pricking his finger, squinting at a number on a tiny screen, and then going quiet. Not scared-quiet. Just calculating-quiet. The quiet of a man doing math he never asked to learn.

That man is my father. And that number — that small, brutal, flashing number — is his blood glucose reading.

I am not a doctor. I never claimed to be. But I am someone who spends most of his waking hours inside AI tools, digital systems, data visualization, and online health research. I know how to build things. I know how to take information and turn it into something a person can actually use. And the day I watched my dad stare at that glucometer with zero context — no trend, no history, no idea what to do next — I made a decision.

I would use everything I know to help him feel good.

That decision became Fikrago GlucoPro — a free, browser-based 3D metabolic dashboard I built from scratch, no backend, no data harvesting, no subscription wall. You can use it right now at https://chrisayoub1.github.io/GLUCOPRO1/. This article is not a sales pitch. It is the story of why I built it, what it actually does, and why a flat chart will never be enough for someone who is fighting for their metabolic life every single morning.

Let us be honest about the state of glucose tracking apps in 2025. Most of them are beautiful on the App Store screenshots and infuriating in real life. You download them, you create an account, you hand over your email, your birthday, sometimes your location — and in exchange you get a line graph. A flat, lifeless, two-dimensional line graph that could have been built in Microsoft Excel in 1998.

The data is there. The problem is that it does not communicate.

Here is what I mean. A glucose reading of 140 mg/dL after lunch means something very different from a reading of 140 mg/dL at 3am. A spike after white rice means something different from a spike after stress. Context is everything in metabolic health — and most apps strip context out completely in favor of a cleaner-looking chart that is easier to code.

Then there is the privacy problem. My father does not want his blood sugar data sitting on a company's server somewhere. He does not want to be a health data point in someone's monetization strategy. He is a human being managing a chronic condition, not a target demographic. The idea that logging your glucose reading means accepting that a corporation now owns that medical information — that this has become the default, the assumed trade-off — is something I find genuinely outrageous. We just decided that was fine. We never even debated it.

And then there is the recommendation gap. You log your data. The app shows you a graph. Now what? Most apps stop right there. They give you the mirror but no map. You can see that your numbers are bad. You still have no actionable direction toward making them better — naturally, sustainably, without immediately defaulting to pharmaceutical dependency as the only option.

This is the gap that Fikrago GlucoPro (https://chrisayoub1.github.io/GLUCOPRO1/) was built to close. Not because I had some grand startup vision. Because my father needed something better than what existed, and I had the skills to build it. That is the entire origin story. No funding round. No pitch deck. Just a son who did not want to feel helpless anymore.

There is a version of this article where I spend three paragraphs explaining why you should "consult a healthcare professional" and hedge every sentence with legal disclaimers. That version is cowardly and useless. The truth is that the people who most need better glucose tools are the ones who have already seen the healthcare professional, already received the diagnosis, already been handed the pamphlet — and are now alone at home trying to figure out what to eat for breakfast. That is who GlucoPro is for.

My father is not a tech person. He has never opened a browser console. He would not know what Three.js is if I explained it to him for an hour. What he knows is that his fingers hurt from testing, that some mornings the number is good and he exhales slowly like he has been holding his breath all night, and that other mornings the number is bad and the whole day gets a shadow over it before it has even started.

When I showed him GlucoPro for the first time, I watched him tilt his head at the screen. The 3D bar chart rotated slowly. Each bar represented a glucose reading — color-coded by severity, spatially arranged by time. He could see, in actual three-dimensional space, that his post-dinner readings were consistently taller than his morning ones. He could see the pattern with his eyes instead of having to calculate it in his head.

He said: "It looks like a city."

That is the most accurate description of what good data visualization should feel like. Not a spreadsheet. A city — with tall buildings where the danger is, and low ground where things are calm. You navigate a city intuitively. You do not need a manual. That spatial intelligence is something flat charts completely waste.

You can build this city yourself at https://chrisayoub1.github.io/GLUCOPRO1/ — no download, no account, just open it in any browser and start logging.

Here is what the tool actually does, without the marketing language. You enter a glucose reading and a carbohydrate count for a meal. The tool logs it, stores it locally in your browser — your device, your data, nowhere else — and immediately renders it into the 3D workspace. The bars grow in real time. You can rotate the visualization, zoom in, look at it from different angles. Over days and weeks, you start to see your metabolic landscape take shape.

The smart recommendation engine watches your latest reading and automatically surfaces relevant natural solutions based on where your numbers land. If your glucose is elevated, it suggests specific metabolic resets and natural support resources — not as a replacement for medical advice, but as a starting point for informed self-research. The difference between being handed a pamphlet and being handed a map is the difference between passive patient and active participant in your own health.

Everything happens on one page. Log, visualize, get recommendations, access educational content — no navigation maze, no loading screens, no app switching. For someone like my father who just wants the information without the friction, that single-page design is not a minor convenience. It is the whole point.

I built it this way because I watched him try to use a different health app once. He clicked the wrong tab, got lost in a settings menu, gave up, and closed the laptop. That app had better features than GlucoPro on paper. It was useless to him in practice. A tool that does not get used is not a tool. It is just code sitting on a server.

Fikrago GlucoPro (https://chrisayoub1.github.io/GLUCOPRO1/) was designed to be used. By my father. By people like my father. By anyone who is done waiting for the healthcare system to hand them something that actually feels human.

The privacy-first architecture matters more than most people initially realize. Your glucose data is some of the most sensitive medical information you produce. It reveals dietary habits, sleep patterns, stress responses, and metabolic function over time. Handing that data to a corporation with a vague privacy policy is not a neutral act. Storing it locally — on your own device, only ever accessible to you — is not a technical workaround. It is a philosophical position. Your health data belongs to you. Full stop.

I have written before on this blog about the intersection of AI tools and real human outcomes — how automation and smart systems are not just productivity tricks for freelancers but genuine quality-of-life technologies when built with actual people in mind. The GlucoPro project sits at that exact intersection. It uses AI-informed recommendation logic, Three.js for 3D spatial rendering, and a zero-backend architecture to deliver something that would have cost thousands to develop commercially just five years ago — and it is completely free. That is what happens when someone builds a tool out of love instead of out of a monetization strategy.

If you want to understand how I think about building free tools that generate real value, explore the Fikrago Tools page: https://www.fikrago.com/p/tools.html

There is a question I keep coming back to, and I do not have a clean answer for it yet.

We live in an era where AI can write legal briefs, generate photorealistic images, pass medical licensing exams, and predict protein structures that stumped scientists for decades. We have more raw computational power aimed at human health than at any other point in history. And yet — a diabetic father in Morocco is still squinting at a tiny screen every morning, getting a number with zero context, and going quiet.

Why is the gap between what technology can do and what ordinary people actually have access to still so enormous?

I think the answer is uncomfortable: most health technology is built for health systems, not for health people. It is built for hospitals that need reporting dashboards, for insurance companies that need risk models, for pharmaceutical companies that need trial data. The individual — the actual human being with the chronic condition — is almost always an afterthought. A data source. An end user in the most passive sense of the phrase.

GlucoPro is my refusal to accept that as inevitable. It is small. It is free. It runs entirely in a browser window. But it was built with a specific human being in mind — my father — and that specificity is exactly what most health tech lacks. When you build for one real person, you automatically eliminate an enormous amount of design waste. You cannot hide behind abstract user personas. You cannot ship a feature that confuses him and call it intuitive. You cannot store his data on a third-party server and justify it with a terms-of-service clause he never read.

You have to build something that actually works for the person sitting across from you at the kitchen table.

If you have a family member managing diabetes or pre-diabetes, I genuinely encourage you to try https://chrisayoub1.github.io/GLUCOPRO1/ with them. Sit next to them. Log a reading together. Watch their face when the 3D visualization renders. See if it changes the way they relate to their own data — from passive observation to active pattern recognition. That shift in relationship is not small. It is the beginning of metabolic agency.

And if you are someone who builds things — with code, with AI tools, with whatever skills you have accumulated — I want to suggest that the most meaningful project you will ever ship is probably not the one with the biggest market opportunity. It is the one you build because someone you love needed it and nothing else existed.

That is the bio-hacking no one talks about. Not the cold plunges or the glucose monitors or the intermittent fasting protocols. The bio-hack of deciding that the person in front of you deserves better tools than what the market has bothered to build for them — and then building it yourself.

My father's numbers are not perfect. This tool did not cure anything. But he understands his data better now. He has context. He has a map instead of just a mirror. And some mornings, when the 3D chart looks like a calm, low city instead of a skyline of spikes, he does not go quiet. He just nods, closes the laptop, and gets on with his day.

That is enough. For now, that is everything.

Try the tool: https://chrisayoub1.github.io/GLUCOPRO1/

Explore more on Fikrago:




 

You might like

View all
Previous Post Next Post
Share to other apps
Copy Post Link