Live Updates on Android: Progress Notifications for Delivery and Ride Apps

A customer orders lunch, puts the phone down, and wants to know one thing: how far away is the rider? Today many apps answer with a normal notification that appears once and scrolls away. Android now has a feature built for exactly this moment. It keeps the live status of an ongoing job on the lock screen, at the top of the notification area and as a small chip in the status bar. This post explains what it is, what qualifies and what a business should and should not use it for.

What was introduced

Google's Android 16 documentation introduced progress-centric notifications, built on a new notification style called ProgressStyle. It is designed for user-initiated, start-to-end journeys, and the key use cases Google names are rideshare, delivery and navigation. A progress bar can show segments, such as coloured stretches of a trip, and points, such as "food prepared", "picked up" and "arrived". An icon, such as a small scooter or car, can travel along the bar.

A notification that follows Google's rules can then be promoted to what the current guide calls a Live Update. Promoted notifications appear more prominently: at the top of the notification drawer, on the lock screen and as a chip in the status bar. They are expanded by default and cannot be collapsed. Users can still dismiss or demote them.

What qualifies

The developer guide, updated on 28 October 2026, lists requirements that your developer must meet. In plain terms:

• The notification must use a supported style (the standard style, big text, call style, progress style or metric style).
• The app must declare a special permission, POST_PROMOTED_NOTIFICATIONS, which is a manifest entry and not a pop-up that users see.
• The app must explicitly request promotion, the notification must be ongoing and must have a title.
• It cannot use a custom layout, be a group summary, use forced colour backgrounds or sit in a channel of minimum importance.

The guide also says phone makers can add their own eligibility criteria, and that users can switch Live Updates off per app in Settings. So your developer should check whether promotion is allowed before relying on it and have a fallback to a normal notification.

Good uses for Indian service apps

Google's rule of thumb: use Live Updates for activities that are ongoing, user-initiated and time-sensitive. Examples it lists as appropriate are active navigation, phone calls, rideshare tracking and food delivery tracking. Map that to businesses we see in Tamil Nadu and beyond:

• Food and grocery delivery: order accepted, packed, out for delivery, arriving.
• Cab, auto and school-van tracking: driver on the way, arrived, trip in progress.
• On-demand home services: technician, electrician or cleaner travelling to the customer.
• Water can and cooking gas delivery within a same-day window.
• Queue and booking apps: a clinic token that is about to be called, activated only when the visit is imminent.

What not to use it for

Google is explicit here. Inappropriate uses include ads, promotions, chat messages, alerts, upcoming calendar events and quick access to app features. It also says a Live Update is not appropriate for tracking a package, because the user does not need to watch it constantly. A courier parcel that arrives in three days should use ordinary notifications; a hot meal arriving in twenty minutes can use a Live Update.

The guide warns that posting unwanted Live Updates might cause users to revoke the permission, and tells developers not to repost a Live Update that the user dismissed. Overuse spoils the feature for everyone, including you.

Design details that make it good

• Keep the text short: arrival time, name and state of the journey are the essentials.
• Update it often and accurately; a frozen bar is worse than none.
• Use the status chip to show a short critical value such as minutes remaining.
• Never show an empty state while waiting; use placeholder text such as "Rerouting".
• Add a useful action, such as calling the rider or adding an item to a new order.

Android 17 adds semantic colour options for Live Updates (safe, caution and danger meanings), so status colours can be consistent across apps.

Cost and next steps

For an app that already tracks orders or trips, Live Updates are mostly a notification change plus reliable status events from the server. Without live status data from the backend, there is nothing to show. Test on Android 16 and newer devices from several makers, and keep the normal notification path for everything else.

VS Tech Builders builds order-tracking and booking apps with Firebase and Kotlin. See push notifications explained, our software for restaurants and cloud kitchens, software for water can suppliers and Firebase app development. For the wider release, read Android 16 for business apps.

Sources

Checked on 3 November 2026. Technology changes quickly; always confirm details with the official source before you act on them.

• Progress-centric notifications | Android Developers — Android Developers
• Create live update notifications | Views | Android Developers — Android Developers
• Features and APIs | Android Developers — Android Developers

Frequently asked questions

What is a Live Update on Android?

It is a promoted notification for an ongoing, user-started activity such as a ride or food delivery. It appears at the top of the notification drawer, on the lock screen and as a status bar chip, and it is expanded by default. Users can dismiss it, and they can turn Live Updates off for an app in Settings.

Which Android version introduced progress-style notifications?

Google's documentation says Android 16 introduced progress-centric notifications through the ProgressStyle class. The developer guide for Live Updates, last updated 28 October 2026, describes the promotion rules, and Android 17 added semantic colours. Phone makers may add extra conditions, so test on devices your customers actually use.

Can I use Live Updates to show offers or reminders?

No. Google lists ads, promotions, chat messages, alerts and upcoming calendar events as inappropriate uses, and says Live Updates should not be used for quick access to app features. They are for activities that are in progress, started by the user, and need attention over time. Abuse can lead users to switch the feature off.

Does my delivery app need a special permission?

The app declares POST_PROMOTED_NOTIFICATIONS in its manifest and requests promotion in code. Google calls it a non-runtime permission, so customers are not asked to approve it on a pop-up, though they can still disable Live Updates for the app in settings. Your developer should check that setting before relying on promotion.