1056040 - [Roku] Add marketing messages and imagery to the Firefox Roku channel

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: Screencasting, defect)

Description

[Karen Rudnitski [:kar]]

Need marketing & visual design input for the three pages associated with the Firefox Roku channel:
- Introduction (messaging & illustration)
- Recent history (illustration)
- Help (messaging & illustration)

Need this done ASAP, before we make the channel public.

Comment 1

[Karen Rudnitski [:kar]]

Let's also make sure that the correct icon (Firefox 'release' logo) is also displayed. You can do a visual test in SF with wesj's Roku (at least I'm pretty sure he has one in the office there!)

Comment 2

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

Are we talking about a page like this: http://www.roku.com/channels/#!details/12/netflix but for the "Firefox"/"Nightly" channel ?

Comment 3

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

Attachment: Intro.png

Attaching a screen shot of the "intro" screen

Comment 4

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

Attachment: Recent.png

Here's what we currently have for "recent history"

Comment 5

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

Attachment: Help.png

..and here's "Help/Settings"! 

Do these help? (no pun intended)

Comment 6

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

Attachment: mm_icon_focus_HD.png

Their "channel store" also needs an icon, I think we were using this one (their naming conventions are confusing so it might be different in dimensions but this is the combination of wordmark and logo we were going to use.

Comment 7

[Karen Rudnitski [:kar]]

For the logo, not sure if you want to attach the beta version (since that's what we would be targeting) and prepare the release version for when we're ready to hit release client-side. Is the grey background as per branding guidelines?

Comment 8

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

(In reply to Karen Rudnitski [:kar] from comment #7)
> For the logo, not sure if you want to attach the beta version (since that's
> what we would be targeting) and prepare the release version for when we're
> ready to hit release client-side. Is the grey background as per branding
> guidelines?

I think I'd have to update this to the Beta logo then.

As for the grey, I think I took it from what was a derivative of our color palette adapted to work better on TVs.

Comment 9

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

Also - might be worth noting that our support for SD TV sets are kinda iffy ATM - last I remembered we kinda just hoped for the best there so we might want to do another pass on those too.

So, shall I go ahead and change all the build icons to Beta Channel icons?

Comment 10

[Karen Rudnitski [:kar]]

NOTE: need to have this localized into German, French and Spanish as well as per Roku channel support. 

Anthony - yes, I would suggest getting the beta assets ready since we'll make the channel public at the end of next week (latest Sept 1) in support of our client-side beta.

Comment 11

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

(In reply to Karen Rudnitski [:kar] from comment #10)
> NOTE: need to have this localized into German, French and Spanish as well as
> per Roku channel support. 

That will require more work in the codebase as well as getting localizers set up to provide localizations. We have not talked to Axel yet about exactly how localizers would be providing translations. The code for this project is in Github and the Roku channels do not use exactly the same system for L10N as Mozilla uses.
 
> Anthony - yes, I would suggest getting the beta assets ready since we'll
> make the channel public at the end of next week (latest Sept 1) in support
> of our client-side beta.

Just know that we only have ONE Firefox Roku channel for Beta and Release. If we change the icons to Beta, we'll need to change them to Release in 6 weeks and there will be no Beta asseted Firefox Roku channel. Both Firefox Beta and Firefox Release will be using the Release version of the Firefox Roku channel.

Comment 12

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

(In reply to Mark Finkle (:mfinkle) from comment #11)
> (In reply to Karen Rudnitski [:kar] from comment #10)
> > NOTE: need to have this localized into German, French and Spanish as well as
> > per Roku channel support. 
> 
> That will require more work in the codebase as well as getting localizers
> set up to provide localizations. We have not talked to Axel yet about
> exactly how localizers would be providing translations. The code for this
> project is in Github and the Roku channels do not use exactly the same
> system for L10N as Mozilla uses.

OK. I just realized you mean the Store text and not the Channel text, but in fact both are an issue and both have the problem I mention above.

Comment 13

[Karen Rudnitski [:kar]]

Ok. I'll break the l10n issue out into another bug. English is (obviously) the prio and to be honest, is likely the sole focus from Firefox beta users given Roku's footprint currently. Still a concern, but it's not an overwhelming one.

Re: beta vs release. Good point. If you don't think the code will significantly change for the channel, I'm fine promoting it with our 'release' branding (vs beta or nightly) when making it public between Aug 29 - Sept 1.

Comment 14

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

Ok - I'll go ahead and update them all with the Firefox logo (not beta, not nightly)

Comment 15

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

Attachment: Help_official.png

Attaching preview :) Will update rest of the assets later.

Comment 16

[Karen Rudnitski [:kar]]

From the channel screen, it feels there should be a better-explained 'call to action.

1. it says 'get the latest firefox for android', but not how. Can we use the GPlay logo in the corresponding illustration with a short link that users can follow directing them to our landing page?
2. for the 'send a video to your roku', it still doesn't really explain how to do this. At first I loved the image, but now having just gone through it with 'fresh' eyes, I thought this looked like a TV screen (instead of a tablet or a phone in landscape mode'. Maybe it would be more clear to have a 'magnifying glass' over where the 'send video to' icon would be (or circle it on the 'screen')? It just isn't obvious enough, I don't think :/

Comment 17

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

(In reply to Karen Rudnitski [:kar] from comment #16)
> From the channel screen, it feels there should be a better-explained 'call
> to action.
> 
> 1. it says 'get the latest firefox for android', but not how. Can we use the
> GPlay logo in the corresponding illustration with a short link that users
> can follow directing them to our landing page?

I think that's a fair point. But adding a short link would best be done via the "Help & Settings" page since the way this layout is structured isn't really for that (i.e. we'd just be sticking a text link in the image and I'm not convinced about how legibility would scale in that sense).

NI-ing Mark about the Help & Settings page

> 2. for the 'send a video to your roku', it still doesn't really explain how
> to do this. At first I loved the image, but now having just gone through it
> with 'fresh' eyes, I thought this looked like a TV screen (instead of a
> tablet or a phone in landscape mode'. Maybe it would be more clear to have a
> 'magnifying glass' over where the 'send video to' icon would be (or circle
> it on the 'screen')? It just isn't obvious enough, I don't think :/

Magnifying glass would be a bit confusing cause there's a lot of connotations associated with it (like search, zoom, etc) that also don't translate in the touch screen World. I could think about simplifying it to _just_ the 'cast' icon and then just have a finger pointing towards it.. will go off and try that now heh

Comment 18

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

(In reply to Anthony Lam (:antlam) from comment #17)
> (In reply to Karen Rudnitski [:kar] from comment #16)
> > From the channel screen, it feels there should be a better-explained 'call
> > to action.
> > 
> > 1. it says 'get the latest firefox for android', but not how. Can we use the
> > GPlay logo in the corresponding illustration with a short link that users
> > can follow directing them to our landing page?
> 
> I think that's a fair point. But adding a short link would best be done via
> the "Help & Settings" page since the way this layout is structured isn't
> really for that (i.e. we'd just be sticking a text link in the image and I'm
> not convinced about how legibility would scale in that sense).
> 
> NI-ing Mark about the Help & Settings page

Easy to do once we have the link. We could even add a QRCode for the link too.

Comment 19

[Karen Rudnitski [:kar]]

Mark - you were *totally* reading my mind!! Is even looking for QR add-ons and got distracted thinking about QR readers again.

Comment 20

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

*antlam cringes at the thought of QR codes*

I'd be open to a QR code but the thought of someone getting up, moving their phone towards the TV, holding it up to it for a few seconds, seems a bit weird.

I'd suggest a beautifully shortened URL might even be better?

Comment 21

[Karen Rudnitski [:kar]]

> Attaching a screen shot of the "intro" screen

I like the picture, but I think I expect 1 or 2 lines of text that explains what I'm to *do*. Or a short link to get more info (I know it's not a seamless, connected experience but if the link is easy enough, it could be used as a fall0-back option)

Comment 22

[Karen Rudnitski [:kar]]

Sigh - apologies for the spam above, looks like I got confused and was responding to an older comment and just ended up repeating myself from yesterday's comments. 

/drinks more coffee

A short link is easy (even shortened with the mz.l format) but ultimately, the image needs to be a bit more explanatory to what the user is to do with something for 'additional info'.

TBH, I don't think a QR code is appropriate until we have a reader readily available in the browser (which was an older debate, especially for Asian countries where QR codes are used more extensively from what we've heard)