Let’s go back to dealing with Live Updateor Real -time updatesa new type of notification that will officially debut with Android 16 QPR1 and which, at present, is already completely implemented in beta 2.1 (available on pixels recorded at the Android beta program) but needs the update of the various apps that will have to become compatible.

In the last few hours, Google has updated the official documentation to show the behavior of Google Maps with this type of notification. Parallel, one emerges sad Decision taken by the development team that does not consider notifications from multimedia readers as “compatible” with this type of treatment.

Follow Google Italia on Telegram, Receive news and offers first

Google Maps will also notify real -time updates on Android

As anticipated at the opening, Google has recently updated the documentation linked to Live Updatesrendered in Italian as Real -time updatesa new type of notification “promoted” by the system that will try to show it in the foreground both in the notification curtain and through one or more chips in the status bar.

The Real -time updates may concern ongoing activities (with distinct beginning and end) that come explicitly started by users and they appear urgentor for which the user’s attention is required during the activity.

An update in real time is often appropriate for activities that provide for a transition between real -time updates and normal notifications. For example, showing a notification of the boarding card is appropriate many hours before a user’s flight, but the notification should become a real -time update only when the user has an imperfection, for example upon arrival at the airport or locally or once the boarding began. On the contrary, a real -time update is not appropriate to trace a package, since the user does not need to constantly monitor it.

In explaining these concepts, Big G has attached a short video showing i Live Update With Google Maps, apps that should be among the first to receive the update to support this new Android 16 functionality. The app is taken as an example for notifications with “active navigation” but other use cases could be telephone calls, shared racing monitoring and monitoring food deliveries.


Live Update will not work with multimedia readers

From the analysis of the official documentation of Live Updateit emerges that musical readers will not be able to see their treated notifications as updates in real time. Let’s try a little to explain the reason but without going too far.

Google explains the criteria so that a notification can be considered an update in real time. Although the apps of musical readers are able to satisfy some key criteria, they cannot satisfy the last limitation: the style of the notification.

To be considered to be considered Live Updatenotifications must be of one of the four types provided: Standard (basic notification without special functions), Bigtext (notification usually used when there is an expandable block of text, such as e-mails), Call (notifications for incoming calls with options such as “Refuse” and “Reply”), Progress (i.e. notifications focused on advancement, another novelty of Android 16).

Multimedia readers exploit a type of ad hoc call note Average Which does, for example, that notifications are always present under the center of the rapid commands and that notifications include the button for the selection of the output.

The transition to the type of notifications Progress it would therefore allow the elegibility as Live Update But some essential features that should disappear would be expenses. It is unlikely that a multimedia app can give up this type.

However, there is hope: other producers from the Android panorama, such as Samsung, have made sure that notifications from the multimedia apps are in all effects notifications in real time due to default. Google should “simply” include type notifications Average in the park of notifications that can be transformed into Live Update.