Google shipped a wonderful feature in Android 16, then forgot to invite anyone to the party.

Live Updates is supposed to replace a dozen chatty notifications with a single, dynamic tracker pinned to your status bar and lock screen.

Apple's version, Live Activities, launched in late 2022 and had a healthy roster of third-party apps within months.

Android's equivalent, meanwhile, is a ghost town in comparison, and that's embarrassing.

What it takes to reach the status bar as a Live Update

The rules an app has to follow

Live Updates is a highly privileged notification class baked into the OS. Developers who want in must ditch their custom designs and build with set templates instead.

The marquee options are ProgressStyle, introduced with Android 16, and MetricStyle, the fresh addition in Android 17, alongside three other styles for text and calls.

When an app clears the bar, the OS pins the update to the top of the notification shade and shows it prominently on the lock screen.

The Now Bar is Samsung's version of the same idea, a persistent lock screen surface for things happening right now.

Supporting it used to be effectively invite-only, limited to Samsung's own apps and a few partners.

One UI 8 removed that step by ingesting standard Android Live Updates, and the behavior carries through to the new One UI 9.

This means one platform API implementation reaches Google Pixel status bars and Samsung Galaxy lock screens at once. The reach argument has already been made by developers. They ignored it anyway.

Google can't even be bothered to use its own feature

Fourteen months for a stopwatch

Google Maps is the one bright spot. Active navigation pushes ETA and turn-by-turn directions into the status bar chip, and expands into a live trip progress card on the lock screen.

It's a poster child implementation, and for most of the first year, it was basically alone in Google's portfolio.

Google Wallet joined later with flight tracking, and the rest of Google's native lineup is patchy at best.

Google Clock finally joined the party in early August, when version 9.0 started showing running timers and stopwatches as a Live Update in the status bar, on the lock screen, and on the always-on display.

Sit with that timeline for a second. Google first showed this API in the Android 16 betas at the start of 2025, pitched it hard at I/O that May, and shipped it with Android 16.

It took Google more than a year to wire up a stopwatch in its own clock app. If the platform owner doesn't eat its own cooking, why would third-party developers bother?

Why are developers ignoring it?

Five templates and no room to move

Blaming the empty room on lazy developers misses the structural issue. Google's eligibility rules are strict about form.

Apps have to declare a new permission called POST_PROMOTED_NOTIFICATIONS, granted at install rather than through a prompt, and they have to build the notification from one of five approved templates.

Custom designs are rejected outright. For apps that have already shaped their own notification look, that means throwing away the work.

The engineering work is also worse than on iOS. Apple can drive Live Activities entirely through a system-managed remote push service, with no persistent background process required to keep the UI current.

Android has no equivalent system-managed channel. The app has to wake up and rebuild the notification every time, which, for anything continuous, means keeping a foreground service alive.

If you're a developer, you're now looking at a different architecture with unpredictable background execution limits across manufacturers.

A lot of teams can't justify the spend, and even the ones that want to build it for iOS first.

The dominoes that have to fall

For Live Updates to move from novelty to expectation, a few specific dominoes have to fall.

Google has to wire up its own apps. The platform owner needs to prove the framework is reliable and worth looking at.

The bigger lever is pressure. Google could require Live Updates support to get top-tier featuring on the Play Store. It could deprecate legacy notifications and force everyone into the new system.

Right now, Live Updates is trapped in a feedback loop. Users don't look for it because nothing uses it, and developers don't build it because users don't look for it.

Someone at Google has to break that loop, and given that it took the company 14 months to put its own stopwatch in the status bar, I'm not holding my breath.