Overview
Carenly is a shared coordination space for two demanding family situations: caregiving and co-parenting. Both require several people to act from the same plan, but the information is usually spread across chat threads, calendars, notes, documents, and informal decisions.
Carenly brings those responsibilities into one workspace with a consistent model for the people, tasks, plans, files, expenses, and decisions connected to a family.
The problem
Family coordination is not only a calendar problem. A missed handoff, an outdated document, an unclear decision, or an unassigned task can create real stress. Existing tools tend to solve one part of the workflow, forcing families to reconstruct the full picture manually.
Product approach
Each Carenly workspace has a type - caregiving or co-parenting - while sharing a common product foundation. The interface centers on Home, Plan, Tasks, Vault, and Team, with specialized workflows layered on top.
Key areas include:
- shared tasks and responsibility tracking;
- plans, handoffs, and calendar coordination;
- a secure document vault scoped to the active family space;
- expense tracking and settlement guidance for co-parenting;
- member and invitation controls;
- decision history, risk nudges, and contextual workspace signals;
- localized email, push, and application experiences.
Architecture
The public landing site is built with Astro. The application uses Expo and React Native for iOS, Android, and web, with Supabase providing Postgres, row-level security, RPC functions, storage, authentication, and Edge Functions.
The data model is workspace-scoped. Cross-record relationships, documents, expenses, invitations, and member access are enforced against the active care space instead of relying only on interface filtering.
My role
I developed the product concept, information architecture, user flows, mobile and web application, Supabase data model, authentication flows, notification system, localization strategy, and deployment operations.
Current status
Carenly is a private product with a public multilingual landing site. The application code remains private because it contains the full product and operational implementation; this page documents the product without exposing private infrastructure or credentials.