Wikimedia Product/Wikimedia Product Infrastructure team/Web Store Notes
The Product Infrastructure team (passively) maintains browser extensions allowing app users to add the current wiki page to their default reading list.
Web store links:
- Chrome: https://chrome.google.com/webstore/detail/wikipedia-reading-lists/nngeaaogaldpfiedmmpicdnoddglbkmi
- Firefox: https://addons.mozilla.org/en-US/firefox/addon/wikipedia-reading-lists
The Safari extension is a legacy .safariextz
-style extension and is no longer available through official Apple channels as of the sunset of the Safari Extension Gallery in September 2019. It will require converting to a Safari App Extension if we wish to distribute it again through the app store. (T251311)
Code repos:
- WebExtension (Chrome/Firefox): https://github.com/wikimedia/webextension-readinglists
- Safari extension (obsolete): https://github.com/wikimedia/readinglists-extension-safari
Quick start
editPackaging
edit- zip up files intended for distribution
- make sure
manifest.json
is in the root directory of the zip file
Publishing
editChrome
editSign in
edit- go to https://chrome.google.com/webstore/developer/dashboard
- sign in as androiddevconsole@wikimedia.org
To add a new extension
edit- click "add new item"
- upload the zip file
- add all relevant screenshots/details
- save draft or publish
NOTE: See full process for detailed instructions
To edit an existing extension
edit- click the "edit" link corresponding to the relevant extension
- adjust desired info
Firefox
editSign in
edit- go to https://addons.mozilla.org/en-US/developers/
- sign in as androiddevconsole@wikimedia.org
To add a new extension
edit- click "submit a new add-on"
- upload the zip and add screenshots and brief summary
- submit
- full description and details can be added later
NOTE: see full process for detailed instructions
To edit an existing extension
edit- click "edit listing" for the relevant add-on
- to upload a new version, click "upload new version" in the upper left box
- click "edit" in any section to edit any other desired info
Full process
editWeb store process notes copied from https://docs.google.com/document/d/19EQStRx3jNPoEm6M9L6sozk9r9jfQJ1yBuIwK7tf7mU/edit
Chrome
edit- Create your app’s zip file
- Must contain app’s manifest:
- App name
- Version
- Images
- Icon, at least one screenshot and one promo image
- If using Native Client, can reduce size of download package
- Must contain app’s manifest:
- Create a developer account
- Use new account instead of personal
- https://developer.chrome.com/webstore/terms
- For hosted app, need to prove that your dev account owns the URLs that comprise the app
- To have Chrome Web Store show “Available for Android”, app must have same name as Google Play listing, both apps owned by same dev account
- Upload your app
- If need app ID or OAuth access token to complete code = need to upload while still writing code
- Otherwise can wait until app is finished; can upload many times before publishing
- Sign into dev account from above
- If never uploaded before, need to accept dev agreement
- Pick a payments system
- Can omit for free apps
- Provide store content
- Detailed description of app
- 128x128 icon (may reuse app icon) - for store
- At least one 1280x800 or 640x400 screenshot or YouTube video
- 440x280 small tile icon - for Chrome Web Store wall
- Primary category where app should be listed
- App’s language
- Pay the developer signup fee
- Before publishing 1st app, pay one-time $5 fee
- Publishing to test accounts
- Will not appear in search results
- Need to give testers direct link to listing
- Will need to unpublish app if want to publish to world later
- Publishing to the world
- Internationalizing
- Decide which locales you want to support.
- Internationalize and localize the app's UI.
- Localize your app's name and description.
- Upload your app using the Chrome Developer Dashboard.
- Edit your listing, providing localized versions of the detailed description and screenshots.
- Specify which regions you want to support.
- Internationalizing
- Control how fast your app reaches users
- “Max deploy percentage” control can limit the percentage of existing users that are updated to the latest version of the app through the Chrome auto-update mechanism
Firefox
edit- Icons: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/icons
- https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Agreement
- Must provide testing info, and, if applicable, testing credentials required to use the add-on if an account is needed for any part of the add-on’s functionality
- Must provide human-readable source code during submission, as well as instructions on how to reproduce the build
- Must disclose how the add-on collects, uses, stores and shares user data in the privacy policy field on AMO
- Privacy policy must be the full policy text; it cannot be a link to an externally hosted privacy policy. In addition, the privacy policy must:
- be specific and exclusive to the add-on,
- clearly describe the purpose of the data collection,
- set forth the exact data to be collected,
- address the add-on’s particular privacy properties.
- A summary of this information must be included in the add-on’s listing description.
- Add-on must be signed using a Mozilla Certificate
- https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Agreement
- Firefox Account
- Describe Add-on:
- Name
- Add-on URL
- Summary
- This add-on is experimental
- This add-on requires payment, non-free services or software, or additional hardware
- Select up to 2 Firefox categories for this add-on
- Select up to 2 Firefox for Android categories for this add-on
- Support email and website
- License
- This add-on has a privacy policy
- Notes to Reviewer