Closed Bug 810054 Opened 13 years ago Closed 12 years ago

Create Early Adopter Landing Page

Categories

(Marketplace Graveyard :: Developer Pages, defect)

Product:
Marketplace Graveyard
Component:
Developer Pages
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: wenzel, Assigned: ckoehler)

References

Details

(Whiteboard: u=dev c=design p=3 s=2013.1)

Attachments

(5 files, 1 obsolete file)

Have Phone
108.71 KB, image/png
Details
Want phone
221.67 KB, image/png
Details
Subscribe
119.41 KB, image/png
Details
revised wires
112.91 KB, application/pdf
Details
Firefox OS Early Adopters Page
712.70 KB, image/jpeg
Details
The "geek phone" initiative needs a page outlining how to obtain a test device. Ali: Who can help provide information about the requirements for this page?
Whiteboard: u=dev c=design p=3
We can make this live under: https://marketplace.mozilla.org/developers/phone
Summary: Create a "test device" page → Create a "test device" (geekphone) page
Christie, I'm assigning this to you for requirements. Diana mentioned that we'll need documentation and an FAQ, etc. page as well -- I think this should probably live all on the same page.
Assignee: nobody → ckoehler
Target Milestone: --- → 2012-12-13
Summary: Create a "test device" (geekphone) page → Create Early Adopter Landing Page
Hey Christie, Let's set something up, I have a few things I'd like to see integrated into this page/section of the Developer Hub, care to setup a meeting to plan out the reqs?
(In reply to Daniel Buchner [:dbuc] from comment #3) > Let's set something up, I have a few things I'd like to see integrated into > this page/section of the Developer Hub, care to setup a meeting to plan out > the reqs? Let's you and I chat. We've now worked out the requirements from the developer engagement side of things. I'll send you a Zimbra calendar invite.
Target Milestone: 2012-12-13 → 2012-12-20
Target Milestone: 2012-12-20 → ---
Requirements drafted: https://wiki.mozilla.org/Engagement/Developer_Engagement/Early_Adopter_Hardware_Landing_Page#Requirements Let's discuss soon. Target go-live should be end of January.
Attached file Flow and draft wireframes (obsolete) —
Moving this stuff into the bug and out of the email chain.
in response to Fred's question in the email: Should the sign up -> look at resources flow be a chronological order? I.e., Since the devhub link takes them away from the early adopter page with no way to get back (besides the back button), should the UI imply that they should sign up first and then click the "resources" button? I don't think it currently does that. We could explicitly show a 1,2,3 in the graphics for 2a,2b,2c to suggest the order they should do the steps in. If we're localizing into a language that is R->L instead of L->R we would just need to reverse it (which might be more work)
This is looking good. My comments: * We need to use the phrase "FirefoxOS Developer Preview" and not "Early Adopter." (I learned this during my discussions last week with PR & Brand.) * The "I want a phone" link should go directly to the Geeksphone website. This might change in the distant future, but for now, that is the source of developer preview devices. * Is there no way to specify a return page after the user creates a devhub account? If not, can we create an alternate sign up page that includes both the newsletter sign up and the link to more resources?
Answering Fred's questions here: > - 2a: Sign up for Devhub account -- I agree that's just persona, and I > don't think we need it in this context. Instead, they should sign up for > our newsletter (2b). What do you think? What function does having a devhub account serve? Does it just allow developers to submit their apps? If signing up for a devhub account makes no functional difference, then I'm okay if we just ask them to sign up for the newsletter. At some point, we should make sure developers who receive phones are prompted to submit their applications, though. > - Should the sign up -> look at resources flow be a chronological order? > I.e., Since the devhub link takes them away from the early adopter page > with no way to get back (besides the back button), should the UI imply > that they should sign up first and then click the "resources" button? I > don't think it currently does that. If we need to, we can eliminate the call to sign up for a devhub account and just have the newsletter signup and link to resources on one page (a revised version of page 2 in the wireframes. > 3a: Christie, what content should we put there? If none for now, do we > need to put a "coming soon" on the first page and/or allow them to sign > up for the newsletter? If so, are we planning on announcing on that > newsletter when people will be able to buy a dev phone? (In reply to Christie Koehler This won't be a page on devhub. We'll link directly to Geeksphone website from the 'I Want a phone' area on the landing page. > Finally, if we want to hit our intended deadline, we need to move fast. > Christie, if you want to suggest some copy for these pages, that would > be extremely helpful. Likewise, if we have a way to sort out the > graphics soon, that would be good; Michael, is this something you would > be able to help us with? FYI we have a little more breathing room. Only 174 devices will land in Brazil this month; the rest will ship mid-February. I will start working on copy.
(In reply to Christie Koehler [:ckoehler] from comment #9) > Answering Fred's questions here: > > > - 2a: Sign up for Devhub account -- I agree that's just persona, and I > > don't think we need it in this context. Instead, they should sign up for > > our newsletter (2b). What do you think? > > What function does having a devhub account serve? Does it just allow > developers to submit their apps? If signing up for a devhub account makes no > functional difference, then I'm okay if we just ask them to sign up for the > newsletter. At some point, we should make sure developers who receive phones > are prompted to submit their applications, though. There is no functional difference at the moment. The signup is only required to submit an app. > > - Should the sign up -> look at resources flow be a chronological order? > > I.e., Since the devhub link takes them away from the early adopter page > > with no way to get back (besides the back button), should the UI imply > > that they should sign up first and then click the "resources" button? I > > don't think it currently does that. > > If we need to, we can eliminate the call to sign up for a devhub account and > just have the newsletter signup and link to resources on one page (a revised > version of page 2 in the wireframes. Fine by me. Let's cut that part out. Tony, what should that look like? > > 3a: Christie, what content should we put there? If none for now, do we > > need to put a "coming soon" on the first page and/or allow them to sign > > up for the newsletter? If so, are we planning on announcing on that > > newsletter when people will be able to buy a dev phone? (In reply to Christie Koehler > > This won't be a page on devhub. We'll link directly to Geeksphone website > from the 'I Want a phone' area on the landing page. Okay sounds good. What's the target URL then, geekphone.com? > > Finally, if we want to hit our intended deadline, we need to move fast. > > Christie, if you want to suggest some copy for these pages, that would > > be extremely helpful. Likewise, if we have a way to sort out the > > graphics soon, that would be good; Michael, is this something you would > > be able to help us with? > > FYI we have a little more breathing room. Only 174 devices will land in > Brazil this month; the rest will ship mid-February. > > I will start working on copy. I'm glad the timeline was relaxed a little bit. I'll assign this bug to the target milestone 2013.1. I'll file an implementation bug that's blogged by this. Can you please provide (even only preliminary) copy and icons by Tuesday, Jan 29? This will allow UX to give it one last iteration and then off to implementation it goes. Thank you!
Whiteboard: u=dev c=design p=3 → u=dev c=design p=3 s=2013.1
Blocks: 834081
(In reply to Fred Wenzel [:wenzel] from comment #10) > Can you please provide (even only preliminary) copy and icons by Tuesday, > Jan 29? On second thought, let's make this a hard deliverable date. In order to prevent crushing Jen under the weight of a slew of last-minute page implementations (fyi: there are other pages that need landing before MWC too), we need to give her breathing room to implement. This particular page's content needs to arrive on the bug by the time of the Tuesday Ecosystem meeting. Let's make that happen - we can always CRUD it later to optimize it.
(In reply to Daniel Buchner [:dbuc] from comment #11) > On second thought, let's make this a hard deliverable date. In order to > prevent crushing Jen under the weight of a slew of last-minute page > implementations (fyi: there are other pages that need landing before MWC > too), we need to give her breathing room to implement. This particular > page's content needs to arrive on the bug by the time of the Tuesday > Ecosystem meeting. Let's make that happen - we can always CRUD it later to > optimize it. I can come up with copy by then, but I haven't even had a chance to figure out who can help with icons. Does one of you have time to engage with the right person?
Christie, I have been working on some iconography for this page. Please see the following attachments. https://www.dropbox.com/s/xrdvepuu5l2f1a4/FX_Marketplace_EarlyAdopters.ai
Blocks: 834582
Attached file revised wires —
I've revised the documents to include removing the link to signing up for a persona account and the link out to geeksphone.com. Where are we on this? I know we wanted to have everything finished tomorrow, do we need to provide any other graphics for this, or revise the graphics posted? It didn't look like Michael received any feedback on the things he posted last week.
Attachment #703581 - Attachment is obsolete: true
(In reply to Tony Santos [:tsmuse] from comment #18) > Where are we on this? I know we wanted to have everything finished tomorrow, > do we need to provide any other graphics for this, or revise the graphics > posted? It didn't look like Michael received any feedback on the things he > posted last week. I have draft copy that I'm review with Mark later today. We'll also review the icons that Michael created. Mark was in London all weekend for the Apps Day so this is the first change we've had to review things. Will have feedback for you by the morning, PST.
Totally understand, I was in Poland for App Days, so I just wanted to make sure I hadn't fallen behind on anything :)
Okay, Mark and I reviewed. We've simplified the page considerably. It's now one page and we're going to link to either the devhub homepage or Geeskphone. Copy below. The icons Michael did are fine. [HEADLINE] Firefox OS Developer Preview Phone [BODY] Firefox OS is a new mobile operating system built entirely using open web standards. In Firefox OS, HTML5 apps can do “phone things” – they can make the phone vibrate, make a phone call or send a text message. We believe that developers will help bring the power of the web to mobile and so we have worked with Geeksphone and Telefonica to create a device just for you. With a Firefox OS developer preview phone you will be able to create and test your apps on actual hardware, rather than just in the simulator. [ICON: HAVE] I have a developer preview phone Get started today[1] [ICON: WANT] I want a developer preview phone. Order one through Geeksphone[2] [1] link to homepage of devhub [2] http://www.geeksphone.com/
Attachment #706497 - Attachment description: Want Phone → Have Phone
(In reply to Christie Koehler [:ckoehler] from comment #21) > Okay, Mark and I reviewed. We've simplified the page considerably. It's now > one page and we're going to link to either the devhub homepage or > Geeskphone. Copy below. The icons Michael did are fine. Tony, that changes your wireframes, I believe?
It does, but not enough to warrant redoing them again, they've done their job. I handed this off to Michael yesterday afternoon and he should have a mock to share soon.
(In reply to Michael Maslaney from comment #24) > Created attachment 708716 [details] > Firefox OS Early Adopters Page I really like it.
This does look good. I can't see any changes I want to make. Once caveat though: we might need to update the Keon and Peak images. The icons look funky on the Peak and I think one of them has a wrong icon for one of the core apps.
Christie, any updates on this?
(In reply to Jen Fong-Adwent [:ednapiranha] from comment #27) > Christie, any updates on this? On which? To be clear: you can move forward with the design as is. I will work on clarifying if it's okay to use the product images as-is or if we need new ones (this shouldn't block implementation if at all possible).
Christie: Sounds good - since this page in terms of implementation is more or less ready and product images can be considered a separate issue, would it make sense to open a new bug for that and resolve this one?
I'm pretty sure Michael pulled the product images from the Geeksphone page. If we end up with an updated source for product images can you make sure we them too for future use?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Hey Michael, I'll need the PSD for this mock. Thanks!
Christie is this the final copy? Should we be referencing this as "phone things" or should we make it more specific?
I didn't compare what I provided with what's in the psd word-for-word, but what I provided is final copy.
Personally I find the copy to be a bit confusing, mostly "The power of the web to mobile." being a sentence fragment with no verb (I had no idea what that meant when I read it at first.) "Phone things" also seems odd to me; something more akin to "do/perform things/tasks any other phone can perform" makes more sense to me. I don't know what Mozilla's style policy is around Oxford Commas so I'll leave that one alone ;-)
I appreciate the feedback. This text came directly from the announcement on Hacks and was reviewed extensively before being published. Given the volume of work we all have to do before MWC, I'd prefer we not spend time revising copy and getting it re-approved during this cycle. However, the headlines ares something Michael added and I agree the second one is a bit awkward. I will come up with a better one for that paragraph.
Okay, second headline should be: "Bringing the Open Web to mobile devices."
Should we be phrasing our copy in such a way that talks down to developers? I think anyone interested in getting a dev phone already understands that the phone OS does '"phone things"' (sic.), so saying that is like telling a hair dresser that the scissors you're selling do "hair things". Furthermore, I think we should consult the L10n team to make sure that '"phone things"' (sic.) will bear its intended connotation across languages.
Are we localizing this page? That is news to me, but good news at that. Developers aren't the only people that will be landing on this page. I think it's okay to have more general language.
(In reply to Christie Koehler [:ckoehler] from comment #39) > Are we localizing this page? That is news to me, but good news at that. We localize all pages because Firefox OS isn't launching in the US. > Developers aren't the only people that will be landing on this page. Bear in mind that this is the Developer Hub's page for the Developer Phone (which we're only selling to developers). Immediately below it is a big blue button that says "I have a developer phone" (which is presumably targeted towards the developers that own the developer phone). This page is useless to non-developers, and we should be funneling non-developers to less technical places...perhaps the Mozilla Blog or the press site.
The phones will be available for sale to anyone, and we will be giving phones not just to developers. Business partners, press, regular users, etc. will end up with Geeksphone as well as developers. This page will be the destination of devphone.mozilla.org which is printed on the packing of the phone.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: