1245642 - Remind users of saved bookmarks

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[:Margaret Leibovic]

We should start experimenting with saved bookmark reminders. I think it will be hard to come up with a good heuristic for this, so let's just make a prototype that does something simple, like show a notification if the user has a bookmark they haven't visited in over 3 days.

I feel like this may actually be better specifically for all reading list items than for bookmarks, but it shouldn't be hard to make that change once we have a service working.

As far as implementation goes, I think this should be a service that doesn't require the browser to be running, similar to the content notification service Sebastian is working on in bug 1241810.


From the Aha! card (https://mozilla.aha.io/features/FENN-414):

Requirements:

* Find a method to notify and remind users of saved bookmarks

User Stories:

* As a user, I want to be reminded that I've saved bookmarks for later reading
* As a user, I want to disable and enable reminders and notifications

Acceptance Criteria:

* Show some notification (to be discussed) and entry point for users to view saved bookmarks
* Allow to disable feature

KPIs / Measurements Used:

* Track how bookmarks are opened (via notification or while browsing the app)

Additional info:

Differentiator: None of the competitor browsers offer such feature, our value proposition is that based on our data showing popularity of bookmarks, as well as some of Gemma's user research and suggestion, that the user will benefit from this: https://docs.google.com/document/d/15NTT4pcpvIMZPvapxJVE_JpNUM3vpIi8tLvZMrN5Qvc/edit

Comment 1

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

Mfinkle's pitch doc outlines a great point that most Bookmarks are going to be "viewed" since you often have to visit a page to Bookmark it. Apart from the context menu and the share overlay, which actually creates a nice subset of Bookmarks that we can experiment with.

Give that, I have started thinking and sketching what this would mean for our UI too. 

But, I suggest we might want to add "Add a notification section in Settings" to the list of requirements here as well.

Comment 2

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

Attachment: Screen Shot 2016-02-15 at 12.33.37 PM.png

Given the spectrum of "saved" content a user may come to have on mobile, we really have to consider the visuals we're presenting to the user to establish a hierarchy and to avoid confusion..

Right now, I think of viewed/ not viewed as one of the lower end items. In the same way that an email badges items as "new" but adds labels and such, I think we can start with just "bold-ing the text". This has an added benefit of being more scalable since it can be combined with other icons and visual cues that we add to these items.

In this screenshot, I've got the title as Roboto, Medium, #363B40 (same font size and everything), and the URL is Roboto regular, #5F6368. 

Let's start with this first and see how it feels.

Comment 3

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

Side question: do we have the time/date stamp for when said bookmark was added by the user?

Comment 4

[:Margaret Leibovic]

I was under the impression that this bug was going to be about creating a system notification for users to remind them of that unvisited bookmark, not a change to the bookmark list UI.

In order to change our bookmark list UI like this, we'd need to change our bookmarks query to also query history and change the list style depending on whether or not there's a history entry to go with the bookmark. This could potentially get messy if the user clears their history... although I suppose that would also be tricky for the notification reminder. However, given that the notification would only happen once in a while, we could add logic to avoid showing it if the user did clear their history since adding the bookmark. But this would be more difficult for the bookmark list. 

Given the amount of work involved, I think we'd get more engagement bang for our engineering buck if we focus on adding the notification first.

Let's file a separate bug about creating an "unread" state in the bookmark list, and keep this one about the notification.

Comment 5

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to :Margaret Leibovic from comment #4)

> Given the amount of work involved, I think we'd get more engagement bang for
> our engineering buck if we focus on adding the notification first.
> 
> Let's file a separate bug about creating an "unread" state in the bookmark
> list, and keep this one about the notification.

Yes. This bug is about the system notification, designed to pull people back into Firefox to read what they have not.

Comment 6

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

(In reply to :Margaret Leibovic from comment #4)
> I was under the impression that this bug was going to be about creating a
> system notification for users to remind them of that unvisited bookmark, not
> a change to the bookmark list UI.

Yes, we can certainly do that. But to holistically "remind users", we'll need to consider other parts of this UX too. If they forgot they had bookmarks, they'll likely have forgotten which bookmarks we're referring to as well.

For instance, the notification would have to lead "somewhere" and that should probably be the Bookmarks panel (especially if there's more than 1). I think there would need to be some sort of supporting "UI" to indicate which ones are "unread". 

Otherwise, it feels a bit... awkward/broken to the user since there is not visible reason why we just pointed them here. Especially if this was a bookmark made a while ago (as in, it wouldn't simply be at the top). 

This will also be able to stand on it's own without a notification too. I.e. if a user visits the bookmarks panel themselves, they can see an "unread" indicator before our notification even able to notify them.

> In order to change our bookmark list UI like this, we'd need to change our
> bookmarks query to also query history and change the list style depending on
> whether or not there's a history entry to go with the bookmark. This could
> potentially get messy if the user clears their history... although I suppose
> that would also be tricky for the notification reminder. However, given that
> the notification would only happen once in a while, we could add logic to
> avoid showing it if the user did clear their history since adding the
> bookmark. But this would be more difficult for the bookmark list. 
> 
> Given the amount of work involved, I think we'd get more engagement bang for
> our engineering buck if we focus on adding the notification first.
> 
> Let's file a separate bug about creating an "unread" state in the bookmark
> list, and keep this one about the notification.

Sure, I filed bug 1248635 :)

Comment 7

[:Margaret Leibovic]

We need to think about the ROI here. Part of the reason that we decided to pursue this bookmark notification idea is that it sounds like a relatively simple way to increase engagement.

If we're going to grow the scope here to be about showing users unread bookmarks in their bookmark panel, that increases the cost to building this feature.

Let's keep this bug about doing the simple notification. We don't even know if users will like to be reminded of unread bookmarks, so first let's validate our assumption with the easiest thing, then think about adding more features after that.

Comment 8

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

For the notificaiton, we can follow the same format as our other ones (content update, tab queue, etc)

+--------------------------------------------------------+
|                                                        |
|  +-+  2 bookmarks to view                              |
|  +-+  *link*                                           |
|       *link*                                           |
|                                                        |
+--------------------------------------------------------+
|                                                        |
|  +-+  NOTIFICATIONS SETTINGS                           |
|                                                        |
+--------------------------------------------------------+

   Firefox                                             2



+--------------------------------------------------------+
|                                                        |
|  +-+  1 bookmark to view                               |
|  +-+  *link*                                           |
|                                                        |
+--------------------------------------------------------+
|                                                        |
|  +-+  NOTIFICATIONS SETTINGS                           |
|                                                        |
+--------------------------------------------------------+

  Feb 24, 2016

Comment 9

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.