Industry
MedTech
Case Study
AI Assistive Care Platform
If Wi-Fi drops mid-task, the person is stuck. That's someone's afternoon, not a bug for next sprint. At brigit.dev I built the backend so instructions work without internet, and caregivers on the web see what's done and what's missed.
Project Overview
Some people need step-by-step help with daily tasks, medication, therapy, routines. Their caregivers need to know what's done and what's missed. At brigit.dev I built the backend for a product where all of this has to work even when the internet doesn't.
I owned the backend and data layer. The mobile app guides the person through their day. The web side lets caregivers set schedules and check progress.
Care app that guides people through daily tasks offline, and lets caregivers see what's happening from a web dashboard.
Services
- UX/UI Design
- Web Development
- Product Strategy
- Mobile Development
Key Deliverables
- Responsive Design
- Custom Development
- User Experience Improvements
Platform Type
Mobile Application
Tech Stack
- TypeScript
- Next.js
- React Native
- Expo
- NestJS
- PostgreSQL
- Drizzle ORM
The Challenge
If Wi-Fi drops mid-task and the instruction image won't load, the person is stuck. That's not a bug you fix in the next sprint, that's someone's actual afternoon ruined.
Caregivers also need to see what's happening without calling every hour. And when there are multiple caregivers, primary, backup, things can't get out of sync silently.
Approach
Offline-first from the start, not bolted on later. Thousands of task images ship inside the app so instructions load instantly, connection or not. That's a lot of storage and bundling work most products skip.
The mobile side stays calm and simple: here's your next task, here's what to do, mark it done. The web side is for caregivers scheduling tasks, assigning who's responsible, and checking what got completed.
The Solution
People using the app see their day as a clear list of tasks with visual instructions that don't need a network to appear. Reminders fire on time. Completed tasks stay completed even if the phone was offline when they tapped done.
Caregivers log in on web, see each person's schedule and progress, assign primary and backup roles, set up medication times and activity reminders.
When connection comes back, everything syncs without overwriting what happened offline. A completed task stays completed. A caregiver change doesn't vanish.
Key Challenges
-
preloading a huge image library for offline use while keeping the app fast to open, not a small packaging problem
-
sync that caregivers and users can trust, no silent conflicts, no lost completions
-
multiple caregivers coordinating around one person without the UI becoming overwhelming
-
multiple languages for people with very different comfort levels with technology
The Outcome
Daily guidance works without internet. Caregivers can finally see what's done and what isn't without calling to check. Fewer missed tasks because reminders and images don't depend on a live connection.
In medtech, reliability isn't a nice extra. It's the whole point.
Context
Built at brigit.dev. The image preloading alone was more engineering than it looks, thousands of assets, instant load, works offline. Most of the interesting backend work was there.
EdTech at the same company can show a loading spinner. Care guidance can't. That difference shaped everything I built.