Closed
Bug 704040
Opened 14 years ago
Closed 13 years ago
mobile developer tools download link out of date
Categories
(www.mozilla.org :: General, defect)
www.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: groovecoder, Unassigned)
References
()
Details
The "Download for Mac OS X" link at https://www.mozilla.org/en-US/mobile/ points at Firefox 4.0.1 when the latest release is 8.0?
Updated•14 years ago
|
Component: Webdev → www.mozilla.org/firefox
OS: Mac OS X → All
Product: mozilla.org → Websites
QA Contact: webdev → www-mozilla-com
Hardware: x86 → All
Comment 1•14 years ago
|
||
Latest release is now 9.0; and those desktop builds are not even supported (XUL). Should these even be listed anymore? CC'ing Jaclyn/Finkle
So all developer tool builds are no longer supported? If so, we should remove this section - are there other developer tools for Native UI we should point them to instead?
(In reply to Jaclyn Fu from comment #2)
> So all developer tool builds are no longer supported? If so, we should
> remove this section - are there other developer tools for Native UI we
> should point them to instead?
Jaclyn, I would advise eliminating this content from the page all-together. The audience isn't developer-focused, so it's not necessarily supporting the best experience we can provide. Instead, we can work with the MDN team on developer-engagement.
Comment 4•14 years ago
|
||
(In reply to mcbmoz from comment #3)
> (In reply to Jaclyn Fu from comment #2)
> > So all developer tool builds are no longer supported? If so, we should
> > remove this section - are there other developer tools for Native UI we
> > should point them to instead?
It's not as easy. I have a blog post about using the emulator to run the native app on a desktop:
http://starkravingfinkle.org/blog/2011/11/firefox-for-android-using-the-android-emulator/
> Jaclyn, I would advise eliminating this content from the page all-together.
> The audience isn't developer-focused, so it's not necessarily supporting the
> best experience we can provide. Instead, we can work with the MDN team on
> developer-engagement.
I agree.
Ok - Chrissie let's rework this section to point them to the proper MDN resources then? Should we do some copy + link/button or something else?
(In reply to Jaclyn Fu from comment #5)
> Ok - Chrissie let's rework this section to point them to the proper MDN
> resources then? Should we do some copy + link/button or something else?
I'd advise that we should eliminate the content that's there and not replace it. Instead keep things simple, which makes l10n simpler too. MDN isn't localized.
Let's fire up an email thread with Stormy to let her know that we took this away, and ask her what her thoughts are on replacing the content in a future release, where it would help her engagement efforts. This page isn't a developer destination, so I'm thinking this ends up benefiting the user with a cleaner content strategy.
| Reporter | ||
Comment 7•14 years ago
|
||
(In reply to mcbmoz from comment #6)
"MDN isn't localized."
Say what? That's news to me - I have to extract new localization strings every time we push MDN code. :)
(In reply to Luke Crouch [:groovecoder] from comment #7)
> (In reply to mcbmoz from comment #6)
> "MDN isn't localized."
Content localizeded in:
el
es
fr
fy-nl
hu
id
hr
ga-ie
ja
ko
nl
pl
pt-br
pt-pt
ro
sq
th
zh-cn
zh-tw
> Say what? That's news to me - I have to extract new localization strings
> every time we push MDN code. :)
However, the /mobile content is not localized over to the wiki, ex: https://developer.mozilla.org/fr/mobile, so it would still not be a full solution at this time.
Back over to Jaclyn -
are you good to reduce the content on the current page, taking out:
developer tools
replacing with
Need help? Visit our Firefox for Android Support site. (moving that bit of text into the box to keep the symmetry)
Comment 10•14 years ago
|
||
Sounds good. Are we going to use a link or a button to get them to SUMO?
Comment 12•14 years ago
|
||
This is going to get resolved with the next update: Bug 724054
Change:
Replacing the Developer Tools content box with SUMO content, and removing the "Need help?" line (above "Want to test the latest features?"):
Content that will replace the Developer Tools module:
header: Need Help?
button: Visit our Firefox for Android Support site [links to http://support.mozilla.org/mobile]
If it's ok, going to close out!
| Assignee | ||
Updated•14 years ago
|
Component: www.mozilla.org/firefox → www.mozilla.org
Comment 15•14 years ago
|
||
hashing it out in Bug 717741 to update on MDN
| Assignee | ||
Updated•13 years ago
|
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
Comment 16•13 years ago
|
||
The page has been redesigned and those links have gone.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•