3rd Place · Divergent Hackathon

Loading slides…
ExpoReact NativeFirebaseZustandGemini 1.5 FlashNativeWind

KomeKare is a family caregiver coordination app we built natively with Expo and Firebase at the Divergent Hackathon, where it placed 3rd. Caregivers, family members, and healthcare providers all share one patient profile, and Google's Gemini 1.5 Flash summarizes the care data into something each of them can actually act on.

Caregiving is often split between family members, professional caregivers, and medical providers, and none of them see the same picture of the patient. Important information gets lost in text threads, paper notes, and verbal handoffs, and that's how you end up with missed medications and two people doing the same task.

Native Expo app with Firebase as the backend

A native React Native app built with Expo and backed entirely by Firebase: Auth for identity, Firestore and the Realtime Database for care data, and Storage for uploads.

Reason:
With 48 hours, we needed a backend with zero server setup, generous free-tier limits, and real-time sync between caregivers, family, and providers out of the box.

Tradeoff:
We gave up long-term flexibility in the data model (and accepted Firebase's NoSQL model and vendor lock-in) to ship a working real-time app in a weekend.

Zustand with AsyncStorage-backed persistence

Client state (current patient profile, session, cached care data) lives in Zustand, with a persistence middleware bound to AsyncStorage so it survives app restarts.

Reason:
Zustand has so little boilerplate that we could wire up shared state across screens fast without the ceremony of Redux, and still get durable local persistence for free.

Tradeoff:
It has less structure than a more opinionated state library, so as the app grows it takes discipline to keep the state from turning into a pile of ad-hoc shapes.

Gemini 1.5 Flash for AI care insights

Gemini 1.5 Flash summarizes health logs, medication schedules, and caregiver notes into plain-language updates for each person on the profile.

Reason:
Everyone needs a different view of the same data: a caregiver needs a quick task list, a family member needs a plain-language update, and a provider needs a clinical summary. Flash was fast enough at summarizing to work in a live demo.

Tradeoff:
LLMs hallucinate, so care summaries need careful prompting and have to be presented as assistive rather than authoritative, and 48 hours wasn't enough time to harden that as much as it should be.

  • Won 3rd place at the Divergent Hackathon.
  • Built a working native Expo/Firebase prototype in under 48 hours.
  • Demoed Gemini-generated care summaries tailored separately for caregivers, family, and providers.

  • 48 hours forces you to prioritize whatever can actually be demoed, which is a big part of why Firebase and Zustand won: both meant almost no setup.
  • Hallucinations are a much bigger deal in a care app than in most places, because the summary is about someone's medication.
  • A lot of what goes wrong in caregiving is information not making it from one person to the next, and fixing that flow mattered more than adding features.