Technology · Guest status
The best update lives
outside the app.
A guest who has already requested a car should not repeatedly unlock a phone, find a page, and refresh it. The ongoing task belongs on the most glanceable surface the operating system provides.
The distinction
A notification announces a change. A Live Activity carries a changing state.
Push notifications are good interrupts: the request was accepted, the vehicle is ready, payment needs attention. They become noise when every internal step produces another alert.
Apple's Live Activities are designed for an ongoing task visible at a glance on system surfaces such as the Lock Screen and, on supported devices, the Dynamic Island. That makes them a better container for progress than a stack of increasingly stale notifications.
The surface
One journey, two communication tools
Give each tool one job
Push notification
INTERRUPT- Calls attention to a meaningful change
- Can reach a guest without an open app
- Turns stale as the journey advances
Live Activity
ONGOING STATE- Updates one persistent surface
- Shows the current next step at a glance
- Requires platform support and careful lifecycle handling
→Apple documents Live Activities as glanceable progress for an activity, event, or task. Platform locations and constraints are current as of August 23, 2026.
Design a state machine, not a sentence feed
The guest needs a small number of stable states with a clear next action. Internal dispatch events should not leak into the copy.
→When information becomes stale or the task ends, the surface must say so. Apple provides explicit stale and end states rather than expecting the guest to infer them.
Respect the places the system owns
A Live Activity is not a miniature app screen. It appears in different sizes and contexts selected by the operating system.
Glance
Lead with state
Use the few words that answer what is happening now. Property branding is secondary to comprehension.
Action
Offer one next step
If the guest must act, make that action obvious. Otherwise let the surface stay informational.
Freshness
Show uncertainty
A status that cannot update should become visibly stale rather than quietly looking current.
Ending
Resolve cleanly
End the activity when the valet journey ends so yesterday's status does not remain today's instruction.
→Primary sources: Apple ActivityKit documentation and Human Interface Guidelines, reviewed August 23, 2026.
The product test
Can the guest understand the journey without opening anything?
Start a vehicle request, lock the phone, and hand it to someone who did not design the feature. At each state, ask what is happening and whether they need to act. Any hesitation belongs to the interface, not the guest.
The takeaway: the lock screen is not a marketing surface. It is the calmest place to keep a short, changing promise visible.
