01
Capture the meal
Use the camera flow to identify food and estimate carbs, protein, fat, and calories.
Features
Move from meal logging to meal understanding.
GlucIQ brings the surfaces that matter into one calm workflow: photo meal analysis, editable nutrition estimates, CGM context, insulin context, and reviewable history.
Editable estimates
Photo analysis starts the log. You correct the values before saving.
Not dosing advice
Insulin math stays framed as context for your care plan.Dexcom + LibreLinkUp
AI reasoning visible
Meal → response
one editable record from estimate to reviewDexcom + LibreLinkUp
documented integration paths in launch validationFat-Protein Units
FPU-aware insulin math, rare in consumer appsEditable by design
AI estimates stay reviewable before saving Workflow
One loop for the meal decisions that matter
The app experience should stay direct: capture the meal, edit the estimate, add glucose and insulin context, then review the response.
02
Edit the estimate
Adjust portions, language context, and meal details before the record is saved.
03
Add glucose and insulin context
Use connected CGM data when available or log glucose and insulin manually when needed.
04
Review the response
See the meal, glucose movement, insulin context, and notes in a cleaner timeline.
Capability map
What each feature is allowed to claim
Strong health-product copy is specific. GlucIQ should show what the app helps organize while keeping treatment authority with the user and clinician.
Photo meal analysis
Food recognition with editable nutrition estimates before saving.
CGM context
Documented paths for Dexcom OAuth and FreeStyle Libre via LibreLinkUp.
Manual fallback logging
Meal, glucose, and insulin context still work when sync is incomplete.
AI reasoning visibility
Formula context can be shown as explanation, not as autonomous instruction.
Clinician review
Designed around a timeline that is easier to bring into appointments.
Safety language
Insulin-related areas stay framed as informational support.
Review
A better record for the next appointment.
A meal record is only useful when it keeps enough context to answer what happened later. GlucIQ positions the timeline around meal, glucose, insulin, and notes rather than generic wellness metrics.
GlucIQ is informational support. It does not diagnose, treat, or make or automate dosing decisions.
FAQ
Questions people ask before trusting a diabetes app
Can GlucIQ tell me exactly how much insulin to take?
No. GlucIQ organizes meal, glucose, and insulin context, but dosing decisions must follow your clinician-guided care plan.
Are AI carb estimates safe to trust blindly?
No. Estimates are starting points. GlucIQ keeps them editable and clearly separate from treatment instructions.
Does GlucIQ work with any CGM?
Dexcom OAuth and FreeStyle Libre via LibreLinkUp have documented integration paths that are being validated for launch. Stelo, Lingo, Eversense, and health-platform sync are planned.
Can I use GlucIQ without a CGM?
Yes. Manual glucose, meal, and insulin logging is a first-class path. The timeline works the same way.
What is FPU and why does it matter?
Fat-Protein Units estimate the delayed glucose effect of fat and protein. Most consumer apps ignore it; GlucIQ includes it in the visible insulin math.
What if CGM sync is unavailable?
Manual logging keeps the record continuous while a connection is checked or restored.
Is GlucIQ available outside Germany and the US?
GlucIQ begins with DE and US food context. Country-aware recognition expands from there; release availability will be published by region.
What makes this different from a food tracker?
Generic trackers stop at macros. GlucIQ is designed around meal-to-glucose review for diabetes routines, with AI reasoning kept visible.