17 results for tag “add-ons”

  1. Using the AMO theme generator

    Using the AMO theme generator The theme generator on addons.mozilla.org (AMO) guides you through the process of creating a theme for Firefox. Once you have defined the colors and image for your theme, the generator will submit your new theme to AMO. You may...

    /documentation/themes/using-the-amo-theme-generator/

  2. Choosing a Firefox version for extension development

    Choose a Firefox version for web extension development Firefox provides several versions that offer different capabilities for developing web extensions. This article provides an overview of the differences among these versions of Firefox and recommends how to use each in the development lifecycle. Contents...

    /documentation/develop/choosing-a-firefox-version-for-extension-development/

  3. User experience best practices

    User experience best practices You want to make sure your users have a great experience using your extension—when you do, the good reviews and ratings will follow on addons.mozilla.org (AMO) If you are new to the subject of making software usable, a good place...

    /documentation/develop/user-experience-best-practices/

  4. Create an appealing listing

    Creating an appealing add-on listing There are two essential steps to getting people to use your add-on: they need to discover your add-on and open the listing page, then the listing page needs to encourage them to click the Add to Firefox button. The...

    /documentation/develop/create-an-appealing-listing/

  5. Test permission requests

    Test permission requests Your extension may contain two types of permission request: install time and runtime permission requests. This page explains how you can test the way your users will see requests for these permissions. Contents Permission grant behavior during testingObserve or verify install...

    /documentation/develop/test-permission-requests/

  6. Best practices for collecting user data consents

    Prompt users for data and privacy consents If your extension uses cookies or collects user data, it needs to comply with the requirement of the Data Disclosure, Collection and Management section of the Add-on Policies. A common developer question about these policies is how...

    /documentation/develop/best-practices-for-collecting-user-data-consents/

  7. Third Party Library Usage

    Third Party Library Usage To complete the review process at addons.mozilla.org (AMO), reviewers must be able to verify the code in your extension. You may include third-party libraries in your extension. In that case, when you upload your extension to AMO, you will need...

    /documentation/publish/third-party-library-usage/

  8. Submitting an add-on

    Submitting an add-on This article walks through the process of publishing an add-on. If you just want to get started, head to the Submit a New Add-on page on AMO. Contents Listing on AMOSelf-distributionGet help To start, familiarize yourself with the Add-on Policies and...

    /documentation/publish/submitting-an-add-on/

  9. Request the right permissions

    Requesting the right permissions Or how to avoid permissions discouraging users from installing your extensions. Contents IntroductionAdvised permissionsAvoid unnecessary permissionsRequest permissions at runtimeAdd information about permissions to your extensions AMO page Introduction With the introduction of Firefox Quantum (57) the handling of permissions when...

    /documentation/develop/request-the-right-permissions/

  10. Source code submission

    Source code submission To complete the review process at addons.mozilla.org (AMO), reviewers must be able to read the code in your extension. Some build processes render extension code difficult to read. These processes include minifying your code, as well as the use of module...

    /documentation/publish/source-code-submission/

  11. What does review rejection mean to users?

    What does review rejection mean to users? This article explains how users and people looking for your extension are affected should you get a rejection from the Mozilla review process. Contents Review overviewImpact of review rejectionBlocklisting Review overview Any extension you submit to addons.mozilla.org...

    /documentation/publish/what-does-review-rejection-mean-to-users/

  12. Add-on Policies

    Add-on Policies Add-ons extend the core capabilities of Firefox, enabling users to modify and personalize their web experience. A healthy ecosystem, built on trust, is vital for developers to be successful and users to feel safe making Firefox their own. For these reasons, Mozilla...

    /documentation/publish/add-on-policies/

  13. Firefox workflow overview

    Firefox workflow overview Prepare Code Publish* Enhance Retire Choose a Firefox version for web extension development Code your extension Package your extension with web-ext build Responded to Mozilla extension review Retire your extension Choose your IDE or code editor Run your extension with web-ext...

    /documentation/develop/firefox-workflow-overview/

  14. Developing extensions for Firefox for Android (Fennec)

    Developing extensions for Firefox for Android version 68 and earlier Legacy guide to developing extensions for Firefox for Android version 68 and earlier ("Fennec") Contents Set up your computer and Android emulator or deviceSet up your computer and Android emulator or deviceCheck for Firefox...

    /documentation/develop/developing-extensions-for-firefox-for-android-fennec/

  15. Developing extensions for Firefox for Android

    Developing extensions for Firefox for Android Learn more about developing extensions for Firefox for Android Contents Set up your computer and Android emulator or deviceCheck for Firefox for Android compatibilityInstall and run your extension in Firefox for AndroidDebug your extension In August 2020, Mozilla...

    /documentation/develop/developing-extensions-for-firefox-for-android/

  16. Differences between desktop and Android extensions

    Differences between desktop and Android extensions There are some important distinctions to know when developing an extension for Android Contents IntroductionUser interfaceNative application interactionPermissionsOther notes In August 2020, Mozilla launched a new, reimagined Firefox for Android experience (codenamed "Fenix"). The browser for Android has...

    /documentation/develop/differences-between-desktop-and-android-extensions/

  17. Differences between desktop and Android extensions

    User Experience Guidelines for Mobile Extensions Make your extension seamlessly integrate with Firefox for Android Contents IntroductionThe basicsThe extra mileThe last mile Introduction In August 2020, Mozilla launched a new, reimagined Firefox for Android experience (codenamed "Fenix"). The browser for Android has been rebuilt...

    /documentation/develop/user-experience-guidelines-for-mobile-extensions/