Do those notifications you touch sound to you but nothing happens until a minute or two have passed? Google wants this to be a thing of the past as Android 12 will ban apps from using so-called notification springboards. This should put an end to notifications that slowly load pp when you click on them, and the change is already visible in the first preview of Android 12 – affecting even Google’s own apps that were abusing this technique. Trampolines are often used by applications that do not open their own activity when you touch a notification, for example apps that notify you of a link and touching the notification opens the website instead of the application itself. To rid users of a bad waiting experience, Google will make apps that use the springboard method stop working. Interestingly, the Chrome app itself uses this method when you send a link to your own devices since in many cases an app is opened (for example, Twitter) and that has stopped working.
Sharing a link to Twitter via Chrome is considered a “stepping stone” no longer works in Android 12 In fact, Google apps are among the most affected since many notifications from apps like Drive (when a Docs, Sheets or Slides are launched to via a notification), Home and Calendar use this now broken mechanism. Other apps like Pushbullet also send links in the notifications that only take you to the browser, so there is no reason to launch the Pushbullet application only to kill it right after redirecting users to the requested website. There could be a way around the problem by using the PendingIntent class as suggested in the Android documentation. In any case, developers will have to adapt their apps to keep them running on Android 12. While the new requirement may make some activities more cumbersome for developers, normal people will be glad they don’t have to wait for their phones to do. “Stuff” after tapping a notification.