Closed Bug 1210207 Opened 9 years ago Closed 9 years ago

/content page needs to be made pretty

Categories

(Marketplace Graveyard :: Developer Pages, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: krupa.mozbugs, Assigned: kngo)

References

()

Details

https://marketplace-dev.allizom.org/content/ has a lot of white space right now and could use some change in copy and some graphics.

Suggestions:
1. <FxOS logo> + <add-on logo> = <3 (I know right, adorable!)
2. Change the copy of the heading 'New for Firefox OS… Add-ons.' 
.
.
.
Flags: needinfo?(dalmstrom)
The copy and content came from Liz's UX spec: https://drive.google.com/a/mozilla.com/file/d/0By5ZvBZQRgjRNW9Wek1HT3BDb1U/view

And the visual design has Phil's blessing.

I agree that it isn't great, but I think any design, copy, or content change here needs to come from product and has to be a low priority for branch.
Also: (っ˘̩╭╮˘̩)っ
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Can we please change the copy on this page?

How about "Hack on your FirefoxOS phone with Add-ons" instead of "New for Firefox OS… Add-ons."?

It will go better with the second line.
Status: RESOLVED → REOPENED
Flags: needinfo?(ddurst)
Flags: needinfo?(charmston)
Flags: needinfo?(adora)
Resolution: FIXED → ---
This is probably Lisa's call. Happy to make any changes she'd like.
Flags: needinfo?(charmston)
Adding Sandip to the needinfo canoe, he was already working on some other messaging.
Flags: needinfo?(adora) → needinfo?(skamat)
Flags: needinfo?(ddurst)
Priority: -- → P3
Flags: needinfo?(dalmstrom)
(In reply to Lisa Brewster [:adora] from comment #5)
> Adding Sandip to the needinfo canoe, he was already working on some other
> messaging.

I would suggest the following to align with the messaging being created. I am working with +Natalia on this. Natalia, please review as well.

"Hack on Firefox OS with Add-ons. 
Just like for the browser. Only for mobile and more powerful."
Flags: needinfo?(skamat) → needinfo?(nwinter)
I'm not a copywriter, however I'm happy to help by providing a bit more context on the messaging brief (hope that it can inspire you):

Firefox OS 2.5 principles:
Build a platform together, anyone can contribute  (= especially through add-ons)
Value creativity and diversity by inviting anyone to join a global playing field
Open innovation : Create experiences that can transform the lives of people

Value prop:
Firefox OS provides a modular and open mobile platform that you can hack in order to deliver new experiences that people love.

For Makers who want to create new things and make their impact on the world, Firefox OS is the mobile platform that allows them to create new experiences, by empowering them to transform the future. They will not only be able to customise their own experience but they will also be able to share their creations and get recognition. They will also have an impact on the mobile web by improving and adding features to Firefox OS.

I wonder if there's enough place to add 2 lines of text below the tagline that you're suggesting
"Hack on Firefox OS with Add-ons. 
Just like for the browser. Only for mobile and more powerful."

I wonder if the reference to browser is useful (I don't know the audience that might land on this page, if it's web devs who usually develop for desktop, makes totally sense). Maybe we could explain a little bit more what we mean by "more powerful" = You can customise the whole phone experience.

It would be great to know what are the main motivations of devs ("change the world" ? "freedom to create new features" ? "improve the OS" ? "customise your experience"?...) to help defining the best tagline ;-)
Flags: needinfo?(nwinter)
(In reply to krupa raj[:krupa] from comment #3)
> Can we please change the copy on this page?
> 
> How about "Hack on your FirefoxOS phone with Add-ons" instead of "New for
> Firefox OS… Add-ons."?
> 
> It will go better with the second line.

agree. it's a clearer Call To Action whereas the latter is just descriptive.
I think the point about the line that references browser is a good one. I don't think we can/should assume that desktop add-on devs are FxOS add-on devs, so referencing the browser might actually turn more people away ("I have to learn about desktop add-ons first? Forget it"). The important part is the "hacking" (I hate that word) via add-ons, the open invitation, and the notion that you can change a lot of your experience.

*WE* know it's more than desktop can. And *everyone* will know it's for mobile. That second line can go away or change to something entirely different, but what's there isn't useful.</in-my-opinion>
(In reply to David Durst [:ddurst] from comment #9)
> I think the point about the line that references browser is a good one. I
> don't think we can/should assume that desktop add-on devs are FxOS add-on
> devs, so referencing the browser might actually turn more people away ("I
> have to learn about desktop add-ons first? Forget it"). 

good point

> The important part
> is the "hacking" (I hate that word) via add-ons, the open invitation, and
> the notion that you can change a lot of your experience.
> 
> *WE* know it's more than desktop can. And *everyone* will know it's for
> mobile. That second line can go away or change to something entirely
> different, but what's there isn't useful.</in-my-opinion>

My suggestion is highlighting the ability to customize the entire mobile experience. "Hack" as a term may not as user-facing as it is dev-facing. So that's a nuance we need to be aware of.  

For now, I think something along the lines of "Personalize your Firefox OS experience with powerful add-ons" would do. We can iterate if needed towards the moment in time campaign.
We might remove "powerful" from the copy later on. Doesn't really fit and flow as it would without. But nevertheless, changed:

https://github.com/mozilla/marketplace-content-tools/pull/70
Assignee: nobody → kngo
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.