# Glucose tracking is fragmented and unreliable
> Source report: https://painfinder.app/reports/glucose-tracking-is-fragmented-and-unreliable

## 1. What we're building
Build a unified glucose and health companion app that becomes the single place to see, log, export, and act on diabetes data across devices. The core product should combine a live glucose dashboard, full history, meals, insulin, exercise, notes, and caregiver sharing in one timeline-based interface, with reliable Health Connect/Apple Health sync, CSV/Sheets export, and support for Dexcom, Libre, Nightscout, xDrip+, Garmin, Apple Watch, and Android widgets. It should also solve the most repeated pain points directly: at-a-glance home-screen/watch visibility, configurable alerts, stable notifications, missed-data recovery, and a clear source-of-truth view when sync breaks.

The must-have feature set should include glucose + insulin together, correction bolus entry, meal logging, trend graphs, summaries like 30/60/90-day averages, manual entry, export/backup, and caregiver access controls. The strongest feature asks point to additions that make the app genuinely useful rather than just another viewer: Apple Watch complications, Siri/voice queries for glucose, Nightscout compatibility, Health Connect integration, and tools for pattern analysis that connect glucose to meals, exercise, sleep, cycle context, and insulin-on-board. Position it as the trusted hub that replaces app-juggling, spreadsheets, and fragile shortcuts with one dependable diabetes workflow.

**Working name:** GlucoPulse
**Tagline:** Unified glucose + insulin timeline with reliable sync, alerts, and CSV export.
**Main goal:** Users can open GlucoPulse and immediately see accurate glucose history, add insulin/meal context, and export reliable backups.
**Target users:** People with diabetes who use CGMs and want one phone/watch hub that works across Apple Health/Health Connect and supports caregiver sharing.

**Main user result:** A user gets a unified timeline showing current glucose plus insulin/corrections and meal entries, with dependable export and a clear last-known source-of-truth view when sync breaks.
**5-minute outcome:** In the first 5 minutes, the user connects at least one data source (Apple Health or Health Connect), sees glucose on the Dashboard/Timeline, and exports a CSV backup for the last 24 hours.
**What we solve first:** Reliable ingestion into one timeline + visible data recovery state + CSV export (so the user can trust their history and analyze later).
**Out of scope for MVP:**
- Apple Watch complications and Siri/voice queries
- Full multi-CGM receiver modes (Dexcom receiver phone mode, xDrip+) in MVP
- Advanced pattern analysis recommendations beyond basic averages

## 2. Why this is worth building
- Verdict: **MEDIUM** (68/100)
- The problem is strongly and repeatedly confirmed across many chunks: users complain about fragmented health stacks, broken syncing, unreliable CGM behavior, and missing analysis tools. The same pain shows up in different forms for Google health products, Dexcom/Libre apps, Apple Health/Health Connect, and third-party diabetes workflows. The consistency of manual workarounds is especially telling: people are already building their own exports, dashboards, and bridges because the official experience is not sufficient. This is a high-confidence opportunity for a unified, trustworthy glucose-and-health layer.

**Current pain:** Glucose visibility is scattered across CGM apps and health platforms, and sync can be incomplete or clipped. Users also struggle to get usable glucose + meal/insulin context when devices/apps are flaky.
**Current workaround:** Users combine Health Connect + other apps to move data, and manually log or export to spreadsheets/Sheets. They also rely on CGM-specific apps (e.g., Dexcom/Nightscout) for partial visibility and export later.
**Why existing tools fail:** Health platforms (Apple Health/Health Connect) may receive clipped/inaccurate glucose or fail to connect, forcing workaround stacks. CGM apps don’t provide a unified diabetes timeline with reliable source-of-truth, caregiver sharing of actual values, and stable notifications.

## 3. Must-have capabilities
### 3.1 Unified timeline for glucose, meals, insulin, exercise, sleep, notes, and medication
**Why:** Users repeatedly asked for one place to track diabetes alongside broader health context.

### 3.2 Reliable Health Connect sync with Google Fit and Samsung Health, plus Apple Health integration
**Why:** Users want the app to be the bridge between major health ecosystems instead of another silo.

### 3.3 Export and backup health data, including CSV export and date-range export
**Why:** Users want a dependable backup path and a way to move data into Sheets and other tools.
**Evidence:** post #12166 — *"Export Health Connect data to Google Sheets"*

### 3.4 Home-screen, lock-screen, watch, and exercise-time glucose visibility
**Why:** At-a-glance access is a top pain point, especially during workouts and when users need quick checks.

### 3.5 Configurable alerts with stable notifications and fewer false low alarms
**Why:** People want better critical alerts and less noisy overnight sensing.

### 3.6 Manual glucose entry, correction bolus entry, and insulin-on-board aware dose calculation
**Why:** Users want to log events directly and calculate doses using active insulin, not just view CGM data.

### 3.7 Caregiver sharing with actual glucose values, role-based permissions, and edit/input access
**Why:** The product must support remote monitoring without reducing sharing to alerts-only.

### 3.8 Multi-source CGM compatibility including Dexcom, Libre, Nightscout, xDrip+, and Dexcom receiver/phone receiver mode
**Why:** Users are forced into workaround stacks today and want one app that can ingest from the sources they already use.
**Evidence:** post #12329 — *"Can it grab data from nightscout?"*

### 3.9 Summary analytics for 30/60/90-day averages, trends, and pattern analysis tied to meals/exercise/sleep
**Why:** Users want longer-range summaries and better cross-domain insight, not just raw graphs.

## 4. Use cases & user stories
GlucoPulse MVP provides a phone-first dashboard and unified timeline for glucose + insulin (including correction bolus) + meal entries. It supports at least one mainstream health-source sync (Apple Health or Health Connect), provides stable alerts configuration, and offers CSV export for backups.

### Use cases
**4.1 A person with diabetes reviews overnight glucose, meal entries, and alerts in one morning workflow**
After waking up, the user opens the app and immediately sees current glucose, overnight lows, and the last meal and insulin entries on a single timeline. Because the app syncs from Apple Health or Health Connect and keeps a visible history even when CGM apps are flaky, they can compare sleep, dinner, and correction bolus timing before deciding whether to log a manual correction and share the update with a caregiver.

**4.2 A caregiver and the person with diabetes coordinate around real glucose values during the day**
A parent or partner receives a shared view that shows the actual glucose number, trend, and recent event history rather than a vague alert. If the device sync breaks, they still see the last known values and can add notes or insulin/meal events, while the primary user exports the data to Sheets later for review with a clinician or for a weekly reflection.

### User stories
- **As a Person with diabetes using multiple devices**, I want to see glucose, insulin, meals, sleep, and exercise in one timeline, *so that* I can understand what caused a spike or low without jumping between apps
- **As a Caregiver**, I want to receive the actual glucose number and have permissioned access to events, *so that* I can help respond quickly and keep an accurate shared record

## 5. Pages & form factor
**Form factor:** Cross-platform mobile app with cloud sync and companion web dashboard
**Why:** The core pain is continuous glucose visibility and reliable data aggregation across phones, watches, and caregiver workflows, which is inherently mobile-first. A companion web dashboard is needed for deep analysis, exports, and caregiver/admin management, while the mobile app handles logging, alerts, and wearable access in daily life.

### Pages
**5.1 Dashboard**
Primary home screen for the user's current glucose status, recent trends, and quick access to the most important actions.
Key elements:
- Current glucose card with trend arrow and timestamp
- Time-in-range / average glucose summary cards
- Recent timeline preview
- Active alerts banner
- Quick-add buttons for meal, insulin, exercise, note, and glucose
- Sync status indicator

**5.2 Timeline**
Unified chronological log of glucose and all context events so users can see cause-and-effect across meals, medication, sleep, exercise, and notes.
Key elements:
- Filter chips by event type
- Unified event list with glucose readings and context entries
- Expandable event cards
- Correlation markers between meals and glucose changes
- Date picker / jump-to-day control

**5.3 Log Entry**
Fast capture screen for manual or scanned data entry, including future-dated food logs and corrections when sensor data is missing or wrong.
Key elements:
- Entry type selector
- Food search / barcode / meal notes
- Glucose value entry
- Insulin and correction bolus fields
- Date and time controls including future date
- Save and repeat buttons

**5.4 Insights**
Analytics page for trends, averages, comparisons, and personalized glucose response insights across time ranges and categories.
Key elements:
- 30/60/90-day trend charts
- Average glucose and GMI cards
- Meal response comparisons
- Time-in-range and variability charts
- Searchable insights list
- Export controls

**5.5 Alerts**
Control center for glucose alarms and notification behavior, with emphasis on reliability and fewer false lows.
Key elements:
- High/low threshold settings
- Critical alert toggles
- Alarm quiet hours / sleep mode
- Alert history
- False alarm feedback actions
- Per-device notification status

**5.6 Sharing**
Caregiver and follower management area for permissions, live sharing, and role-based access to actual glucose values and edits.
Key elements:
- Caregiver list
- Role and permission editor
- Live glucose share preview
- Edit/input access toggles
- Stop sharing control
- Invite link / QR flow

**5.7 Integrations**
Connection and import/export management for CGMs, Health Connect, Apple Health, wearables, and backup destinations.
Key elements:
- Source connection cards
- Import status / last sync timestamps
- Health Connect permissions
- Apple Health write/read controls
- Export destinations
- Manual CSV upload/import

### Key functions
- **Import CGM data from multiple sources** *[on: Integrations]*
  - Trigger: User connects a device or uploads a supported source file
  - Pulls glucose readings from Dexcom, Libre, Nightscout, xDrip+, receiver modes, or CSV imports into the unified timeline.
- **Sync Health Connect data** *[on: Integrations]*
  - Trigger: User enables background sync or refreshes manually
  - Keeps glucose-adjacent data from Google Fit, Samsung Health, and other Health Connect sources in sync with the app.
- **Write glucose to Apple Health** *[on: Integrations]*
  - Trigger: User toggles Apple Health export on iPhone
  - Writes full-range glucose records into Apple Health instead of clipped or partially stored values.
- **Add manual glucose reading** *[on: Log Entry]*
  - Trigger: User taps quick-add glucose or enters a reading after fingerstick
  - Creates a manual glucose event with timestamp, source label, and optional notes for cases where the CGM is wrong or unavailable.
- **Record correction bolus** *[on: Log Entry]*
  - Trigger: User enters insulin correction dose from the quick-add menu
  - Logs correction insulin as a first-class event and attaches it to current glucose context for later analysis and IOB calculations.
- **Calculate insulin on board** *[on: Dashboard]*
  - Trigger: User opens dose helper or enters a bolus amount
  - Estimates remaining active insulin to help users make safer correction decisions without re-entering the same math each time.
- **Export date-range data to CSV** *[on: Integrations]*
  - Trigger: User selects a date range and taps export
  - Exports health and glucose records for a specific interval into CSV for spreadsheets, backup, or analysis.
- **Export Health Connect to Google Sheets** *[on: Integrations]*
  - Trigger: User chooses Google Sheets as export destination
  - Pushes selected Health Connect and glucose data into a spreadsheet for reporting, sharing, or personal analysis.
- **Share live glucose with caregivers** *[on: Sharing]*
  - Trigger: User invites a follower or caregiver and enables live sharing
  - Shares actual glucose values and trend data with permissioned viewers rather than just alarms.
- **Disable follower access** *[on: Sharing]*
  - Trigger: User opens a follower row and taps stop sharing
  - Immediately revokes a follower's access to glucose data and future updates.
- **Configure false-low protection** *[on: Alerts]*
  - Trigger: User adjusts overnight alarm behavior or marks an alert as inaccurate
  - Lets users tune low-threshold behavior and sleep-time alert sensitivity to reduce nuisance alarms.
- **View exercise-time glucose** *[on: Dashboard]*
  - Trigger: User opens workout mode or starts an exercise session
  - Surfaces current glucose in a high-visibility, low-interaction view optimized for exercise and wearable use.

### UX details
- **Dashboard:** Default the home screen to current glucose, trend arrow, and a compact time-in-range summary above the fold, because users want immediate state visibility rather than buried charts.
- **Timeline:** Render glucose readings and meal/medication/exercise entries in one chronological stream with inline correlation markers, since users explicitly want meal logs tied to glucose history.
- **Log Entry:** Allow backdated and future-dated entries for food, because users asked to log meals on a future date and need flexibility for planning and missed captures.
- **Alerts:** Provide a dedicated sleep mode that de-emphasizes noisy notifications and prioritizes only truly critical lows/highs to address overnight alarm fatigue.
- **Sharing:** Show the actual glucose value in shared caregiver views and offer a hard revoke action for any follower, not just alert-only sharing.
- **Integrations:** Support explicit source tiles for Health Connect, Apple Health, Dexcom, Libre, Nightscout, and xDrip so users can see what is connected and what is missing at a glance.
- **Exports:** Offer regular backup plus one-off date-range export because users need both routine safety copies and targeted analysis files.
- **Android / Wearables:** Treat watch and lock-screen visibility as first-class surfaces, since users want glucose readable during exercise and without opening the phone.

## 6. Monetization
**Model:** (unspecified)

## 7. Competitors to beat
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| Dexcom G7 | Reported to give impossible low readings, beeping, and needing calibration; another commenter says their G7s fail after about 4 days and calibration does not work. | about $50 or $60 per month; also cited as about USD$4400 per year for consumables in one comment | 29 |
| Google Fit | Users say it does not consolidate sources cleanly and can show the phone as the source instead of a true combined step count. | not specified in this chunk | 26 |
| Apple Health | Used as a destination, but users say it is receiving clipped/inaccurate glucose data and should be able to store full-range records. | unknown | 21 |
| Health Connect | One user says steps never appear even though other data does, and another says it is not connecting at all. | not mentioned | 14 |
| xDrip+ | Not a direct solution to the complaint; it is offered as an Android workaround for syncing glucose data. | not specified in this chunk | 13 |
| Nightscout | Mentioned as a partial workaround for Garmin, but not enough by itself to solve the full Garmin-to-CGM issue for the user. | not stated | 9 |
| Dexcom Clarity | Used for review/reporting, but in this chunk it is described as moving stats around and not being straightforward to find. | Not mentioned | 8 |
| Samsung Health | Used as a comparison point; no direct verdict other than a question of how Google Health compares. | not specified in this chunk | 7 |

## 8. Distribution
- Top subreddits to launch in: r/Type1Diabetes, r/diabetes, r/GooglePixel, r/dexcom, r/diabetes_t1, r/Android, r/type2diabetes, r/GoogleFit, r/healthIT, r/minecraftbuilders

## 9. Users & roles
**Primary persona:** Diabetes patient (multi-device CGM user)
**Secondary personas:**
- Caregiver / remote supporter

**Roles:**
- **Caregiver viewer** — Can view shared glucose values and timeline events within granted time ranges; cannot delete or change logs.
- **Primary user** — Can import, edit, and manually log glucose/meal/insulin events; can grant/revoke caregiver access.
- **Caregiver editor** — Can add notes/events (optionally insulin/corrections depending on permission settings).

## 10. Data model & integrations
- (no data model extracted)

## 11. States
**Empty state:** The app shows an onboarding card to connect Apple Health/Health Connect, with a blank Dashboard and “No data yet” timeline.
**Error state:** The app shows “Sync failed” with last-known glucose timestamp and a “Try backfill / Export available data” action.

## 12. Analytics & metrics
- (not synthesized for this report)

## 13. Risks & open questions
- (no risks/questions extracted)

## 14. Post-launch
- See https://painfinder.app/reports/glucose-tracking-is-fragmented-and-unreliable for DM-able hot leads (workarounds × buying intent).
- See https://painfinder.app/reports/glucose-tracking-is-fragmented-and-unreliable for verified key quotes you can use as landing copy.

## 15. Suggested build order (3-week MVP cut)
- Week 1: §3 must-haves + §5 page 1.
- Week 2: §5 remaining pages + auth/persistence if needed.
- Week 3: §6 monetization wiring + analytics + launch checklist.

## 16. Setup hints (your stack overrides these)
- `pnpm create next-app . --typescript --tailwind --app`
- `npx shadcn@latest init`
- The agent SHOULD ask the user before committing to a stack.

## 17. How to use this file
You're an AI coding agent reading this in AGENTS.md. Your job:
1. Confirm the stack with the user (their preferences override this file).
2. Scaffold an MVP covering §3 + §5 page-1 first.
3. Defer §6 (monetization) and §14 (post-launch) until §3 ships and works.
4. Re-fetch the live PRD anytime via:
   curl https://painfinder.app/api/public/reports/glucose-tracking-is-fragmented-and-unreliable/export.json?size=compact

## 18. Verbatim key quotes (top 10)
> "Apple and Google still allow it"  
> — Privacy & sharing, post #12542

> "This app is fucking evil"  
> — General research & advice, post #12542

> "I always report them cause they are also making illegal claims"  
> — General research & advice, post #12542

> "The Google Fit - Fitbit  - Health Connect fragmentation has been infuriating."  
> — Device integration, post #12240

> "if this ties them all together i'm all for it."  
> — Device integration, post #12240

> "wait, what about Google Fit?"  
> — Device integration, post #12252

> "I would _love_ to use this.

However, I don't trust Google to not sell this information to my Health Insurance provider"  
> — Privacy & sharing, post #12252

> "they have record of that."  
> — Health records & export, post #12543

> "It does make it easy to manage and cancel subscriptions."  
> — General research & advice, post #12542

> "Epic wants $25k just to talk to them."  
> — Device integration, post #12513

## 19. Manual workarounds users cobble together (top 15)
1. **glucose logging automation** — *User built their own regex-based Shortcut steps to extract glucose values from screenshots and write them into Apple Health.*
   > "I used your idea to get the sensor data from the Libre 3 App to Apple Health"
2. **nutrition tracking** — *Manual food weighing and meal entry to track nutrients/carbs/calories, then stopping due to burden.*
   > "I used an app for a month diligently, weighing everything and entering every meal"
3. **healthcare app compliance platform** — *Founder describes the broader process of building healthcare software as requiring heavy compliance work rather than a turnkey tool.*
   > "Every simple feature becomes a compliance nightmare."
4. **all-in-one health tracking hub** — *The user combines multiple apps manually instead of using a single health hub.*
   > "I cobble together a few that talk to Health Connect."
5. **health data export / analytics** — *The author created their own export app to move data out of Health Connect.*
   > "I built the **Health Data Export** android app"
6. **CGM-aware display clock** — *The commenter relies on a cheap generic clock as a substitute.*
   > "we currently use a cheap AliExpress clock that works but that is another level."
7. **diabetes-specific food response tracking** — *The commenter recommends measuring food impact manually rather than relying on the app alone.*
   > "I would get a manual glucose monitor and test strips and start seeing how your body responds to different meals and snacks"
8. **glucose management coaching or logging** — *The poster manages glucose through diet and walking rather than a dedicated app workflow.*
   > "I do go out for lot of walks and lost a lot of weight, at this point I am just managing my glucose with diet."
9. **account migration / data portability** — *Recreated accounts to avoid future Google account/data lockout issues*
   > "I ended up creating a new account and started over from scratch with my health journey"
10. **health data migration / wearable switch** — *Exported Fitbit data and replaced the device ecosystem with Garmin*
   > "I was using Fitbit with Workspace (Legacy) account, but since they have been forcing us to move to the lame gmail account I just exported all data and bought Garmin."
11. **data export / backup** — *Uses Google Takeout to export Fitbit data*
   > "I think you might be able to export your Fitbit data at [https://takeout.google.com/]"
12. **customer support / payout correction** — *Escalated the payout issue to support after the form failed*
   > "I contacted Google Support right away"
13. **refund / payout UX** — *Manually navigating and re-checking the form to avoid the wrong payout choice*
   > "I was simply checking out the options on their form and clicked on the cash payment. It locked me in"
14. **bug investigation / QA** — *Manual testing to diagnose the camera bug*
   > "I performed a new test"
15. **bug reporting / support** — *Filing/iterating bug reports with Google to chase a fix*
   > "I am immediately updating my official bug report with Google"

## 20. "I would pay for…" quotes (top 10)
1. wants: Google Health app / unified Google health experience
   > "I would _love_ to use this."
2. wants: pre-built healthcare components
   > "Would've saved me a year of pain and most of my money if I'd known that from the start."
3. wants: not a buying intent for health; excluded?
   > "What about a new wallet/payment system? Or maybe a new message app? We don't have enough of those!"
4. wants: A full-featured health logging app / Android health hub
   > "I discovered **[Guava Health](https://guavahealth.com/)** and it looks exactly like what I was searching for!"
5. wants: A promising Android health hub alternative
   > "Check out Guava Health. Thank me later."
6. wants: A true Apple Health equivalent on Android
   > "I would like to know as well."
7. wants: A reliable export/analysis tool for Health Connect data
   > "I tried to find a reliable way to get my Health Connect data out of Android and into something I can actually analyze"
8. wants: Future-dated food logging
   > "please let me log food on a future date."
9. wants: Macro target tracking
   > "I'd love to be able to set protein/carb/fat targets"
10. wants: Progress photo storage
   > "Please add progress photos!"

## 21. Hot leads summary
- 187 hot leads identified (users who BOTH built a workaround AND signaled buying intent)
- Tier breakdown: 9 hot / 29 warm / 149 cold
- DM-able usernames available at: https://painfinder.app/reports/glucose-tracking-is-fragmented-and-unreliable#hot-leads (kept off this file for privacy — see live report)

## 22. Full competitor list (top 10)
| Name | Why it fails | Price | Mentions |
|---|---|---|---|
| Dexcom G7 | Reported to give impossible low readings, beeping, and needing calibration; another commenter says their G7s fail after about 4 days and calibration does not work. | about $50 or $60 per month; also cited as about USD$4400 per year for consumables in one comment | 29 |
| Google Fit | Users say it does not consolidate sources cleanly and can show the phone as the source instead of a true combined step count. | not specified in this chunk | 26 |
| Apple Health | Used as a destination, but users say it is receiving clipped/inaccurate glucose data and should be able to store full-range records. | unknown | 21 |
| Health Connect | One user says steps never appear even though other data does, and another says it is not connecting at all. | not mentioned | 14 |
| xDrip+ | Not a direct solution to the complaint; it is offered as an Android workaround for syncing glucose data. | not specified in this chunk | 13 |
| Nightscout | Mentioned as a partial workaround for Garmin, but not enough by itself to solve the full Garmin-to-CGM issue for the user. | not stated | 9 |
| Dexcom Clarity | Used for review/reporting, but in this chunk it is described as moving stats around and not being straightforward to find. | Not mentioned | 8 |
| Samsung Health | Used as a comparison point; no direct verdict other than a question of how Google Health compares. | not specified in this chunk | 7 |
| xDrip | Used as a workaround recommendation because Dexcom's Android app is buggy; not presented as an official replacement. | - | 9 |
| mySugr | Mentioned as a recommendation for Bluetooth glucometer integration, but not described as solving the broader workflow. | paywall for some features; free with an Accu-chek meter | 7 |

## 23. Where this conversation lives (top subreddits)
- r/Type1Diabetes (57 posts)
- r/diabetes (56 posts)
- r/GooglePixel (56 posts)
- r/dexcom (53 posts)
- r/diabetes_t1 (52 posts)
- r/Android (29 posts)
- r/type2diabetes (24 posts)
- r/GoogleFit (19 posts)
- r/healthIT (12 posts)
- r/minecraftbuilders (3 posts)