Skip to content
Back to Project Archive

Vireo Wellness

Wellness UI demo v2.0.0 — mock meals, glucose charts, simulated devices. Vision is private offline journal; shipped scope is frontend prototype.

Vireo Wellness Logo
// PROJECT_ID
vireo-wellness
// AUTHOR
DHAATRIK CHOWDHURY
// SUBJECT
CASE STUDY
// CLASSIFICATION
PUBLIC // OPEN
// TELEMETRY
STATUS: DEMO // DATA: MOCK // PERSISTENCE: NOT_SHIPPED
// IMPACT.LOG
// FUCKUP_LOG
RECORDED
[ FUCKUP LOG ]  I described Vireo as an offline PWA with IndexedDB and a meditation timer on this site — the repo ships mock-data UI with simulated Bluetooth and no persistence layer.

SYS.STATUS: v2.0.0 demo — polished wellness UI, mock data, simulated devices

Vireo Wellness is a React SPA that demonstrates a calm, mobile-optimized health tracking interface: dashboard nutrition stats, meal logging from a built-in food database, blood glucose charts, and simulated Bluetooth device pairing. The upstream README states it is currently powered by comprehensive mock data.

This page splits vision from shipped because my portfolio previously claimed IndexedDB, PWA install, and meditation features that are not in the repo.

What it is (scope)

Vision (where I want this to go)

  • Private health journal with data on your device — no cloud rent on sensitive notes
  • Offline-first PWA after persistence is wired
  • Real device integrations when APIs exist
  • Calm UX without streak-guilt gamification

Shipped today (what v2.0.0 proves)

SurfaceWhat you do there
Dashboard”Eaten” nutrition summary, interactive blood glucose chart (mock-populated)
Daily MealsLog meals by category; search built-in food DB; view macros
DevicesSimulated Bluetooth scan, pairing animation, battery/status display
TimelineDate picker for navigating logs and goals
ThemePermanent dark mode (Tailwind CSS v4)

Stack: React 19.1, TypeScript 5.8, Vite 6, Tailwind 4, Recharts, Framer Motion, React Router 7, Vitest + Playwright.

Not shipped: vite-plugin-pwa, IndexedDB/local persistence, meditation timer, Web Bluetooth, real health backend.

Who I built it for

  • Developers prototyping wellness UI before backend integration
  • Anyone evaluating meal-logging and chart layouts with realistic mock flows
  • Future-me when persistence and PWA plugins get wired

Not for: users expecting offline journal persistence today, real CGM/device data, or meditation timer functionality.

Fuckups & learnings

  • Portfolio ahead of repo. IndexedDB, 100% offline, meditation timer — marketing fiction at v2.0.0. README correctly leads with mock data.
  • Mock data is a design tool, not a privacy product. Entries do not survive refresh until storage ships.
  • Simulated Bluetooth teaches UX early. Pairing flows and status chips without permission dialogs.
  • Calm UI over streak hell. Wellness surfaces should not punish broken habits.

Honest limitations

LimitationReality
Mock dataCharts and meals demonstrate UI — not your real health records
No persistenceNo IndexedDB/localStorage journal in shipped deps
No PWANo vite-plugin-pwa in package.json
Simulated devicesBluetooth pairing is UI simulation, not Web Bluetooth
No meditation timerNot implemented in this repo

Deep-dive transmissions

Read in order for the full story:

  1. Why Vireo — wellness UI today vs the private journal I advertised — vision vs shipped, mock-data honesty

Run it locally

git clone https://github.com/dhaatrik/vireo-wellness.git
cd vireo-wellness
npm install
npm run dev

Tests: npm run test — Vitest. CI: lint → test → build.

Closing transmission

Polished surface, honest mock data, simulated devices. The journal I want is coming; the demo I have is already useful for UI iteration. Start with why-and-what if you want the full vision-vs-shipped confession.