1263969 - Consider giving more info about content notifications/website updates

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

I got a content notification for the first time this morning and I felt the notification didn't really explain why it was there. It said:

Gravel Racing on Compass Tires
urlurlurl

Have we considered explaining the notification a bit? e.g.

Some content that may interest you
Wordpress – Gravel Racing on Compass Tires

Comment 1

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

We could also add a UI (in the style of tab queues) when the user clicks the notification to explain what the page they're going to is, e.g.:

We thought you might like this article so we decided to share it with you! If you'd prefer not to receive these, check out the notification settings below!
  SETTINGS     GOT IT

Comment 2

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

(In reply to Michael Comella (:mcomella) from comment #0)
> I got a content notification for the first time this morning and I felt the
> notification didn't really explain why it was there. It said:
> 
> Gravel Racing on Compass Tires
> urlurlurl
> 
> Have we considered explaining the notification a bit? e.g.
> 
> Some content that may interest you
> Wordpress – Gravel Racing on Compass Tires

To explain it in the title of the notification would get really repetitive really fast since this is only a piece of knowledge the user only really needs to learn once. I'm also concerned that it feels very "ad-like" and uses language that isn't really suggested by the guidelines.

I think this "aha! moment" is something that we're better off not OVER explaining for this initial stage of the experiment. But perhaps something we can look at later on down the line when we grow our supported sites.

(In reply to Michael Comella (:mcomella) from comment #1)
> We could also add a UI (in the style of tab queues) when the user clicks the
> notification to explain what the page they're going to is, e.g.:

Yeah, perhaps a helper UI will help. I can see that. But we'll have to give more though to when we show it so that it's not "too much". 

Every time a user Bookmarks a supported site perhaps? but I really want to avoid bogging down our Bookmarking UX that is currently very quick and easy.

The helper UI is something I'll think about some more here.

Comment 3

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Renaming to be less prescriptive about a designed solution. 

E.g. perhaps a learn more link in settings > Notification?

Comment 4

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

(In reply to Anthony Lam (:antlam) from comment #2)
> To explain it in the title of the notification would get really repetitive
> really fast since this is only a piece of knowledge the user only really
> needs to learn once. I'm also concerned that it feels very "ad-like" and
> uses language that isn't really suggested by the guidelines.

What if the notification only showed the "Content Notification" text once or twice (or until the user engages), then switched to the current view?

Comment 5

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

(In reply to Michael Comella (:mcomella) from comment #4)
> (In reply to Anthony Lam (:antlam) from comment #2)
> > To explain it in the title of the notification would get really repetitive
> > really fast since this is only a piece of knowledge the user only really
> > needs to learn once. I'm also concerned that it feels very "ad-like" and
> > uses language that isn't really suggested by the guidelines.
> 
> What if the notification only showed the "Content Notification" text once or
> twice (or until the user engages), then switched to the current view?

what is "the Content Notification text"? This sounds difficult to follow, would it be possible to see a build or some screenshots of what you're suggesting?

Comment 6

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

(In reply to Anthony Lam (:antlam) from comment #5)
> what is "the Content Notification text"? This sounds difficult to follow,
> would it be possible to see a build or some screenshots of what you're
> suggesting?

For example:

First three times notification appears:
  <Article title>
  An article that may interest you

Remaining times:
  <Article title>
  <Article subtitle>

Comment 7

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Hm, I see what you mean now! Though, the benefit here seems marginal. 

If the user wants more info about this notification and why they're getting it, etc... I don't think that subtitle change will really solve that. 

A helper UI after the user bookmarks a supported site (for example) might be more useful, obvious and contextual too. We could think about that after we gauge some feedback in front of our users first (we're going to saturate the helper UI soon).

On the other hand, I worry that we're over thinking the issue here a bit and possibly even confusing the user further. By creating multiple variations/messaging of the same thing, it might sound like it's a different notification altogether. Plus, if it's "an article that may interest" me, my logical next question (in order to warrant me "clicking the notification" rather than swiping to dismiss it) would be "what's the article?".

Comment 9

[Sebastian Kaspari (:sebastian; :pocmo)]

Content notification code was removed in bug 1396604.