Closed
Bug 1044994
Opened 11 years ago
Closed 10 years ago
[UX] Loop first run tour
Categories
(Hello (Loop) :: Client, defect, P1)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1084075
backlog | Fx35+ |
People
(Reporter: RT, Unassigned)
References
Details
(Whiteboard: [ux][FTE])
User Story
As a FF browser user using Loop for the first time, I'd like to be taken through a first run tour so I know how Loop works.
FTU tour should include the following:
* What is a link
* How to set a URL an exp date and name
* How to share a link
* Receive incoming call and how to answer
* Default answering mode explained
Updated•10 years ago
|
Flags: firefox-backlog+
Updated•10 years ago
|
Summary: Loop first run tour → [UX] Loop first run tour
Whiteboard: [ux] [qa-]
Comment 1•10 years ago
|
||
Is this the same as the tour shown as part of the Firefox upgrade (whatsnew) page (bug 1049017)? It seems like we could re-use the same UITour mechanism to have the tour initiated by a content page if this is something different. :habber is working on the UX for the firstrun, whatsnew and product page tours.
See Also: → 1049017
Comment 2•10 years ago
|
||
Moving to P3 not because it is truly lower priority, but to indicate that we're asking the Desktop folks to take this one. If we can reuse or leverage work (a tour) that has been done for another feature, that'd be great.
Priority: P2 → P3
Comment 3•10 years ago
|
||
(In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #2)
> Moving to P3 not because it is truly lower priority, but to indicate that
> we're asking the Desktop folks to take this one. If we can reuse or
> leverage work (a tour) that has been done for another feature, that'd be
> great.
There is currently a project in progress addressing Loop onboarding that will display during the upgrade and firstrun experience, as mattn mentioned the tracking bug for above. Here are a list of bugs being started on and/or considered now: https://docs.google.com/a/mozilla.com/spreadsheets/d/1998Z68sed6BTVLECQhkXpPqacq-UZDb9ebLzFg36gE0/edit?usp=sharing
Updated•10 years ago
|
Assignee: nobody → dhenein
Status: NEW → ASSIGNED
Iteration: --- → 34.3
Points: --- → 13
Flags: qe-verify-
Whiteboard: [ux] [qa-] → [ux]
Updated•10 years ago
|
Iteration: 34.3 → 35.1
Updated•10 years ago
|
Priority: P3 → P1
Target Milestone: mozilla34 → mozilla35
Updated•10 years ago
|
Assignee: dhenein → nobody
Iteration: 35.1 → ---
Reporter | ||
Comment 4•10 years ago
|
||
After discussions with Darrin, the UX will be:
* The first time a user opens the panel, he gets a "Try it yourself" button in the panel (together with ToU, privacy policy and branding which get displayed in the panel until the user receives his first call)
* Clicking "Try it yourself" opens the tour in a new tab
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
Whiteboard: [ux] → [ux][rooms]
Updated•10 years ago
|
Depends on: fx-UITour-Hello
Updated•10 years ago
|
No longer depends on: fx-UITour-Hello
Updated•10 years ago
|
Status: ASSIGNED → NEW
Updated•10 years ago
|
backlog: --- → Fx35+
Comment 5•10 years ago
|
||
(In reply to Romain Testard [:RT] from comment #4)
> After discussions with Darrin, the UX will be:
> * The first time a user opens the panel, he gets a "Try it yourself" button
The two strings that landed are:
first_time_experience_title={{clientShortname}} — Join the conversation
first_time_experience_button_label=Get Started
I assume "Try it yourself" was supposed to replace "Get Started" but it wasn't on our radar for 35.
It's unclear if this is a UX bug where more work needs to be done by Darrin?
Comment 6•10 years ago
|
||
I'm looking at the copy spreadsheet and "Get Started" is the string approved for the in-product start button. (In reply to Matthew N. [:MattN] (behind on reviews - focused on Loop) from comment #5)
> (In reply to Romain Testard [:RT] from comment #4)
> > After discussions with Darrin, the UX will be:
> > * The first time a user opens the panel, he gets a "Try it yourself" button
>
> The two strings that landed are:
> first_time_experience_title={{clientShortname}} — Join the conversation
> first_time_experience_button_label=Get Started
>
> I assume "Try it yourself" was supposed to replace "Get Started" but it
> wasn't on our radar for 35.
>
> It's unclear if this is a UX bug where more work needs to be done by Darrin?
I'm looking at the copy spreadsheet and "Get Started" is the string approved for the in-product start button.
Flags: needinfo?(dhenein)
Comment 7•10 years ago
|
||
The final string for the in-panel button which opens the tour is "Get Started" as found here: https://docs.google.com/a/mozilla.com/spreadsheets/d/1dRhHrnjWIM5cWoKKXs71DHJwZ_nIFeTxwg8zyoFKgiA/
Flags: needinfo?(dhenein)
Updated•10 years ago
|
Updated•10 years ago
|
Target Milestone: mozilla35 → ---
Updated•10 years ago
|
Whiteboard: [ux][rooms] → [ux][FTE]
Comment 8•10 years ago
|
||
Hi Holly,
This is under Loop::client - but we believe the work for this particular is happening on the web team? Is this a duplicate of a bug that's happening on the web work side already? If yes - do you know the bug number?
Flags: needinfo?(hhabstritt.bugzilla)
Comment 9•10 years ago
|
||
(In reply to sescalante from comment #8)
> Hi Holly,
>
> This is under Loop::client - but we believe the work for this particular is
> happening on the web team? Is this a duplicate of a bug that's happening on
> the web work side already? If yes - do you know the bug number?
Hi Shell,
The Dev browser /firstrun experience is a combination of engineering and webprod work, so there is a mix of bugs for this. Let me know if either of these helps you with what you need:
Webprod implementation bug for the Dev Browser /firstrun page
https://bugzilla.mozilla.org/show_bug.cgi?id=1085703
Tracking bug for the engineering work
https://bugzilla.mozilla.org/show_bug.cgi?id=1080942
Flags: needinfo?(hhabstritt.bugzilla)
Comment 10•10 years ago
|
||
thanks Holly, resolving as duplicate of the bug for UI tour content creation.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Comment 11•10 years ago
|
||
The dev browser bug is unrelated to Hello.
You need to log in
before you can comment on or make changes to this bug.
Description
•