[meta] Allow a like-new experience for returning users

NEW
Unassigned
(Needinfo from 2 people)

Status

()

Firefox
General
2 years ago
2 months ago

People

(Reporter: verdi, Unassigned, NeedInfo)

Tracking

(Blocks: 2 bugs, {meta})

unspecified
Firefox 57
Points:
---
Dependency tree / graph
Bug Flags:
qe-verify -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [photon-onboarding] )

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
Created attachment 8746819 [details]
auto-refresh.png

Continuing the discussion from Bug 1095739 comment10 and 11.

New flowchart attached. 

(In reply to :Gijs Kruitbosch (back May 3rd) from comment #11) 
> OK, so even in the 60-days-unused case you want to automatically refresh
> (rather than give them the choice but not always do it)? But only in the
> case where Firefox isn't the default browser (based on the flowchart you
> attached)?

After more thought, since default browser is such a weak signal, I think we can auto-refresh all profiles older than 60 days (or whatever the right time frame is).


> OK, so we also need a special what's new page. Note that we already have the
> 'about:welcomeback' page which lets people restore tabs and continue on
> their way. We could modify that. Opening a secondary page in addition to
> that page seems like it might not be a great experience / very useful.

In this new version, I think we should skip displaying the about:welcomeback page (only for the auto-refresh case) and show whatever page(s) a new installation would see. The user could still restore their previous session from the default home page or the history menu.

> I also think we need to fix bug 1017919 and bug 1054947 (and potentially
> other blockers of bug 498181) before enabling auto-reset in the 60-days case.

Yes, Bug 1017919 is definitely a prerequisite for this.
Keywords: meta

Updated

9 months ago
Blocks: 1349422

Comment 1

9 months ago
After investigated Bug 1017919, looks like that is actionable. We can start to fix the issue from there.
(In reply to Evan Tseng [:evanxd] from comment #1)
> After investigated Bug 1017919, looks like that is actionable. We can start
> to fix the issue from there.

Shouldn't we be filing all the bugs that would complete the flow chart attachment 8746819 [details] first? Let's not dive into engineering without knowing where the low hanging fruits are please. Thanks.
Flags: needinfo?(evan)

Comment 3

9 months ago
> Shouldn't we be filing all the bugs that would complete the flow chart
> attachment 8746819 [details] first? Let's not dive into engineering without
> knowing where the low hanging fruits are please. Thanks.

Yes, Fischer and I was working on learning the flow chart https://bugzilla.mozilla.org/attachment.cgi?id=8746819&action=edit, and ready to file the breakdown bugs. We're filing the bugs.
Flags: needinfo?(evan)

Updated

9 months ago
Depends on: 1351609

Updated

9 months ago
Depends on: 1351611

Updated

9 months ago
Depends on: 1351612

Updated

9 months ago
Depends on: 1351616

Updated

9 months ago
Depends on: 1351619

Updated

9 months ago
Depends on: 1351631

Comment 4

9 months ago
After learned the flow chart[1], looks like we would like to implement the 4 (Onboarding tour, Experience for returning users, Experience for updating users, Add-on migration) items listed on the Photon UX/ENG Planning sheet, right? If so, I think we could update the bug title to make it clear, not like the current tile only mentioned the returning users part. Thanks.

[1]: https://bugzilla.mozilla.org/attachment.cgi?id=8746819
Flags: needinfo?(mverdi)

Updated

9 months ago
Depends on: 1351641

Updated

9 months ago
Depends on: 1351941

Comment 5

9 months ago
(In reply to Evan Tseng [:evanxd] from comment #4)
> After learned the flow chart[1], looks like we would like to implement the 4
> (Onboarding tour, Experience for returning users, Experience for updating
> users, Add-on migration) items listed on the Photon UX/ENG Planning sheet,
> right? If so, I think we could update the bug title to make it clear, not
> like the current tile only mentioned the returning users part. Thanks.
> 
> [1]: https://bugzilla.mozilla.org/attachment.cgi?id=8746819
Hi Michael,
Follow Evan's question.
From today's online meeting, it seems that 
 - the Photon onBoarding flow is different from the flow[1] this bug and 
 - the Photon onBoarding scope(Focus on new users on 57) is different from this scope of this bug
Is the above understanding, right?

Why asking this is to make sure we are working on the right specs and the right bug, thank you.

[1] attachment 8746819 [details]: auto-refresh.png
Flags: needinfo?(mverdi)

Updated

9 months ago
Flags: needinfo?(mverdi)

Comment 6

9 months ago
We should change to correct component (maybe Activity Stream or new tab) from the "General" for some sub-bugs after we have a conclusion of adding the overlay into Activity Stream or new tab pages.
Flags: needinfo?(evan)

Updated

9 months ago
Whiteboard: [Onboarding] → [photon] [Onboarding]

Updated

9 months ago
Flags: qe-verify-
Summary: Breakdown: Allow a like-new experience for returning users → [meta] Allow a like-new experience for returning users

Updated

8 months ago
Whiteboard: [photon] [Onboarding] → [photon-onboarding]

Updated

8 months ago
No longer depends on: 1351941

Updated

8 months ago
No longer depends on: 1017919

Updated

8 months ago
No longer depends on: 1351631

Updated

8 months ago
Depends on: 1357666
Depends on: 1334662

Updated

7 months ago
Target Milestone: --- → Firefox 57

Updated

7 months ago
Depends on: 1367699

Updated

7 months ago
Depends on: 1369255

Updated

6 months ago
Depends on: 1361294

Updated

6 months ago
Depends on: 1376558

Updated

6 months ago
No longer depends on: 1361294

Updated

5 months ago
No longer depends on: 1334662

Updated

5 months ago
Depends on: 1381650

Updated

5 months ago
Depends on: 1353194

Comment 7

3 months ago
Just a note that every dependency on this bug is now closed.
You need to log in before you can comment on or make changes to this bug.