Back to all projects

Healthcare / App case study

Ruby / FLOW_RUBY

An offline-first educational cycle-care prototype with pill tracking, local Dexie storage, a Capacitor mobile shell, optional single-tenant Supabase sync, and consent-controlled bring-your-own-key AI connections.

Offline-first educational health prototype

01 / Overview

What it’s built for.

Keep core health logs usable offline while offering optional sync and consent-controlled external assistant connections.

Who it serves

People exploring personal cycle logs and pill schedules in a device-local companion.

02 / Features

Inside the app.

Personal logging

Organize cycle and health logs, insights, trends, and settings in a mobile-first interface.

Pill schedules

Record taken or missed doses, inspect a recent streak, and show due or missed check-in alerts.

Optional connections

Use native bridges, configured cloud sync, or a bring-your-own-key assistant with category-level consent.

03 / Workflow

From task to outcome.

  1. Complete onboarding and record personal logs locally.

  2. Configure a pill schedule and record daily doses.

  3. Review trends and informational cycle estimates.

  4. Optionally enable configured sync or choose what context is shared with the assistant.

04 / Technical layers

How the pieces work.

Interface

React · TypeScript · Vite

Touch-oriented screens connect today’s logs, insights, trends, and settings.

Local logic and storage

Cycle engine · Dexie · IndexedDB

Core logs and tracking work on the device without a Supabase connection.

Mobile shell

Capacitor · Native bridges

Android/iOS project shells contain notification, haptic, widget, and other platform integrations.

Optional services

Supabase · BYOK AI transports

Cloud sync follows the documented single-tenant model; external AI context is consent-controlled.

05 / Limitations

What to keep in mind.

  • Cycle estimates are informational, not contraception or medical advice.
  • The shared sync schema requires owner-scoped authentication and RLS before public multi-user use.
  • Source code and mobile shells do not establish physical-device acceptance or app-store release.

06 / Evidence

Follow the source.

These descriptions were reviewed against the linked source snapshot on October 12, 2026. Repository code and documentation may evolve after this review.