Inspiration
What it does
How we built it
Challenges we ran into
Accomplishments that we're proud of
What we learned
What's next for Elderhub: Family Care Log
Inspiration
Most medication apps assume the person holding the phone is tracking their own pills. Elderhub started with a different question: what does a family member need when they are helping a parent or spouse? The answer was not another alarm. It was one current care record that could be read and acted on by the people sharing the work.
What it does
Elderhub: Family Care Log gives each person their own medications, schedules, dose history, visits, vitals, tasks, bills, notes, contacts, check-in status, and emergency card. The Today screen brings the next actions together. Helpers can mark doses and tasks on someone else’s behalf, and the emergency card can be read or shared as plain text. The first person gets every feature free, invited family members are free, and the record stays usable offline.
How we built it
The app is a native iOS app built with Swift 6, SwiftUI, and SwiftData. SwiftData is the local mirror so every screen renders without waiting for a network. Supabase provides family circles and row-level access control. The sync engine is offline-first, with an outbox and per-entity conflict rules. RevenueCat powers Elderhub Plus, which unlocks additional care recipients while keeping invited helpers free. Scheduling, recurrence, Today summaries, reminders, and exports are pure or shared services so the rules stay testable outside the views.
Challenges
The hard part was not entering a medication. It was keeping the record trustworthy across family members and unreliable connectivity. We designed reminders around one request per person per dose time to fit the device budget, made dose log IDs deterministic so correcting a dose does not create duplicate history, and kept account and handset roles separate. Sharing is scoped per recipient, and losing access removes only that person’s local copy without deleting the family record.
What I learned
A family care product has to make the next action obvious while staying honest about what it does. Empty states, offline behavior, permission boundaries, and emergency presentation are part of the product, not edge cases. The result is a care log that can start locally and become a shared circle when the family is ready.
Log in or sign up for Devpost to join the conversation.