Closed Bug 844170 Opened 11 years ago Closed 11 years ago

FHR final strings needed for v1

Categories

(Marketing :: Copy, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lco, Assigned: matej)

References

()

Details

(Whiteboard: [fhr])

FHR wireframes: http://cl.ly/2q3V1n1c0k0n

We need to come up with the final strings for the Header, Dashboard View, and Tips Pane for the Health Report.

I'd like to close on this by Feb. 6, or earlier if possible so that we can send them out for localization.

We also need to finalize strings for the Cover Page and the Graph, but we are waiting on the visual design of the Cover Page, and the final visualization of the Graph before we can start those strings.
Whiteboard: [fhr]
I'm guessing you meant March 6 instead of Feb. 6. That sounds good to me. I am on it.
(In reply to Matej Novak [:matej] from comment #1)
> I'm guessing you meant March 6 instead of Feb. 6. That sounds good to me. I
> am on it.

Heh, clearly I was in a rush to get this out. Yes, I meant Feb. 6 :)
(In reply to Larissa Co [:lco] from comment #2)
> (In reply to Matej Novak [:matej] from comment #1)
> > I'm guessing you meant March 6 instead of Feb. 6. That sounds good to me. I
> > am on it.
> 
> Heh, clearly I was in a rush to get this out. Yes, I meant Feb. 6 :)

ughhhh. I mean MARCH 6.
Blocks: 815278
Here are the strings Larissa asked me to have a look at. I've included the line I changed and what I changed it to, but let me know if you have any questions.


OLD: Raw Data 

NEW: Stats & Data OR Numbers & Data


OLD: 
Firefox Health Report provides you with insights about your browser's performance. Learn More.

NEW: 
Get insights and information about the performance of your version of Firefox. Learn more.


OLD: Share with Mozilla

NEW: Data sharing


OLD: Enabled

NEW: On


OLD: Disabled

NEW: Off


OLD: 
Data about your browser use won’t be shared with Mozilla anymore.

You will still be able to see information about your browser's health even though sharing is disabled.

Learn how we handle your data in our privacy policy.

NEW:
You’ve chosen to stop sharing data with Mozilla, but you’ll still be able to see how your browser is performing.

Learn how we handle and protect your data in our privacy policy.


OLD: 
Data about your browser use will now be shared with Mozilla periodically.

Thanks for contributing to our mission by helping to improve our products!

Learn how we handle your data in our privacy policy.

NEW:
You’ve chosen to share your browser data with Mozilla from time to time. Thanks for being part of our mission to build a brighter future for the Web.

Learn how we handle and protect your data in our privacy policy.


OLD: open for

NEW: time open


OLD: 
Your browser has crashed frequently within the last few days. You might want to:

• Visit our support website 
• View more detailed diagnostics 

NEW: 
It looks like your browser has crashed a number of times recently. To learn more:

• Visit our support site
• See more detailed information


OLD: 
Your browser is 5 versions behind the latest one. Updating your browser now may improve your security, performance, and stability.

NEW: 
Your browser is 5 versions out of date. Update now for the latest security, performance and stability.


OLD: 
Your browser is running slower than usual. You might want to: 

• Visit our support website
• View more detailed diagnostics

NEW:
Your browser seems to be running slower than usual. To learn more:

• Visit our support site
See more detailed information


OLD: 
Firefox is a browser built for you by people like you. If you find Firefox Health Report useful and like our browser, we hope you'll help us improve our products by sharing data about your browser use with us.

NEW: 
Firefox is built with a non-profit mission to keep the power of the Web in people’s hands. If you like the sound of that and find Firefox Health Report useful, help us improve our products for users everywhere by sharing your browser data.

You can also see what information we collect and read about how we handle and protect your data in our privacy policy.
Thanks! I've updated the wireframes (now at v5) with the string revisions. Matej and I talked about a couple of tweaks to some strings in comment 4, so they aren't *exactly* the same. Refer to the wireframes for the definitive strings.

We are still missing strings for the graph portion of the page. Once I have the graph finalized, I will let you know. In the wireframe document, these non-final strings are indicated in YELLOW. 

Link to the updated wireframes: http://cl.ly/0d3y1Y27282J
This is now in a repo at https://github.com/mozilla/fhr-jelly
Priority: -- → P1
Matej: Here are the strings required for the graphs:

See pg. 10 and 16 of http://people.mozilla.com/~lco/FHR/130313%20FHR%20wireframes.pdf for the strings that we need to finalize. They are highlighted in yellow.

Thanks!
Here are the new strings. Let me know if you have any questions.


OLD:
Daily Startup Time

NEW:
Startup time by day


OLD:
Startup time helps describe how well your version of Firefox is performing from day to day; in general faster startup time means better performance. Learn more.

NEW:
Startup time helps determine how well your version of Firefox is performing. In general, faster times (i.e. less time) indicate better performance. Learn more.


OLD:
Welcome to your Firefox Health Report! As you use your browser, we can show you more interesting information about it. Check back in a couple of weeks to start seeing some trends.

NEW:
You'll be able to see more interesting and detailed information the more you use your browser. Check back in a couple of weeks to start seeing some trends.
Thanks, Matej!!! This closes work for v1. I'm going to put the strings into the spec and then will close this bug
Status: NEW → ASSIGNED
Added the link to the MVP document. Please refer to the strings on that doc, and not to the ones on this bug (they are almost the same. I just had to tweak a couple of things for legal)
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Blocks: 853120
You need to log in before you can comment on or make changes to this bug.