The default bug view has changed. See this FAQ.

What should the app locale listings look like?

RESOLVED FIXED in 2013-05-02

Status

Marketplace
Developer Pages
P1
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: clouserw, Assigned: spasovski)

Tracking

(Blocks: 1 bug)

2013-05-02
Points:
---
Dependency tree / graph

Details

Attachments

(4 attachments)

(Reporter)

Description

4 years ago
We need to support showing developers what locales we're assuming their app supports.  This does not include editing those locales or showing these locales to end users.  This is simply a display in the submission flow and/or edit pages.

We've talked about this before so I think we're good here but let me know if this bug isn't clear.
(Reporter)

Updated

4 years ago
Blocks: 866288

Updated

4 years ago
Assignee: msandberg → bram

Comment 1

4 years ago
Created attachment 742869 [details]
edit listing page - country and language - 01

This is what the edit listing page should look like today, with country and language information added.

Keep in mind that I changed the wording of “region” or “locale” into something that would clearly differentiate: “country” and “language”, because these two have distinct values.

Another bit of text I changed is “Localize for: English (US)”. In order to clarify the intent of this menu, I changed the text to say “Edit listing in: English (US)”. I also moved this text to the left-hand side of the page to be more findable.
(Reporter)

Comment 2

4 years ago
Country is not controlled by the manifest.  Only language is.  I like the other changes.

Comment 3

4 years ago
Created attachment 742886 [details]
submit an app - country and language - 01

This mockup visualizes the country and language fields in the submit an app page. Again, since they’re not changeable unless you modify the manifest file, you won’t be able to edit them on the page.

Comment 4

4 years ago
Created attachment 742896 [details]
edit listing page - country and language - 02

In the future, we’ll redesign the Edit Listing interface to enable in-line editing. When this happens, this mockup shows how we can show country and language information on the page.

Comment 5

4 years ago
(In reply to Wil Clouser [:clouserw] from comment #2)
> Country is not controlled by the manifest.  Only language is.  I like the
> other changes.

This sounds good, but it brings up another problem: where should user modify country information? The tricky thing is, country selection is related to both language and pricing, so it can exist on both pages. But then it’d be somewhat confusing.

Country information can exist on either one of these pages:
* On the Edit Listing page — display country alongside language
* On the Compatibility/Payment page – display country alongside price

Should we allow country information to be editable from two places? This would  be confusing. Should we merge compatibility and payment along with edit listing? This is a monumental effort that will make the merged page very lengthy.
(Reporter)

Comment 6

4 years ago
(In reply to Bram Pitoyo [:bram] from comment #5)
> (In reply to Wil Clouser [:clouserw] from comment #2)
> > Country is not controlled by the manifest.  Only language is.  I like the
> > other changes.
> 
> This sounds good, but it brings up another problem: where should user modify
> country information? The tricky thing is, country selection is related to
> both language and pricing, so it can exist on both pages. But then it’d be
> somewhat confusing.
> 
> Country information can exist on either one of these pages:
> * On the Edit Listing page — display country alongside language
> * On the Compatibility/Payment page – display country alongside price
> 
> Should we allow country information to be editable from two places? This
> would  be confusing. Should we merge compatibility and payment along with
> edit listing? This is a monumental effort that will make the merged page
> very lengthy.

If you want to show country on this page just change the text that you currently have telling them to edit their manifest to something like "Change countries under compatibility options" (or whatever that page is called) and make it a link to the page.

Comment 7

4 years ago
Created attachment 742921 [details]
country and language info box - 01

Based on Wil’s idea on comment 6, here’s a mockup of the country and language info box with captions. User can edit country by going to the compatibility/payment page, and edit language by modifying the app manifest file.
(Reporter)

Comment 8

4 years ago
Thanks.  

I think it should say "Edit countries from..." instead of "Edit country in..."

I think we should link to the section in the docs (bug 866286) where it says to edit languages in the manifest file, since it isn't super clear how to do that.

For the help text, country we can probably steal from the current page.  For language how about "Languages your app is localized for.  These are automatically detected from the manifest." ?

Comment 9

4 years ago
I like your suggestions. To summarize the changes:

Country
Help text: Country-specific Marketplaces your app is listed in
Edit text: Edit countries from the Compatibility page (link: app/payments/)

Language
Help Text: Languages your app is localized for
Edit text: Edit language in the app manifest file (link: d.m.o/docs/Apps/Manifest#locales)
(Assignee)

Comment 10

4 years ago
Seems like this is ready for implementation. I'll take over the UI work.
Assignee: bram → dspasovski
https://github.com/mozilla/zamboni/commit/8a65ca1 adds a model method to get the localized names from the current version.
(Assignee)

Comment 12

4 years ago
doneth: https://github.com/mozilla/zamboni/commit/947957b
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Reporter)

Updated

4 years ago
Target Milestone: --- → 2013-05-02
You need to log in before you can comment on or make changes to this bug.