Marketplace/AddingRegionsAndCarriers

From MozillaWiki
Jump to navigation Jump to search

Adding new markets to the marketplace requires some thought. Below are some considerations.

Commercials and Legal

One of the first steps of a formal engagement with a new country / carrier is the alignment of the contractual agreements between our organizations.

Legal

  • Who is the local legal counsel?
  • Are there unique rules, regulations which apply in the given region?
  • Are there unique scenarios with payment / tax support on a local, regional or national level?

Payments

Mozilla works with Operators to ensure consistent and compliant payments systems. If you are a new partner, you can begin your payments on-boarding form, below. The Firefox Marketplace team will use your response to develop the spec for your Marketplace Payments integration.

Key Payments Considerations

  • What currencies are supported for carrier billing? for credit cards?
  • What are the pricing differences for carrier billing vs credit cards?
  • What are the tax breakdowns: carrier billing/credit card, national/local, special (eg. VAT), etc.
  • What is the refund policies & regulatory requirements?
  • Can the carrier do automatic refunds? How do we interface with that system?
  • Who are the local contacts for in-country testing?
  • Can you provide SIM cards for local and foreign testing (at least 10).

Localization and Configuration of Marketplace for a Carrier

Mozilla works with Operators to ensure consistent and compliant content management. If you are a new partner, you can begin your onboarding form, below. The Firefox Marketplace team will use your response to develop the spec for your Marketplace.

Operator Shelf

Mozilla has the ability to customize a category of the Firefox Store just for Operators. Operators can define the content located in the Operator Shelf category up to 15 content items. The content chosen for this page will be shown at random.

v1 Specs (Shelf)

  • Operator Shelf Designs
  • Specs
    • [Category Page Logo]
      • Format: Vector graphic. EPS or AI
      • Color, Regular format: RGB (199,199,199)
      • Mobile Size 64x64 pixels
      • Alternative color suggestions: (0,150,221) (111,78,159) (117,191,67) (254,170,32)
      • Any specific logo behavior or required usage/placement?
    • What company / operator name should Mozilla use in-country?
    • What file should Mozilla use to represent the operator logo on the Operator Shelf page?
    • Who is the UX / Design point of contact to ensure it works with the design of the Firefox Marketplace?
  • Operator Shelf Administration: Operator Shelf Policies & Process

v2 Specs (Collections/Feed)

  • Marketplace Operator Shelf v2 (The Feed) Image Specs(PDF)
  • Specs
    • One image for display in The Feed
      • Format: PNG or JPG
      • Color: RGB
      • Size: 320px x 90px
      • Title text no longer than 25 characters
      • Optional: color for overlay bar provided as hex-rgb (e.g. #FFFFFF)
      • Optional: color for title text provided as hex-rgb (e.g. #FFFFFF)
    • One image for display on the Operator Shelf Page
      • Format: PNG or JPG
      • Color: RGB
      • Size: 320px x 150px
      • Title text no longer than 25 characters
      • By-line text no longer than 43 characters
      • Optional: color for overlay bar provided as hex-rgb (e.g. #FFFFFF)
      • Optional: color for title text provided as hex-rgb (e.g. #FFFFFF)

Please see the Marketplace Operator Shelf v2 (The Feed) Image Specs document linked above for examples of these images in the user interface.

L10n

Mozilla has a robust community who translates our product into many languages. However, local languages must be identified and translators confirmed.

Legal Checklist

  • Any regulatory or legal consumer, privacy, content laws specific to a country?
  • Terms of Use need to be localized to language of the region if it doesn't exist.
  • Privacy Policy needs to be localized to language.
  • Developer Agreement needs to be localized.

Content Rating

  • Are there requlatory standards bodies in the specific carrier or region?
  • Are there conformance rules specific to carrier or region? (eg. USA's COPPA)?

Testing Marketplace

Marketplace is commercially opened and ready for OEM and Carrier testing. OEMs should confirm the latest build with their TAM, Carriers with their Program Manager.

Features for Testing

  • Open the Marketplace
  • Login / Sign-in to Marketplace
  • Browse for a hosted app
  • Browse for a packaged app
  • Download packaged app
  • Run packaged app
  • Run hosted app
  • See an "offline" error screen if Marketplace is opened when not on network / data

Simulating In-Country Testing

In order to see what consumers will see *in the launch country* testers need to

  1. Use a SIM from the launch country

or

  1. ) If no SIM available then
  2. ) update the region to match the launch country: on device, go to Marketplace app > go to the cog icon (settings icon) > change region to reflect the region *of the launch country*
  3. ) update the language: go to device settings > update language to reflect language *in the launch country*

Filing Marketplace Bugs