EveryCare

EveryCare

EveryCare is a Truelogics app that helps families coordinate care for an older relative: medications and dose reminders, tasks, a care circle, check-ins and notifications. I co-founded Truelogics with Muhammad Sarmad, who wrote most of this codebase, so my verified share here is small. My part was the MVP care-coordination pull request, per-person medication alarms with a custom Kotlin and Swift native module, a Today screen led by each family member's status, and a 15-second request deadline so a weak signal counts as offline. The alarm work was still on an unmerged branch in late October 2026.

co-founded

mobile app

Type

Mobile app · Mobile health: family care coordination

Role

Truelogics co-founder/partner (scope: backend/API, mobile/frontend, infrastructure); a small verified commit share in this repo, focused on mobile and API features.

Built with

TypeScript, React Native (Expo), Kotlin, Swift, Go, PostgreSQL, OpenAPI

Also uses

Go chi, Supabase Auth, TanStack Query, Docker Compose, Railway

Last active

2026

What it does

Per-person notification or ringing alarm per medicine, with Taken / Skip / Remind.
Today screen showing each family member's status and who recorded outcomes.
15 s API deadline so weak signal counts as offline.
MVP care coordination and lifecycle controls (PR #15).

How it is built

A Go modular-monolith REST API and an Expo app, kept in sync by TS contracts mirroring the API and an OpenAPI route contract; numbered docs are the engineering source of truth.

My part

Delivered the MVP care-coordination, lifecycle, branding and medication-alerts PR.
Designed and built per-person medication alarms, including a Kotlin/Swift Expo native module.
Added Go API handlers, a Postgres migration and contract updates for reminder styles.
Built the family-status Today screen and the offline-tolerant request deadline.

Decisions

Allow ringing alarms, scoped per user so one person's choice never rings another's phone.

Challenges

Ringing alarms at dose time on both platforms needed a custom native module (Android activity/receivers, iOS module).
Weak mobile signal had to be treated as offline rather than hanging requests.