Closed Bug 1055220 Opened 11 years ago Closed 11 years ago

Copy and Design for the FindMyDevice [FMD] landing page

Categories

(Marketing :: Design, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Due Date:

People

(Reporter: vkrishnamoorthy, Assigned: tflanagan)

References

Details

Attachments

(7 files)

>>Project/Request Title: Copy and Design for the FindMyDevice [FMD] landing page >>Project Overview: Find My Device is a key feature for 2.0. This feature allows a user to locate their device when required. The feature also provides additional functionality to ring, locate, setNote or erase the device. >> Creative Help Needed: Copy: Yes Design: Yes Video: No Other: No >>Creative Specs: :nchapman can comment on this. The landing page for https://find.firefox.com provides a "sign in" button that allows the user to sign in with their FxA account to access the FindMyDevice services. Currently other than the "Sign In" button and some text "Rumor has it that you can't find your device. Don't worry: we're the app for that. Sign in " The page is largely blank. We would like input on how to design the page to provide a Mozilla look and feel as well as input from marketing to see if there is content that can be incorporated in this page without distracting the user from the main purpose i.e. signing into FMD. >>CTA and Design: ni :jrconlin - JR can you attach the screen grab of the website with the map and the verbs? >>Creative Due Date: 2014-09-08 >>Launch Date: 2014-10-15 >>Mozilla Goal: Firefox OS >>Points of Contact: vkrishnamoorthy@mozilla.com, mtreese@mozilla.com, jsavory@mozilla.com, jgruen@mozilla.com, jrconlin@mozilla.com, nchapman@mozilla.com, jbernard@mozilla.com
Flags: needinfo?(jrconlin+bugzilla)
Flags: needinfo?(jrconlin+bugzilla)
Attached image Logged in; control page
After a user logs in, this is the display page for find.firefox.com
Hi Vishy. Sorry about the slow reply here, and thanks for filing the bug. We still are going to need more info to get started, though. Most importantly, can you give direction on the content for the non-signed in page? I know we talked about it last week, but it's important to have it in written form so people who weren't in the meeting will know what you want. We will handle the Mozilla look & feel part as requested, but need firm info on the content. Is it simply a cleaned-up version of what you have now? Is there more we should add? Re: guidance from marketing as to other topics on the page, I think given the timing involved we should move forward without that (unless you already have it)...the page should be extensible enough that we can add links or other info later as needed. Thanks!
To clarify a bit about my ask in comment #4, when I mention content I'm especially thinking of the functional details and states of the page...do we need to leave room for references to an account, legal text, other miscellaneous details like that. Also, am assigning this to Ty but we won't be able to get started until things are more clear.
Assignee: jbalaco → tyronflanagan
Assignee: tyronflanagan → tflanagan
Status: NEW → ASSIGNED
Vishy - any info on my earlier asks?
Flags: needinfo?(vkrishnamoorthy)
hi John, A) Cleaned up version of what we have now with Mozilla look and feel/branding B) replace the current string with some meaningful info I would like to provide a brief synopsis of each of the features (Listed below) with some visuals 1 Locate your phone 2. Ring 3. Lockscreen 4. Erase
Blocks: 1060104
(In reply to vkrishnamoorthy@mozilla.com [:Vishy] from comment #7) > A) Cleaned up version of what we have now with Mozilla look and feel/branding Thanks Vishy. By "what we have now" do you mean the pre-signed in state or the signed-in state as well? > B) replace the current string with some meaningful info > I would like to provide a brief synopsis of each of the features (Listed > below) with some visuals > 1 Locate your phone > 2. Ring > 3. Lockscreen > 4. Erase Can you explain more about what these features are or what we want people to know about them? Is the idea that someone would come to this page and we'd explain about the different things you can do? Which each one have its own call to action?
The feature description draft is in the etherpad https://etherpad.mozilla.org/FMDlandingpage Matej over to you
Flags: needinfo?(vkrishnamoorthy)
Here's my first stab at copy: https://docs.google.com/a/mozilla.com/document/d/1miVp55bj9srSaMT2Jg5IOhMzcw0KAsdXoKvHP8_Dt2s/edit Have a look and let me know what you think.
Thanks Matej. Vishy, what do you think? Can you coordinate feedback from the product side?
Flags: needinfo?(vkrishnamoorthy)
jslater - I have started commenting on the google doc. ni: jbernard for input from marketing
Flags: needinfo?(jbernard)
Flags: needinfo?(vkrishnamoorthy)
In response to comment 12. Vishy, Matej, looks good to me. Approved.
Flags: needinfo?(jbernard)
Hi all, I have created 3 layouts which could be optioned as the Find My Device landing page. Let me know which you prefer (or not), or would like to edit and move forward with.
Awesome, thanks Ty. I know Nick is in the process of gathering feedback from the FMD team, but I'll throw in a quick 2 cents and say that, although all the layouts are nice, option C seems to best fit my understanding of what's needed from this page.
Ty, these look great! I actually like B best for the following reasons: - The imaging indicates its clearly about Find My Device rather than about Firefox OS in general. - The call to action and intro text share prominence with the leading image. - The header and subhead are connected to the intro text which I think makes it more scannable and feels appropriately connected. - The features at the bottom are largely represented but are more tightly coupled to the leading block than C and therefore don't need the "Features" heading. Those are my favorite bits. I'll leave it Vishy to make the final call. Once we do decide which direction we like best, it'd be great to have a specific version of the design for mobile. I'll make the site responsive so there will likely be more than one break point, but I can work with Ty to interpolate the sizes in between desktop and mobile.
These are great. I like both C and B, C edges slightly for me, so Vishy unless you shout we'll move forward with this. J
Nick, you raise some good points here for B. Will still await Vishy's comments.
setting NI on vishy
Flags: needinfo?(vkrishnamoorthy)
my vote would be B as the user can see the feature description as well as the imaging together. Also on the phone, having the image juxtaposing with the description reduces the need to scroll. Having said that C is also good and both are a vast improvement on what we currently have :)
Flags: needinfo?(vkrishnamoorthy)
Sounds like B is the winner - let's close this as fixed.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
actually, let's get agreement from :jslater. Also, dev needs a Mobile version, is Ty the right person to work on that?
Status: RESOLVED → REOPENED
Flags: needinfo?(tflanagan)
Flags: needinfo?(jslater)
Resolution: FIXED → ---
:jslater out this week, setting NI on :matej for design agreement.
Flags: needinfo?(jslater) → needinfo?(Mnovak)
(In reply to Edwin Wong [:edwong] from comment #25) > :jslater out this week, setting NI on :matej for design agreement. I think all the options are great and I agree with B as the pick. Ty, will you be able to help out with the mobile version?
Flags: needinfo?(Mnovak)
(In reply to Matej Novak [:matej] from comment #26) > Ty, will you be able to help out with the mobile version? I can create a mobile-ready PSD today to match version B and pass on all PSDs tomorrow morning.
Here is a mobile mockup. It is a bit of a combination of B and C, however since they use the same visuals, we should be easily able to place them where needed. Something to consider - Is it important to have the Sign In CTA within the initial screen, or are you ok with having it below the copy and image. I mocked up both scenarios. Let me know what you think. In the meantime, here are the PSDs: Desktop (ver. B) - https://www.dropbox.com/s/gxetnp5yme7ilqj/FFxOS_FindDevice_Final.psd?dl=0 Mobile - https://www.dropbox.com/s/t9rt0soownzxjtw/FFxOS_FindDevice_MobileView.psd?dl=0
Looks great! Thanks Ty! I'll get started on coding this up, and then maybe we can experiment with the location of the buttons on a few different devices.
:ty any chance you could hand off sliced up src or discreet images to Nick. This will speed things up for us. Let us know if you can help us out.
(In reply to Edwin Wong [:edwong] from comment #30) > :ty any chance you could hand off sliced up src or discreet images to Nick. > This will speed things up for us. Let us know if you can help us out. Unfortunately I cant help for the next few weeks. I have several projects related to the FFx 10th Anniversary that are taking priority over everything else on my plate.
(In reply to Ty Flanagan from comment #31) > (In reply to Edwin Wong [:edwong] from comment #30) > > :ty any chance you could hand off sliced up src or discreet images to Nick. > > This will speed things up for us. Let us know if you can help us out. > > Unfortunately I cant help for the next few weeks. I have several projects > related to the FFx 10th Anniversary that are taking priority over everything > else on my plate. Hey Ty If you can hand off your source file, I'm happy to do all the asset exporting and stuff.
Flags: needinfo?(tflanagan)
(In reply to [:jgruen] from comment #32) > Hey Ty If you can hand off your source file, I'm happy to do all the asset > exporting and stuff. Hey John, you'll find the links to the PSDs in comment #28
Nick, here's a folder of the assets, LMK if you need more stuff from the mocks. https://www.dropbox.com/sh/vlb9y8sh4lymd26/AADNvIojzQrf96XK2E42bHLwa?dl=0
Flags: needinfo?(nchapman)
Thanks so much jgruen!
Flags: needinfo?(nchapman)
awesome, let's close this.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: