1178217 - Updates to Hello FTU (due to "Talk about this page" feature)

Status: RESOLVED FIXED

(www.mozilla.org :: Pages & Content, defect)

Description

[Alex Gibson [:agibson]]

Following our email discussion, the "Talk about this page" feature that is dues to land in Firefox 40 was not really planned for when we originally designed the Hello FTU. 

Because we can not guarantee where the elements are going to be in the various Hello panels, both the messaging and alignment of UITour panels no longer works as well as it used to.

Given timing, it may be best to show the default "simple" FTU when this lands:

Proposed temporary solution from Habber:

"I think we should just default to this page for 40. Apparently there are new designs coming for 41 and 42."

So, users < 40 would still be able to get the current FTU, but Fx >= 40 would be shown the simple version. 

Does this sounds like a good solution to everyone for now?

Comment 1

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

Hi Alex,

Thanks for the suggestion. Do we have everything we need to deploy the static page? I've referenced what I believe to be the relevant bug here.

Comment 2

[Alex Gibson [:agibson]]

Hi Cory,

I believe we already have everything we need, including strings already translated.

Thanks

Comment 3

[Holly Habstritt Gaal [:Habber]]

(In reply to Alex Gibson [:agibson] from comment #0)
> Following our email discussion, the "Talk about this page" feature that is
> dues to land in Firefox 40 was not really planned for when we originally
> designed the Hello FTU. 
> 
> Because we can not guarantee where the elements are going to be in the
> various Hello panels, both the messaging and alignment of UITour panels no
> longer works as well as it used to.
> 
> Given timing, it may be best to show the default "simple" FTU when this
> lands:
> 
> Proposed temporary solution from Habber:
> 
> "I think we should just default to this page for 40. Apparently there are
> new designs coming for 41 and 42."
> 
> So, users < 40 would still be able to get the current FTU, but Fx >= 40
> would be shown the simple version. 
> 
> Does this sounds like a good solution to everyone for now?

I'm still in favor of this solution for >=40 as we proceed to discuss the best solution to support the design changes in the Hello UI.

Comment 4

[Alex Gibson [:agibson]]

Thanks both, I'll move forward with this for now and put something up on a demo server for review.

Comment 5

[Alex Gibson [:agibson]]

Ok I've made a very quick WIP for this and pushed to demo2

Please make sure to use Firefox 40 or above and to set your config before trying the 'Tour' link in the Hello panel:

loop.gettingStarted.url = https://www-demo2.allizom.org/%LOCALE%/firefox/%VERSION%/hello/start/
browser.uitour.testingOrigins = https://www-demo2.allizom.org

Comment 6

[Alex Gibson [:agibson]]

Attachment: hello-ftu-40.png

Attached a screenshot of what users on Firefox >= 40 will see upon landing on the page.

Comment 7

[Alex Gibson [:agibson]]

Another question is: what level of tracking do we want/need to retain on this version? We can no longer do the full conversation conversion tracking since this is a simplified static page, but we could still track clicks on the copy/share URL buttons for example.

Comment 8

[Holly Habstritt Gaal [:Habber]]

Standard link tracking within the page as well as any tracking possible within the feature elements would be great. What elements, besides copy/share can we track?

Also, is it possible to track which users successfully have their conversation joined? Users whose link was received and interacted with in the non-static version of the tour (that we are taking down) will be redirected to http://cl.ly/image/3E123f2e0Z0f Does this still happen from the new static page? If so, is it possible to track which users made it to this page from the static page you've implemented?

Comment 9

[Alex Gibson [:agibson]]

(In reply to Holly Habstritt Gaal [:Habber] from comment #8)
> Standard link tracking within the page as well as any tracking possible
> within the feature elements would be great. What elements, besides
> copy/share can we track?
> 
> Also, is it possible to track which users successfully have their
> conversation joined? Users whose link was received and interacted with in
> the non-static version of the tour (that we are taking down) will be
> redirected to http://cl.ly/image/3E123f2e0Z0f Does this still happen from
> the new static page? If so, is it possible to track which users made it to
> this page from the static page you've implemented?

We can track on regular things like button clicks on copy/share as before, like mentioned above. Because this is a simplified static page, I assumed we we're not doing the whole tab reconnection / reopening thing anymore. Is this not the case? This would require considerably more thought than this quick fix until it all gets redesigned.

Comment 10

[Holly Habstritt Gaal [:Habber]]

(In reply to Alex Gibson [:agibson] from comment #9)
> (In reply to Holly Habstritt Gaal [:Habber] from comment #8)
> > Standard link tracking within the page as well as any tracking possible
> > within the feature elements would be great. What elements, besides
> > copy/share can we track?
> > 
> > Also, is it possible to track which users successfully have their
> > conversation joined? Users whose link was received and interacted with in
> > the non-static version of the tour (that we are taking down) will be
> > redirected to http://cl.ly/image/3E123f2e0Z0f Does this still happen from
> > the new static page? If so, is it possible to track which users made it to
> > this page from the static page you've implemented?
> 
> We can track on regular things like button clicks on copy/share as before,
> like mentioned above. Because this is a simplified static page, I assumed we
> we're not doing the whole tab reconnection / reopening thing anymore. Is
> this not the case? This would require considerably more thought than this
> quick fix until it all gets redesigned.

Just getting clarification on that as I wasn't sure if it would still happen. The redirect wasn't necessarily something broken by the new Hello UI like the tips/doorhangers were, so I wanted to double check before assuming we would track to that page. 

This interim fix should be as simple on the web and product engineering side as possible. It is fine that this static page is the full experience and that no redirect happens.

Comment 11

[Alex Gibson [:agibson]]

We could still technically make the tab re-connection thing happen, if we really thought it was vital, but then this turns into a much larger piece of dev work (and possibly one of my Q3 deliverables, as opposed to something I can easily fit in between other stuff).

Comment 12

[Alex Gibson [:agibson]]

(In reply to Holly Habstritt Gaal [:Habber] from comment #10)
> Just getting clarification on that as I wasn't sure if it would still
> happen. The redirect wasn't necessarily something broken by the new Hello UI
> like the tips/doorhangers were, so I wanted to double check before assuming
> we would track to that page. 

re: the redirect not breaking by the new UI

Considering that when a tab reconnects, it is not always in the completed state (i.e. it could still be "conversation waiting"). In this case, the UITour step would normally involve a door-hanger, which would now no longer look correct in Fx40 due to the new UI changes.

Comment 13

[Fabio Rios [:frios]]

Do you know if Optimizely be included on the static page? We want to have the ability to update the content so Growth team can test messaging/graphics. Do you need anything from us there?

Bummer on the connected conversation redirect. That said, the Hello team is investigating how to pass some parameters over to the loop server to measure connected calls by source. That may replace the need to see it in Google Analytics. Possible to append another parameter later?

Comment 14

[Alex Gibson [:agibson]]

(In reply to Fabio Rios [:frios] from comment #13)
> Do you know if Optimizely be included on the static page? We want to have
> the ability to update the content so Growth team can test
> messaging/graphics. Do you need anything from us there?

Sure, we can add Optimizely to the static page as a conditional.

Comment 15

[Alex Gibson [:agibson]]

Ok, it looks like this proposal has been put under the noses of plenty of people via email - I'm going to move forward with this and make a PR. I'll mark it as do-not-merge and push the branch to a demo for final approval before we merge.

Comment 16

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

Thanks Alex. Yes, Fabio has approved the static version. Let's make sure Optimizely is enabled on the page please.

Comment 17

[Alex Gibson [:agibson]]

Ok, we have a copy problem:

3: The Hello icon will change to blue once they’ve joined

This is incorrect, the hello icon turns blue as soon as someone has opened a room.

Should it actually say "You will receive a notification once they've joined"?

See also: bug 1145096

Comment 18

[Matej Novak [:matej]]

(In reply to Alex Gibson [:agibson] from comment #17)
> Ok, we have a copy problem:
> 
> 3: The Hello icon will change to blue once they’ve joined
> 
> This is incorrect, the hello icon turns blue as soon as someone has opened a
> room.
> 
> Should it actually say "You will receive a notification once they've joined"?

I actually noticed this same thing yesterday and forgot to follow up on it.

+1 to the suggestion above.

Thanks, Alex.

Comment 19

[Alex Gibson [:agibson]]

(In reply to Matej Novak [:matej] from comment #18)
> (In reply to Alex Gibson [:agibson] from comment #17)
> > Ok, we have a copy problem:
> > 
> > 3: The Hello icon will change to blue once they’ve joined
> > 
> > This is incorrect, the hello icon turns blue as soon as someone has opened a
> > room.
> > 
> > Should it actually say "You will receive a notification once they've joined"?
> 
> I actually noticed this same thing yesterday and forgot to follow up on it.
> 
> +1 to the suggestion above.
> 
> Thanks, Alex.

Ok thanks Matej - we can use an l10n tag for this one, hopefully by the time Firefox 40 lands many locales will have translated. Clearing needs info for Cory.

Comment 20

[Alex Gibson [:agibson]]

Attachment: GitHub pull request

Comment 21

[Alex Gibson [:agibson]]

Ok I've pushed the latest to demo2 for review/testing. All existing GA tracking events are still honored, with the exception of the conversation connected state. So we should still see events like clicking "get started", clicking the copy buttons to share a room etc.

Cory, if you have some time can you please give demo2 a check to see that the events look ok? Thanks

Comment 22

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

Hey Alex,

Looks like all the events are firing on demo2.

http://cl.ly/image/0y422u1K3N2J

Thanks!

Comment 23

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/37618f006cf52e2d94b527492aa7614bbc03fe6d
[fix bug 1178217] Updates to Hello FTU for Firefox 40

https://github.com/mozilla/bedrock/commit/d5998647cf69113be3e11da7e3174aeb528d131b
Merge pull request #3115 from mozilla/bug-1178217-updates-hello-ftu-firefox-40

[fix bug 1178217] Updates to Hello FTU for Firefox 40