Google takes its control on Android a step further so your notifications behave as intended

Earlier this week, Google released an updated version of the Compatibility Definition Document for Android which contains several minor changes but one of them regarding notifications is worth mentioning. The new document reinforces an existing rule that managed API interfaces can’t be changed but explicitly mentions notifications by name.
allo-notification-reply.jpg

Handheld device implementations MUST support the behaviors of updating, removing, replying to, and bundling notifications as described in this section.

Also, handheld device implementations MUST provide:

  • The ability to control notifications directly in the notification shade.
  • The visual affordance to trigger the control panel in the notification shade.
  • The ability to BLOCK, MUTE and RESET notification preference from a package, both in the inline control panel as well as in the settings app.

Google has specifically singled out OEMs that interfere with the way notifications work on Android and obstruct or remove the native notification actions, replies, settings access, and the bundling of notifications. This means that the manufacturer of your phone will now be required to include these features if they want access to Google Play and all the other Google services. Peeking — think of that as a smart pop-up if you’re not familiar with the term — and bundled or inline conversations in peek cards isn’t addressed, so that’s still going to be up to the manufacturers and app developers to support.

It is worth mentioning though that while OEMs do mess around with native Android features, sometimes enhancing them, having them work a different way or even blocking them, they generally tend to leave Android notifications as they are. At least all of the major OEMs you or I have heard of, can’t speak for the gazillion unknown Chinese brands.

This doesn’t mean however that notifications on every Samsung and Huawei will start looking the same as on a Pixel. OEMs are allowed to mess with the looks as long as they keep the features so Samsung can still be Samsung with its Samsung Experience UI and Huawei can still keep its mess of a UI EMUI.

While there have been no rumours or any other piece of information even remotely suggesting that the way Android handles notifications was in a danger, this move could be seen as Google just trying to further tighten its grasp over Android. Although the more Google takes control the more likely it is that some OEMs might step away, Samsung and Huawei being the major names.

Via : Android Police

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Powered by WordPress.com.

Up ↑