The patient
A simple Arabic experience, without an email requirement, designed around responding to reminders.
← Selected work
Sanadi / Personal project
Connecting the people around a medication routine.
A personal project exploring Arabic patient experiences, caregiver follow-up and organizational care coordination.
Personal project · Development pausedApplication not currently deployed
Sanadi began with a family problem: helping an older relative keep track of a medication routine when someone could not always be there to remind them.
The first prototype was built during the Replit 10-Year Buildathon in May 2026. The project developed further afterward, exploring distinct experiences for patients, family caregivers and organizations coordinating several care relationships.
- Caregiver sets up a schedule
- Patient receives an Arabic reminder
- Patient records a response
- Missed responses prompt follow-up
- Caregivers see recorded events
- Reports bring the records together
Simplified account of the project’s intended care workflow. A recorded response is not independent proof that medication was taken.
Who the experience is for.
The caregiver
Schedule management, recorded responses and visibility into reminders that need follow-up.
The organization
A proposed layer for coordinating multiple caregivers and patients, with role-specific oversight.
01 / Different needs
One care network. Different experiences.
The patient and caregiver should not have to navigate the same interface. The patient concept uses a simplified Arabic screen and PIN access; the caregiver handles setup and the wider routine.
The project also explored observers, appointments, health records and escalation through push and Telegram. Those ideas broaden the care network, while making clear responsibilities and reliable behavior more important.
02 / Product model
Individual access, organizational coordination.
I explored free access for family caregivers with a possible paid layer for organizations coordinating multiple care relationships. Individuals could operate outside any organization.
The organizational flow used subscription requests and manual approval. Paid prices were never defined, no payment gateway was integrated, no organization requested a subscription and the project earned no revenue. The commercial model remained a hypothesis.
03 / Current state
A paused project, with lessons to keep.
The initial buildathon prototype and later platform work are separate stages. Development is now paused, and only the landing page remains available; the application itself is not currently deployed.
The portfolio value is in the family problem, role-specific design and care-coordination thinking. The project has not established clinical effectiveness or dependable emergency delivery. Ownership verification, security review and a carefully scoped health-data pilot remain conditions before any restart.