iOS Live Activities: order and arrival tracking on lock screen
Short answer: A Live Activity is a small, constantly updated card on the iPhone lock screen and in the Dynamic Island that shows the progress of something happening right now: an order being prepared, a driver on the way, your place in a queue. Your server keeps it current with special push notifications, within limits Apple sets (an activity can run for up to eight hours, and its data is capped at 4 KB). Android offers a comparable feature called Live Updates. It's worth building when customers would otherwise open your app repeatedly to check a status.
If your app takes orders or bookings that unfold over minutes or hours, your customers probably open it again and again to see where things are. Live Activities move that status to where they look anyway: the lock screen. Here's how they work, what Apple allows, and where they make sense for a small business app.
What a Live Activity is
Apple's ActivityKit documentation, Displaying live data with Live Activities, describes Live Activities as showing your app's current data on the Lock Screen, in the Dynamic Island, in CarPlay, and on a paired Mac or Apple Watch. People can tap one to open your app, ideally deep-linked to the matching screen, and Live Activities can include buttons and toggles for quick actions.
In practice, a Live Activity for a takeaway order might show the restaurant name, a progress bar (received → preparing → out for delivery → delivered) and an estimated time. On iPhones with a Dynamic Island, a compact version sits around the camera cut-out while the customer uses other apps.
The UI is built as part of your app's widget extension, so if your app already has widgets, the same code base is reused.
How it stays up to date
A Live Activity can be updated by the app itself while it's running, but for anything happening on your servers (a kitchen marking an order ready, a driver's position changing) you use ActivityKit push notifications sent through Apple Push Notification service (APNs). Apple's guide to ActivityKit push notifications explains that with push tokens you can:
- Update and end Live Activities
- Start Live Activities remotely (using a push-to-start token), without the customer opening the app first
- Update or end activities for a large audience using channels and broadcast push notifications
That last option suits shared events, such as a match or a queue status everyone is following, rather than individual orders.
Limits that shape the design
These are the constraints from Apple's documentation, as of November 2026. Your developer will plan around them.
| Limit | What Apple's docs say | What it means for you |
|---|---|---|
| Duration | Active for up to eight hours unless ended earlier; then removed from the Dynamic Island, and kept on the Lock Screen for up to four more hours (12 hours maximum) | Fine for orders, rides and same-day appointments; not for multi-day deliveries |
| After ending | The system removes an ended activity automatically four hours after it ended, unless you set an earlier dismissal or the person removes it | End it promptly with a final "Delivered" state |
| Data size | Static and dynamic data, including push updates, can't exceed 4 KB combined | Send status and a few fields, not maps or images |
| Update frequency | A certain budget of ActivityKit pushes per hour; priority 5 or 10 | Send only meaningful changes; save priority 10 for important ones |
| Frequent updates | An Info.plist setting allows frequent updates; people can turn this off in Settings | Only for genuinely fast-changing events |
The update budget is the one that catches teams out. A driver's position pinging every few seconds will hit it. Design around stages ("Driver is 5 minutes away") rather than continuous movement.
Use cases: where it fits and where it doesn't
| Business | What the Live Activity shows | Typical stages | Good fit? |
|---|---|---|---|
| Takeaway or food delivery | Order progress and estimated time | Received, preparing, out for delivery, delivered | Yes: short, time-sensitive, frequently checked |
| Taxi or private hire | Driver arrival and trip progress | Driver assigned, arriving, on trip, arrived | Yes: exactly what customers watch |
| Barber or clinic walk-in queue | Place in queue and estimated wait | Joined, number ahead, "you're next", called in | Yes, if you run a live queue |
| Click and collect | Order ready status | Picking, ready to collect, collected | Often; useful when prep takes under a few hours |
| Appointment reminder for next week | — | — | No: not ongoing, and over the eight-hour limit |
| Parcel delivery over several days | — | — | Only for the final delivery day |
| Promotions or offers | — | — | No: not an ongoing task, and Android's rules exclude it |
Android's equivalent: Live Updates
Android 16 introduced progress-centric notifications (ProgressStyle) for journeys like rideshare and delivery, and Android's Live Updates build on such styles. The Live Update documentation describes promoted notifications that appear more prominently, including at the top of the notification drawer and as a status bar chip, expanded by default and not collapsible. To qualify, a notification must use one of the supported styles (including ProgressStyle), request the promoted notification permission and promotion, be marked ongoing, and avoid custom views. Users can turn the feature off per app, and device makers can add their own criteria.
Google's usage criteria are clear: Live Updates are for activities that are ongoing, user-initiated and time-sensitive. Appropriate examples it lists include active navigation, phone calls, rideshare tracking and food delivery tracking; inappropriate ones include ads, promotions, chat messages, alerts and upcoming calendar events.
If your app is on both platforms, design one set of order stages and show them through Live Activities on iOS and Live Updates on Android.
What it takes to build
- Your back end must know the stages. If the kitchen or dispatcher doesn't record "ready" or "out for delivery" in a system, there's nothing to show. This is often the real project.
- A widget extension in the iOS app for the Live Activity layouts (lock screen, compact and expanded Dynamic Island).
- Server-side push handling for ActivityKit tokens and APNs requests, with sensible update frequency.
- An Android notification using the Live Update requirements, if you support Android.
- Testing on real devices, including what happens when the customer turns the feature off.
FAQ
Do customers need to allow anything?
Live Activities can be switched off by the customer, and Android users can disable Live Updates per app. Design the app so order tracking still works inside it.
Can a Live Activity start without the customer opening the app?
Apple's push-to-start tokens allow your server to start one remotely, once the app is set up for it.
Is this worth it for a small app?
If customers routinely reopen your app to check a status during an order or ride, yes. If your orders take days, a good tracking page and notifications at each stage are a better investment.
Does it replace normal push notifications?
No. Use a Live Activity for the ongoing status and normal notifications for the moments that need attention.
If your customers keep reopening the app to check on an order, lock-screen tracking may be the upgrade they notice most, so describe your order stages to us and we'll tell you what it would take.
Sources
- https://developer.apple.com/documentation/activitykit/displaying-live-data-with-live-activities
- https://developer.apple.com/documentation/activitykit/starting-and-updating-live-activities-with-activitykit-push-notifications
- https://developer.android.com/develop/ui/compose/notifications/live-update
- https://developer.android.com/about/versions/16/features/progress-centric-notifications