Fixture-first iOS prototype
RelayCare
A consent-aware SwiftUI prototype for explicit family coordination and review-before-sharing updates.
9T1 Labs / iOSRelayCare
- Categories
- iOS
- Year
- 2026
- Role
- Creator
Premise
Coordinate clearly without turning care into surveillance.
RelayCare gives a household a focused Today view, scoped access controls, a review-before-sharing update flow, a manual call handoff, and readable local activity history.
It is deliberately nonclinical and cannot be relied on for emergencies, passive monitoring, safety detection, location tracking, or a guaranteed response.
Interaction
Every shared action stays explicit.
Review today
See check-ins, practical tasks, and fixture activity in one focused list.
Choose access
Decide which family-circle members can see a specific update.
Review wording
Inspect generated fixture transcript text before sharing anything.
Confirm handoff
Choose a fixture contact and review the number before opening the Phone app.
Read history
Use the local activity view to understand what the fixture recorded.
System
A reusable Swift package with deterministic local behavior.
The repository is self-contained and has no third-party runtime dependency, server, API key, or signing identity requirement for the Simulator build.
SwiftUI presentation
- Today
- Circle
- Activity
- Transcript review
- Manual call choice
Domain
- Consent rules
- Coordination tasks
- Delivery wording
- Call coordinator
Fixture repositories
- People
- Activities
- Transcripts
- Receipts
- Online and offline states
- Storage
- All demo people, tasks, decisions, transcripts, and receipts are held in memory.
- Delivery
- A fixture receipt proves only that the injected repository returned the same request identifier.
Boundaries
The language avoids claims the prototype cannot support.
| Area | Current behavior | Not claimed |
|---|---|---|
| Health | User-entered coordination events | Medical advice, diagnosis, treatment, or a health record |
| Safety | Explicit check-ins and manual choices | Emergency monitoring, crisis detection, or guaranteed response |
| Messaging | Deterministic fixture receipt | A real message was sent, received, or read |
| Calls | Opens an iOS telephone URL after review | The Phone app opened, the call connected, or anyone answered |
Build notes
The package and app are designed to verify independently.
Reusable core
The Swift package separates domain and presentation code from the Simulator app entry point.
Tested decisions
Package tests cover consent, delivery wording, store behavior, and the manual call flow.
Reproducible bundle
Build and install scripts produce a signed Simulator application without an Xcode project.
Still unresolved
Real coordination would require a different trust model.
Identity
Accounts, authentication, household membership, and scoped authorization are not implemented.
Delivery
Real messaging, notifications, synchronization, and provider receipts need server-side infrastructure.
Persistence
Device storage, retention, deletion, and cross-device conflict behavior remain outside the fixture prototype.