Thanks Peter. Do you have a screenshot of the button you're referring to? Is it in the notification itself? 

Yes, it's our own action button. See attached.

Deleted: screen-shot-2015-03-04-at-2-35-05-pm-copy.png 13.9 KB

	screen-shot-2015-03-04-at-2-35-05-pm-copy.png 13.9 KB View Download

> is an indication that users know how to find this.

Do you mean that they know how to find the "Site Settings" button? How well do we think they know how to get into the Android notification settings? That requires a long-press on the notification, is that correct? 

You mention the possibility of having an "Unsubscribe" button - is that actually possible to implement with Android channels? I thought that Chrome wasn't able to manipulate the Android settings?

> Do you mean that they know how to find the "Site Settings" button? How well do we think they know how to get into the Android notification settings? That requires a long-press on the notification, is that correct?

No, the opposite. See the graph I linked to: the number of people disabling notifications for Chrome as an app rose steeply due to a website changing behaviour. I interpret this as a signal that people know how to disable notifications for an app (and therefore a channel in O).

> You mention the possibility of having an "Unsubscribe" button - is that actually possible to implement with Android channels? I thought that Chrome wasn't able to manipulate the Android settings?

We can't change the channel permission, but we can do things like drop the subscription. It's more applicable to older Android versions. I don't think I'm in favor of this option anyway -- it's something I've heard others mention.

Note that blocking notifications at the OS level became much more discoverable in Android N+, since it used to require a long-press, but now swiping a notification slightly to the left/right (a very common gesture, since it's how you dismiss notifications) shows a settings cog, and clicking on that settings cog shows the options for blocking the notification (same as long-pressing the notification).

Ah thanks for the explanation. I'm ok just removing the button and not adding anything.

What actually happens when you click the settings-cog. johnme@ you mention that it shows the options for blocking the notification - does it show a specific toggle for the channel of the notification? Or does it just show a list of channels for that app? It would be nice if it took you to the specific channel. I understand that's out of our control though.

In any case, removing the button sgtm. 

@raymes - right now it takes you to notification site settings for that site, but we could make it take you to channel settings for the specific site once  crbug.com/700377  is done, as per the long press gesture.

I'm a bit hesitant about removing the button altogether because although notification settings have become *more* discoverable since N on Android, with the swipe + longpress gestures, these still aren't as discoverable as an action button. There's also the 'feature-removal' perception problem, if users are used to seeing the setting button and then it disappears. On the other hand most apps don't put setting buttons on their notifications, and it does mean we have less space for notification content. Curious what UX people think on this. 

Just looping back around on this, what behavior did we end up going with for the initial channels launch? 

My sense is that the channels are sufficient on O FWIW.

re #8: The button is currently still present on O and in the version that has site channels enabled by default (M62). 

I'm okay with this making this change in a future release subject to design approval.

Looking at some use counter data --

Notifications.ShowSiteSettings counts the number of clicks on the Site Settings button. Notifications.Persistent.Shown counts the number of Web Notification shows. Be sure to specialize the dashboard to Android when looking at the metrics.

In the past week we've seen a CTR on this button of less than 0.01% by less than 0.05% of users. It's not clear whether they actually reset permission after this click. The rate of increase we see in Notifications.AppNotificationStatus definitely is higher than that. (Mind that the histogram is cumulative, however.)

I don't think it's urgent, but FWIW I think it'd make sense to at some point remove the button in O since that follows the platform paradigm, and since the CTR on the button is so low as Peter points out.

I suggest we proceed with the plan to remove the button for O+ for now, unless there are any objections.