CallTime
Family availability coordination with one-tap video calling for grandparents.
Problem Defined
"Families struggle to coordinate quick calls across generations because availability is fragmented across texts, calendars, and ad hoc check-ins."
Strategic Context
Grandparents and family helpers need a low-friction way to know when loved ones are available now versus later.
Competitive Imbalance
General messaging tools optimize for conversation volume, not calm, glanceable availability coordination for older adults.
System Hypothesis
A privacy-preserving availability layer plus one-tap FaceTime launch increases successful family connection moments while reducing coordination overhead.
Process Architecture
How the system was designed, tested, and refined.
DEFINE
Identify where family calling intent breaks down before connection happens.
- • Mapped grandparent-to-family contact routines
- • Reviewed failed-call patterns and rescheduling loops
- • Prioritized low-vision and low-complexity UI needs
- • Early assumptions required too much calendar literacy
- • Dense UI mockups increased hesitation in older testers
- • Users need immediate, confidence-building status cues rather than full schedule detail
- • Reduced state language to available now, busy now, and next available
MAP
Map invite, trust, and availability flow from first install to first successful call.
- • Designed family invite token journey
- • Mapped role boundaries for grandparent and family member
- • Separated raw calendar data from shared availability state
- • Initial flow exposed too many setup tasks before value was visible
- • First value must happen in the first session with minimal setup friction
- • Moved onboarding toward immediate family invite and mock availability preview
VALIDATE
Validate whether derived availability increases call success without exposing sensitive calendar data.
- • Prototype-tested large touch targets with older adults
- • Validated derived-state labels against family expectations
- • Simulated invite acceptance and return flows
- • Long-form legal/privacy copy blocked invite completion
- • Clarity and reassurance copy outperform completeness in early onboarding
- • Kept legal acceptance explicit but reduced first-run cognitive load
EXECUTE
Ship the first operational stack with auth hooks, invites, and availability scaffolding.
- • Built SwiftUI feature shells for auth, home, family, and invite flows
- • Added LEARN bootstrap placeholder service
- • Implemented availability and invite data models
- • Tried to over-spec backend coupling before core client flow was stable
- • A stable client architecture accelerates backend integration decisions
- • Standardized webhook-first LEARN integration path for canonical identity sync
MEASURE
Track whether the system increases successful family call connections.
- • Defined first-call conversion and invite acceptance signals
- • Tracked setup completion bottlenecks
- • Measured availability-state confidence in user interviews
- • Initial telemetry focused on taps instead of completed connection outcomes
- • Connection completion is the north-star metric, not interaction count
- • Prioritized call completion and invite conversion in event design
Rule Application
How doctrine was operationalized.
Intellectual Rigor
01_INT- • Separating derived availability from raw event data
- • Defining observable first-call success metrics before expansion
Privacy constraints and success metrics are encoded in V1 architecture decisions.
Tactical Execution
02_TAC- • Shipping invite and availability scaffolds before advanced social features
- • Aligning identity sync to signed server webhooks
Core connection path reached implementation readiness with minimal dependency risk.
Human Calibration
03_HUM- • Large-touch, low-friction interaction design
- • Reducing language complexity for elder-first confidence
User-facing states are intentionally constrained to reduce decision fatigue.
Machine Leverage
04_AI- • Derived availability synthesis from calendar signals
- • Backend-signed identity synchronization to LEARN canonical records
System can coordinate identity and availability context without exposing raw private data.
Product Architecture
SwiftUI iOS app with invite links, family graph, derived availability states, and direct FaceTime launch actions.
AI Leverage
Derived availability synthesis and intent-aware coordination support without exposing raw calendar details.
Outcomes & Learnings
Families connect faster when availability is glanceable, privacy-preserving, and actioned through a single-tap call path.
Launch System