Conditional reminders (iOS)
Rem-ly
Reminders that fire on a condition instead of a clock — arriving somewhere, a calendar event starting, a contact opening the app, being near another person — targeting yourself or a mutual contact.
A strong case study should explain the workflow, the constraints, and the product judgment behind the interface.
Primary metric
Built, not yet deployed
Product maturity
2/3 shipped signals
Role
Product architecture, condition-engine design, and full SwiftUI/SwiftData implementation.
Challenge
"Remind me at 5pm" fails the moment the useful trigger is a place, a person, or an event — and the condition might be about someone other than whoever receives it.
Approach
A condition engine with one monitor per trigger type (location, calendar, contact-presence, proximity), evaluated against an explicit "subject" that can differ from the recipient, on SwiftUI + SwiftData with Supabase for auth, Realtime, and Edge Functions.
Impact
Reminders that match how people think about follow-ups — "when I see Sarah, remind her about the form" — instead of forcing everything into a timestamp.
Product snapshot
Rem-ly
Product snapshot
Matches how people actually think about follow-ups instead of forcing everything into a timestamp.
Highlights
- Condition engine, per-trigger monitors
- Self or mutual-contact targeting
- Realtime sync via Supabase