canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,043
edits
Marketplace/Features/Country Stores: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
|Feature name=Region Stores | |Feature name=Region Stores | ||
|Feature stage=Definition | |Feature stage=Definition | ||
|Feature status= | |Feature status=Complete | ||
|Feature version=Marketplace June | |Feature version=Marketplace June | ||
|Feature health=OK | |Feature health=OK | ||
|Feature status note= | |Feature status note=Looking for feedback from l10n. | ||
}} | }} | ||
{{FeatureTeam | {{FeatureTeam | ||
| Line 11: | Line 11: | ||
|Feature feature manager=Wil Clouser | |Feature feature manager=Wil Clouser | ||
|Feature lead engineer=Unassigned | |Feature lead engineer=Unassigned | ||
|Feature localization lead=Chris Hofmann | |||
|Feature qa lead=Krupa Raj | |Feature qa lead=Krupa Raj | ||
|Feature additional members=Michael Treese | |||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature overview=App stores that target users of different regions and languages need a way to deliver relevant, local content to those users. The Mozilla Marketplace will have a phased roll-out to particular locales, while still allowing users worldwide to discover and use apps. To facilitate this, we need a way for users to be taken to the most appropriate region store with their preferred language, and for developers to indicate which regions their content should be displayed in. | |Feature overview=App stores that target users of different regions and languages need a way to deliver relevant, local content to those users. The Mozilla Marketplace will have a phased roll-out to particular locales, while still allowing users worldwide to discover and use apps. To facilitate this, we need a way for users to be taken to the most appropriate region store with their preferred language, and for developers to indicate which regions their content should be displayed in. | ||
|Feature users and use cases=1. A user who lives in Brazil (supported | |Feature users and use cases=1. A user who lives in Brazil (supported region) speaks Portuguese and opens the Marketplace app. He should see the Marketplace in Portuguese with featured Brazilian apps and locally popular apps. Prices should be displayed in Reals. | ||
2. A user in New Zealand ( | 2. A user in New Zealand (supported region) searches for "restaurant ratings" to find a good restaurant ratings and reviews app. Yelp doesn't have relevant content in NZ, but DineOut does. Users in different regions have rated the apps accordingly. Search results should surface DineOut as a locally relevant app despite Yelp dwarfing it in global popularity. | ||
3. Hulu is only allowed to license streaming video content within the US, and does not want their app listing to be available outside of the US. | 3. Hulu is only allowed to license streaming video content within the US, and does not want their app listing to be available outside of the US. | ||
4. A user in Russia ( | 4. A user in Russia (unsupported region) loads the Mozilla Marketplace. She should see international, country-agnostic content and be able to use all the features of the Marketplace. | ||
|Feature non-goals=We | |||
5. An English-speaking user from the United States visits France on a business trip, having previously visited the Marketplace from the US. His experience should remain unchanged. | |||
6. An English-speaking student from the US studying abroad in France purchases a B2G phone. The Marketplace initially loads in French / France, but she changes the language to English to better understand the content. | |||
|Feature dependencies=IP-based geolocation service | |||
Identification of locale codes B2G will send | |||
|Feature non-goals=We will not block users from accessing other regions or content in the Marketplace. Apps that require certainty of a user's location (e.g. for content licensing purposes) should detect that themselves inside their app. | |||
|Feature functional spec=A user's localized experience in the Marketplace hinges on two components: language and region. Language is based on the user's browser's preferred language settings (e.g. en-US, pt-BR, etc.). Region is based on the user's physical location, determined by IP address. Both language and region are automatically detected but can be changed by the user. | |Feature functional spec=A user's localized experience in the Marketplace hinges on two components: language and region. Language is based on the user's browser's preferred language settings (e.g. en-US, pt-BR, etc.). Region is based on the user's physical location, determined by IP address. Both language and region are automatically detected but can be changed by the user. | ||
| Line 54: | Line 62: | ||
==== Developers ==== | ==== Developers ==== | ||
By default, apps are listed in all | By default, apps are listed in all regions. Developers may opt out of particular regions at submission or through managing their app's details. | ||
Managing regions: | |||
http://f.cl.ly/items/302c0g1C1U2f051M3Z1c/Screen%20Shot%202012-06-01%20at%202.33.40%20PM.png | |||
http://f.cl.ly/items/ | Once regions are selected: | ||
http://f.cl.ly/items/1T121H2z2J1C0G2d0n1p/Screen%20Shot%202012-06-01%20at%202.35.55%20PM.png | |||
http://f.cl.ly/items/343O0y1E3Z263W0z3u0B/Screen%20Shot%202012-06-01%20at%202.48.58%20PM.png | |||
When a new region becomes officially supported, apps that are listed in Unsupported will automatically be added to the new region. Apps not listed in Unsupported will not be listed in the new region and must opt in. | |||
|Feature implementation plan=Phase 1: | |Feature implementation plan=Phase 1: | ||
For June, the features above except for the regional popularity score and dependencies (regional popular lists and search results) are included. | For June, the features above except for the regional popularity score and dependencies (regional popular lists and search results) are included. | ||