All projects & case studies
Open SourceHealthcareMobile

Open Source · Healthcare

EveryCare

Senior-care coordination — one workspace for solo self-care, families, and professional caregivers (formerly GenxCare and MeraCare).

View source on GitHub
Shipped a care workspace where seniors, families, and professional caregivers coordinate on one product
Built the core loop: join a care circle, invite members, assign recurring tasks and medications, record completions, and escalate overdue items without alarmist language
Made solo use work with no other caregiver, then invite family or professionals later

Overview

Coordination, not surveillance: seniors, families, and professional caregivers use the same app, and the relationship to the senior decides what each person can see and do.

The challenge

Families and professional caregivers coordinate daily care across texts, calendars, and memory. Seniors need independence, not surveillance; caregivers need a shared workspace for tasks, medications, appointments, and a calm trail of what actually happened.

The solution

A React Native + Expo mobile app on a Go modular-monolith REST API, PostgreSQL (Supabase), and Supabase Auth (Apple + Google). Offline-friendly core flows persist in `expo-sqlite`. Every meaningful action writes an immutable `CareEvent` so the activity timeline is not UI state.

What we delivered

  • Go REST API with OpenAPI contract; TypeScript contracts package mirroring the API
  • Care-event pipeline: domain command → transaction → `CareEvent` → notifications
  • Recurring tasks, medication schedules (delete-vs-stop rules once a dose exists), appointments, notes, and per-senior message streams
  • Expo Router mobile app, optimistic updates, and least-privilege relationship permissions
  • Offline core workflows on `expo-sqlite`; Apple/Google sign-in via Supabase Auth
  • Dockerized local Postgres, pnpm workspace, and integration tests gated on `TEST_DATABASE_URL`

Architecture

Expo app (TanStack Query + Zustand + expo-sqlite)
              REST (OpenAPI)
        Go modular monolith
   PostgreSQL · Supabase Auth · Supabase Storage

Key engineering decisions

  • One app, four modes — role and relationship decide the UI, not a separate caregiver binary
  • Go modular monolith + versioned REST instead of microservices
  • Server state in TanStack Query, UI state in Zustand, durable offline data in SQLite
  • Supabase for Postgres hosting, Auth, and storage; the Go API owns business logic

Tech stack

GoReact NativeExpoPostgreSQLSupabase Authexpo-sqlite

Engagement

2026 · Creator & Lead Engineer · Open source

Results

An open-source senior-care platform that treats family and professional care as modes of one workspace, with an event log families can trust.

Lessons learned

  • In care software, the relationship model *is* the product. Build one platform whose permissions follow who you are to the senior — not two apps that have to stay in sync.

Have a hard problem like this?

Let's talk about what you're building.

Start a projectDiscuss your MVPGet a project estimate