Work1Buddy
1Buddy — founding the core companion for a GLP-1 app
GLP-1 companion app
- Role
- Lead mobile developer of the core companion
- Period
- Jun – Sep 2026
- Client
- Insight Labs
- Status
- Shipped
1Buddy walks someone starting GLP-1 medication through onboarding, then lives on a home timeline: shots or pills, food, weight, mood, side effects. I founded and led the core companion — onboarding, auth, the entitlement gate, the home timeline, the food AI pipeline and the reminder system.
Highlights
- Empty repo to 30+ screen onboarding in six weeks
- Two parallel medication products — injectable and oral
- At-most-once push reminders on a scheduled backend
On the App Store
From the 1Buddy App Store listing — Insight Labs' artwork.
- Expo
- React Native
- Supabase
- RevenueCat
- Expo Push
Six weeks from README to product
I took the repository from a README to a shipping core: a thirty-plus screen onboarding flow, Apple Sign-In as the durable identity, row-level-secured profiles, a subscription gate on the home screen, and native tabs. Guests can start onboarding and only become an account when there is something worth saving.
Food logging without the key on the device
Food logging runs as an async job pipeline: the client enqueues, server-side functions do the model work for text and photo identification plus barcode lookup, and the result streams back to the home timeline in realtime. The model credentials never reach the app. Photo upload had to move to a direct file upload path after the standard React Native blob route failed on device.
Reminders that fire once
Medication reminders are the feature where a bug is a real-world consequence — a double-send at 7am is a person taking a second dose. I built per-install device registration, three scheduled push jobs (injection, daily check-in, pill) and at-most-once send tracking, then spent ten commits getting the scheduler correct in production across secret storage, timezone fire windows and token format.
Oral GLP-1 as a parallel product
Pills are not injections with a different label — different cadence, different screens, different logs, different reminder rules. I shipped the oral path as its own product surface, with the injection UI hidden entirely for pill users rather than disabled.
Scope note
1Buddy has a lead contributor who authored the majority of the repository — the attribution stack, the community feed, the AI coach and later feature ports are theirs, not mine. My scope is the core companion described above.
Links



