Comparta

Comparta is a care coordination platform for the people who hold a caregiving situation together: the adult child managing a parent’s medications, the siblings splitting appointments, the nurse and the social worker who need to stay in the loop without living inside a group text.

I built it because the off-the-shelf tools did not fit the shape of the problem. Care is not one to-do list. It is medications and missed doses, appointments, insurance documents, and decisions with real consequences, handled by a rotating cast of family and professionals who each need a different view of the same situation.

The problem

When someone needs care, the coordination scatters. Medication schedules live in one app, the calendar in another, the important documents in an inbox, and the actual decisions in a thread nobody can find later. The work falls hardest on one person, usually a family member, and the context is the first thing lost when a new caregiver steps in. The people doing this work do not need another generic task app. They need a shared place that understands how care actually moves.

How it works

Everything in Comparta is organized around a circle: one care recipient and the group supporting them. Each member has an explicit role, from coordinator down to read-only observer. Inside the circle, the pieces of care are modeled as what they really are. Medications can be logged with dose logging and adherence history. Messages split into a family channel and a professional channel so clinical conversation does not get lost in the everyday chat.

How it is built

Comparta runs on the web and on native iOS and Android, all from one codebase. A shared TypeScript core defines the data types and validation once, so the two apps never drift apart on what a task or a medication is allowed to be. The web app is built on Next.js and deployed on Vercel; the mobile app is React Native; both sit on a single Supabase Postgres backend.

Where it stands

Comparta is a working product, not a prototype. There is a fifteen-table data model live in Supabase, a deployed web application with full authentication and invite flows, and a native mobile app built from the same shared code. The web and mobile experiences are at feature parity, and the design holds a single calm visual language across both, chosen on purpose to avoid the alarm and burnout that clinical-looking software adds to an already heavy job.

What travels

Most of what makes Comparta work is not specific to caregiving. A real role and permission model enforced at the database, one codebase serving web and mobile, shared validation so the clients cannot disagree, and privacy treated as a feature from the first commit. Those are the pieces I reach for whenever software has to be trusted with something that matters.