As you know some app notifications you tap after which nothing occurs till a minute or two have handed? Google is trying to make this a thing of the past on the latest Android 12 OS, forbidding applications from utilizing so-called notification trampolines.
That should very effectively banish slowly opening notifications, and the update is already having an impact on apps on Android 12 now.
Notification trampolines are normally used by applications that do not open the activity of their own while you tap a notification like once you share links with your self by way of an app and tapping the notification opens the website instead of the mobile app.
Google additionally makes use of this technique for its own "Send to your Devices" function in Chrome browser. To avoid wasting users from a bad waiting experience, Google is prepared to break apps that depend on this method and is already showing a toast that the implementation goes away as soon as Android 12 goes stable.
There is likely to be a way around the issue by using the PendingIntent class as recommended in the Android documentation, however solely rigid testing will tell. In any case, the developers have confirmed to us that they may implement whatever modifications are essential to support Android going ahead.
Google will in all probability have to change the way it handles notifications in a few of its apps, too.
Whereas the brand new requirement would possibly make some activities extra cumbersome for developers, regular people will in all probability just be comfortable that they no longer have to wait around for their devices to do something after tapping on a notification.
That should very effectively banish slowly opening notifications, and the update is already having an impact on apps on Android 12 now.
Notification trampolines are normally used by applications that do not open the activity of their own while you tap a notification like once you share links with your self by way of an app and tapping the notification opens the website instead of the mobile app.
Google additionally makes use of this technique for its own "Send to your Devices" function in Chrome browser. To avoid wasting users from a bad waiting experience, Google is prepared to break apps that depend on this method and is already showing a toast that the implementation goes away as soon as Android 12 goes stable.
There is likely to be a way around the issue by using the PendingIntent class as recommended in the Android documentation, however solely rigid testing will tell. In any case, the developers have confirmed to us that they may implement whatever modifications are essential to support Android going ahead.
Google will in all probability have to change the way it handles notifications in a few of its apps, too.
Whereas the brand new requirement would possibly make some activities extra cumbersome for developers, regular people will in all probability just be comfortable that they no longer have to wait around for their devices to do something after tapping on a notification.
Post A Comment:
0 comments: