1045495 - Link clicker UI needs new UX for notification of non supported platform

Status: RESOLVED FIXED

(Hello (Loop) :: Client, defect, P2)

Description

[Romain Testard [:RT]]

Implementation of new UX for non supported platform scenarios (iOS).
Current experience: https://call.mozilla.com/#unsupportedDevice

Comment 1

[Romain Testard [:RT]]

Darrin, could you please provide UX for this?

Comment 2

[Romain Testard [:RT]]

Arcadio, we discussed about this. Can you let us know if you have specific wording requirements given this is an opportunity to promote Firefox to non Firefox users?

Comment 3

[Darrin Henein [:darrin]]

The actual UX will be pretty much the same as https://people.mozilla.org/~dhenein/labs/loop-link-spec/#link-expired, with different copy provided from marketing. Rather than "The URL is no longer available", I imagine we would have something like "Firefox Hello only works in Web-RTC enabled browsers" or something along those lines. I'm clearing my needinfo for now, as this is likely just a copy change.

Comment 4

[:shell escalante]

can we make this the minimal bug possible - which is to just change the product name to Hello instead of Loop?  We can revisit later for the design possibilities. If there's more wording wanted, fine - but i'd say spending design implementation time here is not where we want to invest first.  i could be wrong.

Comment 5

[Maire Reavy [:mreavy]]

Since this is link clicker side, I'm moving this to the Fx 35 cycle (sept 1 - oct 13)

Comment 6

[Mark Banner (:standard8)]

(In reply to sescalante from comment #4)
> can we make this the minimal bug possible - which is to just change the
> product name to Hello instead of Loop?  We can revisit later for the design
> possibilities. If there's more wording wanted, fine - but i'd say spending
> design implementation time here is not where we want to invest first.  i
> could be wrong.

I think the wording is fine (I believe it has been validated before) - see https://call.mozilla.com/#unsupportedDevice (WebRTC! will be replaced at the appropriate time).

Arcadio, if you can confirm this text, then we could update the UX to match what Darrin suggests.

Comment 7

[Romain Testard [:RT]]

Arcadio can you please let us know if you have views on wording there?

Comment 8

[alainez]

Mark, RT,

Here are the lines. Let me know if these work and hopefully we already have these. 


"Firefox Hello only works in browsers that support WebRTC"
“Get Firefox and enjoy free audio and video conversations with friends”

Comment 9

[Romain Testard [:RT]]

Thanks.
This bug is about non supported platforms (iOS).
What should we tell the user given he won't be able to download Firefox on iOS?

Comment 10

[:shell escalante]

taking off priority until have missing info

Comment 11

[:shell escalante]

updating user story with darrin's UX and arcadios wording.

Comment 12

[:shell escalante]

Hi Arcadio - so go through with Darrin and RT - the words make sense for browser but not for unsupported platforms.  so need to determine what to write for those.

Also - both this and bug 1045498, should they have the Hello logo there as well?  or are we going to stick with the UX listed in the User Story (Firefox logo only).  Just need marketing decision on that.

Comment 13

[:shell escalante]

Hi Arcadio - so go through with Darrin and RT - the words make sense for browser but not for unsupported platforms.  so need to determine what to write for those.

Also - both this and bug 1045498, should they have the Hello logo there as well?  or are we going to stick with the UX listed in the User Story (Firefox logo only).  Just need marketing decision on that.

Comment 14

[:shell escalante]

We're not planning to take this bug unless we hear some good direction on what we should put for wording.  Right now we just say "you are on an unsupported platform".  not sure we have anything helpful to suggest

Comment 15

[Sevaan Franks [:sevaan]]

I would suggest that on unsupported platforms we just tell the user that: Sorry! <PLATFORM> does not currently support Firefox Hello!

Again though, in Darrin's UX (https://people.mozilla.org/~dhenein/labs/loop-link-spec/#link-expired) rather than just an empty white page.

Comment 16

[Romain Testard [:RT]]

(In reply to Sevaan Franks [:sevaan] from comment #15)
> I would suggest that on unsupported platforms we just tell the user that:
> Sorry! <PLATFORM> does not currently support Firefox Hello!
> 
> Again though, in Darrin's UX
> (https://people.mozilla.org/~dhenein/labs/loop-link-spec/#link-expired)
> rather than just an empty white page.

Yes I am OK there - Arcadio is that fine with you?

Comment 17

[Sevaan Franks [:sevaan]]

Attachment: Sorry! <PLATFORM> does not currently support Firefox Hello!

Screen with new text.

Comment 18

[Romain Testard [:RT]]

We should remove the exclamation marks per Arcadio's previous comments on branding.
Arcadio, does this look, fine to you?

Comment 19

[alainez]

That is correct, Romain. No exclamation point after Firefox Hello.

Comment 20

[alainez]

But to answer the question is this OK. It delivers the message that it's a supported platform. 

We could however redirect the user (if the choose) to the Hello product landing page or to learn more about why iOS doesn't support Hello...just want to makes sure it's iOS's problem not Hello's problem in the mind of the user.

Comment 21

[Romain Testard [:RT]]

A link to that SUMO page sounds good?
https://support.mozilla.org/en-US/kb/which-browsers-will-work-firefox-hello-video-chat

Comment 22

[alainez]

That's perfect.

Comment 23

[Romain Testard [:RT]]

Sounds like we're all set, SHell can we add this to the Trello?

Comment 24

[Mark Banner (:standard8)]

Attachment: Loop's link clicker UI needs new UX for notification of non supported platform

I've not got devices to check this on all the different platforms, but I tested it with returning the expected values from the platform detection function.

Comment 25

[Mike de Boer [:mikedeboer]]

Comment on attachment 8559708 [details] [diff] [review]
Loop's link clicker UI needs new UX for notification of non supported platform

Review of attachment 8559708 [details] [diff] [review]:
-----------------------------------------------------------------

LGTM, thanks!

::: browser/components/loop/test/standalone/standaloneAppStore_test.js
@@ +106,2 @@
>      it("should set windowType to `unsupportedDevice` for IOS", function() {
>        // The stub should return true for this test.

nit: please update this comment.

@@ +106,3 @@
>      it("should set windowType to `unsupportedDevice` for IOS", function() {
>        // The stub should return true for this test.
> +      loop.shared.utils.getUnsupportedPlatform.returns("IOS");

This function ought to return strings in all lowercase...

Comment 26

[Mark Banner (:standard8)]

https://hg.mozilla.org/integration/fx-team/rev/ccb3d766ea41

Comment 27

[Ryan VanderMeulen [:RyanVM]]

https://hg.mozilla.org/mozilla-central/rev/ccb3d766ea41