url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://extensionworkshop.com/documentation/develop/request-the-right-permissions/ | Request the right permissions | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Requesting the right permissions Or how to avoid permissions discouraging users from installing your extensions. Contents Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Introduction To inform users of the potential impact of installing an extension, Firefox displays a message showing what permissions an extension is requesting when it's installed. The prompt looks something like this: Also, if an extension update requires additional permissions the user is prompted to approve the permissions before the updated version is installed: If the user chooses not to approve the permissions and cancels the update, the previous version remains installed and available for use. These messages could discourage some users from installing your extension, as they might suggest it's doing something “scary”. We provide users with an explanation of these permissions messages and guidance on how to judge if they're appropriate . However, there are several things you can do to reduce the likelihood of users abandoning the installation of your extension because of these messages; these include: Make sure you aren't requesting unnecessary permissions. Request permissions at runtime, which enables you to ask for the permissions in context and offer a fallback if the user doesn't grant them. Describe why your extension is requesting its permissions in its AMO description. Tip: Permission messages aren't issued when you load an unpacked extension . For information on how to see the standard runtime permission flow, see Test permission requests . Advised permissions Not all permissions result in advice being given to the user. The permissions that trigger the display of a message and the messages they trigger are: Permission Permissions messages Host permissions Access your data for all websites Access your data for sites in the [named] domain Access your data in # other domains Access your data for [named site] Access your data on # other sites” API permissions: bookmarks Read and modify bookmarks browserSettings Read and modify browser settings browsingData Clear recent browsing history, cookies, and related data declarativeNetRequest Block content on any page downloads Download files and read and modify the browser’s download history downloads.open Open files downloaded to your computer find Read the text of all open tabs geolocation Access your location history Access browsing history management Monitor extension usage and manage themes nativeMessaging Exchange messages with programs other than Firefox notifications Display notifications to you pkcs11 Provide cryptographic authentication services privacy Read and modify privacy settings proxy Control browser proxy settings sessions Access recently closed tabs tabs Access browser tabs tabHide Hide and show browser tabs topSites Access browsing history webNavigation Access browser activity during navigation userScripts Allow unverified third-party scripts to access your data Clipboard access: clipboardWrite Input data to the clipboard clipboardRead Get data from the clipboard Other permissions: The manifest key devtools_page * Extend developer tools to access your data in open tabs * This warning can be suppressed by setting the optional permission "devtools" and requesting the permission with the permissions API . See Request permissions at runtime . The permissions that display messages and their messages may differ in other browsers. For information about viewing the permission message in Chrome, see Viewing Warnings. These permissions don't get alerted to users: API permissions: alarms contextMenus contextualIdentities cookies declarativeNetRequestWithHostAccess identity idle menus storage theme webRequest webRequestBlocking Other permissions: unlimitedStorage activeTab Avoid unnecessary permissions This section looks at situations where you might be asking for more permissions than your extension needs and what you should do about them. Ask for only the permissions your extension uses This may seem obvious, but if you create an extension using an earlier example as a template or remove a feature during development or testing, you may be asking for permissions your extension doesn't need. Addressing this involves manually checking your code against the permissions ( permissions and optional_permissions ) that you're requesting in the extension's manifest.json . Use "activeTab" rather than "tabs" and host permissions Take an extension you're developing to help color-blind users. At the user's request, your extension looks for and updates CSS on a web page to replace colors the user may have difficulty distinguishing with safe colors. Your extension must access and update CSS on every page your user visits. You could do this by requesting the "tabs" permission and host permission for "<all_urls>" . "permissions" : [ "<all_urls>" , "tabs" ] Requesting these permissions results in the user getting this advice: The alternative is to request "activeTab" . This permission provides your extension with the same capabilities but only for the active tab and only when run from the extension's UI (that is, from a toolbar button, navigation bar button, context menu, or shortcut key). Importantly, "activeTab" doesn't display a permissions message when installing the extension. Avoid host permission "<all_urls>" if you can As noted in the previous example, requesting host permission "<all_urls>" results in the permissions request message "Access your data for all websites". If your extension is designed to work with one or a few websites or domains, narrow the request. Then, when installing your extension, users see details for the first four websites or domains your extension requests access to. If your extension requests access to more than four websites or domains, the message lists the first three and indicates the number of other requests. Avoid the "unlimitedStorage" permission Only ask for "unlimitedStorage" permission if you expect your extension's local data storage to exceed 5MB; if it's not going to exceed that amount, don't ask for it. Firefox doesn't restrict local storage size, although it does ask users to approve this permission request if you make it. Firefox may add a restriction in the future. If that happens, the limit is unlikely to be less than Chrome's current 5 MB restriction. Request permissions at runtime Users may not understand the context of permissions requested during installation. To provide the user with context, request permissions when they are needed using the Permissions API . Permissions that can be requested a runtime are known as optional permissions . However, not all permissions can be requested at runtime. There are also a small number of optional-only permissions that can only be requested at runtime. An example of one such optional-only permission is the userScript permission in Firefox. A typical scenario for using this approach is the "geoLocation" permission. Say you've written a note-taking extension that includes the ability to add a minimap of the note-takers location. Requesting location access during installation might leave the user unclear why the extension needs to access location, so they might not install it. However, if permission to use location is requested when the user first tries the feature to add a minimap, they'll get a clearer understanding of why the permission is needed and be more likely to grant it. Should they choose not to grant the permission, the extension can offer a graceful fallback—in this example, not adding the minimap—but the important outcome of this approach is that the user has installed and used your extension. Making a runtime permission request is straightforward. Include any permissions you want to request under the manifest.json optional_permissions key. Then, pass the permissions you want granted to permissions.request , which prompts the user to grant the permissions. true is returned if the user grants the request, false if they don't. You can't request all the permissions available to "permissions" using optional permissions. You can't request these API permissions: alarms background contentSettings contextualIdentities debugger downloads downloads.open find identity menus pageCapture privacy storage theme There are a couple of things to note: You can only request permissions inside the handler for a user action, such as from a toolbar button (browser action), shortcut menu item, or similar. If you need to request an optional-only permission, it must be the only permission you request in a permissions.request call. If you request several permissions at once, they are either all granted or all declined; the user cannot choose to grant some and not others. Users can also grant or revoke optional permissions anytime through an extension's option page. Your extension, therefore, needs to test to determine whether it has the necessary permissions or listen to the permissions.onAdded and permissions.onRemoved events. For more information about optional permissions, see optional_permissions and the permissions example. Add information about permissions to your extensions AMO page Permissions messages are most likely to prevent users from installing your extension because the user doesn't understand why permissions are being requested. While the user can get general advice on the impact of a permission, it may not be sufficient for them to understand why a permission is being requested in your extension. To address this issue, provide information in your extension's AMO description explaining what permissions your extension requests and why. A good example of this approach is Gesturefy , which offers users this advice: Permissions explained: Access your data for all websites: This is a key permission, because the complete gesture functionality is injected in every webpage you visit (which means a part of the code is running in each tab). This is necessary, because with the new API there is no other way to track your mouse movement or draw anything on the screen. It’s also needed to perform page specific commands like scroll down or up. Read and modify browser settings: This is required to change the context menu behaviour for MacOS and Linux users to support the usage of the right mouse button. Display notifications: This is used to show a notification on Gesturefy updates or to display certain error messages. Tags: add-ons beginner extensions how-to intermediate permissions Contributors: caitmuenster Zearin_Galaurum rebloor evilpie hellosct1 freaktechnik Last update: Zearin_Galaurum Mar 19, 2021 Up Next Develop Firefox built-in consent for data collection and transmission Develop Best practices for collecting user data consents Develop Build an accessible extension Documentation Topics Develop Publish Manage Enterprise Themes Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Fmqgem-software-limited-mqscx%2F&fromSignIn=true&trk=products_details_guest_nav-header-signin | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_HN | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="r | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#updates | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_SV | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="rymPhb | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#acessing-data-permissions-programmatically | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_PY | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=notion.id&hl=fil | Notion: Notes, Tasks, AI - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion: Notes, Tasks, AI Notion Labs, Inc. In-app purchases 4.8 star 327K reviews 10M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Whether you’re looking to track your personal to-do’s, write and organize class notes, or run project management with a team, Notion is the AI-powered workspace that works your way, for any need. Keep track of your personal and professional goals, take notes about what you care about, and stay organized. "AI's everything app" — Forbes Notion is a productivity app where you can write, plan, and organize your notes, projects, tasks and more - all in one place. Ask Notion AI about project updates, upcoming tasks, and suggestions for a more streamlined workflow. Simplify writing notes, project and task management, and collaboration. Whether for personal, student or professional use, Notion scales to meet your individual needs with customization tools for everyone. FREE FOR PERSONAL USE • Create as many notes, docs, and content as you want. • Use one of thousands of templates to get started. FREE TO TRY WITH YOUR TEAM • Millions run on Notion every day, from next-generation startups to established enterprises. • Import Google Docs, PDFs, and other content types easily to get started • Write and organize meeting notes, or transcribe with AI. • Collaboration and team work at your fingertips, in one connected workspace. • Connect tools like Figma, Slack, and GitHub to Notion. FREE FOR STUDENTS • Your study planner, class notes, to do lists and more, your way. Loved by millions of students worldwide. • Get organized for your best school year yet with beautiful, customizable templates created by students, for students. NOTES & DOCS Communication is made efficient with Notion's flexible building blocks. • Create docs with beautiful templates, images, to-dos, and 50+ more content types. • Meeting notes, projects, design systems, pitch decks, and more. • Find exactly what you need using Search with powerful filters to find content across your workspace. TASKS & PROJECTS Catch all details big and small in any workflow. • Workflow manager: Create your own priority labels, status tags, and automations to choose the exact info you want to track. • Capture every detail in a table. Break projects into manageable tasks to get the work done. AI One tool that does it all - search, generate, analyze, and chat - right inside Notion. • Write better. Use Notion AI to help write and brainstorm. • Get answers. Ask Notion AI questions about all your content and get answers in seconds. • Autofill tables. Notion AI turns overwhelming data into clear, actionable information — automatically. SYNCS WITH BROWSER, MAC, AND WINDOWS APPS. • Pick up on mobile where you left off on desktop. MORE PRODUCTIVITY. FEWER TOOLS. • Track to-dos, write notes, create docs, and manage projects in one connected workspace. THINK IT. MAKE IT. Updated on Jan 13, 2026 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, Photos and videos and 5 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.8 319K reviews 5 4 3 2 1 Sommy Nriama more_vert Flag inappropriate Show review history <path d="M12 17.27L18.18 | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="rymP | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=fi | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="r | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#get-prepared | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=fr | html,body{height:100%;overflow:hidden}body{-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale;color:rgba(0,0,0,0.87);font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif;margin:0;-webkit-text-size-adjust:100%;-moz-text-size-adjust:100%;-ms-text-size-adjust:100%;text-size-adjust:100%}textarea{font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif}a{text-decoration:none;color:#2962ff}img{border:none}*{-webkit-tap-highlight-color:transparent}#apps-debug-tracers{display:none}html,body{overflow:visible}body{overflow-y:scroll}@-webkit-keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@-webkit-keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@-webkit-keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}@keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}.VfPpkd-ksKsZd-XxIAqe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity;position:relative;outline:none;overflow:hidden}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-ksKsZd-XxIAqe::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-ksKsZd-XxIAqe::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded],.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd{overflow:visible}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:0;left:0;width:100%;height:100%}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-ksKsZd-XxIAqe:hover::before,.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe::before,.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):focus::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d)::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):active::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.Tj45d{position:relative}.ncIyJc{position:absolute;overflow:hidden;left:-1px;top:auto;width:1px;height:1px}.VfPpkd-NLUYnc-V67aGc{position:absolute;left:0;-webkit-transform-origin:left top;-ms-transform-origin:left top;transform-origin:left top;line-height:1.15rem;text-align:left;text-overflow:ellipsis;white-space:nowrap;cursor:text;overflow:hidden;will-change:transform}[dir=rtl] .VfPpkd-NLUYnc-V67aGc,.VfPpkd-NLUYnc-V67aGc[dir=rtl]{right:0;left:auto;-webkit-transform-origin:right top;-ms-transform-origin:right top;transform-origin:right top;text-align:right}.VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{cursor:auto}.VfPpkd-NLUYnc-V67aGc-OWXEXe-ztc6md:not(.VfPpkd-NLUYnc-V67aGc-OWXEXe-ZYIfFd-ztc6md-vXpfLb)::after{margin-left:1px;margin-right:0;content:"*"}[dir=rtl] .VfPpkd-NLUYnc-V67aGc-OWXEXe-ztc6md:not(.VfPpkd-NLUYnc-V67aGc-OWXEXe-ZYIfFd-ztc6md-vXpfLb)::after,.VfPpkd-NLUYnc-V67aGc-OWXEXe-ztc6md:not(.VfPpkd-NLUYnc-V67aGc-OWXEXe-ZYIfFd-ztc6md-vXpfLb)[dir=rtl]::after{margin-left:0;margin-right:1px}.VfPpkd-NLUYnc-V67aGc{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-family:Roboto,sans-serif;font-family:var(--mdc-typography-subtitle1-font-family,var(--mdc-typography-font-family,Roboto,sans-serif));font-size:1rem;font-size:var(--mdc-typography-subtitle1-font-size,1rem);font-weight:400;font-weight:var(--mdc-typography-subtitle1-font-weight,400);letter-spacing:.009375em;letter-spacing:var(--mdc-typography-subtitle1-letter-spacing,.009375em);text-decoration:inherit;-webkit-text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-transform:inherit;text-transform:var(--mdc-typography-subtitle1-text-transform,inherit);-webkit-transition:color .15s cubic-bezier(.4,0,.2,1),-webkit-transform .15s cubic-bezier(.4,0,.2,1);transition:color .15s cubic-bezier(.4,0,.2,1),-webkit-transform .15s cubic-bezier(.4,0,.2,1);transition:transform .15s cubic-bezier(.4,0,.2,1),color .15s cubic-bezier(.4,0,.2,1);transition:transform .15s cubic-bezier(.4,0,.2,1),color .15s cubic-bezier(.4,0,.2,1),-webkit-transform .15s cubic-bezier(.4,0,.2,1)}.VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-106%) scale(.75);-ms-transform:translateY(-106%) scale(.75);transform:translateY(-106%) scale(.75)}.VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-standard .25s 1;animation:mdc-floating-label-shake-float-above-standard .25s 1}@-webkit-keyframes mdc-floating-label-shake-float-above-standard{0%{-webkit-transform:translateX(0) translateY(-106%) scale(.75);transform:translateX(0) translateY(-106%) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-106%) scale(.75);transform:translateX(4%) translateY(-106%) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-106%) scale(.75);transform:translateX(-4%) translateY(-106%) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-106%) scale(.75);transform:translateX(0) translateY(-106%) scale(.75)}}@keyframes mdc-floating-label-shake-float-above-standard{0%{-webkit-transform:translateX(0) translateY(-106%) scale(.75);transform:translateX(0) translateY(-106%) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-106%) scale(.75);transform:translateX(4%) translateY(-106%) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-106%) scale(.75);transform:translateX(-4%) translateY(-106%) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-106%) scale(.75);transform:translateX(0) translateY(-106%) scale(.75)}}.VfPpkd-RWgCYc-ksKsZd::before,.VfPpkd-RWgCYc-ksKsZd::after{position:absolute;bottom:0;left:0;width:100%;border-bottom-style:solid;content:""}.VfPpkd-RWgCYc-ksKsZd::before{z-index:1}.VfPpkd-RWgCYc-ksKsZd::after{-webkit-transform:scaleX(0);-ms-transform:scaleX(0);transform:scaleX(0);opacity:0;z-index:2}.VfPpkd-RWgCYc-ksKsZd-OWXEXe-auswjd::after{-webkit-transform:scaleX(1);-ms-transform:scaleX(1);transform:scaleX(1);opacity:1}.VfPpkd-RWgCYc-ksKsZd-OWXEXe-JD038d::after{opacity:0}.VfPpkd-RWgCYc-ksKsZd::before{border-bottom-width:1px}.VfPpkd-RWgCYc-ksKsZd::after{border-bottom-width:2px}.VfPpkd-RWgCYc-ksKsZd::after{-webkit-transition:opacity .18s cubic-bezier(.4,0,.2,1),-webkit-transform .18s cubic-bezier(.4,0,.2,1);transition:opacity .18s cubic-bezier(.4,0,.2,1),-webkit-transform .18s cubic-bezier(.4,0,.2,1);transition:transform .18s cubic-bezier(.4,0,.2,1),opacity .18s cubic-bezier(.4,0,.2,1);transition:transform .18s cubic-bezier(.4,0,.2,1),opacity .18s cubic-bezier(.4,0,.2,1),-webkit-transform .18s cubic-bezier(.4,0,.2,1)}.VfPpkd-NSFCdd-i5vt6e{display:-webkit-box;display:-webkit-flex;display:flex;position:absolute;top:0;right:0;left:0;-webkit-box-sizing:border-box;box-sizing:border-box;width:100%;max-width:100%;height:100%;text-align:left;pointer-events:none}[dir=rtl] .VfPpkd-NSFCdd-i5vt6e,.VfPpkd-NSFCdd-i5vt6e[dir=rtl]{text-align:right}.VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-NSFCdd-MpmGFe{-webkit-box-sizing:border-box;box-sizing:border-box;height:100%;pointer-events:none}.VfPpkd-NSFCdd-MpmGFe{-webkit-box-flex:1;-webkit-flex-grow:1;flex-grow:1}.VfPpkd-NSFCdd-Ra9xwd{-webkit-box-flex:0;-webkit-flex:0 0 auto;flex:0 0 auto;width:auto}.VfPpkd-NSFCdd-i5vt6e .VfPpkd-NLUYnc-V67aGc{display:inline-block;position:relative;max-width:100%}.VfPpkd-NSFCdd-i5vt6e .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{text-overflow:clip}.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{max-width:133.3333333333%}.VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd{padding-left:0;padding-right:8px;border-top:none}[dir=rtl] .VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd[dir=rtl]{padding-left:8px;padding-right:0}.VfPpkd-NSFCdd-i5vt6e-OWXEXe-di8rgd-V67aGc .VfPpkd-NSFCdd-Ra9xwd{display:none}.VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-NSFCdd-MpmGFe{border-top:1px solid;border-bottom:1px solid}.VfPpkd-NSFCdd-Brv4Fb{border-left:1px solid;border-right:none;width:12px}[dir=rtl] .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-NSFCdd-Brv4Fb[dir=rtl]{border-left:none;border-right:1px solid}.VfPpkd-NSFCdd-MpmGFe{border-left:none;border-right:1px solid}[dir=rtl] .VfPpkd-NSFCdd-MpmGFe,.VfPpkd-NSFCdd-MpmGFe[dir=rtl]{border-left:1px solid;border-right:none}.VfPpkd-NSFCdd-Ra9xwd{max-width:calc(100% - 24px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d .VfPpkd-fmcmS-OyKIhb::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d .VfPpkd-fmcmS-OyKIhb::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-fmcmS-OyKIhb::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-fmcmS-OyKIhb::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-fmcmS-OyKIhb::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d .VfPpkd-fmcmS-OyKIhb::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-fmcmS-OyKIhb{position:absolute;top:0;left:0;width:100%;height:100%;pointer-events:none}.VfPpkd-fmcmS-yrriRe{border-top-left-radius:4px;border-top-left-radius:var(--mdc-shape-small,4px);border-top-right-radius:4px;border-top-right-radius:var(--mdc-shape-small,4px);border-bottom-right-radius:0;border-bottom-left-radius:0;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-align:baseline;-webkit-align-items:baseline;align-items:baseline;padding:0 16px;position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;overflow:hidden;will-change:opacity,transform,color}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd{color:rgba(0,0,0,.87)}@media all{.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-moz-placeholder{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::placeholder{color:rgba(0,0,0,.54)}}@media all{.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgba(0,0,0,.54)}}.VfPpkd-fmcmS-yrriRe .VfPpkd-fmcmS-wGMbrd{caret-color:#6200ee;caret-color:var(--mdc-theme-primary,#6200ee)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd,.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-M1Soyc{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe .VfPpkd-NLUYnc-V67aGc{top:50%;-webkit-transform:translateY(-50%);-ms-transform:translateY(-50%);transform:translateY(-50%);pointer-events:none}.VfPpkd-fmcmS-wGMbrd{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-family:Roboto,sans-serif;font-family:var(--mdc-typography-subtitle1-font-family,var(--mdc-typography-font-family,Roboto,sans-serif));font-size:1rem;font-size:var(--mdc-typography-subtitle1-font-size,1rem);font-weight:400;font-weight:var(--mdc-typography-subtitle1-font-weight,400);letter-spacing:.009375em;letter-spacing:var(--mdc-typography-subtitle1-letter-spacing,.009375em);text-decoration:inherit;-webkit-text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-transform:inherit;text-transform:var(--mdc-typography-subtitle1-text-transform,inherit);height:28px;-webkit-transition:opacity .15s 0ms cubic-bezier(.4,0,.2,1);transition:opacity .15s 0ms cubic-bezier(.4,0,.2,1);width:100%;min-width:0;border:none;border-radius:0;background:none;-webkit-appearance:none;-moz-appearance:none;appearance:none;padding:0}.VfPpkd-fmcmS-wGMbrd::-ms-clear{display:none}.VfPpkd-fmcmS-wGMbrd::-webkit-calendar-picker-indicator{display:none}.VfPpkd-fmcmS-wGMbrd:focus{outline:none}.VfPpkd-fmcmS-wGMbrd:invalid{-webkit-box-shadow:none;box-shadow:none}@media all{.VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{-webkit-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}.VfPpkd-fmcmS-wGMbrd::-moz-placeholder{-moz-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}.VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{-ms-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}.VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{-ms-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}.VfPpkd-fmcmS-wGMbrd::placeholder{-webkit-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}}@media all{.VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{-ms-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}}@media all{.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder, .VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{-webkit-transition-delay:40ms;transition-delay:40ms;-webkit-transition-duration:.11s;transition-duration:.11s;opacity:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd::-moz-placeholder, .VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd::-moz-placeholder{transition-delay:40ms;transition-duration:.11s;opacity:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder, .VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{transition-delay:40ms;transition-duration:.11s;opacity:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder, .VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{transition-delay:40ms;transition-duration:.11s;opacity:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd::placeholder,.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd::placeholder{-webkit-transition-delay:40ms;transition-delay:40ms;-webkit-transition-duration:.11s;transition-duration:.11s;opacity:1}}@media all{.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder,.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{transition-delay:40ms;transition-duration:.11s;opacity:1}}.VfPpkd-fmcmS-MvKemf{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-family:Roboto,sans-serif;font-family:var(--mdc-typography-subtitle1-font-family,var(--mdc-typography-font-family,Roboto,sans-serif));font-size:1rem;font-size:var(--mdc-typography-subtitle1-font-size,1rem);font-weight:400;font-weight:var(--mdc-typography-subtitle1-font-weight,400);letter-spacing:.009375em;letter-spacing:var(--mdc-typography-subtitle1-letter-spacing,.009375em);text-decoration:inherit;-webkit-text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-transform:inherit;text-transform:var(--mdc-typography-subtitle1-text-transform,inherit);height:28px;-webkit-transition:opacity .15s 0ms cubic-bezier(.4,0,.2,1);transition:opacity .15s 0ms cubic-bezier(.4,0,.2,1);opacity:0;white-space:nowrap}.VfPpkd-fmcmS-yrriRe-OWXEXe-V67aGc-NLUYnc .VfPpkd-fmcmS-MvKemf,.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-MvKemf{opacity:1}@supports (-webkit-hyphens:none){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-MvKemf{-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-align-self:center;align-self:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;height:100%}}.VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{padding-left:0;padding-right:2px}[dir=rtl] .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c,.VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c[dir=rtl]{padding-left:2px;padding-right:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{padding-left:0;padding-right:12px}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c,.VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c[dir=rtl]{padding-left:12px;padding-right:0}.VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{padding-left:12px;padding-right:0}[dir=rtl] .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB,.VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB[dir=rtl]{padding-left:0;padding-right:12px}.VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{padding-left:2px;padding-right:0}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB,.VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB[dir=rtl]{padding-left:0;padding-right:2px}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be{height:56px}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::after{background-color:rgba(0,0,0,.87);background-color:var(--mdc-ripple-color,rgba(0,0,0,.87))}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:hover .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-fmcmS-OyKIhb::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-fmcmS-OyKIhb::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be::before{display:inline-block;width:0;height:40px;content:"";vertical-align:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me){background-color:rgb(244.8,244.8,244.8)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-RWgCYc-ksKsZd::before{border-bottom-color:rgba(0,0,0,.42)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):hover .VfPpkd-RWgCYc-ksKsZd::before{border-bottom-color:rgba(0,0,0,.87)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-RWgCYc-ksKsZd::after{border-bottom-color:#6200ee;border-bottom-color:var(--mdc-theme-primary,#6200ee)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc{left:16px;right:auto}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc[dir=rtl]{left:auto;right:16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-106%) scale(.75);-ms-transform:translateY(-106%) scale(.75);transform:translateY(-106%) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd{height:100%}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-NLUYnc-V67aGc{display:none}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc::before{display:none}@supports (-webkit-hyphens:none){.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-MvKemf{-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-align-self:center;align-self:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;height:100%}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc{height:56px;overflow:visible}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-37.25px) scale(1);-ms-transform:translateY(-37.25px) scale(1);transform:translateY(-37.25px) scale(1)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-34.75px) scale(.75);-ms-transform:translateY(-34.75px) scale(.75);transform:translateY(-34.75px) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:.75rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:1rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-text-field-outlined .25s 1;animation:mdc-floating-label-shake-float-above-text-field-outlined .25s 1}@-webkit-keyframes mdc-floating-label-shake-float-above-text-field-outlined{0%{-webkit-transform:translateX(0) translateY(-34.75px) scale(.75);transform:translateX(0) translateY(-34.75px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-34.75px) scale(.75);transform:translateX(4%) translateY(-34.75px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-34.75px) scale(.75);transform:translateX(-4%) translateY(-34.75px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-34.75px) scale(.75);transform:translateX(0) translateY(-34.75px) scale(.75)}}@keyframes mdc-floating-label-shake-float-above-text-field-outlined{0%{-webkit-transform:translateX(0) translateY(-34.75px) scale(.75);transform:translateX(0) translateY(-34.75px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-34.75px) scale(.75);transform:translateX(4%) translateY(-34.75px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-34.75px) scale(.75);transform:translateX(-4%) translateY(-34.75px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-34.75px) scale(.75);transform:translateX(0) translateY(-34.75px) scale(.75)}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-wGMbrd{height:100%}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-MpmGFe{border-color:rgba(0,0,0,.38)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe{border-color:rgba(0,0,0,.87)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me).VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me).VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me).VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-NSFCdd-MpmGFe{border-color:#6200ee;border-color:var(--mdc-theme-primary,#6200ee)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb{border-top-left-radius:4px;border-top-left-radius:var(--mdc-shape-small,4px);border-top-right-radius:0;border-bottom-right-radius:0;border-bottom-left-radius:4px;border-bottom-left-radius:var(--mdc-shape-small,4px)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb[dir=rtl]{border-top-left-radius:0;border-top-right-radius:4px;border-top-right-radius:var(--mdc-shape-small,4px);border-bottom-right-radius:4px;border-bottom-right-radius:var(--mdc-shape-small,4px);border-bottom-left-radius:0}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb{width:max(12px,var(--mdc-shape-small,4px))}}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Ra9xwd{max-width:calc(100% - max(12px, var(--mdc-shape-small, 4px))*2)}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe{border-top-left-radius:0;border-top-right-radius:4px;border-top-right-radius:var(--mdc-shape-small,4px);border-bottom-right-radius:4px;border-bottom-right-radius:var(--mdc-shape-small,4px);border-bottom-left-radius:0}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe[dir=rtl]{border-top-left-radius:4px;border-top-left-radius:var(--mdc-shape-small,4px);border-top-right-radius:0;border-bottom-right-radius:0;border-bottom-left-radius:4px;border-bottom-left-radius:var(--mdc-shape-small,4px)}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc{padding-left:max(16px,calc(var(--mdc-shape-small, 4px) + 4px))}}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc{padding-right:max(16px,var(--mdc-shape-small,4px))}}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc{padding-left:max(16px,calc(var(--mdc-shape-small, 4px) + 4px))}}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc{padding-right:max(16px,var(--mdc-shape-small,4px))}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c{padding-left:0}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c{padding-right:max(16px,var(--mdc-shape-small,4px))}}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c[dir=rtl]{padding-right:0}@supports (top:max(0%)){[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c[dir=rtl]{padding-left:max(16px,var(--mdc-shape-small,4px))}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c{padding-right:0}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c{padding-left:max(16px,calc(var(--mdc-shape-small, 4px) + 4px))}}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c[dir=rtl]{padding-left:0}@supports (top:max(0%)){[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c[dir=rtl]{padding-right:max(16px,calc(var(--mdc-shape-small, 4px) + 4px))}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c{padding-left:0;padding-right:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd{padding-top:1px}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-OyKIhb::after{background-color:transparent;background-color:var(--mdc-ripple-color,transparent)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc{left:4px;right:auto}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc[dir=rtl]{left:auto;right:4px}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-wGMbrd{display:-webkit-box;display:-webkit-flex;display:flex;border:none!important;background-color:transparent}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e{z-index:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od{-webkit-box-orient:vertical;-webkit-box-direction:normal;-webkit-flex-direction:column;flex-direction:column;-webkit-box-align:center;-webkit-align-items:center;align-items:center;width:auto;height:auto;padding:0;-webkit-transition:none;transition:none}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od .VfPpkd-NLUYnc-V67aGc{top:19px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od .VfPpkd-NLUYnc-V67aGc:not(.VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe){-webkit-transform:none;-ms-transform:none;transform:none}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od .VfPpkd-fmcmS-wGMbrd{-webkit-box-flex:1;-webkit-flex-grow:1;flex-grow:1;height:auto;min-height:1.5rem;overflow-x:hidden;overflow-y:auto;-webkit-box-sizing:border-box;box-sizing:border-box;resize:none;padding:0 16px;line-height:1.5rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be::before{display:none}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-10.25px) scale(.75);-ms-transform:translateY(-10.25px) scale(.75);transform:translateY(-10.25px) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-textarea-filled .25s 1;animation:mdc-floating-label-shake-float-above-textarea-filled .25s 1}@-webkit-keyframes mdc-floating-label-shake-float-above-textarea-filled{0%{-webkit-transform:translateX(0) translateY(-10.25px) scale(.75);transform:translateX(0) translateY(-10.25px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-10.25px) scale(.75);transform:translateX(4%) translateY(-10.25px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-10.25px) scale(.75);transform:translateX(-4%) translateY(-10.25px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-10.25px) scale(.75);transform:translateX(0) translateY(-10.25px) scale(.75)}}@keyframes mdc-floating-label-shake-float-above-textarea-filled{0%{-webkit-transform:translateX(0) translateY(-10.25px) scale(.75);transform:translateX(0) translateY(-10.25px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-10.25px) scale(.75);transform:translateX(4%) translateY(-10.25px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-10.25px) scale(.75);transform:translateX(-4%) translateY(-10.25px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-10.25px) scale(.75);transform:translateX(0) translateY(-10.25px) scale(.75)}}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-wGMbrd{margin-top:23px;margin-bottom:9px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd{margin-top:16px;margin-bottom:16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd{padding-top:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-27.25px) scale(1);-ms-transform:translateY(-27.25px) scale(1);transform:translateY(-27.25px) scale(1)}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-24.75px) scale(.75);-ms-transform:translateY(-24.75px) scale(.75);transform:translateY(-24.75px) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:.75rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:1rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-textarea-outlined .25s 1;animation:mdc-floating-label-shake-float-above-textarea-outlined .25s 1}@-webkit-keyframes mdc-floating-label-shake-float-above-textarea-outlined{0%{-webkit-transform:translateX(0) translateY(-24.75px) scale(.75);transform:translateX(0) translateY(-24.75px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-24.75px) scale(.75);transform:translateX(4%) translateY(-24.75px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-24.75px) scale(.75);transform:translateX(-4%) translateY(-24.75px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-24.75px) scale(.75);transform:translateX(0) translateY(-24.75px) scale(.75)}}@keyframes mdc-floating-label-shake-float-above-textarea-outlined{0%{-webkit-transform:translateX(0) translateY(-24.75px) scale(.75);transform:translateX(0) translateY(-24.75px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-24.75px) scale(.75);transform:translateX(4%) translateY(-24.75px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-24.75px) scale(.75);transform:translateX(-4%) translateY(-24.75px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-24.75px) scale(.75);transform:translateX(0) translateY(-24.75px) scale(.75)}}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-wGMbrd{margin-top:16px;margin-bottom:16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc{top:18px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-k4Qmrd-gmhCAd .VfPpkd-fmcmS-wGMbrd{margin-bottom:2px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-k4Qmrd-gmhCAd .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{-webkit-align-self:flex-end;align-self:flex-end;padding:0 16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-k4Qmrd-gmhCAd .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd::after{display:inline-block;width:0;height:16px;content:"";vertical-align:-16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-k4Qmrd-gmhCAd .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd::before{display:none}.VfPpkd-fmcmS-kHQaff{-webkit-align-self:stretch;align-self:stretch;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-orient:vertical;-webkit-box-direction:normal;-webkit-flex-direction:column;flex-direction:column;-webkit-box-flex:1;-webkit-flex-grow:1;flex-grow:1;max-height:100%;max-width:100%;min-height:56px;min-width:-webkit-fit-content;min-width:-moz-fit-content;min-width:fit-content;min-width:-moz-available;min-width:-webkit-fill-available;overflow:hidden;resize:both}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-kHQaff{-webkit-transform:translateY(-1px);-ms-transform:translateY(-1px);transform:translateY(-1px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-wGMbrd,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{-webkit-transform:translateY(1px);-ms-transform:translateY(1px);transform:translateY(1px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff{-webkit-transform:translateX(-1px) translateY(-1px);-ms-transform:translateX(-1px) translateY(-1px);transform:translateX(-1px) translateY(-1px)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff[dir=rtl]{-webkit-transform:translateX(1px) translateY(-1px);-ms-transform:translateX(1px) translateY(-1px);transform:translateX(1px) translateY(-1px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-wGMbrd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{-webkit-transform:translateX(1px) translateY(1px);-ms-transform:translateX(1px) translateY(1px);transform:translateX(1px) translateY(1px)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-wGMbrd,[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-wGMbrd[dir=rtl],.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd[dir=rtl]{-webkit-transform:translateX(-1px) translateY(1px);-ms-transform:translateX(-1px) translateY(1px);transform:translateX(-1px) translateY(1px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c{padding-left:0;padding-right:16px}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c[dir=rtl]{padding-left:16px;padding-right:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc{max-width:calc(100% - 48px);left:48px;right:auto}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc[dir=rtl]{left:auto;right:48px}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{max-width:calc(133.3333333333% - 85.3333333333px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc{left:36px;right:auto}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc[dir=rtl]{left:auto;right:36px}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc :not(.VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd) .VfPpkd-NSFCdd-Ra9xwd{max-width:calc(100% - 60px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-37.25px) translateX(-32px) scale(1);-ms-transform:translateY(-37.25px) translateX(-32px) scale(1);transform:translateY(-37.25px) translateX(-32px) scale(1)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe[dir=rtl]{-webkit-transform:translateY(-37.25px) translateX(32px) scale(1);-ms-transform:translateY(-37.25px) translateX(32px) scale(1);transform:translateY(-37.25px) translateX(32px) scale(1)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-34.75px) translateX(-32px) scale(.75);-ms-transform:translateY(-34.75px) translateX(-32px) scale(.75);transform:translateY(-34.75px) translateX(-32px) scale(.75)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe[dir=rtl],.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe[dir=rtl]{-webkit-transform:translateY(-34.75px) translateX(32px) scale(.75);-ms-transform:translateY(-34.75px) translateX(32px) scale(.75);transform:translateY(-34.75px) translateX(32px) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:.75rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:1rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-text-field-outlined-leading-icon .25s 1;animation:mdc-floating-label-shake-float-above-text-field-outlined-leading-icon .25s 1}@-webkit-key | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=notion.id&hl=es_GT | Notion: Notes, Tasks, AI - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion: Notes, Tasks, AI Notion Labs, Inc. In-app purchases 4.8 star 327K reviews 10M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Whether you’re looking to track your personal to-do’s, write and organize class notes, or run project management with a team, Notion is the AI-powered workspace that works your way, for any need. Keep track of your personal and professional goals, take notes about what you care about, and stay organized. "AI's everything app" — Forbes Notion is a productivity app where you can write, plan, and organize your notes, projects, tasks and more - all in one place. Ask Notion AI about project updates, upcoming tasks, and suggestions for a more streamlined workflow. Simplify writing notes, project and task management, and collaboration. Whether for personal, student or professional use, Notion scales to meet your individual needs with customization tools for everyone. FREE FOR PERSONAL USE • Create as many notes, docs, and content as you want. • Use one of thousands of templates to get started. FREE TO TRY WITH YOUR TEAM • Millions run on Notion every day, from next-generation startups to established enterprises. • Import Google Docs, PDFs, and other content types easily to get started • Write and organize meeting notes, or transcribe with AI. • Collaboration and team work at your fingertips, in one connected workspace. • Connect tools like Figma, Slack, and GitHub to Notion. FREE FOR STUDENTS • Your study planner, class notes, to do lists and more, your way. Loved by millions of students worldwide. • Get organized for your best school year yet with beautiful, customizable templates created by students, for students. NOTES & DOCS Communication is made efficient with Notion's flexible building blocks. • Create docs with beautiful templates, images, to-dos, and 50+ more content types. • Meeting notes, projects, design systems, pitch decks, and more. • Find exactly what you need using Search with powerful filters to find content across your workspace. TASKS & PROJECTS Catch all details big and small in any workflow. • Workflow manager: Create your own priority labels, status tags, and automations to choose the exact info you want to track. • Capture every detail in a table. Break projects into manageable tasks to get the work done. AI One tool that does it all - search, generate, analyze, and chat - right inside Notion. • Write better. Use Notion AI to help write and brainstorm. • Get answers. Ask Notion AI questions about all your content and get answers in seconds. • Autofill tables. Notion AI turns overwhelming data into clear, actionable information — automatically. SYNCS WITH BROWSER, MAC, AND WINDOWS APPS. • Pick up on mobile where you left off on desktop. MORE PRODUCTIVITY. FEWER TOOLS. • Track to-dos, write notes, create docs, and manage projects in one connected workspace. THINK IT. MAKE IT. Updated on Jan 13, 2026 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, Photos and videos and 5 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.8 319K reviews 5 4 3 2 1 Sommy Nriama more_vert Flag inappropriate Show review history </span | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=notion.id&hl=gsw | Notion: Notes, Tasks, AI - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion: Notes, Tasks, AI Notion Labs, Inc. In-app purchases 4.8 star 327K reviews 10M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Whether you’re looking to track your personal to-do’s, write and organize class notes, or run project management with a team, Notion is the AI-powered workspace that works your way, for any need. Keep track of your personal and professional goals, take notes about what you care about, and stay organized. "AI's everything app" — Forbes Notion is a productivity app where you can write, plan, and organize your notes, projects, tasks and more - all in one place. Ask Notion AI about project updates, upcoming tasks, and suggestions for a more streamlined workflow. Simplify writing notes, project and task management, and collaboration. Whether for personal, student or professional use, Notion scales to meet your individual needs with customization tools for everyone. FREE FOR PERSONAL USE • Create as many notes, docs, and content as you want. • Use one of thousands of templates to get started. FREE TO TRY WITH YOUR TEAM • Millions run on Notion every day, from next-generation startups to established enterprises. • Import Google Docs, PDFs, and other content types easily to get started • Write and organize meeting notes, or transcribe with AI. • Collaboration and team work at your fingertips, in one connected workspace. • Connect tools like Figma, Slack, and GitHub to Notion. FREE FOR STUDENTS • Your study planner, class notes, to do lists and more, your way. Loved by millions of students worldwide. • Get organized for your best school year yet with beautiful, customizable templates created by students, for students. NOTES & DOCS Communication is made efficient with Notion's flexible building blocks. • Create docs with beautiful templates, images, to-dos, and 50+ more content types. • Meeting notes, projects, design systems, pitch decks, and more. • Find exactly what you need using Search with powerful filters to find content across your workspace. TASKS & PROJECTS Catch all details big and small in any workflow. • Workflow manager: Create your own priority labels, status tags, and automations to choose the exact info you want to track. • Capture every detail in a table. Break projects into manageable tasks to get the work done. AI One tool that does it all - search, generate, analyze, and chat - right inside Notion. • Write better. Use Notion AI to help write and brainstorm. • Get answers. Ask Notion AI questions about all your content and get answers in seconds. • Autofill tables. Notion AI turns overwhelming data into clear, actionable information — automatically. SYNCS WITH BROWSER, MAC, AND WINDOWS APPS. • Pick up on mobile where you left off on desktop. MORE PRODUCTIVITY. FEWER TOOLS. • Track to-dos, write notes, create docs, and manage projects in one connected workspace. THINK IT. MAKE IT. Updated on Jan 13, 2026 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, Photos and videos and 5 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.8 319K reviews 5 4 3 2 1 Sommy Nriama more_vert Flag inappropriate Show review history <pa | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=notion.id&hl=fr | Notion: Notes, Tasks, AI - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion: Notes, Tasks, AI Notion Labs, Inc. In-app purchases 4.8 star 327K reviews 10M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Whether you’re looking to track your personal to-do’s, write and organize class notes, or run project management with a team, Notion is the AI-powered workspace that works your way, for any need. Keep track of your personal and professional goals, take notes about what you care about, and stay organized. "AI's everything app" — Forbes Notion is a productivity app where you can write, plan, and organize your notes, projects, tasks and more - all in one place. Ask Notion AI about project updates, upcoming tasks, and suggestions for a more streamlined workflow. Simplify writing notes, project and task management, and collaboration. Whether for personal, student or professional use, Notion scales to meet your individual needs with customization tools for everyone. FREE FOR PERSONAL USE • Create as many notes, docs, and content as you want. • Use one of thousands of templates to get started. FREE TO TRY WITH YOUR TEAM • Millions run on Notion every day, from next-generation startups to established enterprises. • Import Google Docs, PDFs, and other content types easily to get started • Write and organize meeting notes, or transcribe with AI. • Collaboration and team work at your fingertips, in one connected workspace. • Connect tools like Figma, Slack, and GitHub to Notion. FREE FOR STUDENTS • Your study planner, class notes, to do lists and more, your way. Loved by millions of students worldwide. • Get organized for your best school year yet with beautiful, customizable templates created by students, for students. NOTES & DOCS Communication is made efficient with Notion's flexible building blocks. • Create docs with beautiful templates, images, to-dos, and 50+ more content types. • Meeting notes, projects, design systems, pitch decks, and more. • Find exactly what you need using Search with powerful filters to find content across your workspace. TASKS & PROJECTS Catch all details big and small in any workflow. • Workflow manager: Create your own priority labels, status tags, and automations to choose the exact info you want to track. • Capture every detail in a table. Break projects into manageable tasks to get the work done. AI One tool that does it all - search, generate, analyze, and chat - right inside Notion. • Write better. Use Notion AI to help write and brainstorm. • Get answers. Ask Notion AI questions about all your content and get answers in seconds. • Autofill tables. Notion AI turns overwhelming data into clear, actionable information — automatically. SYNCS WITH BROWSER, MAC, AND WINDOWS APPS. • Pick up on mobile where you left off on desktop. MORE PRODUCTIVITY. FEWER TOOLS. • Track to-dos, write notes, create docs, and manage projects in one connected workspace. THINK IT. MAKE IT. Updated on Jan 13, 2026 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, Photos and videos and 5 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.8 319K reviews 5 4 3 2 1 Sommy Nriama more_vert Flag inappropriate Show review history <path d="M12 17.27L18 | 2026-01-13T09:30:03 |
https://ai.google.dev/api/palm?hl=ja | PaLM (decommissioned) | Gemini API | Google AI for Developers メイン コンテンツにスキップ / English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Shqip Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 API キーを取得する クックブック Community ログイン ドキュメント API リファレンス Gemini API ドキュメント API リファレンス API キーを取得する クックブック Community 概要 API バージョン 機能 モデル コンテンツの生成 Live API Live Music API Interactions API トークン ファイル バッチ API キャッシュ エンベディング ファイル検索 ファイル検索ストア ドキュメント すべてのメソッド 非推奨 PaLM（廃止） SDK リファレンス Python Go TypeScript Java C# ホーム Gemini API API リファレンス フィードバックを送信 PaLM (decommissioned) メソッド: models.generateText エンドポイント パスパラメータ リクエストの本文 JSON 表現 レスポンスの本文 認可スコープ 入力メッセージを指定して、モデルからレスポンスを生成します。 エンドポイント 投稿 https: / /generativelanguage.googleapis.com /v1beta /{model=models /*}:generateText パスパラメータ model string 必須。補完の生成に使用する Model または TunedModel の名前。例: models/text-bison-001、tunedModels/sentence-translator-u3b7m。形式は models/{model} です。 リクエストの本文 リクエストの本文には、次の構造のデータが含まれます。 フィールド prompt object ( TextPrompt ) 必須。モデルにプロンプトとして渡される自由形式の入力テキスト。 プロンプトが指定されると、モデルは入力テキストの補完として予測される TextCompletion レスポンスを生成します。 safetySettings[] object ( SafetySetting ) 省略可。安全でないコンテンツをブロックするための、一意の SafetySetting インスタンスのリスト。 この制限は GenerateTextRequest.prompt と GenerateTextResponse.candidates に適用されます。 SafetyCategory タイプごとに設定は 1 つだけにする必要があります。API は、これらの設定で設定されたしきい値を満たしていないプロンプトとレスポンスをブロックします。このリストは、safetySettings で指定された各 SafetyCategory のデフォルト設定をオーバーライドします。リストに指定された特定の SafetyCategory に SafetySetting がない場合、API はそのカテゴリのデフォルトの安全性設定を使用します。テキスト サービスでは、有害カテゴリ HARM_CATEGORY_DEROGATORY、HARM_CATEGORY_TOXICITY、HARM_CATEGORY_VIOLENCE、HARM_CATEGORY_SEXUAL、HARM_CATEGORY_MEDICAL、HARM_CATEGORY_DANGEROUS がサポートされています。 stopSequences[] string 出力生成を停止する文字シーケンスのセット（最大 5 個）。指定した場合、API は停止シーケンスが最初に出現した時点で停止します。停止シーケンスはレスポンスには含まれません。 temperature number 省略可。出力のランダム性を制御します。注: デフォルト値はモデルによって異なります。 getModel 関数から返された Model の Model.temperature 属性をご覧ください。 値の範囲は [0.0,1.0] です。値が 1.0 に近いほど、より多様でクリエイティブなレスポンスが生成されます。値が 0.0 に近いほど、モデルからより直接的なレスポンスが生成されます。 candidateCount integer 省略可。返す生成されたレスポンスの数。 この値は [1, 8] の範囲で指定してください。設定しない場合、デフォルトで 1 になります。 maxOutputTokens integer 省略可。候補に含めるトークンの最大数。 設定されていない場合、デフォルトで Model 仕様で指定された outputTokenLimit になります。 topP number 省略可。サンプリング時に考慮するトークンの累積確率の最大値。 このモデルでは、Top-k と Nucleus サンプリングを組み合わせて使用します。 トークンは割り当てられた確率に基づいて並べ替えられ、最も可能性の高いトークンのみが考慮されます。Top-k サンプリングは、考慮するトークンの最大数を直接制限しますが、Nucleus サンプリングは累積確率に基づいてトークンの数を制限します。 注: デフォルト値はモデルによって異なります。 getModel 関数から返された Model の Model.top_p 属性をご覧ください。 topK integer 省略可。サンプリング時に考慮するトークンの最大数。 このモデルでは、Top-k と Nucleus サンプリングを組み合わせて使用します。 Top-k サンプリングでは、最も確率の高い topK 個のトークンのセットが考慮されます。デフォルトは 40 です。 注: デフォルト値はモデルによって異なります。 getModel 関数から返された Model の Model.top_k 属性をご覧ください。 レスポンスの本文 成功した場合、レスポンスの本文には GenerateTextResponse のインスタンスが含まれます。 メソッド: models.countTextTokens エンドポイント パスパラメータ リクエストの本文 JSON 表現 レスポンスの本文 JSON 表現 認可スコープ テキストに対してモデルのトークナイザーを実行し、トークン数を返します。 エンドポイント 投稿 https: / /generativelanguage.googleapis.com /v1beta /{model=models /*}:countTextTokens パスパラメータ model string 必須。モデルのリソース名。これは、モデルが使用する ID として機能します。 この名前は、 models.list メソッドから返されるモデル名と一致する必要があります。 形式: models/{model} 形式は models/{model} です。 リクエストの本文 リクエストの本文には、次の構造のデータが含まれます。 フィールド prompt object ( TextPrompt ) 必須。モデルにプロンプトとして渡される自由形式の入力テキスト。 レスポンスの本文 models.countTextTokens からのレスポンス。 prompt のモデルの tokenCount を返します。 成功した場合、レスポンスの本文には次の構造のデータが含まれます。 フィールド tokenCount integer model が prompt をトークン化するトークンの数。 常に非負の値です。 JSON 表現 { "tokenCount" : integer } メソッド: models.generateMessage エンドポイント パスパラメータ リクエストの本文 JSON 表現 レスポンスの本文 JSON 表現 認可スコープ 入力 MessagePrompt に基づいてモデルからレスポンスを生成します。 エンドポイント 投稿 https: / /generativelanguage.googleapis.com /v1beta /{model=models /*}:generateMessage パスパラメータ model string 必須。使用するモデルの名前。 形式: name=models/{model} 。形式は models/{model} です。 リクエストの本文 リクエストの本文には、次の構造のデータが含まれます。 フィールド prompt object ( MessagePrompt ) 必須。モデルにプロンプトとして渡される構造化されたテキスト入力。 プロンプトが指定されると、モデルはディスカッションの次のメッセージとして予測されるものを返します。 temperature number 省略可。出力のランダム性を制御します。 値の範囲は [0.0,1.0] です。 1.0 に近い値ほど、より多様なレスポンスが生成されます。一方、 0.0 に近い値ほど、モデルから驚くようなレスポンスが返される可能性は低くなります。 candidateCount integer 省略可。返す生成されたレスポンス メッセージの数。 この値は [1, 8] の範囲で指定する必要があります。設定しない場合、デフォルトで 1 になります。 topP number 省略可。サンプリング時に考慮するトークンの累積確率の最大値。 このモデルでは、Top-k と Nucleus サンプリングを組み合わせて使用します。 ニュークリアス サンプリングでは、確率の合計が topP 以上の最小のトークンセットが考慮されます。 topK integer 省略可。サンプリング時に考慮するトークンの最大数。 このモデルでは、Top-k と Nucleus サンプリングを組み合わせて使用します。 Top-k サンプリングでは、最も確率の高い topK 個のトークンのセットが考慮されます。 レスポンスの本文 モデルからのレスポンス。 これには、候補メッセージと、時系列順に並べられたメッセージ形式の会話履歴が含まれます。 成功した場合、レスポンスの本文には次の構造のデータが含まれます。 フィールド candidates[] object ( Message ) モデルからの候補レスポンス メッセージ。 messages[] object ( Message ) モデルで使用される会話履歴。 filters[] object ( ContentFilter ) プロンプトとレスポンスのテキストのコンテンツ フィルタリング メタデータのセット。 これは、このレスポンスから候補をブロックした SafetyCategory 、ブロックをトリガーした最小の HarmProbability 、そのカテゴリの HarmThreshold 設定を示します。 JSON 表現 { "candidates" : [ { object ( Message ) } ] , "messages" : [ { object ( Message ) } ] , "filters" : [ { object ( ContentFilter ) } ] } メソッド: models.countMessageTokens エンドポイント パスパラメータ リクエストの本文 JSON 表現 レスポンスの本文 JSON 表現 認可スコープ 文字列に対してモデルのトークナイザーを実行し、トークン数を返します。 エンドポイント 投稿 https: / /generativelanguage.googleapis.com /v1beta /{model=models /*}:countMessageTokens パスパラメータ model string 必須。モデルのリソース名。これは、モデルが使用する ID として機能します。 この名前は、 models.list メソッドから返されるモデル名と一致する必要があります。 形式: models/{model} 形式は models/{model} です。 リクエストの本文 リクエストの本文には、次の構造のデータが含まれます。 フィールド prompt object ( MessagePrompt ) 必須。トークン数を返すプロンプト。 レスポンスの本文 models.countMessageTokens からのレスポンス。 prompt のモデルの tokenCount を返します。 成功した場合、レスポンスの本文には次の構造のデータが含まれます。 フィールド tokenCount integer model が prompt をトークン化するトークンの数。 常に非負の値です。 JSON 表現 { "tokenCount" : integer } メソッド: models.embedText エンドポイント パスパラメータ リクエストの本文 JSON 表現 レスポンスの本文 JSON 表現 認可スコープ 入力メッセージが指定されたモデルからエンベディングを生成します。 エンドポイント 投稿 https: / /generativelanguage.googleapis.com /v1beta /{model=models /*}:embedText パスパラメータ model string 必須。使用するモデル名。形式は model=models/{model} です。形式は models/{model} です。 リクエストの本文 リクエストの本文には、次の構造のデータが含まれます。 フィールド text string 省略可。モデルがエンベディングに変換する自由形式の入力テキスト。 レスポンスの本文 EmbedTextRequest へのレスポンス。 成功した場合、レスポンスの本文には次の構造のデータが含まれます。 フィールド embedding object ( Embedding ) 出力専用。入力テキストから生成されたエンベディング。 JSON 表現 { "embedding" : { object ( Embedding ) } } メソッド: models.batchEmbedText エンドポイント パスパラメータ リクエストの本文 JSON 表現 レスポンスの本文 JSON 表現 認可スコープ EmbedTextRequest JSON 表現 同期呼び出しで、入力テキストが指定されたモデルから複数のエンベディングを生成します。 エンドポイント 投稿 https: / /generativelanguage.googleapis.com /v1beta /{model=models /*}:batchEmbedText パスパラメータ model string 必須。エンベディングの生成に使用する Model の名前。例: models/embedding-gecko-001 形式は models/{model} です。 リクエストの本文 リクエストの本文には、次の構造のデータが含まれます。 フィールド texts[] string 省略可。モデルがエンベディングに変換する自由形式の入力テキスト。現在の上限は 100 テキストです。これを超えるとエラーがスローされます。 requests[] object ( EmbedTextRequest ) 省略可。バッチのエンベディング リクエスト。 texts または requests のいずれか 1 つのみを設定できます。 レスポンスの本文 EmbedTextRequest へのレスポンス。 成功した場合、レスポンスの本文には次の構造のデータが含まれます。 フィールド embeddings[] object ( Embedding ) 出力専用。入力テキストから生成されたエンベディング。 JSON 表現 { "embeddings" : [ { object ( Embedding ) } ] } EmbedTextRequest モデルからテキスト エンベディングを取得するリクエスト。 フィールド model string 必須。使用するモデル名。形式は model=models/{model} です。 text string 省略可。モデルがエンベディングに変換する自由形式の入力テキスト。 JSON 表現 { "model" : string , "text" : string } ContentFilter JSON 表現 BlockedReason 単一のリクエストの処理に関連付けられたコンテンツ フィルタリング メタデータ。 ContentFilter には、理由とオプションのサポート文字列が含まれます。理由は指定されていない場合があります。 フィールド reason enum ( BlockedReason ) リクエストの処理中にコンテンツがブロックされた理由。 message string フィルタリングの動作を詳しく説明する文字列。 JSON 表現 { "reason" : enum ( BlockedReason ) , "message" : string } BlockedReason コンテンツがブロックされた理由のリスト。 列挙型 BLOCKED_REASON_UNSPECIFIED ブロックされた理由が指定されていません。 SAFETY 安全性設定によりコンテンツがブロックされました。 OTHER コンテンツはブロックされましたが、理由は分類されていません。 埋め込み JSON 表現 エンベディングを表す浮動小数点数のリスト。 フィールド value[] number エンベディング値。 JSON 表現 { "value" : [ number ] } メッセージ JSON 表現 構造化テキストの基本単位。 Message には、 author と Message の content が含まれます。 author は、メッセージがテキストとしてモデルに供給されるときにメッセージにタグを付けるために使用されます。 フィールド author string 省略可。このメッセージの作成者。 これは、このメッセージのコンテンツがテキストとしてモデルに渡されるときに、そのコンテンツにタグを付けるためのキーとして機能します。 作成者は任意の英数字文字列にできます。 content string 必須。構造化された Message のテキスト コンテンツ。 citationMetadata object ( CitationMetadata ) 出力専用。この Message のモデル生成 content の引用情報。 この Message がモデルの出力として生成された場合、このフィールドには content に含まれるテキストのアトリビューション情報が入力されることがあります。このフィールドは出力でのみ使用されます。 JSON 表現 { "author" : string , "content" : string , "citationMetadata" : { object ( CitationMetadata ) } } MessagePrompt JSON 表現 例 JSON 表現 モデルにプロンプトとして渡されるすべての構造化入力テキスト。 MessagePrompt には、会話のコンテキストを提供する構造化されたフィールドのセット、モデルがさまざまな方法で応答するように準備するユーザー入力/モデル出力メッセージ ペアの例、ユーザーとモデルの会話のターンを交互に表す会話履歴またはメッセージのリストが含まれます。 フィールド context string 省略可。有効な回答を得るために最初にモデルに提供する必要のあるテキスト。 空でない場合、この context は examples と messages の前にモデルに渡されます。 context を使用する場合は、継続性を維持するために、すべてのリクエストで context を指定してください。 このフィールドには、コンテキストを提供して回答を導くために、モデルに対するプロンプトの説明を入力できます。例: 「このフレーズを英語からフランス語に翻訳して。」、「この文の感情を、喜び、悲しみ、中立のいずれかに分類して。」 このフィールドに含まれる内容は、入力サイズの合計がモデルの inputTokenLimit を超え、入力リクエストが切り捨てられた場合、メッセージ履歴よりも優先されます。 examples[] object ( Example ) 省略可。モデルが生成する内容の例。 これには、ユーザー入力とモデルがエミュレートする必要があるレスポンスの両方が含まれます。 これらの examples は、会話メッセージと同じように扱われますが、 messages の履歴よりも優先されます。入力の合計サイズがモデルの inputTokenLimit を超える場合、入力は切り捨てられます。アイテムは examples の前に messages からドロップされます。 messages[] object ( Message ) 必須。最近の会話履歴のスナップショット（時系列順に並べ替えられています）。 2 人の著者が交互に執筆します。 入力の合計サイズがモデルの inputTokenLimit を超えると、入力は切り捨てられます。最も古いアイテムが messages から削除されます。 JSON 表現 { "context" : string , "examples" : [ { object ( Example ) } ] , "messages" : [ { object ( Message ) } ] } 例 モデルに指示するために使用される入出力の例。 モデルがどのように回答すべきか、または回答の形式をどのようにすべきかを示します。 フィールド input object ( Message ) 必須。ユーザーからの入力 Message の例。 output object ( Message ) 必須。入力に対してモデルが出力する内容の例。 JSON 表現 { "input" : { object ( Message ) } , "output" : { object ( Message ) } } GenerateTextResponse JSON 表現 TextCompletion JSON 表現 SafetyFeedback JSON 表現 候補の補完を含む、モデルからのレスポンス。 フィールド candidates[] object ( TextCompletion ) モデルからの候補レスポンス。 filters[] object ( ContentFilter ) プロンプトとレスポンスのテキストのコンテンツ フィルタリング メタデータのセット。 これは、このレスポンスから候補をブロックした SafetyCategory 、ブロックをトリガーした最小の HarmProbability 、そのカテゴリの HarmThreshold 設定を示します。これは、少なくとも 1 つのレスポンスのブロックを解除するために必要な SafetySettings の最小の変更を示します。 ブロックは、リクエストの SafetySettings （または API のデフォルトの SafetySettings ）によって構成されます。 safetyFeedback[] object ( SafetyFeedback ) コンテンツ フィルタリングに関連する安全性のフィードバックを返します。 JSON 表現 { "candidates" : [ { object ( TextCompletion ) } ] , "filters" : [ { object ( ContentFilter ) } ] , "safetyFeedback" : [ { object ( SafetyFeedback ) } ] } TextCompletion モデルから返された出力テキスト。 フィールド output string 出力専用。モデルから返された生成テキスト。 safetyRatings[] object ( SafetyRating ) 回答の安全性に関する評価。 カテゴリごとに 1 つのレーティングのみが許可されます。 citationMetadata object ( CitationMetadata ) 出力専用。この TextCompletion のモデル生成 output の引用情報。 このフィールドには、 output に含まれるテキストのアトリビューション情報が入力されることがあります。 JSON 表現 { "output" : string , "safetyRatings" : [ { object ( SafetyRating ) } ] , "citationMetadata" : { object ( CitationMetadata ) } } SafetyFeedback リクエスト全体の安全性に関するフィードバック。 このフィールドは、安全設定により入力またはレスポンスのコンテンツがブロックされた場合に設定されます。SafetyFeedback は、すべての HarmCategory に存在するとは限りません。各 SafetyFeedback は、リクエストで使用された安全性設定と、結果を返すために許可されるべき最小の HarmProbability を返します。 フィールド rating object ( SafetyRating ) コンテンツから評価された安全性のレーティング。 setting object ( SafetySetting ) リクエストに適用された安全性設定。 JSON 表現 { "rating" : { object ( SafetyRating ) } , "setting" : { object ( SafetySetting ) } } TextPrompt JSON 表現 モデルにプロンプトとして渡されるテキスト。 モデルは、この TextPrompt を使用してテキスト補完を生成します。 フィールド text string 必須。プロンプトのテキスト。 JSON 表現 { "text" : string } フィードバックを送信 特に記載のない限り、このページのコンテンツは クリエイティブ・コモンズの表示 4.0 ライセンス により使用許諾されます。コードサンプルは Apache 2.0 ライセンス により使用許諾されます。詳しくは、 Google Developers サイトのポリシー をご覧ください。Java は Oracle および関連会社の登録商標です。 最終更新日 2025-07-24 UTC。 ご意見をお聞かせください [[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-07-24 UTC。"],[],[]] 利用規約 プライバシー Manage cookies English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Shqip Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=en_CA | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPh | 2026-01-13T09:30:03 |
https://bsky.app/intent/compose?text=Nuxt%203.12%0A%0Ahttps%3A%2F%2Fnuxt.com%2Fblog%2Fv3-12 | Bluesky JavaScript Required This is a heavily interactive web application, and JavaScript is required. Simple HTML interfaces are possible, but that is not what this is. Learn more about Bluesky at bsky.social and atproto.com . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=notion.id&hl=es_CR | Notion: Notes, Tasks, AI - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion: Notes, Tasks, AI Notion Labs, Inc. In-app purchases 4.8 star 327K reviews 10M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Whether you’re looking to track your personal to-do’s, write and organize class notes, or run project management with a team, Notion is the AI-powered workspace that works your way, for any need. Keep track of your personal and professional goals, take notes about what you care about, and stay organized. "AI's everything app" — Forbes Notion is a productivity app where you can write, plan, and organize your notes, projects, tasks and more - all in one place. Ask Notion AI about project updates, upcoming tasks, and suggestions for a more streamlined workflow. Simplify writing notes, project and task management, and collaboration. Whether for personal, student or professional use, Notion scales to meet your individual needs with customization tools for everyone. FREE FOR PERSONAL USE • Create as many notes, docs, and content as you want. • Use one of thousands of templates to get started. FREE TO TRY WITH YOUR TEAM • Millions run on Notion every day, from next-generation startups to established enterprises. • Import Google Docs, PDFs, and other content types easily to get started • Write and organize meeting notes, or transcribe with AI. • Collaboration and team work at your fingertips, in one connected workspace. • Connect tools like Figma, Slack, and GitHub to Notion. FREE FOR STUDENTS • Your study planner, class notes, to do lists and more, your way. Loved by millions of students worldwide. • Get organized for your best school year yet with beautiful, customizable templates created by students, for students. NOTES & DOCS Communication is made efficient with Notion's flexible building blocks. • Create docs with beautiful templates, images, to-dos, and 50+ more content types. • Meeting notes, projects, design systems, pitch decks, and more. • Find exactly what you need using Search with powerful filters to find content across your workspace. TASKS & PROJECTS Catch all details big and small in any workflow. • Workflow manager: Create your own priority labels, status tags, and automations to choose the exact info you want to track. • Capture every detail in a table. Break projects into manageable tasks to get the work done. AI One tool that does it all - search, generate, analyze, and chat - right inside Notion. • Write better. Use Notion AI to help write and brainstorm. • Get answers. Ask Notion AI questions about all your content and get answers in seconds. • Autofill tables. Notion AI turns overwhelming data into clear, actionable information — automatically. SYNCS WITH BROWSER, MAC, AND WINDOWS APPS. • Pick up on mobile where you left off on desktop. MORE PRODUCTIVITY. FEWER TOOLS. • Track to-dos, write notes, create docs, and manage projects in one connected workspace. THINK IT. MAKE IT. Updated on Jan 13, 2026 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, Photos and videos and 5 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.8 319K reviews 5 4 3 2 1 Sommy Nriama more_vert Flag inappropriate Show review history <path d="M12 17.27L | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=notion.id&hl=hr | Notion: Notes, Tasks, AI - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion: Notes, Tasks, AI Notion Labs, Inc. In-app purchases 4.8 star 327K reviews 10M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Whether you’re looking to track your personal to-do’s, write and organize class notes, or run project management with a team, Notion is the AI-powered workspace that works your way, for any need. Keep track of your personal and professional goals, take notes about what you care about, and stay organized. "AI's everything app" — Forbes Notion is a productivity app where you can write, plan, and organize your notes, projects, tasks and more - all in one place. Ask Notion AI about project updates, upcoming tasks, and suggestions for a more streamlined workflow. Simplify writing notes, project and task management, and collaboration. Whether for personal, student or professional use, Notion scales to meet your individual needs with customization tools for everyone. FREE FOR PERSONAL USE • Create as many notes, docs, and content as you want. • Use one of thousands of templates to get started. FREE TO TRY WITH YOUR TEAM • Millions run on Notion every day, from next-generation startups to established enterprises. • Import Google Docs, PDFs, and other content types easily to get started • Write and organize meeting notes, or transcribe with AI. • Collaboration and team work at your fingertips, in one connected workspace. • Connect tools like Figma, Slack, and GitHub to Notion. FREE FOR STUDENTS • Your study planner, class notes, to do lists and more, your way. Loved by millions of students worldwide. • Get organized for your best school year yet with beautiful, customizable templates created by students, for students. NOTES & DOCS Communication is made efficient with Notion's flexible building blocks. • Create docs with beautiful templates, images, to-dos, and 50+ more content types. • Meeting notes, projects, design systems, pitch decks, and more. • Find exactly what you need using Search with powerful filters to find content across your workspace. TASKS & PROJECTS Catch all details big and small in any workflow. • Workflow manager: Create your own priority labels, status tags, and automations to choose the exact info you want to track. • Capture every detail in a table. Break projects into manageable tasks to get the work done. AI One tool that does it all - search, generate, analyze, and chat - right inside Notion. • Write better. Use Notion AI to help write and brainstorm. • Get answers. Ask Notion AI questions about all your content and get answers in seconds. • Autofill tables. Notion AI turns overwhelming data into clear, actionable information — automatically. SYNCS WITH BROWSER, MAC, AND WINDOWS APPS. • Pick up on mobile where you left off on desktop. MORE PRODUCTIVITY. FEWER TOOLS. • Track to-dos, write notes, create docs, and manage projects in one connected workspace. THINK IT. MAKE IT. Updated on Jan 13, 2026 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, Photos and videos and 5 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.8 319K reviews 5 4 3 2 1 Sommy Nriama more_vert Flag inappropriate Show review history <path d="M12 17.27L18.1 | 2026-01-13T09:30:03 |
https://extensionworkshop.com/documentation/develop/onboard-upboard-offboard-users/ | Onboard, upboard, offboard users | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Best practices for onboarding, upboarding, and offboarding users The first few minutes after someone installs your extension can be critical to its success. Your new user needs to know where to start and how to use the features of your browser extension. Contents Onboarding Upboarding Offboarding A Think Aloud User Research Study, conducted by Mozilla in August 2018, found that poor post-install tabs can erode any trust people had gained in an extension from its addons.mozilla.org listing. So much so, that in some cases study participants wanted to immediately remove the extension. The research also found that too much information or protracted setup requirements can have a similar negative impact on people’s perception of an extension. The best extensions provide people with just the information they need to get started, without requiring too much time or effort for set up. Equally, if the extension has any limitations, these should be mentioned during installation to avoid unnecessary support requests or, worse, poor reviews. However, engaging with people and keeping them informed isn’t just about the first few minutes after installation, it also applies when you upgrade your extension and even when the user removes your extension. Onboarding A good onboarding experience is essential for every browser extension and is not hard to do. You can onboard people through a new tab or popup window. Detecting installation You can listen for your extension’s installation using runtime.onInstalled as follows: browser . runtime . onInstalled . addListener ( async ( { reason , temporary } ) => { if ( temporary ) return ; // skip during development switch ( reason ) { case "install" : { const url = browser . runtime . getURL ( "views/installed.html" ) ; await browser . tabs . create ( { url } ) ; // or: await browser.windows.create({ url, type: "popup", height: 600, width: 600, }); } break ; // see below } } ) ; Onboarding page content Your onboarding page or popup should provide the essential information people need to get started. The content should, therefore, be brief and to the point. If your extension has many features, provide a separate help guide. The page should also complement the details provided on addons.mozilla.org , not repeat them in detail: the focus of the startup page should be how to use your extension, rather than what it does. Consider adding the following information to the onboarding page, in roughly the order it’s listed below: Your extension’s name, as it appears on addons.mozilla.org , along with its icon or logo. A brief overview of your extension’s features and functions, enough information to reassure the new user they’ve installed the right extension. Practical information on how to use the extension, including details on how to access its features from a toolbar button, address bar button, sidebar, or context menu. Include at least one simple activity that the user can do immediately. If your extension has many features, focus on providing instructions for the things users do first. Tip : Provide an introductory video: showing someone how to use your extension can be a lot more effective than telling them. If you do create a video, provide closed captioning or a transcript to make sure it’s accessible. If your extension features can be customized, explain the options available and provide a link to the settings page. If settings are a significant feature of the extension or the range of settings is large, don’t expect your new user to be happy working through several pages of settings now: consider providing quick links to specific configurations. Tip : Use runtime.openOptionsPage() to open the settings page. If the user needs an account for your web service to make use of the extension, provide them with a link to sign in or register. If your extension has paid features, let the user know what those features are and how much they cost. If you have tiered payments, provide a comparison chart or link to one on the extension’s website. Tip : If you fund the extension’s development from donations, now is a good time to tell people and provide a link to the donate page. Provide links to additional information such as the extension support page, help guide, tutorials, and alike. Tip : If you have other extensions, give them a mention. Having read your onboarding page, your new user should be confident about starting to use the extension immediately and know where to go if they need more information or support. If possible, they should have had some hands-on experience with key features. Page design Pay attention to the design and style of the page. Keep it consistent with your extension’s web page and AMO listing. For example, use consistent icons and colors. This helps reassure your user that they’ve installed and are using the right product. Follow the Photon Design System , where this doesn’t conflict with your product’s design. Don’t include advertising on your post-install page. Ads can degrade people’s trust in an extension, draw people away before they engage with your extension, and create confusion about what extension has been installed among other drawbacks. Onboarding page examples Here's an example of a good onboarding page: Ghostery – Privacy Ad Blocker As the features of Ghostery are mostly silent, this onboarding screen gives users two options for the initial setup: A simple one-click option and a link to the full settings so they can customize how Ghostery works. Upboarding When you update to your extension, take the opportunity to tell your users about the new features and any fixed issues. In addition to being an opportunity to engage with active users, you can also re-engage with people who may have stopped or never started using your extension. Detecting an upgrade You can listen for your extension’s updates using runtime.onInstalled as follows: browser . runtime . onInstalled . addListener ( async ( { reason , temporary } ) => { if ( temporary ) return ; // skip during development switch ( reason ) { // see above case "update" : { const url = browser . runtime . getURL ( "views/updated.html" ) ; await browser . tabs . create ( { url } ) ; // or: await browser.windows.create({ url, type: "popup", height: 600, width: 600, }); } break ; } } ) ; Tip : If your upgrade involves requesting additional permissions, see Test permission requests for details on how to test those changes. Upboarding page content Consider adding the following information to the update page: A brief description of your extension. This should be enough so your regular users can identify which extension has updated and enough to entice lapsed users back to using the extension. A list of the new or improved features or issues corrected in this update. Include information on how to find and use the new or improved features. If any of the new features require payment to use, let the user know what those features are and how much they cost. If you have tiered payments, provide a comparison chart or link to one on the extension’s website. This is also a good time to request donations, remembering to add a link to the donate page. Provide links to key information such as the extension support page, help guide, tutorials, and alike. Upboarding page examples Here are some examples of good upboarding pages: Snap Links Plus This page provides a brief description of Snap Links Plus before listing the improvements made in the release. Clint, the developer, also makes it clear that the project is an unpaid personal one and provides users with details of where they can contribute. He also kindly mentions the people who helped create the extension. Offboarding When a user decides to remove your extension, don’t miss the opportunity to gather feedback on why the extension hasn’t worked for them: you may not be able to get this user back but, by addressing their concerns you can hopefully reduce the number of users who might remove your extension in the future. Setting up an offboarding page link To gather information from leaving users, you need to set up an external webpage and then specify this in runtime.setUninstallURL() . This page then opens when a user removes the extension. Page content Consider adding the following information to the offboarding page: A “help us improve” message. A survey about why the user is removing the extension. Offer them a list of the most likely reasons and an optional free text area to provide more details. Remember to keep everything brief. A departing user is unlikely to respond to a multiple question quiz about why they are going. Offboarding page examples Here are some examples of good offboarding pages: Grammarly for Firefox This page provides a personal message from one of the Grammarly developers, a short list of reasons why the user might be removing the extension, and a text box where they can provide more information. Adblock Plus This page provides a link to reinstalling the extension, guarding against accidental removal. Then it offers a list of reasons why the user might have removed the extension, with the final option expanding into a textbox for details of other reasons. There is also a handy reminder that this information is sent to Adblock Plus and a link to their privacy policy. Tags: distribution guide install remove upgrade user-experience webextensions Contributors: alxwrd NiklasGollenstede David263 rebloor hamatti Last update: hamatti Oct 18, 2022 Up Next Develop User experience best practices Develop Differences between desktop and Android extensions Develop User experience guidelines for mobile extensions Documentation Topics Develop Publish Manage Enterprise Themes Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=en_US | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname=" | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_US | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname= | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=en_AU | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname=" | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#know-your-privacy-settings | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://extensionworkshop.com/documentation/develop/build-a-secure-extension/ | Build a secure extension | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Security best practices Here is a list of best practices you should follow to keep the users of your extension safe. If you don't follow these best practices your extension may fail the reviews on addons.mozilla.org (AMO), preventing you from distributing your add-on or resulting in it being blocked from installation in Firefox. Don’t inject or incorporate remote scripts If you identify a service that you wish to use in your extension, don’t inject the service’s script from a remote source. Such an approach is risky, as the code could be changed without your knowing—and, importantly, without the knowledge and consent of the extensions user—compromising the security of your extension. You should therefore add a copy of the script into your extension’s code. Ensure you insert remote content safely Make sure you follow best practices when your extension makes use of remote content: insert strings using safe native DOM manipulation methods: document.createElement() , Element.setAttribute() , and Node.textContent . use jQuery functions attr() and text() to insert strings. sanitize HTML content with DOMPurify . DOMPurify versions 2.0.6 and older contain a cross-site-scripting security vulnerability. Please ensure you are using the latest version. AMO will allow the latest 2.x version at the time of submission; previous versions will not be accepted due to their security vulnerabilities. use templating engine commands that escape any HTML before inserting it. For more information, see Safely inserting external content into a page . Use XHR for Google Analytics If you want to add Google Analytics to your extension don't insert the Google Analytics JavaScript code. Rather, it’s recommended that the Google Analytics REST API is used in an XHR call, such as: let request = new XMLHttpRequest ( ) ; let message = "v=1&tid=" + GA_TRACKING_ID + "&cid= " + GA_CLIENT_ID + "&aip=1" + "&ds=add-on&t=event&ec=AAA&ea=" + aType ; request . open ( "POST" , "https://www.google-analytics.com/collect" , true ) ; request . send ( message ) ; You can find more information in the blog post Using Google Analytics in Extensions . Use the standard extension content security policy (CSP) The standard policy restricts the sources from which your extension can load <script> and <object> resources, and disallows potentially unsafe practices such as the use of eval() . While the manifest.json key content_security_policy enables you to modify the content security policy for your extension, this isn’t recommended as the policy helps prevent extensions from inadvertently executing malicious content. If your modified CSP allows remote script injection your extension will get rejected from AMO during review. For more information, see Default content security policy . Share objects with in-page JavaScript with care Firefox provides wrappedJSObject so a content script can access JavaScript objects created by page scripts. The danger here is that a malicious web page could, for example, modify the functions of JavaScript objects to run code of its own. For more information, see Accessing page script objects from content scripts . Use window.eval() in content scripts with caution You should be very careful when running code in the context of a page. A malicious web page could attempt to run code of its own by exploiting the use of window.eval() . It might do this by, for example, redefining objects your code might want to evaluate. For more information, see Never use eval! Create your UI with extension components Create the UI for your extension using the built-in extension UI features , such as bundled pages, pageAction , and popups on pageAction and browserAction . Don’t add UI elements, such as buttons or toolbars, directly to web pages. If you do, scripts on the web page could compromise your extension. See Keybase Browser Extension Insecure for an example of the potential issues. If the standard UI components aren’t sufficient for your needs use iframes with data URLs to prevent fingerprinting, or add iframe s to the extension code so a page can’t interact with your UI content, such as buttons. Add eslint-plugin-no-unsanitized to ESLint If you make use of ESLint to check your extension code, consider adding eslint-plugin-no-unsanitized . This ESLint rules plug-in will flag instances where unsanitized code from APIs or user input could cause issues. Don’t inject moz-extension paths directly When injected links, includes, or images include paths to moz-extension://{internal UUID} , a page’s tracking script could use this information to fingerprint the user, as the internal UUID is unique to the extension installation and, therefore, the user. The best way to avoid this issue is to follow the general advice about not injecting content. However, if you believe injecting content is your only practical approach, ensure that moz-extension paths are embedded inside an iframe using a data URL or the srcdoc attribute. Ensure that third-party libraries are up to date Reputable third-party libraries will be updated when any issues are found. The use of outdated (and potentially insecure) third-party libraries is strongly discouraged and, when a significant risk is identified, AMO may act to block extensions using the out of date code. Therefore, always use the latest version of any third-party libraries when you create your extension. Then, be aware of updates to those libraries and be prepared to update your extension to ensure its using an up to date version of the library. Do not modify third-party libraries Modifications to a third-party library are a significant indicator that a developer is trying to hide malicious code within code that is generally known and trusted. AMO will therefore try to detect changes to third-party libraries and may disable extensions when it finds changes. Tags: beginner extensions intermediate reviews security webextensions Contributors: caitmuenster irenesmith tomrittervg rebloor Last update: caitmuenster Sep 15, 2020 Up Next Develop Request the right permissions Develop Firefox built-in consent for data collection and transmission Develop Best practices for collecting user data consents Documentation Topics Develop Publish Manage Enterprise Themes Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#prompt-after-install | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=fa | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="rymPhb | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_NI | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=de_CH | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymP | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=hi | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="ry | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#offboarding | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=as | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymP | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=bn | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname=" | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_CO | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPh | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=cs | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb | 2026-01-13T09:30:03 |
https://fr-fr.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1w9T5h4SFIM-3PmCUHPrcl-t1jb-segjkGEn4zpU67vWNthY4RTydxRIQCc8JgYepeq7aDBl0HymBVlYUfdIe8WqUBykPipderUBMoNtpsjiPXCEhOEQ5bn0VuDhbm4hgo8yTdvk4h2QfH | Facebook Facebook Adresse e-mail ou téléphone Mot de passe Informations de compte oubliées ? Créer un compte Cette fonction est temporairement bloquée Cette fonction est temporairement bloquée Il semble que vous ayez abusé de cette fonctionnalité en l’utilisant trop vite. Vous n’êtes plus autorisé à l’utiliser. Back Français (France) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Deutsch S’inscrire Se connecter Messenger Facebook Lite Vidéo Meta Pay Boutique Meta Meta Quest Ray-Ban Meta Meta AI Plus de contenu Meta AI Instagram Threads Centre d’information sur les élections Politique de confidentialité Centre de confidentialité À propos Créer une publicité Créer une Page Développeurs Emplois Cookies Choisir sa publicité Conditions générales Aide Importation des contacts et non-utilisateurs Paramètres Historique d’activité Meta © 2026 | 2026-01-13T09:30:03 |
https://www.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1w9T5h4SFIM-3PmCUHPrcl-t1jb-segjkGEn4zpU67vWNthY4RTydxRIQCc8JgYepeq7aDBl0HymBVlYUfdIe8WqUBykPipderUBMoNtpsjiPXCEhOEQ5bn0VuDhbm4hgo8yTdvk4h2QfH | Facebook Facebook 이메일 또는 휴대폰 비밀번호 계정을 잊으셨나요? 새 계정 만들기 일시적으로 차단됨 일시적으로 차단됨 회원님의 이 기능 사용 속도가 너무 빠른 것 같습니다. 이 기능 사용에서 일시적으로 차단되었습니다. Back 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=en_SG | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPh | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=en_IN | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=eu | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname=" | 2026-01-13T09:30:03 |
https://scrabblewordfinder.org/scrabble-words-with/v/and/z | Scrabble Words with V and Z - ScrabbleWordFinder.org --> Dictionary Two Letter Words Word List Words with Friends Finder Scrabble Words with 'V' and 'Z' List of scrabble words which contains the letter V as well as the letter Z 15 Letter Words civilianization comprehensivize conventionalize conveyorization derivatizations desilverization devalorizations devitalizations envenomizations evangelizations extensivization governmentalize incentivization individualizers individualizing misvocalization overadvertizing overcapitalized overcapitalizes overcentralized overcentralizes overdramatizing overemphasizing overfertilizing overgeneralized overgeneralizes overglamorizing overhomogenized overhomogenizes overspecialized overspecializes overutilization overzealousness proverbializing provincializing readvertizement relativizations reprivatization revalorizations revisualization revitalizations revolutionizers revolutionizing subcivilization substantivizing subvocalization trivializations uncivilizedness universalizable vascularization ventriloquizing vernacularizing virtualizations vitriolizations volatilizations 14 Letter Words adverbializing advertizements civilizational collectivizing conservatizing conversaziones derivatization devalorization devitalization envenomization evangelization galvanizations hypercivilized individualized individualizer individualizes ovariectomized overadvertized overadvertizes overcapitalize overcentralize overdramatized overdramatizes overemphasized overemphasizes overfertilized overfertilizes overgeneralize overglamorized overglamorizes overhomogenize overidealizing overorganizing overspecialize privatizations proverbialized proverbializes provincialized provincializes pulverizations relativization revalorization revitalization revolutionized revolutionizer revolutionizes sovietizations subjectivizing substantivized substantivizes supercivilized trivialization ultracivilized universalizing vacuolizations vandalizations variolizations vectorizations ventriloquized ventriloquizes verbalizations vernacularized vernacularizes vernalizations victimizations villagizations virtualization visualizations vitriolization volatilization volcanizations vulcanizations vulgarizations — — ADVERTISEMENT — — 13 Letter Words adverbialized adverbializes advertizement civilianizing civilizations collectivized collectivizes conservatized conservatizes conversazione conversazioni conveyorizing desilverizing divinizations eventualizing extravaganzas galvanization incentivizing individualize novelizations objectivizing overadvertize overanalyzing overcivilized overdramatize overemphasize overfertilize overglamorize overidealized overidealizes overorganized overorganizes overutilizing overzealously privatdozents privatization proverbialize provincialize pulverization readvertizing rendezvousing reprivatizing revolutionize semicivilized sovietization subjectivized subjectivizes substantivize subvocalizing uncivilizedly universalized universalizes unvulgarizing vacuolization vagabondizing valorizations vandalization vaporizations variolization vascularizing vasectomizing vectorization velarizations ventriloquize verbalization vernacularize vernalization victimization villagization virilizations visualization vitalizations vocalizations volatilizable volcanization vowelizations vulcanization vulgarization 12 Letter Words adverbialize advertizings bathmitzvahs bolshevizing civilianized civilianizes civilization collectivize conservatize conveyorized conveyorizes czarevitches decivilizing derivatizing desilverized desilverizes devalorizing devitalizing devocalizing divinization evangelizers evangelizing eventualized eventualizes extravaganza incentivized incentivizes novelization objectivized objectivizes overanalyzed overanalyzes overgrazings overidealize overorganize overutilized overutilizes privatdozent pulverizable readvertized readvertizes rejuvenizing relativizing rendezvoused rendezvouses reprivatized reprivatizes revalorizing revitalizing subcivilized subjectivize subvocalized subvocalizes trivializing unadvertized universalize unverbalized unvulgarized unvulgarizes vagabondized vagabondizes valorization vaporization vascularized vascularizes vasectomized vasectomizes velarization virilization virtualizing vitalization vitaminizing vitriolizing vocalization volatilizing vowelization vulcanizable vulcanizates 11 Letter Words advertizers advertizing barmitzvahs basmitzvahs bathmitzvah bathmizvahs batmitzvahs bolshevized bolshevizes civilianize civilizable conveyorize czareviches decivilized decivilizes derivatized derivatizes desilverize devalorized devalorizes devitalized devitalizes devocalized devocalizes evangelized evangelizer evangelizes eventualize galvanizers galvanizing incentivize objectivize overanalyze overglazing overgrazing overprizing overutilize overzealous privatizers privatizing pulverizers pulverizing readvertize rejuvenized rejuvenizes relativized relativizes reprivatize revalorized revalorizes revitalized revitalizes silverizing slivovitzes slivowitzes sovietizing subvocalize trivialized trivializes uncivilized unvizarding unvocalized unvulgarize vagabondize vajazzlings vampirizing vandalizing vaporizable vascularize vasectomize vassalizing vectorizing verbalizers verbalizing vernalizing victimizers victimizing virtualized virtualizes visualizers visualizing vitaminized vitaminizes vitriolized vitriolizes vizierships volatilized volatilizes volcanizing vulcanizate vulcanizers vulcanizing vulgarizers vulgarizing zidovudines 10 Letter Words activizing advertized advertizer advertizes avianizing avizandums barmitzvah basmitzvah bathmizvah batmitzvah bolshevize civilizers civilizing czarevitch decivilize derivatize devalorize devitalize devocalize divinizing evangelize galvanized galvanizer galvanizes izvestiyas jarovizing novelizers novelizing overglazed overglazes overgrazed overgrazes overprized overprizes oversizing pavonazzos privatized privatizer privatizes pulverized pulverizer pulverizes pulvilized rejuvenize relativize rendezvous revalorize revitalize rivalizing schvartzes schvitzing silverized silverizes sovietized sovietizes trivialize unvizarded vajazzling valorizing vampirized vampirizes vandalized vandalizes vaporizers vaporizing vassalized vassalizes vectorized vectorizes velarizing verbalized verbalizer verbalizes vernalized vernalizes victimized victimizer victimizes virilizing virtualize visualized visualizer visualizes vitalizers vitalizing vitaminize vitriolize vizierates viziership vizirships vocalizers vocalizing volatilize volcanized volcanizes volumizers volumizing vowelizing vulcanized vulcanizer vulcanizes vulgarized vulgarizer vulgarizes zanamivirs zidovudine 9 Letter Words activized activizes advertize avianized avianizes avizandum avizefull civilized civilizer civilizes czarevich czarevnas divinized divinizes galvanize izvestias izvestiya jarovized jarovizes novelized novelizer novelizes overglaze overgraze overprize oversized oversizes overzeals pavonazzo pozidrive privatize pulverize rivalized rivalizes schvartze schvitzed schvitzes shvartzes shvitzing silverize slivovitz slivowitz sovietize sovkhozes tzarevnas unvizards vajazzled vajazzles valorized valorizes vampirize vandalize vaporized vaporizer vaporizes varisized vassalize vectorize velarized velarizes verbalize vernalize victimize virilized virilizes visualize vitalized vitalizer vitalizes vizaments vizarding vizcachas vizierate vizierial vizirates vizirship vizorless vizzieing vocalized vocalizer vocalizes volcanize volumized volumizer volumizes vowelized vowelizes vulcanize vulgarize vuvuzelas zanamivir 8 Letter Words activize avianize cervezas civilize czarevna divinize izvestia jarovize kuvaszok mazeltov mitzvahs mitzvoth novelize oversize overzeal rivalize shvartze shvitzed shvitzes sovkhozy tzarevna unvizard vajazzle valorize vaporize velarize virilize vitalize vizament vizarded vizcacha vizirate vizirial vizoring vocalize volumize vowelize vuvuzela zelkovas zemstvos zyzzyvas 7 Letter Words avizing avyzing cerveza evzones mitzvah schvitz sovkhoz vizards viziers vizored vizslas vizying vizzied vizzies zelkova zemstva zemstvo zouaves zyzzyva 6 Letter Words avized avizes avyzed avyzes cezves evzone kuvasz shvitz suivez vezirs vizard vizied vizier vizies vizirs vizors vizsla vizzie vozhds zouave — — ADVERTISEMENT — — 5 Letter Words avize avyze cezve vezir vizir vizor vozhd 4 Letter Words vizy You may also find this curated "lists of words" page useful (which is based on most frequent searches by the users) : Word List Enter up to 15 letters, use ? as wildcards --> ✘ Clear Find Words Advanced Options Select Dictionary TWL06 (US, Canada and Thailand) SOWPODS (UK and Others) Enable (Words with Friends) Starts with Ends with Must include --> Recent Articles Single Player Indoor Games 5 Tips to Help You in Wordscapes Board Games Quiz Scrabble Quiz Scrabble vs. Scrabble Deluxe Tips to Win at Uno Wordscapes Rules and Tips and Tricks Top 10 Puzzle Games for Android Tips & Tricks for Spelling Bee Bananagrams vs. Scrabble Most Popular Word Games of 2022 Scrabble vs Crossword Scrabble vs Scrabble Junior Four Letter Scrabble Words Board Games to Play with Family and Friends Scrabble vs. Lexulous Word Games for Kids Benefits of Playing Scrabble from Childhood Guide To Win Boggle With Friends Words With Friends - Rules & Tips Scrabble vs Words With Friends Tips & Tricks to Win at Scrabble Word Lists Two Letter Words Three Letter Words Vowel Only Words Words Without Vowels Words with Q but no U Words with Q but no E Words with Z and X Words with Z and Q Words with Z and V Words with Z and J Words with Q and X Words with Q and j Words ending in W Words ending in Z Words ending in Q Words ending in J Words ending in V Words ending in C words that end with QUE words that end with ER words that end with TY words that end with UN words that end with XE words that end with XI words that end with AY words that end with NET words that end with WARE words that end with ZIG 3 letter words with X 3 letter words with Z 3 letter words with E 3 letter words with U 3 letter words with Q 3 letter words with V 3 letter words with J 4 letter words starting with A 4 letter words starting with E 4 letter words starting with O 4 letter words starting with R 5 letter words starting with C 5 letter words starting with S 5 letter words starting with A 5 letter words ending with X 5 letter words ending with C See Full List Disclaimer SCRABBLE® is a registered trademark. All intellectual property rights in and to the game are owned in the U.S.A and Canada by Hasbro Inc., and throughout the rest of the world by J.W. Spear & Sons Limited of Maidenhead, Berkshire, England, a subsidiary of Mattel Inc. Mattel and Spear are not affiliated with Hasbro. Words with Friends is a trademark of Zynga with Friends. ScrabbleWordFinder.org is not affiliated with SCRABBLE®, Mattel Inc, Hasbro Inc, Zynga with Friends or Zynga Inc in any way. This site is for entertainment purposes only. © 2013-2025 ScrabbleWordFinder.org | Privacy Policy About Feedback Advertise Contact | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#advised-permissions | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=et | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname=" | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#request-permissions-at-runtime | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=is | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="ry | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=en_GB | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname=" | 2026-01-13T09:30:03 |
https://wordunscrambler.me/free-games-like-wordle | Free Games Like Wordle ☰ MENU × Home Check Dictionary Word Descrambler Word Scramble Wordfeud Helper Word Descrambler Anagram Solver Random Word Generator Wordle Solver Quordle Solver Sitemap About Free Games Like Wordle What other way to kick off the start of 2022 than a new word game popping up and becoming everyone’s new obsession? Because that’s exactly what Wordle did! Created by Josh Wardle for his wife, Wordle featured a daily puzzle that everyone could solve. It quickly became a daily routine for some since the site only allowed one puzzle per day. But what about those who just couldn’t get enough? Lucky for you, there are tons of other word games just like Wordle for you to try out! Wordle dupes Sure, Wordle is fun and all, but sometimes, that excitement and challenge of solving the daily wordle of the day can be short-lived and you’re left wanting for more. If you’re looking for games that try to emulate Wordle, these dupes will give you the same vibes but a different taste. So the next time you find yourself restless and waiting for the next day to come, give these five games a try and play ‘til you drop! 1. Wheeldle Courtesy: Foodle As the ultimate Wordle dupe, Wheeldle allows players to play as much as they want without any limit at all. It features an attractive retro aesthetic with fun sound bits that play for every click that you make. And if you’re someone who likes to challenge themselves by keeping track of your score, then you’ll definitely enjoy the score and streak tracker built into the game. Win as many games as you can, build your streak, and play to your heart’s content in this never-ending Wordle puzzle! 2. Themed Dupes Courtesy: Worldle Wanna see how much knowledge you have in a particular area? Then these next three games are for you! Come and test your knowledge in these three themed Wordle dupes: Geography, Songs, and Flags. a. Worldle From the name itself, it should need no introduction because it’s time to guess some countries! In Worldle, players are shown a simple image of a country and it’s up to you to guess which one it is. Instead of showing which letters you got right, it’ll tell you how far off you are from the correct answer based on the country you initially put. Let’s say that the country to guess is Hungary and you had put down Bosnia and Herzegovina, the system will then tell you that you are 388km from the target country and it’s towards the North. Not only do you need to know a ton of countries but also knowledge of geography and directions is a definite must! You could also make a few tweaks to the game to cater to your needs. If you’d like a little bit of a challenge, then you could opt to have the country outline erased, or even rotated to add some difficulty! Keeping track of your streak is also a breeze since the website has its own icon that you could press to show your win history. b. Heardle Think you know a lot of songs? Well, think again, because in this version of Wordle, it’s up to you to guess what song the website is playing. It’ll start off with just a couple of seconds from the song, then will continuously lengthen the more wrong answers you get. Don’t let your guard down though because some of these songs are quite unknown – but hey, what better way to discover new tunes to add to your Spotify playlist? Play Heardle Here c. Flagle Unlimited Flagle Unlimited is like Worldle but not quite. Just as the name suggests, Flagle shows you different flags from different countries and it’s your task to figure out where it’s from. But don’t be fooled by it though, because the flag isn’t shown outright. Only parts of it get revealed for each wrong answer you get. Flagle Unlimited Any geography lover out there would certainly love this game because of how challenging it is – that is, of course, if you’re a certified flag expert. But even then, it’s nice to see where you stand from time to time. 3. Quordle What if solving one word at a time is too elementary for you? Then how about solving four words at a time? Now that should get you going! Daily Quordle The challenge with Quordle is that you have to guess all four words at the same time, and the letters you input will apply to all words. You have a total of nine tries to get all of them right and strategy is key. You need to figure out how you’re going to juggle managing these puzzles at once. You can also try our quordle solver if you need any hints during play. 4. Dordle Was four words a little too much for you? Then perhaps solving two words at the same time is more your speed. Play Dordle It has the same mechanics as Quordle but is made for those who think that four words at a time are a bit much. There are two modes for you to choose from: Daily Dordle and Free Dordle. The former one is just like Wordle wherein you’ll have two words of the day that you have to accomplish and it’ll reset for the next day. Meanwhile, in the latter, you get to play to your heart’s content. 5. Queerdle For all the queer queens, kings, and allies out there, there’s a game that’s specially curated for you! Introducing the exciting world of Queerdle, where you can test just how much queer lingo you know. All accepted words in the system must be queer related or else it won’t be considered valid. Time to test your queer knowledge and see if you’ve got what it takes! Queerdle Word games Enough with the Wordle dupes, it’s time to explore some word games that have the same feel but different gameplay. After all, having a bit of variety in your life could be good! Here are other word games worth checking out! Hangman This should need no introduction because the ever-popular game of Hangman remains a favorite pastime today! But for those who are not in the know, Hangman is a fun and easy game to play by yourselves or with a friend. The gist is simple: there is a word that you must guess, but for every wrong letter that you input, a contraption keeps getting added ‘till you’ve placed enough wrong letters to actually “hang the man” (which of course is just a doodle and not a real man). There are tons of websites to choose from with each having a special quirk: timed challenges, themed ones, or even unlimited play! If you’re with a friend, why not play among yourselves offline? All you really need is a pen, paper, and some imagination. Text Twist 2 Jumbled letters are always a fun way to challenge yourself. With over 600,000 words in the English language, who knows how many word combinations you can create with a few seemingly random letters – you’d be shocked! It’s a great game for those who want to hone their quick-thinking skills and be entertained while at it. Wordscapes What word game list would be complete without Wordscapes? You all know it, and you all love it! As a combination between anagrams and crosswords, it’s like getting the best of both worlds when it comes to these word puzzles. Include the fact that there are just so many features, levels, challenges, and more that make your daily gaming experience exciting. 4 Pics 1 Word Anyone who grew up during the mid-2000s would definitely know that 4 Pics 1 Word was the OG word game. For those who need a refresher, all you really need to do is combine the four photos shown before you and deduce what word it might be referring to. It’s simple, yet fun and very addicting. No matter your style, there will always be a word game out there that’s just for you! What are your interests? Math? Geography? Or maybe even queer lingo? Whatever it is, the creative minds of people have made it possible for you to enjoy a fun game of “Wordle” but with a special tweak. So what are you waiting for? Explore all of these fun Wordle dupes! Thank you for reading so far. If you enjoyed reading this article you may want to check out these articles as well - Wordle tips for beginners Popular Word games in 2024 Card games to play Wordle alternatives Scrabble Quiz Published on 21 Nov 2024 Author: Marinel Other pages : Jumble Solver Word Finder Words with Friends Cheat Word Solver Wordle Solver © 2025 WordUnscrambler.me Word Scramble Word Descrambler Sitemap About Contact Privacy | 2026-01-13T09:30:03 |
https://scrabblewordfinder.org/dictionary/offs | offs - Dictionary Checker - Scrabble Word Finder --> Dictionary Two Letter Words Word List Words with Friends Finder Scrabble Dictionary Check words in Scrabble Dictionary and make sure it's an official scrabble word. Enter the word you want to check Check Dictionary Yes Valid in these dictionaries TWL/NWL (Scrabble US / Canada / Thailand) SOWPODS/CSW (Scrabble UK / International) ENABLE (Words with Friends) Meaning of offs No definition found! Look up here instead. Use this Scrabble® dictionary checker tool to find out whether a word is acceptable in your scrabble dictionary. When you enter a word and click on Check Dictionary button, it simply tells you whether it's valid or not, and list out the dictionaries in case of valid word. Additionally, you can also read the meaning if you want to know more about a particular word. Share on Twitter Facebook Back to Scrabble Word Finder Enter up to 15 letters, use ? as wildcards --> ✘ Clear Find Words Advanced Options Select Dictionary TWL06 (US, Canada and Thailand) SOWPODS (UK and Others) Enable (Words with Friends) Starts with Ends with Must include --> Recent Articles Single Player Indoor Games 5 Tips to Help You in Wordscapes Board Games Quiz Scrabble Quiz Scrabble vs. Scrabble Deluxe Tips to Win at Uno Wordscapes Rules and Tips and Tricks Top 10 Puzzle Games for Android Tips & Tricks for Spelling Bee Bananagrams vs. Scrabble Most Popular Word Games of 2022 Scrabble vs Crossword Scrabble vs Scrabble Junior Four Letter Scrabble Words Board Games to Play with Family and Friends Scrabble vs. Lexulous Word Games for Kids Benefits of Playing Scrabble from Childhood Guide To Win Boggle With Friends Words With Friends - Rules & Tips Scrabble vs Words With Friends Tips & Tricks to Win at Scrabble Word Lists Two Letter Words Three Letter Words Vowel Only Words Words Without Vowels Words with Q but no U Words with Q but no E Words with Z and X Words with Z and Q Words with Z and V Words with Z and J Words with Q and X Words with Q and j Words ending in W Words ending in Z Words ending in Q Words ending in J Words ending in V Words ending in C words that end with QUE words that end with ER words that end with TY words that end with UN words that end with XE words that end with XI words that end with AY words that end with NET words that end with WARE words that end with ZIG 3 letter words with X 3 letter words with Z 3 letter words with E 3 letter words with U 3 letter words with Q 3 letter words with V 3 letter words with J 4 letter words starting with A 4 letter words starting with E 4 letter words starting with O 4 letter words starting with R 5 letter words starting with C 5 letter words starting with S 5 letter words starting with A 5 letter words ending with X 5 letter words ending with C See Full List Disclaimer SCRABBLE® is a registered trademark. All intellectual property rights in and to the game are owned in the U.S.A and Canada by Hasbro Inc., and throughout the rest of the world by J.W. Spear & Sons Limited of Maidenhead, Berkshire, England, a subsidiary of Mattel Inc. Mattel and Spear are not affiliated with Hasbro. Words with Friends is a trademark of Zynga with Friends. ScrabbleWordFinder.org is not affiliated with SCRABBLE®, Mattel Inc, Hasbro Inc, Zynga with Friends or Zynga Inc in any way. This site is for entertainment purposes only. © 2013-2025 ScrabbleWordFinder.org | Privacy Policy About Feedback Advertise Contact | 2026-01-13T09:30:03 |
https://scrabblewordfinder.org/dictionary/occy | occy - Dictionary Checker - Scrabble Word Finder --> Dictionary Two Letter Words Word List Words with Friends Finder Scrabble Dictionary Check words in Scrabble Dictionary and make sure it's an official scrabble word. Enter the word you want to check Check Dictionary Yes Valid in these dictionaries SOWPODS/CSW (Scrabble UK / International) Meaning of occy No definition found! Look up here instead. Use this Scrabble® dictionary checker tool to find out whether a word is acceptable in your scrabble dictionary. When you enter a word and click on Check Dictionary button, it simply tells you whether it's valid or not, and list out the dictionaries in case of valid word. Additionally, you can also read the meaning if you want to know more about a particular word. Share on Twitter Facebook Back to Scrabble Word Finder Enter up to 15 letters, use ? as wildcards --> ✘ Clear Find Words Advanced Options Select Dictionary TWL06 (US, Canada and Thailand) SOWPODS (UK and Others) Enable (Words with Friends) Starts with Ends with Must include --> Recent Articles Single Player Indoor Games 5 Tips to Help You in Wordscapes Board Games Quiz Scrabble Quiz Scrabble vs. Scrabble Deluxe Tips to Win at Uno Wordscapes Rules and Tips and Tricks Top 10 Puzzle Games for Android Tips & Tricks for Spelling Bee Bananagrams vs. Scrabble Most Popular Word Games of 2022 Scrabble vs Crossword Scrabble vs Scrabble Junior Four Letter Scrabble Words Board Games to Play with Family and Friends Scrabble vs. Lexulous Word Games for Kids Benefits of Playing Scrabble from Childhood Guide To Win Boggle With Friends Words With Friends - Rules & Tips Scrabble vs Words With Friends Tips & Tricks to Win at Scrabble Word Lists Two Letter Words Three Letter Words Vowel Only Words Words Without Vowels Words with Q but no U Words with Q but no E Words with Z and X Words with Z and Q Words with Z and V Words with Z and J Words with Q and X Words with Q and j Words ending in W Words ending in Z Words ending in Q Words ending in J Words ending in V Words ending in C words that end with QUE words that end with ER words that end with TY words that end with UN words that end with XE words that end with XI words that end with AY words that end with NET words that end with WARE words that end with ZIG 3 letter words with X 3 letter words with Z 3 letter words with E 3 letter words with U 3 letter words with Q 3 letter words with V 3 letter words with J 4 letter words starting with A 4 letter words starting with E 4 letter words starting with O 4 letter words starting with R 5 letter words starting with C 5 letter words starting with S 5 letter words starting with A 5 letter words ending with X 5 letter words ending with C See Full List Disclaimer SCRABBLE® is a registered trademark. All intellectual property rights in and to the game are owned in the U.S.A and Canada by Hasbro Inc., and throughout the rest of the world by J.W. Spear & Sons Limited of Maidenhead, Berkshire, England, a subsidiary of Mattel Inc. Mattel and Spear are not affiliated with Hasbro. Words with Friends is a trademark of Zynga with Friends. ScrabbleWordFinder.org is not affiliated with SCRABBLE®, Mattel Inc, Hasbro Inc, Zynga with Friends or Zynga Inc in any way. This site is for entertainment purposes only. © 2013-2025 ScrabbleWordFinder.org | Privacy Policy About Feedback Advertise Contact | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#avoid-unnecessary-permissions | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=ca | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-Str | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_EC | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <div class="VfPpkd-xl07Ob-XxIAqe VfPpkd-xl07Ob q6oraf P77izf B6Yvkd" jscontroller="ywOR5c" jsaction="keydown:I481le;JIbuQc:j697N(rymPhb);XVaHYd:c9v4Fb(rymPhb);Oyo5M:b5fzT(rymPhb);DimkCe:TQSy7b(rymPhb);m0LGSd:fAWgXe(rymPhb);WAiFGd:k | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#commands | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#add-information-about-permissions-to-your-extensions-amo-page | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=gu | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity | 2026-01-13T09:30:03 |
https://www.mozilla.org/nl/products/ | Mozilla’s producten - Mozilla — Mozilla Help ons uw Mozilla-ervaring te verbeteren Naast cookies die nodig zijn om deze website te laten functioneren, vragen we uw toestemming voor het plaatsen van enkele aanvullende cookies om uw surfbehoeften beter te begrijpen en uw ervaring te verbeteren. Wees gerust – we waarderen uw privacy. Alle aanvullende cookies accepteren Alle aanvullende cookies weigeren Cookie-instellingen Menu Firefox-browsers Producten Menu Producten sluiten Mozilla VPN Mozilla Monitor Firefox Relay MDN Plus Thunderbird Alle producten Over ons Menu Over ons sluiten Onze missie Over Mozilla Het Mozilla-manifest Meewerken Blog Ons werk Mozilla Foundation Mozilla.ai Mozilla Ventures Mozilla-advertenties Mozilla Builders Nieuwe Mozilla-producten Producten Firefox is nog maar het begin. De productfamilie van Mozilla is ontworpen om u online veiliger en slimmer te houden. Firefox Download de browser die automatisch meer dan 2000 datatrackers blokkeert. Verbeterde bescherming tegen volgen is standaard in elke Firefox-browser. Firefox downloaden Firefox wordt niet meer ondersteund op Windows 8.1 en lager. Download Firefox ESR (Extended Support Release) om Firefox te gebruiken. 64-bits Firefox ESR downloaden 32-bits Firefox ESR downloaden Download een andere build Firefox wordt niet meer ondersteund op macOS 10.14 en lager. Download Firefox ESR (Extended Support Release) om Firefox te gebruiken. Firefox ESR downloaden Firefox-privacyverklaring Firefox Focus Uw speciale privacybrowser met automatische advertentieblokkering en beveiliging tegen volgen. Firefox Relay Bescherm uw echte e-mailadres om uw Postvak IN te beschermen. Firefox Relay verkrijgen Mozilla Monitor Bekijk of uw persoonlijke gegevens zijn gelekt bij een bedrijfslek en meld u aan voor toekomstige waarschuwingen. Controleren op datalekken Mozilla VPN Surf, stream en voer werk uit op servers in meer dan 30 landen, voor een veilige internetverbinding met een nieuw perspectief. Mozilla VPN downloaden MDN Plus Hulpbronnen voor ontwikkelaars, door ontwikkelaars. Ondersteun MDN en maak het van uzelf met collecties, notificaties en speelterreinen. MDN ondersteunen Thunderbird Benader al uw e-mail, agenda’s en contacten in één snelle app. Filter en organiseer ze zoals u dat wilt. Thunderbird downloaden Eén aanmelding. Alles Mozilla. Firefox Mozilla VPN Relay Monitor Voer uw e-mailadres in om een Mozilla-account aan te maken. E-mailadres Doorgaan Door verder te gaan, gaat u akkoord met de Servicevoorwaarden en Privacyverklaring . Hebt u al een account? Aanmelden of meer info over meedoen met Mozilla Voeg vertrouwen toe aan uw advertentieaankoop. Meer info over Mozilla Ads Bedrijf Leiderschap Perscentrum Banen Contact Ondersteuning Producthulp Een bug melden Mozilla localiseren Beveiliging Ontwikkelaars Developer Edition Enterprise Hulpmiddelen MDN Firefox-uitgaveopmerkingen @Mozilla volgen Bluesky (@mozilla.org) Instagram (@mozilla) LinkedIn (@mozilla) TikTok (@mozilla) Spotify (@mozilla) @Firefox volgen Bluesky (@firefox.com) Instagram (@firefox) YouTube (@firefoxchannel) TikTok (@firefox) Doneren Alle talen Taal عربي Беларуская Bosanski Català Maya Kaqchikel Čeština Cymraeg Dansk Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Frysk Galego Avañe'ẽ हिन्दी (भारत) Hrvatski Hornjoserbsce magyar Հայերեն Interlingua Bahasa Indonesia Italiano 日本語 ქართული Taqbaylit Қазақ 한국어 ພາສາລາວ Melayu Norsk bokmål Nederlands Norsk nynorsk ਪੰਜਾਬੀ (ਭਾਰਤ) Polski Português (do Brasil) Português (Europeu) rumantsch Română Русский Scots සිංහල slovenčina سرائیکی Slovenščina Shqip Српски Svenska Тоҷикӣ ไทย Türkçe Українська اُردو Tiếng Việt 中文 (简体) 正體中文 (繁體) Bezoek de moedermaatschappij zonder winstoogmerk van de Mozilla Corporation , Mozilla Foundation . Onderdelen van deze inhoud zijn ©1998–2026 door individuele medewerkers van mozilla.org. Inhoud is beschikbaar onder een Creative Commons-licentie . Privacyverklaring voor website Cookies Juridisch Richtlijnen voor deelname aan de gemeenschap Over deze website | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_CR | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname=" | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#determine-your-consent-flow | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=am | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="rymPh | 2026-01-13T09:30:03 |
https://extensionworkshop.com/extension-basics/#specifying-data-types | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:03 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_MX | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54 | 2026-01-13T09:30:03 |
https://addons.mozilla.org/el/firefox/user/15472597/ | Προφίλ του χρήστη Χρήστης Firefox 15472597 – Πρόσθετα για το Firefox (el) Για να χρησιμοποιήσετε αυτά τα πρόσθετα, θα χρειαστεί να κάνετε λήψη του Firefox . Απόρριψη σημείωσης Πρόσθετα προγράμματος περιήγησης Firefox Επεκτάσεις Θέματα Περισσότερα… για το Firefox Λεξικά και πακέτα γλωσσών Άλλα προγράμματα περιήγησης Πρόσθετα για Android Σύνδεση Αναζήτηση Αναζήτηση Χρήστης Firefox 15472597 Αναφορά χρήστη Επεκτάσεις από Χρήστης Firefox 15472597 Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Θέματα από Χρήστης Firefox 15472597 Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Δεν υπάρχουν ακόμη βαθμολογίες Μετάβαση στην αρχική σελίδα της Mozilla Πρόσθετα Σχετικά Blog προσθέτων Firefox Εργαστήριο επεκτάσεων Κέντρο προγραμματιστών Πολιτικές προγραμματιστών Blog κοινότητας Φόρουμ Αναφορά σφάλματος Οδηγίες κριτικής Προγράμματα περιήγησης Desktop Mobile Enterprise Προϊόντα Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Απόρρητο Cookie Νομικά Εκτός από τα μέρη όπου αναφέρεται διαφορετικά, το περιεχόμενο του ιστοτόπου υπόκειται στην άδεια Creative Commons Attribution Share-Alike License v3.0 ή τυχόν νεότερες εκδόσεις. Αλλαγή γλώσσας Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T09:30:04 |
https://extensionworkshop.com/extension-basics/#onboarding | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:04 |
https://extensionworkshop.com/extension-basics/#taxonomy | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:04 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=es_VE | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymP | 2026-01-13T09:30:04 |
https://extensionworkshop.com/documentation/develop/user-experience-best-practices/ | User experience best practices | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug 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 to start is Jakob Nielsen’s Usability Heuristics . We recommend all developers use Nielsen’s Heuristics as a checklist when building and testing your user experience (UX). Here we lay out the six steps to creating specific Firefox and extension UX features so that you can build an extension that entices, informs, delights, and retains your users. In addition to the steps described here, your extension should follow Add-on Policies , which include being transparent with users about user security, privacy and control. Contents 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again 1. Keep it focused The best Firefox extensions provide users with a new feature or capability that addresses a need—be it smarter, more efficient, or more enjoyable browsing. Ideally, your extension saves the user time, money, or frustration. An extension is best when it is centered around one main use case, and addresses that use case as well as possible for the target audience: It should add one function or set of closely related functions to the browser, modify a function of the browser, or modify web pages. Determine if you have achieved this by asking whether you can easily communicate the features and purpose of the extension in three (short) sentences or less. 2. Give users what they need, where they need it Choosing the right way, or combination of ways, to make your extension's functionality available to the user can have a significant effect on usability. Asking a few simple questions about your extension’s functionality can quickly guide you to the right choices: Does my extension work on most websites and web pages? If your extension provides the user with features they can use on almost every website or page, give the user access to it from a toolbar button using the browser action . This might include providing access to your image editor or opening a page from your website. Where you have several features you want to give the user access, you can add a popup to the button (a popup appears like a door hanger that opens when the user selects the browser action button). Does my extension work for only some web sites and pages? If your extension offers a feature for a type of web page or specific domains, give the user access to it from an address bar button using a page action . This might include providing access to your RSS reader on pages with RSS feeds or providing an extended feature to pages on your website. Where you have several features you want to give the user access, you can add a popup to the button. Does my extension need to show information or offer actions in parallel with web pages? If your extension includes information or actions that a user would want immediate access to while viewing any web page, use a sidebar . This might include notes the user can make about a page’s content or a feature offering various font substitutions to improve readability. Does my extension offer functionality specific to page content or other browser features? If your extension offers features the user might want to access in context, add them to an appropriate context menu . This might include offering access to an image editor on the image context menu or offering extended copy features on the context menu for selected page content. Does my extension have settings the user can adjust? If your extension enables the user to change and save settings that affect the behavior of the extension, use an options page to provide a standard Preferences link to settings from the Add-on Manager. In the Windows operating system, the “Preferences” button is labeled “Options”. Does my extension need to gather a lot of information or display content in addition to the current tabs? Where your extension needs to gather or display significant amounts of information (more than is suitable for an alert or would benefit from additional formatting) use bundled web pages to deliver forms and similar content. Does my extension try to help the user find web pages or content? If your extension includes functionality to locate web pages or content, such as offering a site-specific search, use address bar suggestions to deliver those recommendations. Does my extension offer tools for developers? If you are providing tools for developers, add them to the Firefox developer tools using developer tools panels . 3. Keep the user informed Ensuring the user knows what will happen, is happening, and has happened in your extension is an essential part of building trust and ensuring a happy user. Tell the user what will happen, before it happens Users should understand what will happen when they click a button: Do provide a meaningful, descriptive button label. Do provide tooltips that describe the action that the button will perform. Do not put the name of the extension alone in the tooltip, unless it is descriptive of the action the button will perform. Do not use the tooltip for any other types of information such as elaborate statistics about your extension. Keep the tooltip content simple and focused on what will happen when the user clicks the button. If something is really important and the user may not be aware, notify them If your extension has completed a critical, long running background task, use the operating system’s native notifications to update the user when the task completes. This can be useful where the user may not be focusing on the extension or the browser, when the task finishes. However, use notifications sparingly. If it is sufficient for the user to discover that a process has completed when they return to the browser or extension, do not use notifications. Use browserAction badges sparingly To inform users of important events, you can add a badge over the toolbar icon of a browserAction . Do so sparingly—do not use badges to provide regular or persistent status updates. When it comes to coloring a badge , using one of four colors for notifications of different severity is recommended: Casual: blue Success: green Warning: yellow Error: red Use of Firefox colors is suggested, for more details see Firefox Colors . However, for purposes of Chrome and Opera compatibility, we support any color you wish to use. 4. Be Firefoxy in look and feel Your users have chosen Firefox for a reason, possibly several reasons, so match your extension’s look and feel to that of Firefox using the Firefox Photon Design System . Following Photon will ensure that your extension integrates with the Firefox experience and will make it easier for people to use. 5. Great onboarding experience The first few minutes after someone installs your extension can be critical to its success. Your new user needs to know where to start and how to use the features of your browser extension. Provide an onboarding page that gives users the essential information they need to get started. Keep the information brief and to the point, and provide simple configuration options if applicable. For more information on creating an onboarding page, see Best practices for onboarding, upboarding, and offboarding users . In case the user skips the onboarding page, ensure that your extension is ready to be used immediately after installation. It should be optimized for its main use case, and work as expected for most users without the need for customization. 6. Test, test, and then test again Testing is a vital part of creating an outstanding UX for your extension. There are two key aspects of testing your UX: Test across devices and platforms to ensure your extension works and performs well in as many places as possible. This includes considering factors such as the user’s screen size and resolution—just because your extension looks good and is easy to use on your desktop monitor does not mean it looks as good and works as well on a smaller laptop screen, or, indeed, vice versa. Test with as many users as possible. Do not assume that you know your audience, as people’s backgrounds and experience can make a huge difference to how they interact with your extension. So, allow for user testing as part of your extension’s development. Testing tips: In AMO you have the option to identify your extension as "experimental" or publish a beta or other non-final release . If you flag your extension as experimental it is listed in AMO, but with a lower profile. When the extension is ready for a wider audience, you can turn off the experimental flag in AMO. If you have a published extension, you can use the Development channel to offer an alpha or beta version for testing. You will need to direct your testers to the Development Channel of your extension’s listing or let your testers know the link to use to install your extension. When you are happy with your update, you can publish it as the new release version of your extension. If you want to distribute your extension to users outside AMO, you can find the instructions for doing so, and the installation instructions you need to provide users, in the article on the manual installation of add-ons . Remember that, if you're testing updates to an extension distributed through AMO, you need to send users updated versions of your extension as you make improvements. Use the Responsive Design Mode to test your extension for its behavior on other screen sizes and device types. Creating a great extension is an iterative process. While we’ve laid out the six steps here, you’ll likely revisit these as you learn what works and what doesn’t through user feedback, testing, and time. Tags: add-ons extensions guide ui ux Contributors: MeridelW andrewtruongmoz rebloor hellosct1 wbamberg 0711kps atsay bryanyou Last update: rebloor Mar 18, 2019 Up Next Develop Differences between desktop and Android extensions Develop User experience guidelines for mobile extensions Develop Developing extensions for Firefox for Android Documentation Topics Develop Publish Manage Enterprise Themes Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:04 |
https://nuxt.com/blog/v4#whats-new | Announcing Nuxt 4.0 · Nuxt Blog v4.2.2 Docs Modules Templates Resources Enterprise Blog Search… k 59.3K Blog Announcing Nuxt 4.0 Release · July 15, 2025 Announcing Nuxt 4.0 Nuxt 4.0 is here! A thoughtful evolution focused on developer experience, with better project organization, smarter data fetching, and improved type safety. Daniel Roe @danielroe.dev Nuxt 4.0 is here! 🎉 After a year of real-world testing, we're excited to announce the official release of Nuxt 4. This is a stability-focused major release, introducing a few thoughtful breaking changes in order to improve development experience. If you've been following along, you'll recognize many of these features and changes — and if you're new to them, we hope you'll welcome them. 🔥 What's new? Nuxt 4 is all about making your development experience smoother: Cleaner project organization with the new app/ directory structure Smarter data fetching - we've taken the opportunity to address some inconsistencies and improve performance with the data layer Better TypeScript support with project-based separation between the different contexts in your project - app code, server code, shared/ folder, and configuration Faster CLI and development with adoption of internal sockets and a faster CLI Why these features in particular? Mostly because these kind of improvements have required making changes that are technically breaking. In general, we aim for a hype-free approach to releases. Rather than save up features for a big release, we've been shipping improvements in Nuxt 3 minor releases. We've also spent a lot of time figuring out how to implement these changes in a backwards-compatible way, and I hope that means that most Nuxt 3 projects can upgrade with a minimum of effort. I'd advise reading through the upgrade guide before you start, to understand what areas of your app might be affected. 🗂️ New project structure The biggest visible change is how projects are organized. Your application code now lives in an app/ directory by default: my-nuxt-app/ ├─ app/ │ ├─ assets/ │ ├─ components/ │ ├─ composables/ │ ├─ layouts/ │ ├─ middleware/ │ ├─ pages/ │ ├─ plugins/ │ ├─ utils/ │ ├─ app.vue │ ├─ app.config.ts │ └─ error.vue ├─ content/ ├─ public/ ├─ shared/ ├─ server/ └─ nuxt.config.ts This helps keep your code separate from node_modules/ and .git/ , which makes file watchers faster (especially on Windows and Linux). It also gives your IDE better context about whether you're working with client or server code. Don't want to migrate? That's totally fine! Nuxt will detect your existing structure and keep working exactly as before. 🎨 Updated UI templates Nuxt’s starter templates have an all new look, with improved accessibility, default titles, and template polish ( #27843 ). 🔄 Smarter data fetching We've made useAsyncData and useFetch work better. Multiple components using the same key now share their data automatically. There's also automatic cleanup when components unmount, and you can use reactive keys to refetch data when needed. Plus, we've given you more control over when cached data gets used. Some of these features have already been made available in Nuxt v3 minor releases, because we've been rolling this out gradually. Nuxt v4 brings different defaults, and we expect to continue to work on this data layer in the days to come. 🔧 Better TypeScript experience Nuxt now creates separate TypeScript projects for your app code, server code, shared/ folder, and builder code. This should mean better autocompletion, more accurate type inference and fewer confusing errors when you're working in different contexts. With Nuxt 4, you will only need one tsconfig.json file in your project root! This is probably the single issue that is most likely to cause surprises when upgrading, but it should also make your TypeScript experience much smoother in the long run. Please report any issues you encounter. 🙏 ⚡ Faster CLI and development In parallel with the release of v4, we've been working on speeding up @nuxt/cli . Faster cold starts - Development server startup is noticeably faster Node.js compile cache - Automatic reuse of the v8 compile cache Native file watching - Uses fs.watch APIs for fewer system resources Socket-based communication - The CLI and Vite dev server now communicate via internal sockets instead of network ports, reducing overhead — particularly on Windows These improvements combined can make a really noticeable difference in your day-to-day development experience, and we have more planned. 🚀 How to upgrade Although any major release brings breaking changes, one of our main aims for this release is to ensure that the upgrade path is as smooth as possible. Most of the breaking changes have been testable with a compatibility flag for over a year. Most projects should upgrade smoothly, but there are a few things to be aware of: Nuxt 2 compatibility has been removed from @nuxt/kit . (This will particularly affect module authors.) Some legacy utilities and deprecated features have been cleaned up. The new TypeScript setup might surface some type issues that were hidden before. A few modules might need further updates for full Nuxt 4 compatibility. Don't worry though — for most breaking changes, there are configuration options to revert to the old behavior while you adjust. 1. Update Nuxt Our recommendation for upgrading is to run: npx nuxt upgrade --dedupe This will deduplicate your lockfile as well, and help ensure that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem. 2. Optional: use migration tools We’ve also partnered with Codemod to automate many, though not all, migration steps: npm yarn pnpm bun npx codemod@latest nuxt/4/migration-recipe yarn dlx codemod@latest nuxt/4/migration-recipe pnpm dlx codemod@latest nuxt/4/migration-recipe bun x codemod@latest nuxt/4/migration-recipe 3. Test and adjust Run your tests, check that everything builds correctly, and fix any issues that come up. The upgrade guide has detailed migration steps for specific scenarios. We'd recommend reading through it in full before starting your upgrade, to understand what areas of your app might be affected. 🗺️ What's next? We're planning quick patch releases to address any issues that come up. Nuxt 3 will continue to receive maintenance updates (both bug fixes and backports of features from Nuxt 4) until the end of January 2026, so there's no rush if you need time to migrate. Looking ahead, we plan to release Nuxt 5 on the sooner side, which will bring Nitro v3 and h3 v2 for even better performance, as well as adopting the Vite Environment API for an improved (and faster!) development experience. And there's a lot more in the works too! And, quite apart from major releases, we have a lot of exciting features planned to make their way into Nuxt 3.x and 4.x release branches, including support for SSR streaming ( #4753 ), a first-party accessibility module ( #23255 ), built-in fetch caching strategies ( #26017 ), more strongly typed fetch calls (landing in Nitro v3), dynamic route discovery ( #32196 ), multi-app support ( #21635 ) and more. ❤️ Thank you This release is credit to so many people, particularly those who have been testing v4 compatibility mode over the past year. I'm really grateful — thank you for all your help! Happy coding with Nuxt 4! 🚀 📑 Full release notes Read the full release notes of Nuxt v4.0.0 . A huge thank you to everyone who's been a part of this release. ❤️ ← Back to blog Copy URL Copy URL Nuxt on LinkedIn Nuxt on Bluesky Nuxt on X Table of Contents Table of Contents 🔥 What's new? 🗂️ New project structure 🔄 Smarter data fetching 🔧 Better TypeScript experience ⚡ Faster CLI and development 🚀 How to upgrade 1. Update Nuxt 2. Optional: use migration tools 3. Test and adjust 🗺️ What's next? ❤️ Thank you 📑 Full release notes Links Edit this article Star on GitHub Become a Sponsor Nuxt on Discord Nuxt on Bluesky Nuxt on X Nuxt on GitHub Community Nuxters Team Design Kit Explore Modules Templates Showcase Enterprise Support Agencies Sponsors Subscribe to our newsletter Stay updated on new releases and features, guides, and community updates. Subscribe Nuxt on X Nuxt on BlueSky Nuxt on LinkedIn Nuxt on Discord Nuxt on GitHub Copyright © 2016-2026 Nuxt - MIT License | 2026-01-13T09:30:04 |
https://www.progress.com/infrastructure-management | --> AI-Powered IT Infrastructure Management Solutions | Progress Put AI to work for your business with Progress Agentic RAG Learn More skip navigation AI Progress Agentic RAG New AI Product Overview AI Thought Leadership Solutions Artificial Intelligence Develop the responsible AI-powered applications and experiences you need, deploy them where and how you want and manage it all with Progress AI-driven products. Data Platform Accelerate data, AI and analytics projects, manage costs and deliver enterprise growth with the Progress Data Platform. Digital Experience Real solutions for your organization and end users built with best of breed offerings, configured to be flexible and scalable with you. Infrastructure Management Progress infrastructure management products speed the time and reduce the effort required to manage your network, applications and underlying infrastructure. Federal Solutions Software products and services for federal government, defense and public sector. Products Data Platform Agentic RAG New MarkLogic Semaphore OpenEdge DataDirect Corticon Digital Experience Sitefinity Telerik Kendo UI Corticon DataDirect ShareFile Podio MOVEit DevOps Chef Infrastructure Management & Operations Flowmon Kemp LoadMaster WhatsUp Gold UI/UX Tools Telerik Kendo UI Fiddler Test Studio Document collaboration and File Transfer ShareFile Automate MFT New MOVEit WS_FTP View All Products Support Support By Product Customer Portal Download Center Support Guide Community Services Resources Resources Resource Center Papers Webinars Videos Documentation Knowledge Base Blogs Events Customer Stories FAQs Training Instructor-Led Training On-Demand Training Partners Find a Partner Become a Partner Partner Login Deal Registration New Company About Progress Company Overview Leadership Corporate Development Corporate Social Responsibility Federal Solutions News & Info Investor Relations Press Releases Trust Center Careers Offices Site search Search User SupportLink PartnerLink Telerik Your Account 1-800-477-6473 Ready to Talk? Site search GO Progress Infrastructure Management Progress AI-powered software helps businesses establish a resilient cloud and IT infrastructure ready for today’s turbulent cyber-threat landscape. Our AIOps solutions help customers better manage and secure the infrastructure for their mission-critical applications. See why so many IT and Security professionals rely on Progress. Explore Foundation Products Resilient Infrastructure = Superior Application Experiences Our infrastructure management products speed the time and reduce the effort required to manage your network, applications and underlying infrastructure. Optimize Your Network with Full Visibility and Decisive Intelligence Get a holistic view of your network and quickly identify the root cause of any network degradation or failure that can hamper your application initiatives. Deliver Highly Available, Highly Secure Applications Provide maximum reliability and availability via load-balanced application workloads with built-in Zero Trust capabilities needed for modern, multi-cloud apps. Protect Against Modern Cyber Threats Using the Power of AI Reduce risk and improve resilience across your on-premises, hybrid and cloud environments with intelligent network visibility and security monitoring. Automate Infrastructure Configuration & Compliance Efforts Help meet exacting compliance requirements needed to address cyber threats relating to misconfiguration for your on-premises and multi-cloud environments. Download INFRA Brochure PDF, 15.1MB Progress Infrastructure Portfolio Our infrastructure product portfolio frees you up to focus on your mission while helping to effectively manage your network, applications and underlying infrastructure. Progress Kemp LoadMaster Progress Flowmon Progress WhatsUp Gold Progress Chef Deliver Highly Available, Highly Secure Applications Load balance and harden the environments of your essential applications and services across your hybrid cloud ecosystem. Learn More About Kemp LoadMaster Visualize Traffic and Secure the Network Gain network observability and improve your network defenses with AI-driven threat detection and response. Learn More About Flowmon Monitor Up/Down Status, Availability and Performance At-a-Glance Find and fix network problems fast by monitoring your entire IT infrastructure. Learn More About WhatsUp Gold Support Infrastructure Automation, Security and Compliance Configure, deploy and manage your application infrastructure across platforms at scale. Learn More About Chef Gartner Peer Reviews 5.0 Full network visibility, AI-Driven security & performance metrics for network as well as Load balance scheduler. It's ease to use, complete customer support, easy to integrate & implement and frequent usable. Read the full review 5.0 Our clients get insight into the health, configuration, and compliance of their system in a single platform. Also, since everything is in code, the ways to customize Chef cookbooks, profiles, and to tailor policy for each node are limitless. Review collected by and hosted on G2.com.” Read the full review 5.0 Keep your company on its toes with Progress WhatsUp Gold. Its functionality to monitor networks, making it the best choice in the market, the technical support is able to solve any concerns during installation, the interface is intuitive, provides customization tool adapted without any inconvenience to our devices. Read the full review 5.0 We've used Kemp products for years. They are solid platforms that do exactly what we require them to do in load-balancing our traffic. They just work. Their support team is also top-notch. The very few configuration issues we've run into, they've been able to take care of the same day. Read the full review Related Resources Webinar What’s New in Progress Flowmon 13? Video Solution Tutorial - NPMD: Investigations Blog Post Progress Software Unveils Subsidiary to Fast-Track AI-Driven Digital Transformation Blog Post Threat Detection and Response: How Flowmon Detected an Attack in Real Time Technology Data Platform Digital Experience DevOps Infrastructure Management & Operations UI/UX Tools Document Collaboration and File Transfer Quick Links Products Trials Services Partners Support Events Blogs About Company Customer Stories Awards Investor relations Offices Careers 40 Years of Progress Contact us Global Headquarters, USA 1-800-477-6473 or find a local contact Copyright © 2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved. Progress and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings. All rights in any other trademarks contained herein are reserved by their respective owners and their inclusion does not imply an endorsement, affiliation, or sponsorship as between Progress and the respective owners. Terms of Use Privacy Center Trust Center Trademarks License Agreements Code of Conduct Do Not Sell or Share My Personal Information Powered by Progress Sitefinity | 2026-01-13T09:30:04 |
https://www.linkedin.com/products/commentsold/ | CommentSold | LinkedIn Skip to main content LinkedIn CommentSold in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in CommentSold Commenting Systems by CommentSold See who's skilled in this Add as skill Learn more Report this product About Save Time & Scale. Automate your comment selling and invoicing. Boost engagement and sales with our streamlined multi-channel platform. 30-Day Free Trial. Media Products media viewer No more previous content No more next content Similar products Coral Coral Commenting Systems IntenseDebate IntenseDebate Commenting Systems ProjectHuddle ProjectHuddle Commenting Systems Superflow Superflow Commenting Systems Thrive Comments Thrive Comments Commenting Systems Hyvor Talk Hyvor Talk Commenting Systems Sign in to see more Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language | 2026-01-13T09:30:04 |
https://www.refrens.com/en-ae/free-invoice-templates | Free Invoice Templates | Online Invoice Templates | Refrens Login Signup Login Signup Become a Refrens Partner Learn More Login Signup Free Invoice Templates Professional Invoice Template to give a modern look to your invoice. Customize. Download PDF. Print. Email Invoices for FREE. Create Invoice for Free Activate Premium for Free Our Users Rate Refrens ⭐ 4.8/5 based on 11700+ Ratings Create Your Invoice in Less than 2 Minutes 1 Add Invoice Details 2 Design & Share (optional) Add your business, client and item details Change template, color, fonts, download pdf, print etc Create Your First Invoice 1 Add Invoice Details 2 Design & Share (optional) Add your business, client and item details Change template, color, fonts, download pdf, print etc Choose the Best Invoice Template For Your Business (You can choose the template in last step after making the invoice) Professional Invoice Template LetterHead Invoice Template TAX Invoice Template Print-Friendly Invoice Template Business Invoice Template Modern Invoice Template VAT Invoice Template Consulting Invoice Template (Available in 250 colors) Create Online Invoices for FREE Create Invoice Now Features Customizable Invoice Add and edit multiple fields and columns such as an address, contact information, product description. Brand Your Template Select an invoice template that suits your business nature and stand out from your competitors. Customize your invoice format by adding a logo and signature. Use Magic Color Choose the most suitable color from your logo and make the invoice look professional. Multiple fonts supported. Special Purpose Templates Invoice templates like professional invoice template, letterhead format, business invoice format, print-friendly templates. All for free. No Watermark. Manage and Send Invoices Manage all your invoices in one place. Download as PDF, Print, Email, or share via WhatsApp. Easy Access Anywhere Easy to use dashboard for mobile and desktop. Get email alerts in real-time. Frequently Asked Questions (FAQ) Can I add a logo to the invoice template? Yes, you can add a logo to the invoice and can also change the color of your invoice template, matching your logo. Can I add more details to the invoice template? Yes, Refrens invoice templates are customizable. You can add additional fields or columns like shipping details, discounts, additional charges, custom fields for both client and product or service line item. Can I save invoices as a PDF Format? Yes. You can easily download it in PDF format or can click on the print option and can save as PDF. How many documents can I make on Refrens? You can create 15 documents on Refrens for absolutely free. Once the threshold of 15 documents is reached, you can buy our premium plans to keep continue creating the documents. Do I have to create a account to use a free invoice template? Creating an account on Refrens is necessary to use the free invoice templates. After signing up, you can access all the invoices in one place which makes managing your business invoices a lot easier. Create Invoice For Free Can I create and send invoices from my mobile device? Yes, you can create and send invoices from your mobile device. With Refrens, you can easily generate invoices using a UAE invoice template right from your phone. This allows you to manage your billing process on the go, without the need for a computer. Our platform offers a variety of invoice templates tailored to different needs, including the correct tax invoice format for businesses in the UAE. You can customize each invoice template UAE to include all the essential details like your client’s information, services provided, and the total amount. Once the invoice is ready, you can send it directly to your clients via email or whatsapp. This makes it easy to keep your invoicing process smooth and efficient, no matter where you are. With Refrens, you also get real-time tracking for each invoice, so you’ll know when your client has viewed it and when payment is due. Refrens allows you to handle all your invoicing needs directly from your mobile device. It’s quick, easy, and reliable, ensuring that you stay on top of your business, even when you’re on the move. Can I Send Invoices to International Clients Using a UAE Invoice Template with Multi-Currency Support? Yes, you can send invoices to international clients using a UAE invoice template that supports multiple currencies. As businesses expand globally, sending invoices across borders becomes a regular part of operations.Our template with multi-currency options ensures you can cater to clients in different countries while keeping your invoices professional and compliant with UAE regulations. Why You Need a UAE Invoice Template with Multi-Currency Support Using an invoice template UAE with multi-currency support simplifies your invoicing process when dealing with clients outside the UAE. It allows you to bill clients in their preferred currency, reducing confusion and ensuring smoother payments. This feature is particularly helpful for businesses that work with international clients regularly. One of the key benefits of using such a template is that it automatically calculates the correct exchange rate and displays the final amount clearly in preferred currency. This ensures that your clients understand exactly what they owe, which can help speed up the payment process. Benefits of Using a UAE Invoice Template with Multi-Currency 1. Simplifies International Transactions: By including a multi-currency option, you make it easier for your clients to pay you in their local currency, which can reduce delays in processing payments. 2. Ensures Tax Compliance: Using a UAE-compliant invoice format ensures that your invoices meet all legal and tax requirements in the UAE. This is crucial, especially when you’re dealing with clients from different countries. 3. Professional Presentation: A well-organized UAE invoice template with multi-currency support makes your business appear more professional, which helps build trust with your clients. Make Invoicing Easier with Refrens At Refrens, we provide customizable invoice templates that cater to businesses in the UAE, making it easy to send invoices both locally and internationally. Our templates are designed to support multiple currencies, helping you handle cross-border transactions smoothly. Whether you're invoicing in USD, EUR, or any other currency, our templates are built to manage the exchange rates and ensure compliance with UAE tax regulations. Create Invoice For Free Why Use Refrens Free Invoice Templates? Having a small business or service agency or being a freelancer, it is very hard, time-consuming, and cumbersome when you try to create invoices through Excel, Word, Google Sheets, or Docs. Some people use Word or Google Docs to simplify the invoicing process because you can create quite good-looking invoices from MS Word. But it is always harder to calculate taxes like VAT, or any other additional charges associated with it. Whereas some use Excel or Google spreadsheets to create one and there is a huge benefit to using Excel as it can easily calculate taxes like VAT with its automatic formulas. You can also make your own formula to create a predefined invoice. However, Excel also has a huge drawback of professionalism. Invoices created through Excel don't look attractive and lack professionalism even when using professional invoice templates. When you are running a business, not only you have to create invoices but also have to maintain the client data, invoices, different reports like VAT. For example: To manage all the invoices in one place. To manage all your client data. To create and maintain VAT report. You want to know which invoices are paid, unpaid or partially paid. You want to know your earnings for the month or year. When it comes to the above tasks both Word and Excel fail. So, having proper invoicing software for your business not only helps to create invoices but also helps in managing all the data in one place without searching for each file. At Refrens, you can manage all your invoices, expenses, your client, and payment details in one place. Refrens is not only for invoicing it is a complete tool to manage your finances. You can create a professionally designed invoice using the UAE invoice generator with multiple invoice templates . Other than this, Refrens also provides the following tools like Quotation generator Proforma invoice template Purchase order generator Quotation Template Word Delivery Note Template How to Make An Invoice Using Invoice Template? Using the Refrens platform it is easy to create invoices instantly. When creating an invoice you must add these crucial elements, without these elements no invoice can be completed. Following is the simple and easiest way to create an invoice using the free invoice template . Step 1: Add Information to Invoice Invoice Header - It is always a good practice to add the word “INVOICE” at the top of the invoice as invoice title. The invoice header is the section where you add the invoice number, invoice issue date, and due date. In addition, you also need to add other reference numbers like the PO number, quotation number. In this section, you also get the option of adding the business logo which is a good way to promote your brand. Billed By Section - As the name suggests, in this section, you add all the information about your business that includes business name if you own any business or if you are a freelancer, you can use your name instead of the business name. Moreover, you can add your email, mobile number, address, city. Billed To Section - Same as billed by section, you need to add the information about the buyer or client who is buying or paying for the products or services from you. Shipping Details - This section is only useful for those who sell tangible products. You need to add shipping details like address, city, state, Pin Code, challan number, date, and transport. If you are offering any service or digital products, you can avoid this section. Item Section - Here you add the product or service name, description, images, quantity, rate, discount, and VAT. You can also add custom columns to add more detail to the product or service. Terms & Conditions - You need to add terms and conditions of invoice and payments. Bottom Section - At the bottom of the invoice, you can add notes, attachments, and signatures as well. Congrats your invoice is created now. The next step helps you to get paid faster. Step 2: Customize Invoice Using Invoice Templates You can easily customize your invoice by choosing the best invoice template that fits your business. Change the template as per the requirements and change the color of the template that you love. You can also make use of Magic colors that helps you to select the best color from your business logo. In addition, you can also change the fonts of the invoice heading and the best part is all these features are completely free. FREE INVOICE TEMPLATE WITH NO COST. Promote Your Brand With Invoice Template Invoices are important materials of any business and are used to convey the information sold by any business. Invoices are the only material that helps the business to get paid faster. If any invoice is professionally built and conveys the information in an easy way, the chances of getting paid on time increase by 40%. Refrens clearly knows the importance of invoices that are beautifully designed. So, Refrens developed multiple invoice templates for different kinds of businesses. Whether you are a professional, business owner, freelancer, graphic designer or you love the color blue, there is a free invoice template for you. You can create an invoice that suits your business using templates and send them to your clients for free. In addition, every uniquely designed invoice template has the option to add a business or personal logo that makes your client aware of your brand. Moreover, Refrens never promotes or add Refrens’ name or logo to any of your invoices. Easy Printable Invoice Templates Maybe you still follow the traditional method of creating invoices and printing them. No worry, Refrens got you covered as well. All the online invoice templates are printable and we have a printer-friendly template as well. You can easily print with one click. If you need any specific template for printing purposes, you can use our print-friendly invoice template and can customize it as per the need. Not just print, you save your invoice in PDF format as well and can also send via Email or WhatsApp. As Refrens is a completely online invoicing platform, all the invoices get saved here. You can access all the invoices anytime and anywhere. Having this benefit, you can easily create the invoice from anywhere and can be saved to print for later purposes. Free Invoice Template Highlights Invoicing is a pushover using the Refrens invoice template. Beautifully designed invoice templates , streamline your invoice cycle process. Knowing this our Refrens team has developed multiple invoice formats to create an invoice that fits your business needs. Here are some of the highlights of the Refrens invoice format . Fully Customized Invoice. Multiple Invoice Colors (Available in 24 colors) Magic Color using Company or Personal Logo. Professionally Designed Invoice. All invoices are compact and print-friendly. Changes fonts of the invoice heading. Includes all the essential elements of the invoice. Auto calculates discounts, additional charges, VAT. Add attachments and signature. Special Purpose Invoice Format Refrens team is very well aware of the importance of the invoice template for freelancers and small businesses. Knowing this fact, our team developed multiple templates according to the business run by small business owners and freelancers. Professional Invoice Template - Designed for professionals like chemists, lawyers, designers, freelancers, content writers, etc. Letterhead Template - Not just big corporates but businesses of all sizes can make their custom letterhead to communicate between two parties. Refrens team build letterhead for all types of businesses. Business Invoice Template - If the letterhead does not attract you, here is the template that is definitely made for all business purposes. Modern Invoice Template - Specially designed for startups and newbie freelancers which helps to accept the payment faster. Print-friendly Invoice Template - Black and white template with compact and easy to print invoice. VAT Invoice Template - Specially designed for traders and import & exports businesses and for the businesses registered under VAT. Quote Templates Excel Quotation Templates Consulting Invoice Templates Consultants are those who advise or guide the organization or business or an individual to achieve the goal using the expertise. Consultants vary for different industries such as IT consultants, software consultants, freelance consultants, legal consultants, business consultants, etc. After the completion of the project, these consultants bill their clients using a [ UAE consultant invoice template ]. For different industries, different templates can be used. Most of the consultants charge per hour rate. If any consultant is VAT registered then they can ask for a VAT invoice as well. Which Invoice Template Format Should A UAE Business Use? As mentioned earlier, some individuals and businesses prefer Word or Google Docs format for their business, then there are those who prefer Excel or Google Sheets to create invoice templates . Both these methods are best in their own way, but still, these two methods fail when you look at the different pictures of the invoice. Using Word or Excel, you would never know the status of the invoices such as paid, unpaid, part- paid or How much are your earnings at the end of the week or month or even at the end of the year. It is always time-consuming to keep track of all your invoices in a particular folder. The best option is to use tools that are specially designed for making invoices. You can use the tool to minimize your invoice-creating effort. You can get the best of both Word and Excel in one tool. Auto calculation as well as amazing templates for invoices . Use Refrens invoice template format to accomplish your invoicing cycle seamlessly and make your invoicing statement simple. Invoice Templates in PDF Format Be it today or tomorrow, creating an invoice for your client will always remain an important aspect of your business. But the process of creating invoices has drastically changed. Earlier, business owners used to write invoices and paper mail to their clients. But today it isn't an effective way to save time and get paid faster. Using a ready-made invoice template for your business, not only saves your time but also helps you to get paid faster than usual. No matter what business you are into, creating and sending invoices to your clients using Refrens invoice PDF templates . Download your invoice in PDF format, print, or email to your client directly. Simply create an invoice, select the free invoice template and color that fits your business. Email your client and get paid faster. Benefits of Using Refrens Free Invoice Template Format Create 20 Invoices. No Hidden Charges. Professional Layout Format. Fully Customizable Invoice. Save client data to reuse in the future which avoids retyping of client information again and again. Generate VAT report. Collect Payment Online. Status of the invoices like paid, unpaid, partly paid. Bulk upload Invoices and Expenses. Manage and download all payment reports. Add multiple team members or users. Send Invoices through Email, WhatsApp, or through link sharing. Free Customer Support to resolve your queries. Is Invoice Template Free in UAE? Yes, all the templates available on Refrens for generating an invoice, quotation, proforma invoice, or purchase order are 100% free. Not just templates, all the customization available like color change, magic color from logo uploaded, font heading, etc are also free of cost. All you have to add is to add information about your company, client details, detailed information about the product or service you offer, and select the invoice template you love. If you are creating a proforma invoice then you can use a proforma invoice template to customize the invoice. After creating the invoice, you can email the client, download the invoice as a PDF or you can print the same. The invoice gets saved and you can access it from anywhere and anytime. There is no limit to creating invoices on Refrens. Not just invoice generation, you can also create recurring invoices, accept payments, organize invoices, client management and VAT reports. Create Invoice For Free 🌐 Global 🇦🇺 Australia 🇧🇭 Bahrain 🇨🇦 Canada 🇭🇰 Hong Kong 🇮🇳 India 🇮🇩 Indonesia 🇰🇪 Kenya 🇰🇼 Kuwait 🇲🇾 Malaysia 🇵🇰 Pakistan 🇶🇦 Qatar 🇿🇦 South Africa 🇱🇰 Sri Lanka 🇦🇪 UAE 🇬🇧 United Kingdom 🇺🇸 USA 🇻🇳 Vietnam Company About Us | Contact Us | Blog | Privacy Policy | Terms of Service | Help and Support Products Accounting Software | Invoice Generator | Quotation Generator | Purchase Order Templates | Proforma Invoice Templates | Online Quotation Templates | Word Quotation Templates | Invoice Templates | Quotation Software | Free Invoicing Software | Hire A Freelancer Helpful Links FAQ | Refrens Android App | Refrens iOS App Made with and in Bengaluru. +91 9104043036 +91 9104043036 care@refrens.com Refrens Internet Pvt. Ltd. | All Rights Reserved This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. | 2026-01-13T09:30:04 |
https://extensionworkshop.com/extension-basics/#upboarding | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:04 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=de | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="rymPhb | 2026-01-13T09:30:04 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1w9T5h4SFIM-3PmCUHPrcl-t1jb-segjkGEn4zpU67vWNthY4RTydxRIQCc8JgYepeq7aDBl0HymBVlYUfdIe8WqUBykPipderUBMoNtpsjiPXCEhOEQ5bn0VuDhbm4hgo8yTdvk4h2QfH | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:30:04 |
https://www.mozilla.org/it/products/ | Prodotti Mozilla - Mozilla — Mozilla Aiutaci a migliorare la tua esperienza con Mozilla Oltre ai cookie necessari per il funzionamento di questo sito, vorremmo il tuo consenso per impostare alcuni cookie aggiuntivi che ci aiutano a comprendere meglio le tue esigenze di navigazione e migliorare la tua esperienza. Non preoccuparti: abbiamo sempre a cuore la tua privacy. Accetta tutti i cookie aggiuntivi Rifiuta tutti i cookie aggiuntivi Impostazioni cookie Menu Browser Firefox Prodotti Chiudi il menu Prodotti Mozilla VPN Mozilla Monitor Firefox Relay MDN Plus Thunderbird Tutti i prodotti Chi siamo Chiudi il menu Chi siamo La nostra missione Informazioni su Mozilla Il manifesto Mozilla Collabora con noi Blog Il nostro lavoro Mozilla Foundation Mozilla.ai Mozilla Ventures Mozilla Advertising Mozilla Builders Nuovi prodotti Mozilla Prodotti Firefox è solo l’inizio. La famiglia di prodotti Mozilla è progettata per offrirti un’esperienza online più sicura e consapevole. Firefox Ottieni il browser che blocca automaticamente più di 2000 elementi in grado di tracciare i tuoi dati. La protezione antitracciamento avanzata è inclusa in ogni browser Firefox. Scarica Firefox Firefox non è più supportato su Windows 8.1 e versioni precedenti. Scarica Firefox ESR (Extended Support Release) per continuare a utilizzare Firefox. Scarica Firefox ESR a 64 bit Scarica Firefox ESR a 32 bit Scarica un’altra versione Firefox non è più supportato su macOS 10.14 e versioni precedenti. Scarica Firefox ESR (Extended Support Release) per continuare a utilizzare Firefox. Scarica Firefox ESR Informativa sulla privacy di Firefox Firefox Focus Il browser dedicato alla privacy con protezione automatica dal tracciamento e blocco degli annunci pubblicitari. Firefox Relay Proteggi il tuo indirizzo email reale per un maggior controllo della tua casella di posta Ottieni Firefox Relay Mozilla Monitor Controlla se le tue informazioni personali sono state compromesse in una violazione di dati aziendali e registrati per ricevere avvisi in futuro. Cerca nelle violazioni Mozilla VPN Naviga, guarda contenuti in streaming e lavora appoggiandoti a server in più di 30 Paesi. Osserva il mondo da una nuova prospettiva con una connessione internet sempre sicura. Ottieni Mozilla VPN MDN Plus Risorse per sviluppatori, da sviluppatori. Sostieni MDN e personalizzalo con raccolte, notifiche e aree per provare il tuo codice. Sostieni MDN Thunderbird Accedi a email, calendari e contatti, tutto in un’app veloce. Filtrali e organizzali come preferisci. Scarica Thunderbird Un solo accesso. Tutto Mozilla. Firefox Mozilla VPN Relay Monitor Inserisci la tua email per accedere a account Mozilla. Indirizzo email Continua Proseguendo, confermi di accettare le nostre condizioni di utilizzo del servizio e l’ informativa sulla privacy . Hai già un account? Accedi o scopri di più su come entrare in Mozilla. Aggiungi fiducia al tuo investimento pubblicitario. Ulteriori informazioni su Mozilla Ads Azienda Gruppo dirigente Sala stampa Opportunità di lavoro Contatti Supporto Supporto per i prodotti Segnala un errore Localizzazione in Mozilla Sicurezza Sviluppatori Developer Edition Aziende Strumenti MDN Note di versione di Firefox Segui @Mozilla Bluesky (@mozilla.org) Instagram (@mozilla) LinkedIn (@mozilla) TikTok (@mozilla) Spotify (@mozilla) Segui @Firefox Bluesky (@firefox.com) Instagram (@firefox) YouTube (@firefoxchannel) TikTok (@firefox) Fai una donazione Tutte le lingue Lingua عربي Беларуская Bosanski Català Maya Kaqchikel Čeština Cymraeg Dansk Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Frysk Galego Avañe'ẽ हिन्दी (भारत) Hrvatski Hornjoserbsce magyar Հայերեն Interlingua Bahasa Indonesia Italiano 日本語 ქართული Taqbaylit Қазақ 한국어 ພາສາລາວ Melayu Norsk bokmål Nederlands Norsk nynorsk ਪੰਜਾਬੀ (ਭਾਰਤ) Polski Português (do Brasil) Português (Europeu) rumantsch Română Русский Scots සිංහල slovenčina سرائیکی Slovenščina Shqip Српски Svenska Тоҷикӣ ไทย Türkçe Українська اُردو Tiếng Việt 中文 (简体) 正體中文 (繁體) Visita Mozilla Foundation , l’organizzazione senza fini di lucro che controlla Mozilla Corporation . Parte di questi contenuti sono ©1998–2026 di singoli collaboratori di mozilla.org. I contenuti sono disponibili secondo la licenza Creative Commons . Informativa sulla privacy del sito Cookie Note legali Linee guida per la partecipazione alla comunità Informazioni su questo sito | 2026-01-13T09:30:04 |
https://wordunscrambler.me/7-letter-words-starting-with/e | 7 Letter Words Starting With E - WordUnscrambler.me ☰ MENU × Home Check Dictionary Word Descrambler Word Scramble Wordfeud Helper Word Descrambler Anagram Solver Random Word Generator Wordle Solver Quordle Solver Sitemap About 7 Letter Words Starting with E List of all seven letter words starting with the prefix E . --> Here is the complete list of all seven-letter words, starting with the prefix E. You can play these words in Scrabble, Words with Friends, Word Cookies, Wordfeud , Wordscapes, Jumble or so. In Scrabble , you can try to get bingo (bonus of 50 points) by playing all the seven letter tiles. While it’s not easy to learn all these words, you vastly improve your chances of winning just by learning a few words from these word lists. You can also check out some relevant word lists such as : Six letter words starting with E Five letter words starting with E Four letter words starting with E Three letter words Two letter words 7 Letter Words eagerer eagerly eaglets eagling eanling earache earball earbash earbobs earbuds earcons earding eardrop eardrum earflap earfuls earings earlaps earldom earless earlier earlies earlike earlobe earlock earmark earmuff earners earnest earning earpick earplug earring earshot earthed earthen earthly earwigs earworm easeful easeled easiest eastern easters easting eastlin easying eatable eatages eatches eaterie eatings ebauche ebayers ebaying ebbless ebbtide ebonics ebonies ebonise ebonist ebonite ebonize ebriate ebriety ebriose ecartes ecboles ecbolic eccrine ecdemic ecdyses ecdysis ecdyson echappe echards echelle echelon echidna echinus echiums echoers echoing echoise echoism echoist echoize eclairs eclipse eclogue eclosed ecloses ecocide ecology economy econuts ecorche ecotage ecotone ecotour ecotype ecstasy ectases ectasia ectasis ectatic ecthyma ectopia ectopic ectozoa ectypal ectypes ecuelle ecuries eczemas edacity edaphic eddying edemata edental edgiest edgings edibles edictal edifice edified edifier edifies editing edition editors editrix educate educing eductor eeching eelfare eeliest eellike eelpout eelworm eeriest eevning effable effaced effacer effaces effects effeirs effendi effered efferes effings efforce efforts effrays effulge effused effuses eftsoon egalite egality egences egested eggcups egghead eggiest egglers eggless eggmass eggnogs eggwash egoisms egoists egoless egotise egotism egotist egotize eidetic eidolic eidolon eighths eightvo eikones eilding einkorn eiracks eirenic eisells eiswein ejected ejector ekistic ekpwele elanced elances elanets elapids elapine elapsed elapses elastic elastin elaters elating elation elative elbowed elchees elderly eldings eldress eldrich elected electee elector electro elegant elegiac elegies elegise elegist elegits elegize element elenchi elenchs elevate elevens elevons elfhood elfland elflike elflock eliches elicits eliding elision elitism elitist elixirs ellagic ellipse ellwand elmiest elmwood elocute elodeas elogies elogist elogium eloigns eloined eloiner elopers eloping elopses elshins eltchis eluants eluates eluders eluding eluents elusion elusive elusory eluting elution elutors eluvial eluvium elysian elytral elytron elytrum emacsen emailed emanant emanate embaces embails embaled embales emballs embalms embanks embargo embarks embased embases embassy embaste embathe embayed embayld emblaze emblema emblems emblics embloom embogue emboils embolic embolus embosks embosom embound embowed embowel embower emboxed emboxes embrace embraid embrave embread embroil embrown embrued embrues embrute embryon embryos embused embuses emended emender emerald emerged emerges emeried emeries emerita emeriti emerods emeroid emersed emetics emetine emetins emeutes emicant emicate emigres eminent emirate emitted emitter emmewed emmoved emmoves emodins emonges emongst emoters emoting emotion emotive emoving empaire empaled empaler empales empanel empared empares emparls emparts empathy empayre empeach emperce emperor empight empires empiric emplace emplane employe employs emplume emporia empower empress emprise emprize emptied emptier empties emptily empting emptins emption empusas empuses empyema emulate emulged emulges emuling emulous emulsin emulsor emunged emunges emuring enabled enabler enables enacted enactor enamels enamine enamors enamour enarmed enation encaged encages encalms encamps encased encases encaved encaves enchafe enchain enchant encharm enchase encheer encinal encinas enclasp enclave enclose encloud encoded encoder encodes encomia encored encores encraty encrust encrypt encysts endarch endarts endears endemic enderon endewed endgame endings endiron endited endites endives endlang endleaf endless endlong endmost endnote endogen endopod endorse endowed endower endozoa endplay endrins endship enduing endured endurer endures enduros endways endwise endyses endysis enemata enemies energic energid enerved enerves enewing enfaced enfaces enfants enfelon enfeoff enfever enfiled enfired enfires enfixed enfixes enflame enflesh enfolds enforce enforms enframe enfreed enfrees enfroze engaged engagee engager engages engaols engilds engined enginer engines engirds english englobe engloom engluts engobes engored engores engorge engrace engraff engraft engrail engrain engrams engrasp engrave engross enguard engulfs engulph enhalos enhance enigmas enisled enisles enjambs enjoins enjoyed enjoyer enlaced enlaces enlards enlarge enlight enlinks enlists enliven enlocks enmewed enmoved enmoves ennages enneads ennoble ennuied ennuyed ennuyee enolase enology enomoty enoughs enounce enplane enprint enquire enquiry enraced enraces enraged enrages enrange enranks enrheum enrings enriven enrobed enrober enrobes enrolls enroots enrough enround enseals enseams ensears enserfs ensewed enshell ensigns ensiled ensiles enskied enskies enskyed enslave ensnare ensnarl ensouls enstamp ensteep enstyle ensuing ensured ensurer ensures ensweep enswept entails entamed entames entases entasia entasis entayle entente enteral entered enterer enteric enteron entetee enthral enthuse enticed enticer entices entires entitle entoils entombs entomic entopic entotic entozoa entrail entrain entrall entrant entraps entreat entrees entries entrism entrist entrold entropy entrust entwine entwist enuring envault envelop envenom enviers envious environ enviros envying enwalls enwheel enwinds enwombs enwound enwraps enzians enzoned enzones enzymes enzymic eobiont eoliths eonisms eosines eosinic epacrid epacris epagoge eparchs eparchy epatant epaules epaulet epaxial epazote epeeist epeiras epeiric epeirid eperdue epergne ephebes ephebic epheboi ephebos ephebus ephedra ephelis ephoral epiblem epiboly epicarp epicede epicene epicier epicism epicist epicure epiderm epidote epigeal epigean epigeic epigene epigone epigoni epigons epigram epigyny epilate epilogs epimere epimers epinaoi epinaos episcia episode episome epistle epitaph epitaxy epithem epithet epitome epitope epizoan epizoic epizoon epochal epochas eponyms eponymy epopees epoxide epoxied epoxies epoxyed epsilon epuisee epulary epurate epyllia equable equably equaled equally equants equated equates equator equerry equinal equines equinia equinox equipes equites erasers erasing erasion erasure erathem erbiums erected erecter erectly erector erelong eremite eremuri erepsin erethic ergates ergodic ergotic eriachs ericoid eringos erinite eristic erlangs erlking ermelin ermined ermines erodent eroding erodium erosely erosion erosive erotema eroteme erotica erotics erotise erotism erotize errable errancy errands errants erratas erratic erratum errhine errings eructed erudite erupted eryngos escalop escaped escapee escaper escapes escarps eschars escheat eschews escolar escorts escoted escribe escrocs escroll escrols escrows escuage escudos eserine esloins esloyne esotery espadas espanol esparto espials espiers espouse esprits espying esquire essayed essayer essence essives essoins essoyne estated estates esteems esthete estival estoile estover estrade estrays estreat estrepe estrich estrins estriol estrone estrous estrual estrums estuary etacism etaerio etagere etalage etalons etamine etamins etatism etatist etchant etchers etching eternal etesian ethanal ethanes ethanol ethenes etheric ethical ethinyl ethions ethiops ethmoid ethnics ethoses ethoxyl ethylic ethynes ethynyl etiolin etoiles etourdi etrenne etriers ettling etymons eucaine eucains euchred euchres euclase eucrite eudemon eugarie eugenia eugenic eugenol euglena eulogia eumongs eumungs eunuchs euouaes eupepsy euphons euphony euphory euphroe euploid eupneas eupneic eupnoea eurekas euripus euryoky eustacy eustasy eustele eustyle eutaxia eutexia eutropy evacuee evaders evading evangel evanish evasion evasive evejars eveners evenest evening evented eventer evernet everted evertor evicted evictee evictor evident evilest eviller evinced evinces evirate evitate eviting evocate evokers evoking evolues evolute evolved evolver evolves evovaes evulsed evulses evzones exabyte exactas exacted exacter exactly exactor exacums exalted exalter examens examine example exapted exarate exarchs exarchy excambs exceeds excepts excerpt excheat excided excides excimer exciple excised excises excited exciter excites exciton excitor exclaim exclave exclude excreta excrete excudit excurse excusal excused excuser excuses execute exedrae exeemed exegete exeming exempla exemple exempts exergue exerted exhaled exhales exhaust exhedra exhibit exhorts exhumed exhumer exhumes exigent exilers exilian exiling exility existed exiting exocarp exoderm exodist exogamy exogens exomion exonyms exopods exordia exosmic exotica exotics exotism expands expanse expects expends expense experts expiate expired expirer expires explain explant explode exploit explore exports exposal exposed exposer exposes exposit expound express expugns expulse expunct expunge expurge exscind exsects exserts extatic extends extense extents externe externs extinct extines extirps extolls extorts extract extrait extreat extrema extreme extrude exudate exuding exulted exurban exurbia exuviae exuvial exuvium eyalets eyasses eyeable eyeball eyebank eyebars eyebath eyebeam eyebolt eyebrow eyecups eyefold eyefuls eyehole eyehook eyelash eyeless eyelets eyeliad eyelids eyelift eyelike eyeshot eyesome eyesore eyespot eyewash eyewear eyewink eyliads ADVERTISEMENT Note : Feel free to send us any feedback or report on the new look of our site. Thank you for visiting our website. Other pages : Jumble Solver Word Finder Words with Friends Cheat Word Solver Wordle Solver © 2025 WordUnscrambler.me Word Scramble Word Descrambler Sitemap About Contact Privacy | 2026-01-13T09:30:04 |
https://nuxt.com/blog/v3-11#performance-improvements | Nuxt 3.11 · Nuxt Blog v4.2.2 Docs Modules Templates Resources Enterprise Blog Search… k 59.3K Blog Nuxt 3.11 Release · March 16, 2024 Nuxt 3.11 Nuxt 3.11 is out - with better logging, preview mode, server pages and much more! Daniel Roe @danielroe.dev This is possibly the last minor release before Nuxt v4, and so we've packed it full of features and improvements we hope will delight you! ✨ 🪵 Better logging When developing a Nuxt application and using console.log in your application, you may have noticed that these logs are not displayed in your browser console when refreshing the page (during server-side rendering). This can be frustrating, as it makes it difficult to debug your application. This is now a thing of the past! Now, when you have server logs associated with a request, they will be bundled up and passed to the client and displayed in your browser console. Asynchronous context is used to track and associate these logs with the request that triggered them. ( #25936 ). For example, this code: pages/index.vue < script setup > console . log ( ' Log from index page ' ) const { data } = await useAsyncData ( () => { console . log ( ' Log inside useAsyncData ' ) return $fetch ( ' /api/test ' ) } ) </ script > will now log to your browser console when you refresh the page: Log from index page [ ssr ] Log inside useAsyncData at pages/index.vue 👉 We also plan to support streaming of subsequent logs to the Nuxt DevTools in future. We've also added a dev:ssr-logs hook (both in Nuxt and Nitro) which is called on server and client, allowing you to handle them yourself if you want to. If you encounter any issues with this, it is possible to disable them - or prevent them from logging to your browser console. nuxt.config.ts export default defineNuxtConfig ( { features : { devLogs : false // or 'silent' to allow you to handle yourself with `dev:ssr-logs` hook }, } ) 🎨 Preview mode A new usePreviewMode composable aims to make it simple to use preview mode in your Nuxt app. plugins/test.client.ts const { enabled , state } = usePreviewMode () When preview mode is enabled, all your data fetching composables, like useAsyncData and useFetch will rerun, meaning any cached data in the payload will be bypassed. Read more in Docs > API > Composables > Use Preview Mode . 💰 Cache-busting payloads We now automatically cache-bust your payloads if you haven't disabled Nuxt's app manifest, meaning you shouldn't be stuck with outdated data after a deployment ( #26068 ). 👮♂️ Middleware routeRules It's now possible to define middleware for page paths within the Vue app part of your application (that is, not your Nitro routes) ( #25841 ). nuxt.config.ts export default defineNuxtConfig ( { routeRules : { ' /admin/** ' : { // or appMiddleware: 'auth' appMiddleware : [ ' auth ' ] }, ' /admin/login ' : { // You can 'turn off' middleware that would otherwise run for a page appMiddleware : { auth : false } }, }, } ) Read more in Docs > Guide > Concepts > Rendering#route Rules . ⌫ New clear data fetching utility Now, useAsyncData and useFetch expose a clear utility. This is a function that can be used to set data to undefined, set error to null , set pending to false , set status to idle , and mark any currently pending requests as cancelled. ( #26259 ) < script setup lang = " ts " > const { data , clear } = await useFetch ( ' /api/test ' ) const route = useRoute () watch ( () => route . path , ( path ) => { if ( path === ' / ' ) clear () } ) </ script > Read more in Docs > Getting Started > Data Fetching . 🕳️ New #teleports target Nuxt now includes a new <div id="teleports"></div> element in your app within your <body> tag. It supports server-side teleports, meaning you can do this safely on the server: app.vue < template > < Teleport to = " #teleports " > < span > Something </ span > </ Teleport > </ template > 🚦 Loading indicator and transition controls It's now possible to set custom timings for hiding the loading indicator, and forcing the finish() method if needed ( #25932 ). There's also a new page:view-transition:start hook for hooking into the View Transitions API ( #26045 ) if you have that feature enabled. 🛍️ Server- and client-only pages This release sees server- and client-only pages land in Nuxt! You can now add a .server.vue or .client.vue suffix to a page to get automatic handling of it. Client-only pages will render entirely on the client-side, and skip server-rendering entirely, just as if the entire page was wrapped in <ClientOnly> . Use this responsibly. The flash of load on the client-side can be a bad user experience so make sure you really need to avoid server-side loading. Also consider using <ClientOnly> with a fallback slot to render a skeleton loader ( #25037 ). ⚗️ Server-only pages are even more useful because they enable you to integrate fully-server rendered HTML within client-side navigation. They will even be prefetched when links to them are in the viewport - so you will get instantaneous loading ( #24954 ). 🤠 Server component bonanza When you are using server components, you can now use the nuxt-client attribute anywhere within your tree ( #25479 ). nuxt.config.ts export default defineNuxtConfig ( { experimental : { componentIslands : { selectiveClient : ' deep ' } }, } ) You can listen to an @error event from server components that will be triggered if there is any issue loading the component ( #25798 ). Finally, server-only components are now smartly enabled when you have a server-only component or a server-only page within your project or any of its layers ( #26223 ). Server components remain experimental and their API may change, so be careful before depending on implementation details. 🔥 Performance improvements We've shipped a number of performance improvements, including only updating changed virtual templates ( #26250 ), using a 'layered' prerender cache ( #26104 ) that falls back to filesystem instead of keeping everything in memory when prerendering - and lots of other examples. 📂 Public assets handling We have shipped a reimplementation of Vite's public asset handling, meaning that public assets in your public/ directory or your layer directories are now resolved entirely by Nuxt ( #26163 ), so if you have added nitro.publicAssets directories with a custom prefix, these will now work. 📦 Chunk naming We have changed the default _nuxt/[name].[hash].js file name pattern for your JS chunks. Now, we default to _nuxt/[hash].js . This is to avoid false positives by ad blockers triggering off your component or chunk names, which can be a very difficult issue to debug. ( #26203 ) You can easily configure this to revert to previous behaviour if you wish: nuxt.config.ts export default defineNuxtConfig ( { vite : { $client : { build : { rollupOptions : { output : { chunkFileNames : ' _nuxt/[name].[hash].js ' , entryFileNames : ' _nuxt/[name].[hash].js ' } } } } }, } ) 💪 Type fixes Previously users with shamefully-hoist=false may have encountered issues with types not being resolved or working correctly. You may also have encountered problems with excessive type instantiation. We now try to tell TypeScript about certain key types so they can be resolved even if deeply nested ( #26158 ). There are a whole raft of other type fixes, including some regarding import types ( #26218 and #25965 ) and module typings ( #25548 ). ✅ Upgrading As usual, our recommendation for upgrading Nuxt is to run: nuxi upgrade --force This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem. 👉 Full release notes Read the full release notes of Nuxt v3.11.0 . Thank you for reading this far! We hope you enjoy the new release. Please do let us know if you have any feedback or issues. Happy Nuxting ✨ ← Back to blog Copy URL Copy URL Nuxt on LinkedIn Nuxt on Bluesky Nuxt on X Table of Contents Table of Contents 🪵 Better logging 🎨 Preview mode 💰 Cache-busting payloads 👮♂️ Middleware routeRules ⌫ New clear data fetching utility 🕳️ New #teleports target 🚦 Loading indicator and transition controls 🛍️ Server- and client-only pages 🤠 Server component bonanza 🔥 Performance improvements 📂 Public assets handling 📦 Chunk naming 💪 Type fixes ✅ Upgrading 👉 Full release notes Links Edit this article Star on GitHub Become a Sponsor Nuxt on Discord Nuxt on Bluesky Nuxt on X Nuxt on GitHub Community Nuxters Team Design Kit Explore Modules Templates Showcase Enterprise Support Agencies Sponsors Subscribe to our newsletter Stay updated on new releases and features, guides, and community updates. Subscribe Nuxt on X Nuxt on BlueSky Nuxt on LinkedIn Nuxt on Discord Nuxt on GitHub Copyright © 2016-2026 Nuxt - MIT License | 2026-01-13T09:30:04 |
https://ja-jp.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1w9T5h4SFIM-3PmCUHPrcl-t1jb-segjkGEn4zpU67vWNthY4RTydxRIQCc8JgYepeq7aDBl0HymBVlYUfdIe8WqUBykPipderUBMoNtpsjiPXCEhOEQ5bn0VuDhbm4hgo8yTdvk4h2QfH | Facebook Facebook メールアドレスまたは電話番号 パスワード アカウントを忘れた場合 新しいアカウントを作成 機能の一時停止 機能の一時停止 この機能の使用ペースが早過ぎるため、機能の使用が一時的にブロックされました。 Back 日本語 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) Português (Brasil) Français (France) Deutsch アカウント登録 ログイン Messenger Facebook Lite 動画 Meta Pay Metaストア Meta Quest Ray-Ban Meta Meta AI Meta AIのコンテンツをもっと見る Instagram Threads 投票情報センター プライバシーポリシー プライバシーセンター Facebookについて 広告を作成 ページを作成 開発者 採用情報 Cookie AdChoices 規約 ヘルプ 連絡先のアップロードと非ユーザー 設定 アクティビティログ Meta © 2026 | 2026-01-13T09:30:04 |
https://zh-cn.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1w9T5h4SFIM-3PmCUHPrcl-t1jb-segjkGEn4zpU67vWNthY4RTydxRIQCc8JgYepeq7aDBl0HymBVlYUfdIe8WqUBykPipderUBMoNtpsjiPXCEhOEQ5bn0VuDhbm4hgo8yTdvk4h2QfH | Facebook Facebook 邮箱或手机号 密码 忘记账户了？ 创建新账户 你暂时被禁止使用此功能 你暂时被禁止使用此功能 似乎你过度使用了此功能，因此暂时被阻止，不能继续使用。 Back 中文(简体) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 日本語 Português (Brasil) Français (France) Deutsch 注册 登录 Messenger Facebook Lite 视频 Meta Pay Meta 商店 Meta Quest Ray-Ban Meta Meta AI Meta AI 更多内容 Instagram Threads 选民信息中心 隐私政策 隐私中心 关于 创建广告 创建公共主页 开发者 招聘信息 Cookie Ad Choices 条款 帮助 联系人上传和非用户 设置 动态记录 Meta © 2026 | 2026-01-13T09:30:04 |
https://nuxt.com/blog/v3-12#performance-improvements | Nuxt 3.12 · Nuxt Blog v4.2.2 Docs Modules Templates Resources Enterprise Blog Search… k 59.3K Blog Nuxt 3.12 Release · June 10, 2024 Nuxt 3.12 Nuxt 3.12 is out - full of improvements and preparing the way for Nuxt 4! Daniel Roe @danielroe.dev We're on the road to the release of Nuxt 4, but we've not held back in Nuxt v3.12. 🚀 Testing Nuxt 4 changes Nuxt 4 is on the horizon, and it's now possible to test out the behaviour changes that will be coming in the next major release ( #26925 ) by setting an option in your nuxt.config.ts file: nuxt.config.ts export default defineNuxtConfig ( { future : { compatibilityVersion : 4 , }, } ) As we've been merging PRs for Nuxt 4, we've been enabling them behind this flag. As much as possible we're aiming for backwards compatibility - our test matrix is running the same fixtures in both v3 and v4 compatibility mode. There is a lot to say here, with 10+ different PRs and behaviour changes documented and testable, but for full details, including migration steps, see the v4 upgrade documentation . We'd be very grateful for early testing of what's coming in Nuxt 4! 🙏 📜 Nuxt Scripts auto-install We've been gradually working to release Nuxt Scripts . It's currently in public preview, but we're near a public release, so we've added some stubs for composables that (when used) will prompt installing the @nuxt/scripts module. 👉 Watch out for the launch - and an article explaining more! 🌈 Layer auto-registration and bugfixes Just like ~/modules , any layers within your project in the ~/layers directory will now be automatically registered as layers in your project ( #27221 ). We also now correctly load layer dependencies, which should resolve a range of issues with monorepos and git installations ( #27338 ). 🌐 Built-in accessibility improvements We now have a built-in <NuxtRouteAnnouncer> component and corresponding useRouteAnnouncer composable, which will be added by default to new Nuxt templates going forward. For full details, see the original PR (#25741) and documentation . We're continuing to work on nuxt/a11y - expect to hear more on that in future! 🔥 Performance improvements We've landed some performance improvements as well, many of which are behind the compatibilityVersion: 4 flag, such as a move away from deeply reactive asyncData payloads. Significant improvements include deduplicating modules ( #27475 ) - which will apply mostly to layer users who specify modules in their layers. In one project, we saw 30s+ improvement in starting Nuxt. We've also improved Vite dev server start up time by excluding common ESM dependencies from pre-bundling, and would suggest module authors consider doing the same ( #27372 ). We improved chunk determinism, so sequential builds should be less likely to have completely different chunk hashes ( #27258 ). And we tree shake more client-only composables from your server builds ( #27044 ), and have reduced the size of server component payloads ( #26863 ). 👨👩👧👦 Multi-app support We've landed a couple of changes that take us toward a place of supporting multi-app natively in Nuxt, including a multiApp experimental flag ( #27291 ) and the ability to have multiple Nuxt app instances running in parallel at runtime ( #27068 ). While it's not yet ready, please do follow along on the tracker issue , and feel free to pitch in if this is interesting to you. ⛑️ DX wins We now serialise more things in your dev server logs, including VNodes ( #27309 ) and URLs . We also addressed a bug that could lead to a frozen dev server. When accessing private runtime config in the browser, we now let you know with a more informative error message ( #26441 ). 🪨 Stabilising features We've removed some experimental options that have been stabilised and which we feel no longer need to be configurable: experimental.treeshakeClientOnly (enabled by default since v3.0.0) experimental.configSchema (enabled by default since v3.3.0) experimental.polyfillVueUseHead (disabled since v3.4.0) - implementable in user-land with plugin experimental.respectNoSSRHeader (disabled since v3.4.0) - implementable in user-land with server middleware We've also enabled scanPageMeta by default ( #27134 ). This pulls out any page metadata in your definePageMeta macro, and makes it available to modules (like @nuxtjs/i18n ) so they can augment it. This unlocks much better module/typed routing integration, but has a potential performance cost - so please file an issue if you experience any problems. 💪 Type improvements We now have support for typed #fallback slots in server components ( #27097 ). We've also improved some defaults in your generated tsconfig.json , including setting module: 'preserve' if you have a locally installed TypeScript v5.4 version ( see docs ) - see #26667 , #27485 . 📦 Module author/power user improvements We have shipped a range of type improvements for module authors, including: support for typed module options in installModule ( #26744 ) the option to specify compatibility with certain builders (vite/webpack) in module options ( #27022 ) a new onPrehydrate hook for hooking into the browser hydration cycle ( #27037 ) the ability to access and update resolved runtime configuration within modules, with new build-time useRuntimeConfig and updateRuntimeConfig utils ( #27117 ) 🎨 Inlined UI templates If you previously used @nuxt/ui-templates then it may be worth knowing that we have moved them from a separate repository into the nuxt/nuxt monorepo. (This is purely a refactor rather than a change, although you can expect some new designs for Nuxt v4.) ✅ Upgrading As usual, our recommendation for upgrading is to run: npx nuxi@latest upgrade --force This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem. Full Release Notes Read the full release notes of Nuxt v3.12.0 . A huge thank you to the 75+ Nuxt contributors and community members who have been part of this release. ❤️ Finally, thank you for reading this far! We hope you enjoy v3.12, and please do let us know if you have any feedback or issues. 🙏 Happy Nuxting ✨ ← Back to blog Copy URL Copy URL Nuxt on LinkedIn Nuxt on Bluesky Nuxt on X Table of Contents Table of Contents 🚀 Testing Nuxt 4 changes 📜 Nuxt Scripts auto-install 🌈 Layer auto-registration and bugfixes 🌐 Built-in accessibility improvements 🔥 Performance improvements 👨👩👧👦 Multi-app support ⛑️ DX wins 🪨 Stabilising features 💪 Type improvements 📦 Module author/power user improvements 🎨 Inlined UI templates ✅ Upgrading Full Release Notes Links Edit this article Star on GitHub Become a Sponsor Nuxt on Discord Nuxt on Bluesky Nuxt on X Nuxt on GitHub Community Nuxters Team Design Kit Explore Modules Templates Showcase Enterprise Support Agencies Sponsors Subscribe to our newsletter Stay updated on new releases and features, guides, and community updates. Subscribe Nuxt on X Nuxt on BlueSky Nuxt on LinkedIn Nuxt on Discord Nuxt on GitHub Copyright © 2016-2026 Nuxt - MIT License | 2026-01-13T09:30:04 |
https://extensionworkshop.com/extension-basics/#your-consent-dialogs | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:04 |
https://extensionworkshop.com/extension-basics/#web-ext-docs | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:04 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=el | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="r | 2026-01-13T09:30:04 |
https://nuxt.com/blog/v3-5#interactive-server-components | Nuxt 3.5 · Nuxt Blog v4.2.2 Docs Modules Templates Resources Enterprise Blog Search… k 59.3K Blog Nuxt 3.5 Release · May 16, 2023 Nuxt 3.5 Nuxt 3.5.0 is out, bringing Vue 3.3, new defaults, interactive server components, typed pages, environment config - and much more. Daniel Roe @danielroe.dev ⚡️ Vue 3.3 released Vue 3.3 has been released, with lots of exciting features, particularly around type support. new defineOptions macro 'generic' components typed slots and using external types in defineProps ... and more This also brings a significant improvement to data fetching when navigating between nested pages ( #20777 ), thanks to @antfu and @baiwusanyu-c . Read the full release announcement for more details. 🙌 Nitropack v2.4 We've been working on lots of improvements to Nitro and these have landed already in Nitro v2.4 - you may already have this upgrade, which contains a lot of bug fixes, updates to the module worker format for Cloudflare, Vercel KV support and more. One note: if you're deploying to Vercel or Netlify and want to benefit from incremental static regeneration, you should now update your route rules: routeRules: { - - '/blog/**': { swr: 3000 }, + + '/blog/**': { isr: 3000 }, } Read the full release notes . 💖 Rich JSON payloads Rich JSON payload serialisation is now enabled by default ( #19205 , #20770 ). This is both faster and allows serialising complex objects in the payload passed from the Nuxt server to client (and also when extracting payload data for prerendered sites). This now means that various rich JS types are supported out-of-the-box : regular expressions, dates, Map and Set and BigInt as well as NuxtError - and Vue-specific objects like ref , reactive , shallowRef and shallowReactive . You can find an example in our test suite. This is all possible due to Rich-Harris/devalue#58 . For a long time, Nuxt has been using our own fork of devalue owing to issues serialising Errors and other non-POJO objects, but we now have transitioned back to the original. You can even register your own custom types with a new object-syntax Nuxt plugin: plugins/custom-payload-type.ts export default definePayloadPlugin ( () => { definePayloadReducer ( ' BlinkingText ' , data => data === ' <original-blink> ' && ' _ ' ) definePayloadReviver ( ' BlinkingText ' , () => ' <revivified-blink> ' ) } ) You can read more about how this works here . 🛝 Interactive server components This feature should be considered highly experimental, but thanks to some great work from @huang-julien we now support interactive content within server components via slots ( #20284 ). You can follow the server component roadmap at #19772 . ⏰ Environment config You can now configure fully typed, per-environment overrides in your nuxt.config.ts : nuxt.config.ts export default defineNuxtConfig ( { $production : { routeRules : { ' /** ' : { isr : true } } }, $development : { // } } ) If you're authoring layers, you can also use the $meta key to provide metadata that you or the consumers of your layer might use. Read more about per-environment overrides . 💪 Fully typed pages You can benefit from fully typed routing within your Nuxt app via this experimental integration with unplugin-vue-router - thanks to some great work from @posva ! Out of the box, this will enable typed usage of navigateTo , <NuxtLink> , router.push() and more. You can even get typed params within a page by using const route = useRoute ( ' route-name ' ) . Enable this feature directly in your nuxt.config.ts : nuxt.config.ts export default defineNuxtConfig ( { experimental : { typedPages : true } } ) 🔎 'Bundler' module resolution We now have full support within Nuxt for the bundler strategy of module resolution . We would recommend adopting this if possible. It has type support for subpath exports, for example, but more exactly matches the behaviour of build tools like Vite and Nuxt than Node16 resolution. nuxt.config.ts export default defineNuxtConfig ( { typescript : { tsConfig : { compilerOptions : { moduleResolution : ' bundler ' } } } } ) This turns on TypeScript's ability to 'follow' Node subpath exports. For example, if a library has a subpath export like mylib/path that is mapped to mylib/dist/path.mjs then the types for this can be pulled in from mylib/dist/path.d.ts rather than requiring the library author to create mylib/path.d.ts . ⚗️ Separate server types We plan to improve clarity within your IDE between the 'nitro' and 'vue' part of your app, we've shipped the first part of this via a separate generated tsconfig.json for your ~/server directory ( #20559 ). You can use by adding an additional ~/server/tsconfig.json with the following content: { " extends " : " ../.nuxt/tsconfig.server.json " } Although right now these values won't be respected when type checking ( nuxi typecheck ), you should get better type hints in your IDE. 💀 Deprecations Although we have not typed or documented the build.extend hook from Nuxt 2, we have been calling it within the webpack builder. We are now explicitly deprecating this and will remove it in a future minor version. ✅ Upgrading As usual, our recommendation for upgrading is to run: npx nuxi upgrade --force This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem. 📃 Full changelog Read the full release note on https://github.com/nuxt/nuxt/releases/tag/v3.5.0 ← Back to blog Copy URL Copy URL Nuxt on LinkedIn Nuxt on Bluesky Nuxt on X Nuxt 3.6 Nuxt 3.6 is out, bringing performance improvements, fully static server components, better style inlining, static presets, increased type safety - and much more. Nuxt 3.4 Nuxt 3.4.0 is the latest release of Nuxt 3, bringing exciting new features, including support for the View Transitions API, transferring rich JavaScript payloads from server to client - and much more. Table of Contents Table of Contents ⚡️ Vue 3.3 released 🙌 Nitropack v2.4 💖 Rich JSON payloads 🛝 Interactive server components ⏰ Environment config 💪 Fully typed pages 🔎 'Bundler' module resolution ⚗️ Separate server types 💀 Deprecations ✅ Upgrading 📃 Full changelog Links Edit this article Star on GitHub Become a Sponsor Nuxt on Discord Nuxt on Bluesky Nuxt on X Nuxt on GitHub Community Nuxters Team Design Kit Explore Modules Templates Showcase Enterprise Support Agencies Sponsors Subscribe to our newsletter Stay updated on new releases and features, guides, and community updates. Subscribe Nuxt on X Nuxt on BlueSky Nuxt on LinkedIn Nuxt on Discord Nuxt on GitHub Copyright © 2016-2026 Nuxt - MIT License | 2026-01-13T09:30:04 |
https://www.telerik.com/videos/product/teststudio | Telerik Videos, Telerik Products Video Tutorials skip navigation All Products Product Bundles DevCraft All Telerik .NET tools and Kendo UI JavaScript components in one package. Now enhanced with: MCP Servers Embedded Reporting Document Processing Libraries SSO Account Sign-in Web Kendo UI UI for Angular UI for Vue UI for jQuery KendoReact UI for Blazor UI for ASP.NET Core UI for ASP.NET MVC UI for ASP.NET AJAX Mobile UI for .NET MAUI Document Management Telerik Document Processing Desktop UI for .NET MAUI UI for WinUI UI for WinForms UI for WPF Reporting Telerik Reporting Telerik Report Server Testing & Mocking Test Studio Telerik JustMock CMS Sitefinity AI Productivity Tools MCP Servers UI/UX Tools ThemeBuilder Design System Kit Templates and Building Blocks Debugging Fiddler Fiddler Everywhere Fiddler Classic Fiddler Everywhere Reporter FiddlerCore Free Tools KendoReact Free VB.NET to C# Converter Testing Framework View all products Demos Services Blogs Docs & Support Pricing Shopping cart Your Account Account Overview Your Licenses Downloads Support Center Forum Profile Payment Methods Edit Profile Log out Login Contact Us Get A Free Trial close mobile menu Get the Most of Our Products with Videos and Video Tutorials Search Videos Tips to help you find the information you seek: If you are searching for instructions and tutorial, using the technology, component, and the instructions you need will yield the best result. Good examples are " How to create Angular dropdowns " or " Getting Started with .NET MAUI ". We archive our release webinars. Using the keyword " release " will allow you to browse our collection. Filter videos: Filter by Topic Select Design Desktop Mobile People Reporting Software Quality Web Filtery by Product Select DevCraft Fiddler Fiddler Classic Fiddler Everywhere Kendo Grid Kendo UI Kendo UI for Angular Kendo UI for jQuery KendoReact React Wednesdays Telerik Document Processing Telerik JustMock Telerik Reporting Telerik UI for .NET MAUI Telerik UI for ASP.NET AJAX Telerik UI for ASP.NET Core Telerik UI for ASP.NET MVC Telerik UI for Blazor Telerik UI for WinForms Telerik UI for WinUI Telerik UI for WPF Test Studio ThemeBuilder ThemeBuilder Pro or Filter by Show Select .NET Dev Show CodeItLive Specials Dev by Design DevReach Eat, Sleep, Code React Wednesdays Snorkeling in MAUI Telerik & Kendo UI Release The Blazor Power Hour The CodeItLive Chat Show UI Fridays UI Mondays Showing 53 videos. Clear Filter × Software Quality Test Studio Desktop Testing Video Tutorial Watch Video July 26, 2022 Software Quality Test Studio Accelerate Your Test Automation with Test Studio Watch Video June 14, 2022 Software Quality Test Studio How To Make Functional Automated Tests Watch Video June 14, 2022 Software Quality Test Studio Test Recorder for WPF Video Tutorial – Test Studio Watch Video May 26, 2022 Software Quality Test Studio The Success of Test Automation Explained Watch Video May 13, 2022 Software Quality Test Studio Does UI Testing Really Fit into CI/CD? Watch Video May 12, 2022 1 2 3 4 5 6 7 8 9 Next Are You Planning a Complex or Multi-Platform Project Soon? If Yes, Look at Our Best Value Offer Save time and money by getting 1,250+ .NET and JavaScript UI components for building web, desktop, and mobile apps. Plus, embedded reporting, automated testing, and mocking tools. See Plans & Pricing More about Telerik DevCraft Explore Other Resources Getting Started Demos Webinars Case studies Whitepapers FAQs Learning Documentation Virtual Classroom Videos Release history Roadmap What's new Infographics Community Forums Blogs Events Developer Central Progress Community Support Progress Influencer Licenses Progress Ninja Program Support Product questions Support policy Feedback and feature requests Pricing and Licensing FAQ Services Consulting Educational Modernization Outsourcing Complete .NET Toolbox Telerik DevCraft Complete JavaScript Toolbox Kendo UI Get Products Free Trials Pricing Resources DX Hub Demos Documentation Release History Forums Blogs Webinars Videos Professional Services Partners Virtual Classroom Events FAQs Recognition Success Stories Testimonials Get in touch Contact Us USA: +1 888 679 0442 UK: +44 13 4483 8186 India: +91 406 9019447 Bulgaria: +359 2 8099850 Australia: +61 3 7068 8610 165k+ 50k+ 17k+ 4k+ 14k+ Contact Us 165k+ 50k+ 17k+ 4k+ 14k+ Telerik and Kendo UI are part of Progress product portfolio. Progress is the leading provider of application development and digital experience technologies. Company Technology Awards Press Releases Media Coverage Careers Offices Company Technology Awards Press Releases Media Coverage Careers Offices Copyright © 2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved. Progress and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings. All rights in any other trademarks contained herein are reserved by their respective owners and their inclusion does not imply an endorsement, affiliation, or sponsorship as between Progress and the respective owners. Terms of Use Site Feedback Privacy Center Trust Center Do Not Sell or Share My Personal Information Powered by Progress Sitefinity | 2026-01-13T09:30:04 |
https://yle.fi/t/18-34837/fi | Kotimaa | Yle.fi | Uutiset, urheilu, ilmiöt Hyppää sisältöön Hyppää sisältöön Etusivu Venäjän hyökkäys UMK26 Sanapyramidi Hae Valikko Haemme säätietoja... Hae Ylen sisältöjä Lähetä uutiskuva tai ‑video Pinnalla nyt Venäjän hyökkäys UMK26 Sanapyramidi Talviolympialaiset Etusivu Uutisia lyhyesti Tuoreimmat Urheilu Sää Paikallisuutiset Kotimaa Ulkomaat Politiikka Talous Kulttuuri Tiede Luonto Oppiminen Abitreenit Kolumnit Uutiset viittomakielellä Selkouutiset Uutisluokka Elävä arkisto Teksti-TV Uutiskirjeet TV-opas Radio-opas RSS-syötteet Yle Areena. Sarjat. Podcastit. Suorat. Svenska Sápmi News Новости Новини Uudizet karjalakse Lähetä uutiskuva tai ‑video Asiakaspalvelu Ylen yhteystiedot Uutisten yhteystiedot Evästeasetukset Sulje valikko Kotimaa Hirmupakkasissa hiihtovaellukselle lähteneitä on haettu moottorikelkoilla ja helikopterilla Lapin erämaasta Sää 11:17 Poliisi epäilee: kaksi miestä katkaisi lipputangon ja repi Iranin lippua suurlähetystöllä Rikosepäilyt 10:40 Sisäilman piti olla pilalla, ja siksi Helsinki myi taidemuseon kymppitonnilla – uusi omistaja ei löydä ongelmia Kulttuuri 10:36 Syyttäjä: ”Tunnelbusters”-kolmikko vahingoitti Suomen puolustusta julkaisemalla tuhansien kohteiden tietoja netissä Rikokset 10:08 Matkailija voi levittää tietämättään sikoja tappavaa tautia – siksi ruokatehdas rajoittaa työntekijöidensä matkustusta Elintarvikkeet 10:03 Vanhusasiavaltuutettu haluaa puuttua vanhusten sitomiseen Terveydenhuolto 9:50 Kauniaisten traktoriturma: Näkyvyys oli hyvä, kun 10-vuotias kuoli jäätyään traktorin alle koulun läheisyydessä Oikeudenkäynnit 8:01 Vastaavalta päätoimittajalta: Auta meitä paremmiksi Media 7:45 420 Ranskalaiset ajoivat laivansa jumiin jäihin Suomen edustalla – tarkoituksella Tutkimus 7:28 Valtteri Taube alkoi kirjoittaa tekoälyllä somepäivityksiä – lopputulos valtava menestys: tilauksia lähes 500 000 euron edestä Työelämä 6:40 79 Itämerellä on pakko ottaa käyttöön vanhat navigointimenetelmät, koska laivojen paikannusta häiritään enemmän kuin koskaan Liikenne 6:00 56 Oikeudenkäynti ”tunnelisotavideoista” alkaa Oikeudenkäynnit 2:01 Poliisi selvittää häiriökäyttäytymistä Iranin suurlähetystöllä Rikosepäilyt 12.1. Satakunta on putomassa itsenäisten vaalipiirien joukosta – vaalijohtaja muutoksesta: ”Vaikea selittää” Vaalit 12.1. Kittilän lentokaaoksen takana ilmiö, jota ei ole nähty 30 vuoteen – turistit pääsevät vihdoin koteihinsa Matkailu 12.1. Historiallisia karjalaisia lehtiä ilmestyi verkkoon Historia 12.1. Helsinkiläislapsille ilmainen Aku Ankka kotiin – Tutkimus etsii keinoja heikentyneen lukutaidon parantamiseen Tutkimus 12.1. Moottoritien vaihtuva nopeusrajoitus pysyy kahdeksassakympissä, vaikka on kuskien mielestä normaali talvikeli Liikenne 12.1. Keskisarjan luentotilaisuus sujui rauhallisesti Tapahtumat 12.1. Muistisairas vanhus kuoli turkulaisessa hoivakodissa – kysyimme Esperiltä, miksi vanhuksia sidotaan Rikokset 12.1. Vapaaehtoiset meripelastajat auttoivat tuhansia Onnettomuudet 12.1. Tullin palvelussa käyttökatko haavoittuvuuden takia Viranomaiset 12.1. Tämä on karu totuus somen videoista, joissa ”huiputetaan” tappavan vaarallisia radiomastoja Onnettomuudet 12.1. ”Mahtaako mies tulla takaisin?” – Ystävä ja valmennettava kertoo huolestaan Jari Saariosta Merenkulku 12.1. Teemu Keskisarjan luento väestönvaihdosta täytti kirjaston Lahdessa – paikalla myös poliisi Yhteiskunta 12.1. Fitburg-alus on poistunut Suomesta Rikosepäilyt 12.1. Turun tuomiokirkko sulkeutuu pian – lähes tuhat kävi jättämässä hyvästit yhden päivän aikana Rakennukset 12.1. Paljakan hiihtokeskuksen brittisijoittajaa ei ikinä saatu kiinni, joten Kainuun käräjäoikeus purki maanvuokrasopimukset Elinkeinoelämä 12.1. Osuuskauppa Keskimaa aloittamassa yli 200 työntekijää koskevat muutosneuvottelut – Keuruun ABC saatetaan sulkea Elinkeinoelämä 12.1. Opiskelija-asuntosäätiö näki iskun paikan Lappeenrannassa – rakentaa taloja, koska nyt saa hyviä diilejä Opiskelu 12.1. Haaparannan kuolonkolari: myös auton omistajaa syytetään törkeästä kuolemantuottamuksesta Oikeudenkäynnit 12.1. Maitotilojen raju muutos näkyy Kainuussa: tiloista liki 90 prosenttia on lopettanut, mutta maitoa tuotetaan yhä enemmän Maatalous 12.1. Kuljettaja kuoli nokkakolarissa rekan kanssa Siilinjärvellä – valtatie 5:n liikenne oli poikki tunteja Onnettomuudet 12.1. Teollisuuden Voimalle lupa sijoittaa hyvin matala-aktiivista ydinjätettä maaperään Energia 12.1. Antifasistit vastustavat Teemu Keskisarjan luentoa – tutkija kehottaa kuulijoita kriittisyyteen Yhteiskunta 12.1. Poliisi epäilee kahta miestä taposta karaokebaarin edustalla Helsingissä – epäillyillä rikostaustaa Rikosepäilyt 12.1. Nammon nallitehdas käynnistyy Vihtavuoressa – Yle pääsi ensimmäisenä kurkistamaan tarkasti varjeltuun tuotantolaitokseen Teollisuus 12.1. Keikkatauolta palaavan Gettomasan konserttiliput myytiin hujauksessa – Jyväskylän pesäpallostadionille lisäkatsomot Kulttuuri 12.1. Suomi haluaa lähteä jääpallon kotikisoista maailmanmestarina – MM-kisat starttasivat tänään Porissa Jääpallo 12.1. HUS keskittää tekonivelleikkaukset Ortoniin helpottaakseen hoitoon pääsyä Terveydenhuolto 12.1. Näytä lisää på svenska: inrikes in English: domestic news Tuoreimmat 11:17 Sää Hirmupakkasissa hiihtovaellukselle lähteneitä on haettu moottorikelkoilla ja helikopterilla Lapin erämaasta 11:09 Iivo Niskasesta tipahti ilahduttava tieto – Kerttu Niskaselta kova päätös 11:09 Talous Tekoäly ja velka hallitsevat markkinoita tänä vuonna, sanoo Blackrockin Pohjoismaiden-päästrategi Ylen haastattelussa 10:57 Talous Energiantuotannon investointien ennakoidaan hyytyvän 10:40 Rikosepäilyt Poliisi epäilee: kaksi miestä katkaisi lipputangon ja repi Iranin lippua suurlähetystöllä 10:36 Kulttuuri Sisäilman piti olla pilalla, ja siksi Helsinki myi taidemuseon kymppitonnilla – uusi omistaja ei löydä ongelmia 10:08 Rikokset Syyttäjä: ”Tunnelbusters”-kolmikko vahingoitti Suomen puolustusta julkaisemalla tuhansien kohteiden tietoja netissä 10:06 Liikenne Wienin lentoasema suljettu jään vuoksi 10:03 Elintarvikkeet Matkailija voi levittää tietämättään sikoja tappavaa tautia – siksi ruokatehdas rajoittaa työntekijöidensä matkustusta 9:50 Terveydenhuolto Vanhusasiavaltuutettu haluaa puuttua vanhusten sitomiseen 9:39 Talous Fortum raamisopimukseen pienydinvoimalaa kehittävän suomalaisyhtiön kanssa 9:16 Media Pohjoismaalaisten medialukutaito on hyvä, mutta ikäryhmien väliset erot ovat suuria 9:04 Levottomuudet Iranissa oleskelee 91 matkustusilmoituksen tehnyttä suomalaista 8:47 Viihde UMK26-kilpailijajulkistus 14.1. 8:43 Kansainvälinen politiikka Maailman suurin saari irtosi Euroopan mantereesta 55 miljoonaa vuotta sitten – miksi se kuuluu Tanskalle? Tästä keskustellaan nyt 1 Media Vastaavalta päätoimittajalta: Auta meitä paremmiksi 420 2 Työelämä Valtteri Taube alkoi kirjoittaa tekoälyllä somepäivityksiä – lopputulos valtava menestys: tilauksia lähes 500 000 euron edestä 79 3 Liikenne Itämerellä on pakko ottaa käyttöön vanhat navigointimenetelmät, koska laivojen paikannusta häiritään enemmän kuin koskaan 56 Takaisin sivun alkuun Yle yhtiönä Tietosuojalauseke Saavutettavuusseloste Evästekäytännöt Asiakaspalvelu Avoimet työpaikat Ylen perus- ja yhteystiedot | 2026-01-13T09:30:04 |
https://www.telerik.com/about/success-stories | Success Stories with Telerik Products skip navigation All Products Product Bundles DevCraft All Telerik .NET tools and Kendo UI JavaScript components in one package. Now enhanced with: MCP Servers Embedded Reporting Document Processing Libraries SSO Account Sign-in Web Kendo UI UI for Angular UI for Vue UI for jQuery KendoReact UI for Blazor UI for ASP.NET Core UI for ASP.NET MVC UI for ASP.NET AJAX Mobile UI for .NET MAUI Document Management Telerik Document Processing Desktop UI for .NET MAUI UI for WinUI UI for WinForms UI for WPF Reporting Telerik Reporting Telerik Report Server Testing & Mocking Test Studio Telerik JustMock CMS Sitefinity AI Productivity Tools MCP Servers UI/UX Tools ThemeBuilder Design System Kit Templates and Building Blocks Debugging Fiddler Fiddler Everywhere Fiddler Classic Fiddler Everywhere Reporter FiddlerCore Free Tools KendoReact Free VB.NET to C# Converter Testing Framework View all products Demos Services Blogs Docs & Support Pricing Shopping cart Your Account Account Overview Your Licenses Downloads Support Center Forum Profile Payment Methods Edit Profile Log out Login Contact Us Get A Free Trial close mobile menu Success Stories That Inspire Us We live in interesting times. See how we support our clients and help them evolve their business to meet their daily challenges, by increasing speed and reducing costs. Read the stories that inspire us to continue to provide even better products and solutions Agricultural DevCraft SoDak Labs Cuts Development Time 40% with Progress Telerik Read the Whole Story Technology Software DevCraft Kendo UI HP Uses Progress Telerik to Slash Development Time by Up to 40% Read the Whole Story Progress Telerik is: 275K+ customers 3.4M+ developers 400+ awards Find Businesses Like Yours. Filter by Industry Select Agricultural Charity Construction Finance Government Healthcare Human Resources Miscellaneous Software Technology Transportation Travel Filter by Product Select DevCraft Fiddler Everywhere Kendo UI Kendo UI for Angular Kendo UI for Vue KendoReact Progress Telerik Telerik Report Server Telerik Reporting Telerik UI for ASP.NET AJAX Telerik UI for ASP.NET Core Telerik UI for ASP.NET MVC Telerik UI for Blazor Telerik UI for WinForms Telerik UI for WPF Test Studio Technology Software Kendo UI KendoReact Icanpreneur Launches First “Accelerator-as-a-Software” Platform, Leveraging Kendo UI for a Seamless Customer Experience Read the Whole Story Technology Test Studio Vistaprint – how a global marketing services giant created a unified automated testing platform with Telerik Test Studio Read the Whole Story Software Test Studio How Scorpion Software Saved $100k a Year with Telerik Test Studio Read the Whole Story Healthcare Telerik UI for ASP.NET Core Appointment Reminders.com Speeds App Development While Creating Superior Customer Experiences with Progress Telerik Read the Whole Story Telerik UI for Blazor KlipTok Leverages Telerik UI in Blazor-Powered App to Improve Its Functionality for Twitch Users and Streamers Read the Whole Story Software Technology Kendo UI for Angular Telerik UI for ASP.NET MVC Kendo UI for Vue BAYOOTEC Delivers Integrated Digital Transformation UX 15% Faster with Kendo UI Read the Whole Story 1 2 3 4 5 6 7 Next Telerik® DevCraft Product Bundle Are You Planning a Complex or Multi-Platform Project Soon? If Yes, Look at Our Best Value Offer Save time and money by getting 1,250+ .NET and JavaScript UI components for building web, desktop, and mobile apps. Plus, embedded reporting, automated testing, and mocking tools. More about Telerik DevCraft What Developers Say After being in the industry for over 20 years I have seen a lot of frameworks come and go, but Kendo UI is by far the best for hybrid/mobile/native apps. Not only for its ease of use but it plays well with others. Geovanni Hudson Sr. Web/UI Application Engineer, PCYC We at PatientMatters have recently purchased Telerik Test Studio and if it were not for the fine communication from your support staff, I would not have been able to convince my management to do so. They were always available to answer the tough questions and were extremely interested in the success of our usage of this product. Please accept our sincere appreciation for the excellent technical support as well as the gentlemen they are. Both myself and my Chief Technical Officer can see that they are a great asset to your organization. Leon Esses Quality Assurance Analyst, Patient Matters Kendo UI allowed us to build a new product from scratch for our customers very quickly. Moreover, it saved us a lot of time, without the need to deal with cross browser compatibility. Kendo UI is efficient, powerful and gives to our customers a great User Experience. Nicolas Dujardin R&D Manager, ATHIC Complete .NET Toolbox Telerik DevCraft Complete JavaScript Toolbox Kendo UI Get Products Free Trials Pricing Resources DX Hub Demos Documentation Release History Forums Blogs Webinars Videos Professional Services Partners Virtual Classroom Events FAQs Recognition Success Stories Testimonials Get in touch Contact Us USA: +1 888 679 0442 UK: +44 13 4483 8186 India: +91 406 9019447 Bulgaria: +359 2 8099850 Australia: +61 3 7068 8610 165k+ 50k+ 17k+ 4k+ 14k+ Contact Us 165k+ 50k+ 17k+ 4k+ 14k+ Telerik and Kendo UI are part of Progress product portfolio. Progress is the leading provider of application development and digital experience technologies. Company Technology Awards Press Releases Media Coverage Careers Offices Company Technology Awards Press Releases Media Coverage Careers Offices Copyright © 2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved. Progress and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings. All rights in any other trademarks contained herein are reserved by their respective owners and their inclusion does not imply an endorsement, affiliation, or sponsorship as between Progress and the respective owners. Terms of Use Site Feedback Privacy Center Trust Center Do Not Sell or Share My Personal Information Powered by Progress Sitefinity | 2026-01-13T09:30:04 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=fr_CH | html,body{height:100%;overflow:hidden}body{-webkit-font-smoothing:antialiased;-moz-osx-font-smoothing:grayscale;color:rgba(0,0,0,0.87);font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif;margin:0;-webkit-text-size-adjust:100%;-moz-text-size-adjust:100%;-ms-text-size-adjust:100%;text-size-adjust:100%}textarea{font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif}a{text-decoration:none;color:#2962ff}img{border:none}*{-webkit-tap-highlight-color:transparent}#apps-debug-tracers{display:none}html,body{overflow:visible}body{overflow-y:scroll}@-webkit-keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@keyframes mdc-ripple-fg-radius-in{from{-webkit-animation-timing-function:cubic-bezier(.4,0,.2,1);animation-timing-function:cubic-bezier(.4,0,.2,1);-webkit-transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1);transform:translate(var(--mdc-ripple-fg-translate-start,0)) scale(1)}to{-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}}@-webkit-keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@keyframes mdc-ripple-fg-opacity-in{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:0}to{opacity:var(--mdc-ripple-fg-opacity,0)}}@-webkit-keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}@keyframes mdc-ripple-fg-opacity-out{from{-webkit-animation-timing-function:linear;animation-timing-function:linear;opacity:var(--mdc-ripple-fg-opacity,0)}to{opacity:0}}.VfPpkd-ksKsZd-XxIAqe{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity;position:relative;outline:none;overflow:hidden}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-ksKsZd-XxIAqe::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-ksKsZd-XxIAqe::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded],.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd{overflow:visible}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded]::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd::after{top:0;left:0;width:100%;height:100%}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::before,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0);width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe[data-mdc-ripple-is-unbounded].VfPpkd-ksKsZd-mWPk3d::after,.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd.VfPpkd-ksKsZd-mWPk3d::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-ksKsZd-XxIAqe::before,.VfPpkd-ksKsZd-XxIAqe::after{background-color:#000;background-color:var(--mdc-ripple-color,#000)}.VfPpkd-ksKsZd-XxIAqe:hover::before,.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe::before,.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):focus::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d)::after{-webkit-transition:opacity .15s linear;transition:opacity .15s linear}.VfPpkd-ksKsZd-XxIAqe:not(.VfPpkd-ksKsZd-mWPk3d):active::after{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-press-opacity,.12)}.VfPpkd-ksKsZd-XxIAqe.VfPpkd-ksKsZd-mWPk3d{--mdc-ripple-fg-opacity:var(--mdc-ripple-press-opacity,0.12)}.Tj45d{position:relative}.ncIyJc{position:absolute;overflow:hidden;left:-1px;top:auto;width:1px;height:1px}.VfPpkd-NLUYnc-V67aGc{position:absolute;left:0;-webkit-transform-origin:left top;-ms-transform-origin:left top;transform-origin:left top;line-height:1.15rem;text-align:left;text-overflow:ellipsis;white-space:nowrap;cursor:text;overflow:hidden;will-change:transform}[dir=rtl] .VfPpkd-NLUYnc-V67aGc,.VfPpkd-NLUYnc-V67aGc[dir=rtl]{right:0;left:auto;-webkit-transform-origin:right top;-ms-transform-origin:right top;transform-origin:right top;text-align:right}.VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{cursor:auto}.VfPpkd-NLUYnc-V67aGc-OWXEXe-ztc6md:not(.VfPpkd-NLUYnc-V67aGc-OWXEXe-ZYIfFd-ztc6md-vXpfLb)::after{margin-left:1px;margin-right:0;content:"*"}[dir=rtl] .VfPpkd-NLUYnc-V67aGc-OWXEXe-ztc6md:not(.VfPpkd-NLUYnc-V67aGc-OWXEXe-ZYIfFd-ztc6md-vXpfLb)::after,.VfPpkd-NLUYnc-V67aGc-OWXEXe-ztc6md:not(.VfPpkd-NLUYnc-V67aGc-OWXEXe-ZYIfFd-ztc6md-vXpfLb)[dir=rtl]::after{margin-left:0;margin-right:1px}.VfPpkd-NLUYnc-V67aGc{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-family:Roboto,sans-serif;font-family:var(--mdc-typography-subtitle1-font-family,var(--mdc-typography-font-family,Roboto,sans-serif));font-size:1rem;font-size:var(--mdc-typography-subtitle1-font-size,1rem);font-weight:400;font-weight:var(--mdc-typography-subtitle1-font-weight,400);letter-spacing:.009375em;letter-spacing:var(--mdc-typography-subtitle1-letter-spacing,.009375em);text-decoration:inherit;-webkit-text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-transform:inherit;text-transform:var(--mdc-typography-subtitle1-text-transform,inherit);-webkit-transition:color .15s cubic-bezier(.4,0,.2,1),-webkit-transform .15s cubic-bezier(.4,0,.2,1);transition:color .15s cubic-bezier(.4,0,.2,1),-webkit-transform .15s cubic-bezier(.4,0,.2,1);transition:transform .15s cubic-bezier(.4,0,.2,1),color .15s cubic-bezier(.4,0,.2,1);transition:transform .15s cubic-bezier(.4,0,.2,1),color .15s cubic-bezier(.4,0,.2,1),-webkit-transform .15s cubic-bezier(.4,0,.2,1)}.VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-106%) scale(.75);-ms-transform:translateY(-106%) scale(.75);transform:translateY(-106%) scale(.75)}.VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-standard .25s 1;animation:mdc-floating-label-shake-float-above-standard .25s 1}@-webkit-keyframes mdc-floating-label-shake-float-above-standard{0%{-webkit-transform:translateX(0) translateY(-106%) scale(.75);transform:translateX(0) translateY(-106%) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-106%) scale(.75);transform:translateX(4%) translateY(-106%) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-106%) scale(.75);transform:translateX(-4%) translateY(-106%) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-106%) scale(.75);transform:translateX(0) translateY(-106%) scale(.75)}}@keyframes mdc-floating-label-shake-float-above-standard{0%{-webkit-transform:translateX(0) translateY(-106%) scale(.75);transform:translateX(0) translateY(-106%) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-106%) scale(.75);transform:translateX(4%) translateY(-106%) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-106%) scale(.75);transform:translateX(-4%) translateY(-106%) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-106%) scale(.75);transform:translateX(0) translateY(-106%) scale(.75)}}.VfPpkd-RWgCYc-ksKsZd::before,.VfPpkd-RWgCYc-ksKsZd::after{position:absolute;bottom:0;left:0;width:100%;border-bottom-style:solid;content:""}.VfPpkd-RWgCYc-ksKsZd::before{z-index:1}.VfPpkd-RWgCYc-ksKsZd::after{-webkit-transform:scaleX(0);-ms-transform:scaleX(0);transform:scaleX(0);opacity:0;z-index:2}.VfPpkd-RWgCYc-ksKsZd-OWXEXe-auswjd::after{-webkit-transform:scaleX(1);-ms-transform:scaleX(1);transform:scaleX(1);opacity:1}.VfPpkd-RWgCYc-ksKsZd-OWXEXe-JD038d::after{opacity:0}.VfPpkd-RWgCYc-ksKsZd::before{border-bottom-width:1px}.VfPpkd-RWgCYc-ksKsZd::after{border-bottom-width:2px}.VfPpkd-RWgCYc-ksKsZd::after{-webkit-transition:opacity .18s cubic-bezier(.4,0,.2,1),-webkit-transform .18s cubic-bezier(.4,0,.2,1);transition:opacity .18s cubic-bezier(.4,0,.2,1),-webkit-transform .18s cubic-bezier(.4,0,.2,1);transition:transform .18s cubic-bezier(.4,0,.2,1),opacity .18s cubic-bezier(.4,0,.2,1);transition:transform .18s cubic-bezier(.4,0,.2,1),opacity .18s cubic-bezier(.4,0,.2,1),-webkit-transform .18s cubic-bezier(.4,0,.2,1)}.VfPpkd-NSFCdd-i5vt6e{display:-webkit-box;display:-webkit-flex;display:flex;position:absolute;top:0;right:0;left:0;-webkit-box-sizing:border-box;box-sizing:border-box;width:100%;max-width:100%;height:100%;text-align:left;pointer-events:none}[dir=rtl] .VfPpkd-NSFCdd-i5vt6e,.VfPpkd-NSFCdd-i5vt6e[dir=rtl]{text-align:right}.VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-NSFCdd-MpmGFe{-webkit-box-sizing:border-box;box-sizing:border-box;height:100%;pointer-events:none}.VfPpkd-NSFCdd-MpmGFe{-webkit-box-flex:1;-webkit-flex-grow:1;flex-grow:1}.VfPpkd-NSFCdd-Ra9xwd{-webkit-box-flex:0;-webkit-flex:0 0 auto;flex:0 0 auto;width:auto}.VfPpkd-NSFCdd-i5vt6e .VfPpkd-NLUYnc-V67aGc{display:inline-block;position:relative;max-width:100%}.VfPpkd-NSFCdd-i5vt6e .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{text-overflow:clip}.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{max-width:133.3333333333%}.VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd{padding-left:0;padding-right:8px;border-top:none}[dir=rtl] .VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd[dir=rtl]{padding-left:8px;padding-right:0}.VfPpkd-NSFCdd-i5vt6e-OWXEXe-di8rgd-V67aGc .VfPpkd-NSFCdd-Ra9xwd{display:none}.VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-NSFCdd-MpmGFe{border-top:1px solid;border-bottom:1px solid}.VfPpkd-NSFCdd-Brv4Fb{border-left:1px solid;border-right:none;width:12px}[dir=rtl] .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-NSFCdd-Brv4Fb[dir=rtl]{border-left:none;border-right:1px solid}.VfPpkd-NSFCdd-MpmGFe{border-left:none;border-right:1px solid}[dir=rtl] .VfPpkd-NSFCdd-MpmGFe,.VfPpkd-NSFCdd-MpmGFe[dir=rtl]{border-left:1px solid;border-right:none}.VfPpkd-NSFCdd-Ra9xwd{max-width:calc(100% - 24px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be{--mdc-ripple-fg-size:0;--mdc-ripple-left:0;--mdc-ripple-top:0;--mdc-ripple-fg-scale:1;--mdc-ripple-fg-translate-end:0;--mdc-ripple-fg-translate-start:0;-webkit-tap-highlight-color:rgba(0,0,0,0);will-change:transform,opacity}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::after{position:absolute;border-radius:50%;opacity:0;pointer-events:none;content:""}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::before{-webkit-transition:opacity 15ms linear,background-color 15ms linear;transition:opacity 15ms linear,background-color 15ms linear;z-index:1;z-index:var(--mdc-ripple-z-index,1)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::after{z-index:0;z-index:var(--mdc-ripple-z-index,0)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d .VfPpkd-fmcmS-OyKIhb::before{-webkit-transform:scale(var(--mdc-ripple-fg-scale,1));-ms-transform:scale(var(--mdc-ripple-fg-scale,1));transform:scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d .VfPpkd-fmcmS-OyKIhb::after{top:0;left:0;-webkit-transform:scale(0);-ms-transform:scale(0);transform:scale(0);-webkit-transform-origin:center center;-ms-transform-origin:center center;transform-origin:center center}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d-OWXEXe-ZNMTqd .VfPpkd-fmcmS-OyKIhb::after{top:var(--mdc-ripple-top,0);left:var(--mdc-ripple-left,0)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-lJfZMc .VfPpkd-fmcmS-OyKIhb::after{-webkit-animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards;animation:mdc-ripple-fg-radius-in 225ms forwards,mdc-ripple-fg-opacity-in 75ms forwards}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d-OWXEXe-Tv8l5d-OmS1vf .VfPpkd-fmcmS-OyKIhb::after{-webkit-animation:mdc-ripple-fg-opacity-out .15s;animation:mdc-ripple-fg-opacity-out .15s;-webkit-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));-ms-transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1));transform:translate(var(--mdc-ripple-fg-translate-end,0)) scale(var(--mdc-ripple-fg-scale,1))}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::after{top:-50%;left:-50%;width:200%;height:200%}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d .VfPpkd-fmcmS-OyKIhb::after{width:var(--mdc-ripple-fg-size,100%);height:var(--mdc-ripple-fg-size,100%)}.VfPpkd-fmcmS-OyKIhb{position:absolute;top:0;left:0;width:100%;height:100%;pointer-events:none}.VfPpkd-fmcmS-yrriRe{border-top-left-radius:4px;border-top-left-radius:var(--mdc-shape-small,4px);border-top-right-radius:4px;border-top-right-radius:var(--mdc-shape-small,4px);border-bottom-right-radius:0;border-bottom-left-radius:0;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-align:baseline;-webkit-align-items:baseline;align-items:baseline;padding:0 16px;position:relative;-webkit-box-sizing:border-box;box-sizing:border-box;overflow:hidden;will-change:opacity,transform,color}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NLUYnc-V67aGc{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd{color:rgba(0,0,0,.87)}@media all{.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-moz-placeholder{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd::placeholder{color:rgba(0,0,0,.54)}}@media all{.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{color:rgba(0,0,0,.54)}}.VfPpkd-fmcmS-yrriRe .VfPpkd-fmcmS-wGMbrd{caret-color:#6200ee;caret-color:var(--mdc-theme-primary,#6200ee)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-W0vJo-fmcmS{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd,.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me)+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-M1Soyc{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-TvZj5c-OWXEXe-UbuQg{color:rgba(0,0,0,.54)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{color:rgba(0,0,0,.6)}.VfPpkd-fmcmS-yrriRe .VfPpkd-NLUYnc-V67aGc{top:50%;-webkit-transform:translateY(-50%);-ms-transform:translateY(-50%);transform:translateY(-50%);pointer-events:none}.VfPpkd-fmcmS-wGMbrd{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-family:Roboto,sans-serif;font-family:var(--mdc-typography-subtitle1-font-family,var(--mdc-typography-font-family,Roboto,sans-serif));font-size:1rem;font-size:var(--mdc-typography-subtitle1-font-size,1rem);font-weight:400;font-weight:var(--mdc-typography-subtitle1-font-weight,400);letter-spacing:.009375em;letter-spacing:var(--mdc-typography-subtitle1-letter-spacing,.009375em);text-decoration:inherit;-webkit-text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-transform:inherit;text-transform:var(--mdc-typography-subtitle1-text-transform,inherit);height:28px;-webkit-transition:opacity .15s 0ms cubic-bezier(.4,0,.2,1);transition:opacity .15s 0ms cubic-bezier(.4,0,.2,1);width:100%;min-width:0;border:none;border-radius:0;background:none;-webkit-appearance:none;-moz-appearance:none;appearance:none;padding:0}.VfPpkd-fmcmS-wGMbrd::-ms-clear{display:none}.VfPpkd-fmcmS-wGMbrd::-webkit-calendar-picker-indicator{display:none}.VfPpkd-fmcmS-wGMbrd:focus{outline:none}.VfPpkd-fmcmS-wGMbrd:invalid{-webkit-box-shadow:none;box-shadow:none}@media all{.VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{-webkit-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}.VfPpkd-fmcmS-wGMbrd::-moz-placeholder{-moz-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}.VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{-ms-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}.VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{-ms-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}.VfPpkd-fmcmS-wGMbrd::placeholder{-webkit-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}}@media all{.VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{-ms-transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);transition:opacity 67ms 0ms cubic-bezier(.4,0,.2,1);opacity:0}}@media all{.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder, .VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd::-webkit-input-placeholder{-webkit-transition-delay:40ms;transition-delay:40ms;-webkit-transition-duration:.11s;transition-duration:.11s;opacity:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd::-moz-placeholder, .VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd::-moz-placeholder{transition-delay:40ms;transition-duration:.11s;opacity:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder, .VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{transition-delay:40ms;transition-duration:.11s;opacity:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder, .VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd::-ms-input-placeholder{transition-delay:40ms;transition-duration:.11s;opacity:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd::placeholder,.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd::placeholder{-webkit-transition-delay:40ms;transition-delay:40ms;-webkit-transition-duration:.11s;transition-duration:.11s;opacity:1}}@media all{.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder,.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-fmcmS-wGMbrd:-ms-input-placeholder{transition-delay:40ms;transition-duration:.11s;opacity:1}}.VfPpkd-fmcmS-MvKemf{-moz-osx-font-smoothing:grayscale;-webkit-font-smoothing:antialiased;font-family:Roboto,sans-serif;font-family:var(--mdc-typography-subtitle1-font-family,var(--mdc-typography-font-family,Roboto,sans-serif));font-size:1rem;font-size:var(--mdc-typography-subtitle1-font-size,1rem);font-weight:400;font-weight:var(--mdc-typography-subtitle1-font-weight,400);letter-spacing:.009375em;letter-spacing:var(--mdc-typography-subtitle1-letter-spacing,.009375em);text-decoration:inherit;-webkit-text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-decoration:var(--mdc-typography-subtitle1-text-decoration,inherit);text-transform:inherit;text-transform:var(--mdc-typography-subtitle1-text-transform,inherit);height:28px;-webkit-transition:opacity .15s 0ms cubic-bezier(.4,0,.2,1);transition:opacity .15s 0ms cubic-bezier(.4,0,.2,1);opacity:0;white-space:nowrap}.VfPpkd-fmcmS-yrriRe-OWXEXe-V67aGc-NLUYnc .VfPpkd-fmcmS-MvKemf,.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-MvKemf{opacity:1}@supports (-webkit-hyphens:none){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-MvKemf{-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-align-self:center;align-self:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;height:100%}}.VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{padding-left:0;padding-right:2px}[dir=rtl] .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c,.VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c[dir=rtl]{padding-left:2px;padding-right:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c{padding-left:0;padding-right:12px}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c,.VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-qdIk2c[dir=rtl]{padding-left:12px;padding-right:0}.VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{padding-left:12px;padding-right:0}[dir=rtl] .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB,.VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB[dir=rtl]{padding-left:0;padding-right:12px}.VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB{padding-left:2px;padding-right:0}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB,.VfPpkd-fmcmS-yrriRe-OWXEXe-CpWD9d-KW5YQd .VfPpkd-fmcmS-MvKemf-OWXEXe-iJ4yB[dir=rtl]{padding-left:0;padding-right:2px}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be{height:56px}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-OyKIhb::after{background-color:rgba(0,0,0,.87);background-color:var(--mdc-ripple-color,rgba(0,0,0,.87))}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:hover .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-XxIAqe-OWXEXe-ZmdkE .VfPpkd-fmcmS-OyKIhb::before{opacity:.04;opacity:var(--mdc-ripple-hover-opacity,.04)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-ksKsZd-mWPk3d-OWXEXe-AHe6Kc-XpnDCe .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:not(.VfPpkd-ksKsZd-mWPk3d):focus .VfPpkd-fmcmS-OyKIhb::before{-webkit-transition-duration:75ms;transition-duration:75ms;opacity:.12;opacity:var(--mdc-ripple-focus-opacity,.12)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be::before{display:inline-block;width:0;height:40px;content:"";vertical-align:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me){background-color:rgb(244.8,244.8,244.8)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-RWgCYc-ksKsZd::before{border-bottom-color:rgba(0,0,0,.42)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):hover .VfPpkd-RWgCYc-ksKsZd::before{border-bottom-color:rgba(0,0,0,.87)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-RWgCYc-ksKsZd::after{border-bottom-color:#6200ee;border-bottom-color:var(--mdc-theme-primary,#6200ee)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc{left:16px;right:auto}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc[dir=rtl]{left:auto;right:16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-106%) scale(.75);-ms-transform:translateY(-106%) scale(.75);transform:translateY(-106%) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd{height:100%}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-NLUYnc-V67aGc{display:none}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc::before{display:none}@supports (-webkit-hyphens:none){.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-MvKemf{-webkit-box-align:center;-webkit-align-items:center;align-items:center;-webkit-align-self:center;align-self:center;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;height:100%}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc{height:56px;overflow:visible}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-37.25px) scale(1);-ms-transform:translateY(-37.25px) scale(1);transform:translateY(-37.25px) scale(1)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-34.75px) scale(.75);-ms-transform:translateY(-34.75px) scale(.75);transform:translateY(-34.75px) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:.75rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:1rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-text-field-outlined .25s 1;animation:mdc-floating-label-shake-float-above-text-field-outlined .25s 1}@-webkit-keyframes mdc-floating-label-shake-float-above-text-field-outlined{0%{-webkit-transform:translateX(0) translateY(-34.75px) scale(.75);transform:translateX(0) translateY(-34.75px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-34.75px) scale(.75);transform:translateX(4%) translateY(-34.75px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-34.75px) scale(.75);transform:translateX(-4%) translateY(-34.75px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-34.75px) scale(.75);transform:translateX(0) translateY(-34.75px) scale(.75)}}@keyframes mdc-floating-label-shake-float-above-text-field-outlined{0%{-webkit-transform:translateX(0) translateY(-34.75px) scale(.75);transform:translateX(0) translateY(-34.75px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-34.75px) scale(.75);transform:translateX(4%) translateY(-34.75px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-34.75px) scale(.75);transform:translateX(-4%) translateY(-34.75px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-34.75px) scale(.75);transform:translateX(0) translateY(-34.75px) scale(.75)}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-wGMbrd{height:100%}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me) .VfPpkd-NSFCdd-MpmGFe{border-color:rgba(0,0,0,.38)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me):not(.VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe):hover .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe{border-color:rgba(0,0,0,.87)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me).VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me).VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-NSFCdd-Ra9xwd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc:not(.VfPpkd-fmcmS-yrriRe-OWXEXe-OWB6Me).VfPpkd-fmcmS-yrriRe-OWXEXe-XpnDCe .VfPpkd-NSFCdd-MpmGFe{border-color:#6200ee;border-color:var(--mdc-theme-primary,#6200ee)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb{border-top-left-radius:4px;border-top-left-radius:var(--mdc-shape-small,4px);border-top-right-radius:0;border-bottom-right-radius:0;border-bottom-left-radius:4px;border-bottom-left-radius:var(--mdc-shape-small,4px)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb[dir=rtl]{border-top-left-radius:0;border-top-right-radius:4px;border-top-right-radius:var(--mdc-shape-small,4px);border-bottom-right-radius:4px;border-bottom-right-radius:var(--mdc-shape-small,4px);border-bottom-left-radius:0}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Brv4Fb{width:max(12px,var(--mdc-shape-small,4px))}}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-Ra9xwd{max-width:calc(100% - max(12px, var(--mdc-shape-small, 4px))*2)}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe{border-top-left-radius:0;border-top-right-radius:4px;border-top-right-radius:var(--mdc-shape-small,4px);border-bottom-right-radius:4px;border-bottom-right-radius:var(--mdc-shape-small,4px);border-bottom-left-radius:0}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e .VfPpkd-NSFCdd-MpmGFe[dir=rtl]{border-top-left-radius:4px;border-top-left-radius:var(--mdc-shape-small,4px);border-top-right-radius:0;border-bottom-right-radius:0;border-bottom-left-radius:4px;border-bottom-left-radius:var(--mdc-shape-small,4px)}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc{padding-left:max(16px,calc(var(--mdc-shape-small, 4px) + 4px))}}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc{padding-right:max(16px,var(--mdc-shape-small,4px))}}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc{padding-left:max(16px,calc(var(--mdc-shape-small, 4px) + 4px))}}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc+.VfPpkd-fmcmS-yrriRe-W0vJo-RWgCYc{padding-right:max(16px,var(--mdc-shape-small,4px))}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c{padding-left:0}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c{padding-right:max(16px,var(--mdc-shape-small,4px))}}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c[dir=rtl]{padding-right:0}@supports (top:max(0%)){[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c[dir=rtl]{padding-left:max(16px,var(--mdc-shape-small,4px))}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c{padding-right:0}@supports (top:max(0%)){.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c{padding-left:max(16px,calc(var(--mdc-shape-small, 4px) + 4px))}}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c[dir=rtl]{padding-left:0}@supports (top:max(0%)){[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c[dir=rtl]{padding-right:max(16px,calc(var(--mdc-shape-small, 4px) + 4px))}}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-UbuQg-Bz112c{padding-left:0;padding-right:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd{padding-top:1px}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-OyKIhb::before,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-OyKIhb::after{background-color:transparent;background-color:var(--mdc-ripple-color,transparent)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc{left:4px;right:auto}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc[dir=rtl]{left:auto;right:4px}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-wGMbrd{display:-webkit-box;display:-webkit-flex;display:flex;border:none!important;background-color:transparent}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e{z-index:1}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od{-webkit-box-orient:vertical;-webkit-box-direction:normal;-webkit-flex-direction:column;flex-direction:column;-webkit-box-align:center;-webkit-align-items:center;align-items:center;width:auto;height:auto;padding:0;-webkit-transition:none;transition:none}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od .VfPpkd-NLUYnc-V67aGc{top:19px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od .VfPpkd-NLUYnc-V67aGc:not(.VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe){-webkit-transform:none;-ms-transform:none;transform:none}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od .VfPpkd-fmcmS-wGMbrd{-webkit-box-flex:1;-webkit-flex-grow:1;flex-grow:1;height:auto;min-height:1.5rem;overflow-x:hidden;overflow-y:auto;-webkit-box-sizing:border-box;box-sizing:border-box;resize:none;padding:0 16px;line-height:1.5rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be::before{display:none}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-10.25px) scale(.75);-ms-transform:translateY(-10.25px) scale(.75);transform:translateY(-10.25px) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-textarea-filled .25s 1;animation:mdc-floating-label-shake-float-above-textarea-filled .25s 1}@-webkit-keyframes mdc-floating-label-shake-float-above-textarea-filled{0%{-webkit-transform:translateX(0) translateY(-10.25px) scale(.75);transform:translateX(0) translateY(-10.25px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-10.25px) scale(.75);transform:translateX(4%) translateY(-10.25px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-10.25px) scale(.75);transform:translateX(-4%) translateY(-10.25px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-10.25px) scale(.75);transform:translateX(0) translateY(-10.25px) scale(.75)}}@keyframes mdc-floating-label-shake-float-above-textarea-filled{0%{-webkit-transform:translateX(0) translateY(-10.25px) scale(.75);transform:translateX(0) translateY(-10.25px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-10.25px) scale(.75);transform:translateX(4%) translateY(-10.25px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-10.25px) scale(.75);transform:translateX(-4%) translateY(-10.25px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-10.25px) scale(.75);transform:translateX(0) translateY(-10.25px) scale(.75)}}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-wGMbrd{margin-top:23px;margin-bottom:9px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be.VfPpkd-fmcmS-yrriRe-OWXEXe-di8rgd-V67aGc .VfPpkd-fmcmS-wGMbrd{margin-top:16px;margin-bottom:16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd .VfPpkd-NSFCdd-Ra9xwd{padding-top:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-27.25px) scale(1);-ms-transform:translateY(-27.25px) scale(1);transform:translateY(-27.25px) scale(1)}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-24.75px) scale(.75);-ms-transform:translateY(-24.75px) scale(.75);transform:translateY(-24.75px) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:.75rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:1rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-textarea-outlined .25s 1;animation:mdc-floating-label-shake-float-above-textarea-outlined .25s 1}@-webkit-keyframes mdc-floating-label-shake-float-above-textarea-outlined{0%{-webkit-transform:translateX(0) translateY(-24.75px) scale(.75);transform:translateX(0) translateY(-24.75px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-24.75px) scale(.75);transform:translateX(4%) translateY(-24.75px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-24.75px) scale(.75);transform:translateX(-4%) translateY(-24.75px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-24.75px) scale(.75);transform:translateX(0) translateY(-24.75px) scale(.75)}}@keyframes mdc-floating-label-shake-float-above-textarea-outlined{0%{-webkit-transform:translateX(0) translateY(-24.75px) scale(.75);transform:translateX(0) translateY(-24.75px) scale(.75)}33%{-webkit-animation-timing-function:cubic-bezier(.5,0,.701732,.495819);animation-timing-function:cubic-bezier(.5,0,.701732,.495819);-webkit-transform:translateX(4%) translateY(-24.75px) scale(.75);transform:translateX(4%) translateY(-24.75px) scale(.75)}66%{-webkit-animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);animation-timing-function:cubic-bezier(.302435,.381352,.55,.956352);-webkit-transform:translateX(-4%) translateY(-24.75px) scale(.75);transform:translateX(-4%) translateY(-24.75px) scale(.75)}100%{-webkit-transform:translateX(0) translateY(-24.75px) scale(.75);transform:translateX(0) translateY(-24.75px) scale(.75)}}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-wGMbrd{margin-top:16px;margin-bottom:16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc{top:18px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-k4Qmrd-gmhCAd .VfPpkd-fmcmS-wGMbrd{margin-bottom:2px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-k4Qmrd-gmhCAd .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{-webkit-align-self:flex-end;align-self:flex-end;padding:0 16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-k4Qmrd-gmhCAd .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd::after{display:inline-block;width:0;height:16px;content:"";vertical-align:-16px}.VfPpkd-fmcmS-yrriRe-OWXEXe-B7I4Od.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-k4Qmrd-gmhCAd .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd::before{display:none}.VfPpkd-fmcmS-kHQaff{-webkit-align-self:stretch;align-self:stretch;display:-webkit-inline-box;display:-webkit-inline-flex;display:inline-flex;-webkit-box-orient:vertical;-webkit-box-direction:normal;-webkit-flex-direction:column;flex-direction:column;-webkit-box-flex:1;-webkit-flex-grow:1;flex-grow:1;max-height:100%;max-width:100%;min-height:56px;min-width:-webkit-fit-content;min-width:-moz-fit-content;min-width:fit-content;min-width:-moz-available;min-width:-webkit-fill-available;overflow:hidden;resize:both}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-kHQaff{-webkit-transform:translateY(-1px);-ms-transform:translateY(-1px);transform:translateY(-1px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-wGMbrd,.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{-webkit-transform:translateY(1px);-ms-transform:translateY(1px);transform:translateY(1px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff{-webkit-transform:translateX(-1px) translateY(-1px);-ms-transform:translateX(-1px) translateY(-1px);transform:translateX(-1px) translateY(-1px)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff[dir=rtl]{-webkit-transform:translateX(1px) translateY(-1px);-ms-transform:translateX(1px) translateY(-1px);transform:translateX(1px) translateY(-1px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-wGMbrd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd{-webkit-transform:translateX(1px) translateY(1px);-ms-transform:translateX(1px) translateY(1px);transform:translateX(1px) translateY(1px)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-wGMbrd,[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd,.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-wGMbrd[dir=rtl],.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-fmcmS-kHQaff .VfPpkd-fmcmS-yrriRe-JZnCve-gmhCAd[dir=rtl]{-webkit-transform:translateX(-1px) translateY(1px);-ms-transform:translateX(-1px) translateY(1px);transform:translateX(-1px) translateY(1px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c{padding-left:0;padding-right:16px}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c[dir=rtl]{padding-left:16px;padding-right:0}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc{max-width:calc(100% - 48px);left:48px;right:auto}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc[dir=rtl]{left:auto;right:48px}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-MFS4be .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{max-width:calc(133.3333333333% - 85.3333333333px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc{left:36px;right:auto}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc[dir=rtl]{left:auto;right:36px}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc :not(.VfPpkd-NSFCdd-i5vt6e-OWXEXe-NSFCdd) .VfPpkd-NSFCdd-Ra9xwd{max-width:calc(100% - 60px)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-37.25px) translateX(-32px) scale(1);-ms-transform:translateY(-37.25px) translateX(-32px) scale(1);transform:translateY(-37.25px) translateX(-32px) scale(1)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe[dir=rtl]{-webkit-transform:translateY(-37.25px) translateX(32px) scale(1);-ms-transform:translateY(-37.25px) translateX(32px) scale(1);transform:translateY(-37.25px) translateX(32px) scale(1)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{-webkit-transform:translateY(-34.75px) translateX(-32px) scale(.75);-ms-transform:translateY(-34.75px) translateX(-32px) scale(.75);transform:translateY(-34.75px) translateX(-32px) scale(.75)}[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,[dir=rtl] .VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe[dir=rtl],.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe[dir=rtl]{-webkit-transform:translateY(-34.75px) translateX(32px) scale(.75);-ms-transform:translateY(-34.75px) translateX(32px) scale(.75);transform:translateY(-34.75px) translateX(32px) scale(.75)}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:.75rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc.VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe,.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NSFCdd-i5vt6e-OWXEXe-mWPk3d .VfPpkd-NLUYnc-V67aGc-OWXEXe-TATcMc-KLRBe{font-size:1rem}.VfPpkd-fmcmS-yrriRe-OWXEXe-SfQLQb-M1Soyc-Bz112c.VfPpkd-fmcmS-yrriRe-OWXEXe-INsAgc .VfPpkd-NLUYnc-V67aGc-OWXEXe-bF1zU{-webkit-animation:mdc-floating-label-shake-float-above-text-field-outlined-leading-icon .25s 1;animation:mdc-floating-label-shake-float-above-text-field-outlined-leading-icon .25s 1}@-webkit-key | 2026-01-13T09:30:04 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=af | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="r | 2026-01-13T09:30:04 |
https://play.google.com/store/apps/details?id=notion.id&hl=hr | Notion: Notes, Tasks, AI - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion: Notes, Tasks, AI Notion Labs, Inc. In-app purchases 4.8 star 327K reviews 10M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Whether you’re looking to track your personal to-do’s, write and organize class notes, or run project management with a team, Notion is the AI-powered workspace that works your way, for any need. Keep track of your personal and professional goals, take notes about what you care about, and stay organized. "AI's everything app" — Forbes Notion is a productivity app where you can write, plan, and organize your notes, projects, tasks and more - all in one place. Ask Notion AI about project updates, upcoming tasks, and suggestions for a more streamlined workflow. Simplify writing notes, project and task management, and collaboration. Whether for personal, student or professional use, Notion scales to meet your individual needs with customization tools for everyone. FREE FOR PERSONAL USE • Create as many notes, docs, and content as you want. • Use one of thousands of templates to get started. FREE TO TRY WITH YOUR TEAM • Millions run on Notion every day, from next-generation startups to established enterprises. • Import Google Docs, PDFs, and other content types easily to get started • Write and organize meeting notes, or transcribe with AI. • Collaboration and team work at your fingertips, in one connected workspace. • Connect tools like Figma, Slack, and GitHub to Notion. FREE FOR STUDENTS • Your study planner, class notes, to do lists and more, your way. Loved by millions of students worldwide. • Get organized for your best school year yet with beautiful, customizable templates created by students, for students. NOTES & DOCS Communication is made efficient with Notion's flexible building blocks. • Create docs with beautiful templates, images, to-dos, and 50+ more content types. • Meeting notes, projects, design systems, pitch decks, and more. • Find exactly what you need using Search with powerful filters to find content across your workspace. TASKS & PROJECTS Catch all details big and small in any workflow. • Workflow manager: Create your own priority labels, status tags, and automations to choose the exact info you want to track. • Capture every detail in a table. Break projects into manageable tasks to get the work done. AI One tool that does it all - search, generate, analyze, and chat - right inside Notion. • Write better. Use Notion AI to help write and brainstorm. • Get answers. Ask Notion AI questions about all your content and get answers in seconds. • Autofill tables. Notion AI turns overwhelming data into clear, actionable information — automatically. SYNCS WITH BROWSER, MAC, AND WINDOWS APPS. • Pick up on mobile where you left off on desktop. MORE PRODUCTIVITY. FEWER TOOLS. • Track to-dos, write notes, create docs, and manage projects in one connected workspace. THINK IT. MAKE IT. Updated on Jan 13, 2026 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, Photos and videos and 5 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.8 319K reviews 5 4 3 2 1 Sommy Nriama more_vert Flag inappropriate Show review history <path d="M12 17.27L1 | 2026-01-13T09:30:04 |
https://www.telerik.com/support/whats-new/teststudio | What's New in Test Studio Automated Testing Software | Telerik skip navigation Telerik Test Studio Product Bundles DevCraft All Telerik .NET tools and Kendo UI JavaScript components in one package. Now enhanced with: MCP Servers Embedded Reporting Document Processing Libraries SSO Account Sign-in Web Kendo UI UI for Angular UI for Vue UI for jQuery KendoReact UI for Blazor UI for ASP.NET Core UI for ASP.NET MVC UI for ASP.NET AJAX Mobile UI for .NET MAUI Document Management Telerik Document Processing Desktop UI for .NET MAUI UI for WinUI UI for WinForms UI for WPF Reporting Telerik Reporting Telerik Report Server Testing & Mocking Test Studio Telerik JustMock CMS Sitefinity AI Productivity Tools MCP Servers UI/UX Tools ThemeBuilder Design System Kit Templates and Building Blocks Debugging Fiddler Fiddler Everywhere Fiddler Classic Fiddler Everywhere Reporter FiddlerCore Free Tools KendoReact Free VB.NET to C# Converter Testing Framework View all products Overview Solutions Functional UI Testing RESTful API Testing Load Testing Remote Test Execution Agile Teams Web Test Automation Desktop Test Automation Responsive UI Testing Continuous Testing Training Resources Docs and Support Documentation Virtual Classroom Videos Blogs Webinars Whitepapers Case Studies Feedback Portal Technical Support What’s New Roadmap Release Notes Trust Center FAQs Pricing Shopping cart Your Account Account Overview Your Licenses Downloads Support Center Forum Profile Payment Methods Edit Profile Log out Login Contact Us Request a demo Try now close mobile menu Test Studio What's New What's New History Improved Desktop Testing Our latest update introduces the Capture Window and Inspection Point steps for Desktop Testing, enhancing your test automation workflow. The first one allows you to seamlessly capture a screenshot of your application while the Inspection Point helps you debug your application by pausing the test execution and letting you explore the visual tree in the current state of the application. Whether you're automating complex desktop applications or fine-tuning your testing process, these tools provide greater control and stability in your automated testing environment. Enhanced Salesforce Support We're excited to announce support for the latest Salesforce Lightning components' shadow DOM. This enhancement allows you to interact with and automate Salesforce Lightning components that utilize shadow DOM, ensuring accurate and reliable testing of these modern web elements. With this update, your test scripts can now effectively traverse and validate the encapsulated elements within the shadow DOM, providing you with robust and comprehensive testing capabilities for Salesforce Lightning applications. Improved OCR Recognition We've enhanced our Optical Character Recognition (OCR) capabilities with improved accuracy in situations where text and background colors are similar. This update ensures that your automated tests can reliably detect and interpret text even in challenging visual environments, where previous versions might have struggled. With this improvement, you can expect more precise text recognition and validation across a broader range of scenarios, leading to more reliable and effective test results. Improved Scheduling-Related Services Test Studio’s Scheduling feature allows you to configure a set of machines that can execute your automated tests unattended in parallel or all together. The results generated from the scheduled test runs are stored in a centralized location allowing anyone on the team to review them inside Test Studio or in the Executive Dashboard’s web interface. In Test Studio Q1 2024 the communication between these services is being improved. There are additional options to further harden your test environment including the ability to create and import your own custom Scheduling communication encryption. You can also use reverse proxy with client certificate authentication enabled. A Set of New Desktop and WPF Testing Steps and Options B ased on customer feedback and needs we’ve added some new Desktop testing steps and options. These new additions provide more flexibility and productivity while testing desktop applications. The new additions are: • “Do not launch application” option for Desktop tests. • “Scroll to element” step for Desktop tests. • “Launch process” step for Desktop tests. • “Connect to application” step for Desktop tests • “Type text” step for Desktop test. • “Scroll to element” step for WPF tests. • “Connect to application” step for WPF tests. Ongoing bug fixing Test Studio is dedicated to continuously delivering a highly reliable, high performing tool which provides solutions to your testing issues. Our collaborative teams are committed to following through each and every bug report by our customers in order to ensure the ongoing stability of the product, and the resolution of all issues. It’s a daily process which involves identifying, prioritizing, and addressing issues or glitches reported by users or discovered during testing. Regular bug fixing not only enhances the user experience but also bolsters the overall quality of the software. It is an ongoing and essential process to deliver a reliable and bug-free product, reflecting a commitment to excellence and customer satisfaction. Test Studio Product overview Download Free Trial New features & Roadmap What's New Roadmap Release History Have a feature request? Post your feedback via the Test Studio UserVoice portal or the Public forums What's new across all Telerik products? See the updates Previous Product Releases 2024 Q1 R3 2023 R2 2023 Detailed Release Notes List for the Past 19 Years See History Next Steps Schedule a Personal Demo Hosted by our product experts. Browse Pricing Plans Check out the offers. Download Free Trial With dedicated technical support. Complete .NET Toolbox Telerik DevCraft Complete JavaScript Toolbox Kendo UI Get Products Free Trials Pricing Resources DX Hub Demos Documentation Release History Forums Blogs Webinars Videos Professional Services Partners Virtual Classroom Events FAQs Recognition Success Stories Testimonials Get in touch Contact Us USA: +1 888 679 0442 UK: +44 13 4483 8186 India: +91 406 9019447 Bulgaria: +359 2 8099850 Australia: +61 3 7068 8610 165k+ 50k+ 17k+ 4k+ 14k+ Contact Us 165k+ 50k+ 17k+ 4k+ 14k+ Telerik and Kendo UI are part of Progress product portfolio. Progress is the leading provider of application development and digital experience technologies. Company Technology Awards Press Releases Media Coverage Careers Offices Company Technology Awards Press Releases Media Coverage Careers Offices Copyright © 2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved. Progress and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings. All rights in any other trademarks contained herein are reserved by their respective owners and their inclusion does not imply an endorsement, affiliation, or sponsorship as between Progress and the respective owners. Terms of Use Site Feedback Privacy Center Trust Center Do Not Sell or Share My Personal Information Powered by Progress Sitefinity | 2026-01-13T09:30:04 |
https://www.telerik.com/teststudio/test-studio-runtime | Scale Your Test Lab with Remote Test Execution | Test Studio Run-Time skip navigation Telerik Test Studio Product Bundles DevCraft All Telerik .NET tools and Kendo UI JavaScript components in one package. Now enhanced with: MCP Servers Embedded Reporting Document Processing Libraries SSO Account Sign-in Web Kendo UI UI for Angular UI for Vue UI for jQuery KendoReact UI for Blazor UI for ASP.NET Core UI for ASP.NET MVC UI for ASP.NET AJAX Mobile UI for .NET MAUI Document Management Telerik Document Processing Desktop UI for .NET MAUI UI for WinUI UI for WinForms UI for WPF Reporting Telerik Reporting Telerik Report Server Testing & Mocking Test Studio Telerik JustMock CMS Sitefinity AI Productivity Tools MCP Servers UI/UX Tools ThemeBuilder Design System Kit Templates and Building Blocks Debugging Fiddler Fiddler Everywhere Fiddler Classic Fiddler Everywhere Reporter FiddlerCore Free Tools KendoReact Free VB.NET to C# Converter Testing Framework View all products Overview Solutions Functional UI Testing RESTful API Testing Load Testing Remote Test Execution Agile Teams Web Test Automation Desktop Test Automation Responsive UI Testing Continuous Testing Training Resources Docs and Support Documentation Virtual Classroom Videos Blogs Webinars Whitepapers Case Studies Feedback Portal Technical Support What’s New Roadmap Release Notes Trust Center FAQs Pricing Shopping cart Your Account Account Overview Your Licenses Downloads Support Center Forum Profile Payment Methods Edit Profile Log out Login Contact Us Request a demo Try now close mobile menu Remote Test Execution with Test Studio Run-Time Build powerful test labs by creating tests locally and executing them in different environments, on different servers or remote machines using Test Studio Run-Time Add-on. Check out this short video to learn more about Test Studio Run-Time. How to Use Test Studio Run-Time for Test Execution Run tests remotely—on-demand or scheduled Test Studio Ultimate and Web & Desktop Editions automatically detect remote machines with the Run-Time Add-on installed. This allows testers to easily kick-off or schedule test runs on remote systems from within Test Studio. Increase test coverage by creating a powerful test execution matrix Executing UI tests involves simulating browser actions with the mouse or keyboard or sometimes taking screenshots of the current application UI state. Running a test on your local machine blocks your environment resulting in unnecessary waiting for the tests to execute before you can do anything. Using remote test execution will solve this and other challenges associated with scaling your test lab. See example scenario below on the diagram showcasing Test Studio's remote testing architecture. Speed up test execution with distributed tests If running tests in a linear manner is taking too long, slowing down your test execution workflows and impacting overall velocity, simply install Test Studio Run-Time Add-on on a number of servers and distribute your tests for much faster, parallel test execution. Integrate with your continuous integration environment With Run-Time installed on your build servers, agents, and test controllers, you’ll be able to leverage the included test runner to execute tests as part of your build process and continuous integration environment. For detailed information on configuring your build server , check out our technical documentation. Test Studio CI setup Create batch operations and more via command line test runner Run-Time Add-on also includes a powerful command-line test runner complete with parameters that allow you to specify tests, test lists, output / results path, and a number of other custom options. The flexibility of this runner, allows organizations to create batch operations custom to their unique needs. Profile remote servers for load and performance testing Install Run-Time Add-on on remote servers to allow Test Studio to monitor server’s performance as your load or performance tests execute. When configured, Test Studio will overlay this profiling information atop your results so you have all the relevant information in a single, easy-to-analyze report. Scale load tests by adding more Agents For large scale load tests, you will want to distribute the virtual user generation across multiple Agents to increase throughput. Simply install Run-Time on each server you’ll use as an Agent and Test Studio will distribute the load generation accordingly. Licensing and additional information Test Studio Run-Time is an Add-on to Test Studio Ultimate and Test Studio Web & Desktop license editions. Each Test Studio Ultimate license comes with one free Run-Time Add-on. All further Run-Time licenses you need to set up your environment are subject to a separate purchase. Please note that you should always keep versioning in sync. Test Studio Run-Time cannot be used to create or edit tests. Licensing is managed on per-machine basis. Each VM is considered a machine and should be licensed. For further questions about ordering, licensing and product delivery check out our Purchase & Licensing FAQ . For additional information, please contact your sales professional or check the links below. Support and Learning Case Study RevSpring Delivers Higher Quality Releases in a 1/4 of the Time with Test Studio Whitepaper From Manual to Automated Testing Blogs 5 Development Best Practices That Will Help You Craft Better Tests Start here Getting Started Training Professional Services What's New Case Studies Support Resources Documentation Blogs Release History Community Forums Feedback Portal Next Steps Explore Test Studio See detailed description of the Test Studio automation platform. Request a Demo See Test Studio in action in a personalized demo hosted by our automation engineers. Complete .NET Toolbox Telerik DevCraft Complete JavaScript Toolbox Kendo UI Get Products Free Trials Pricing Resources DX Hub Demos Documentation Release History Forums Blogs Webinars Videos Professional Services Partners Virtual Classroom Events FAQs Recognition Success Stories Testimonials Get in touch Contact Us USA: +1 888 679 0442 UK: +44 13 4483 8186 India: +91 406 9019447 Bulgaria: +359 2 8099850 Australia: +61 3 7068 8610 165k+ 50k+ 17k+ 4k+ 14k+ Contact Us 165k+ 50k+ 17k+ 4k+ 14k+ Telerik and Kendo UI are part of Progress product portfolio. Progress is the leading provider of application development and digital experience technologies. Company Technology Awards Press Releases Media Coverage Careers Offices Company Technology Awards Press Releases Media Coverage Careers Offices Copyright © 2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved. Progress and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings. All rights in any other trademarks contained herein are reserved by their respective owners and their inclusion does not imply an endorsement, affiliation, or sponsorship as between Progress and the respective owners. Terms of Use Site Feedback Privacy Center Trust Center Do Not Sell or Share My Personal Information Powered by Progress Sitefinity | 2026-01-13T09:30:04 |
https://www.telerik.com/teststudio/web-testing | Web Application Testing with Test Studio skip navigation Telerik Test Studio Product Bundles DevCraft All Telerik .NET tools and Kendo UI JavaScript components in one package. Now enhanced with: MCP Servers Embedded Reporting Document Processing Libraries SSO Account Sign-in Web Kendo UI UI for Angular UI for Vue UI for jQuery KendoReact UI for Blazor UI for ASP.NET Core UI for ASP.NET MVC UI for ASP.NET AJAX Mobile UI for .NET MAUI Document Management Telerik Document Processing Desktop UI for .NET MAUI UI for WinUI UI for WinForms UI for WPF Reporting Telerik Reporting Telerik Report Server Testing & Mocking Test Studio Telerik JustMock CMS Sitefinity AI Productivity Tools MCP Servers UI/UX Tools ThemeBuilder Design System Kit Templates and Building Blocks Debugging Fiddler Fiddler Everywhere Fiddler Classic Fiddler Everywhere Reporter FiddlerCore Free Tools KendoReact Free VB.NET to C# Converter Testing Framework View all products Overview Solutions Functional UI Testing RESTful API Testing Load Testing Remote Test Execution Agile Teams Web Test Automation Desktop Test Automation Responsive UI Testing Continuous Testing Training Resources Docs and Support Documentation Virtual Classroom Videos Blogs Webinars Whitepapers Case Studies Feedback Portal Technical Support What’s New Roadmap Release Notes Trust Center FAQs Pricing Shopping cart Your Account Account Overview Your Licenses Downloads Support Center Forum Profile Payment Methods Edit Profile Log out Login Contact Us Request a demo Try now close mobile menu Build Robust and Easily Maintainable Web Testing Suites Web automation with Test Studio helps you deploy defect-free web applications across any web technology, covering all your web testing needs—functional, API and load testing. Best-in-class visual test recorder with cross-browser test execution Web-based test results and reports at your ease, including executive dashboard summary Responsive cross-browser web testing without repetitive manual tasks or device switching Explore All Features What Is Web Testing? Fuctional Requirements Input Data Actual vs. Expected Behaviour Validations User Acceptance End-to-End Smoke Regression Unit UI API Integration ASP.NET MVC ASP.NET Ajax ASP.NET Core Blazor PHP jQuery React Angular TESTING TYPES APPLICATION UNDER TEST Web UI Testing Definition Web testing is a software testing practice that ensures applications running in a web browser behave as expected, regardless of browser version, device or form factor. Web testing uncovers defects such as functional variances, security and integration issues, browser version discrepancies, load-related deviations, etc. Web testing verifies: Consistent web UI on multiple browsers or browser versions Responsive application behavior and browser compatibility testing Seamless user transactions based on form validation, API calls, HTML/CSS validation How to Automate Web Tests with Test Studio? Test Studio provides a full suite of web testing tools with different automated web UI testing features and techniques, including web application test recording, cross-browser testing, test scheduling, remote test execution and automated test runs with multiple browsers like IE, Firefox, Edge and Chrome. Broad web technology and framework support Low-code web testing IDE plus out-of-the-box Visual Studio integration Industry-leading functional testing feature set backed by API and load testing at no extra cost What You Get at a Glance Unlimited web tests for web and responsive web applications across multiple browsers Flexible pricing and licensing options without hidden costs Additional load and RESTful API testing packs included for maximum coverage Configurable remote scheduling and execution you can adapt to any deployment environment Seamless integration with source control, bug tracking tools and any CI/CD setup Access to shared web test projects for both QA and Dev through built-in Visual Studio integration Web Testing Features Intuitive Cross-Browser Test Recorder Effortlessly record test steps with highly intuitive point-and-click functionality—without writing a single line of code. For cross-browser testing, simply execute your tests against your browsers of choice. Patented Hybrid Object-Find Logic Leverage DOM-based identification and images to locate visual objects. Thanks to the first of its kind object-find logic along with centralized element management, flaky tests are a problem of the past. Test Results and Reports at Your Fingertips Get visibility into the health of your web test suite with web-based test results and reports. The Test Studio Executive Dashboard offers automation insights along with personalized results. Simple Test Debugging with Step Failure Details Monitor test stability without additional configuration. The Step Failure Details module gives you details about failed test steps along with intelligent suggestions on how to fix the most common failures. Add Web Tests to CI/CD Runs Integrate web tests into your CI pipelines to always be on top of delivery. Add web tests to test lists and schedule them to run locally, remotely or whenever you need to ensure critical functionality works as expected. The One Automation Testing Tool to Cover All Your Bases and Beyond Test Studio gives you all the functional testing tools and techniques that you need to ensure your application meets user or business expectations. Have a Question? Request a Demo What QAs Say Telerik Test Studio enables our quality assurance team to quickly identify potential bugs pre-release within the DevOps pipeline. We have been able to scale and accelerate delivery of new features while reducing our manual testing on existing functionality. The features are deep, yet easy to use. The consistent addition of new and improved features helps improve the efficiency of our testing efforts. Mike Goodwin Director of Technical Support and Quality Assurance, Kiddie Academy® Headless execution allows us to greatly reduce the overall time needed to complete a test cycle. This method also allows us to integrate Test Studio into our CI pipeline so we can run any portion of the test plan at the time of merge and/or deployment. Zachary Hansen Chief Technology Officer, Angus Energy Test Studio is a fantastic platform for anyone who's new to automated testing because it's got a very intuitive UI, but also for somebody who's highly skilled as they can immediately pick up on what Test Studio can do and make very effective use of the tool. Pete O'Grady QA Manager, RevSpring The best thing about Test Studio is easy ramp up which enables anybody to start creating tests within a few days. The centralized element repository is very comfortable, bringing down test maintenance costs. Himanshu Saraowgi QA Engineer, Pegasystems Test Studio integrated seamlessly into our automated software testing needs. Its ease-of-use is unbelievable. It does all the heavy lifting allowing the developer to focus on more in-depth testing. Gregory Hargrove Software Developer, Correct Care Solutions After using the trial for a week we increased our automated testing from 5% to 30%. Test Studio was so easy to incorporate into our existing testing environment! Tests are stable and easy to run and understand. Mark Judson Software Developer, EBSCO Industries Inc. Testing Solutions Modern applications are infinitely complex. With Test Studio you can go deeper in your testing to cover all your bases—test the behavior, responsiveness and performance of your web and WPF applications. Functional UI Testing Maximize test coverage and reduce maintenance while continually improving quality. Test Studio automatically adjusts to app changes, eliminating debt and ensuring new levels of test stability. Load testing Create complex load scenarios to inform critical decisions. Test Studio's load testing suite enables you to verify that your web app meets business needs for speed, performance, and user satisfaction. RESTful API Testing Test Studio's API testing helps you verify the integrity and reliability of your APIs. Plug API testing into CI/CD to leverage the continuous testing approach along with agile development. Responsive Testing Test Studio's features for responsive web testing offer an easy way to validate your UI against different form factors without repetitive testing, switching browser modes or devices. Support and Learning Case Study RevSpring Delivers Higher Quality Releases in a 1/4 of the Time with Test Studio Whitepaper From Manual to Automated Testing Blogs 5 Development Best Practices That Will Help You Craft Better Tests Start here Getting Started Training Professional Services What's New Case Studies Support Resources Documentation Blogs Release History Community Forums Feedback Portal Frequently Asked Questions What are the different types of web application testing? Web testing, or website testing, is verifying that your web application or website is defect-free before it is deployed and made accessible online. As applications nowadays get more complex and dynamic, using a set of APIs and services, web testing can involve checking not only the process output in the user interface, but also API calls, database inputs, client/server communication and other functionality of the application under test. Choosing the types of web application testing that are relevant for you depends on what aspects of your website or app are critical for your business and must be checked on regular basis: the functionality, usability, user interface consistency, integrations, database queries, browser compatibility, performance and security. Some of these web testing types can be combined within the same automated web tests or enhanced by one another. For example, Test Studio allows you to improve your functional web tests with API calls and thus test the integrity and reliability of your APIs calls and integrations. Verifying web functionality can involve automating test runs against different browsers, browser versions and devices, which enables you to check for browser compatibility and responsive behavior at the same time. What are the most common web testing techniques? Proving that your web application works as intended requires a test plan that integrates several testing techniques and leverages a variety of tests, each of which proves some aspect of your application is ready for deployment. The dynamics of how users interact with the web make it difficult for organizations to ensure their apps work well for most users who access them. Although browsers have become more consistent in how they render web applications, different browser versions or devices can still occasionally compromise the quality and integrity of your website. The most common web testing techniques you should consider practicing as part of your regression testing suite or whenever you build changes into the UI, include testing forms, cookies, links and redirects as well as verifying the HTML/CSS as to make sure search engines can crawl your site. Testing business workflows end-to-end is also critical to ensure that users can seamlessly complete user transactions such as logging in, checking out at payment gateways or going through a sequence of webpages to perform an action. Also, making sure that UI changes haven’t caused regressions is key for the success of each consecutive web deployment. What should I look for in web application testing tools? Many testing teams have concerns about whether they should rely on low-code/codeless testing tools and approaches to record their web and cross-browser tests or if they should use open-source libraries and code their tests from scratch. Both ways will work well for you, but which one is more effective depends on your team and organizational needs and skill set. Websites with low complexity can be automated with simple codeless test tools, some of which are free and even available online. However, as your web application and cross-browser test suite expand, these tools will hit limitations. For instance, it may become challenging to keep duplication low by reusing common steps, elements and tests or handle complex UI scenarios requiring to find specific selectors on a page. In those cases, a robust test automation tool will certainly improve your testing experience by providing you greater flexibility and the advanced testing tools that you need. Like most tools out there, Test Studio locates elements based on the DOM tree, but takes it further by adding a patented element detection system and OCR. Test Studio leverages a hybrid technology to identify objects based on both the object’s ID and image as a back-up mechanism and stores them in one centralized location. Elements can be reused across tests to simplify element management and reduce duplication of work. This combination of automation techniques helps eliminate test flakiness and reduce the test maintenance that many low-code testing tools introduce. What are the benefits of test automation for web testing? Automating web testing brings a lot of advantages as it can remove significant barriers that stand in the way of performing thorough and comprehensive website testing: Time efficiencies: Web automation as an opposite to manual web testing saves time that can be dedicated to other important tasks, such as building and maintaining a stable and robust web test suite instead of going through all test cases manually each time a change is introduced to the web UI. Web regression testing is also a time-consuming activity that, when automated, can take care of tedious repetitive tasks, eliminate work duplication and free up time for in-depth exploratory or new feature testing, ensuring product increment delivery happens on time. Test coverage: Testing your web for discrepancies across browsers, browser versions, operating systems, form factors and devices requires you to run the same tests against various scenarios to accommodate all conditions. The more complex the web app is, the bigger the number of test scenarios you need to cover becomes. Recording a test and running it against all varying conditions saves a lot of time while you ensure appropriate coverage of all test scenarios that are critical for your business. Test maintenance: As web applications get more complex and dynamic, end-to-end web tests tend to be the hardest to keep up to date. If you’re using low-level CSS selectors to look for specific elements on the page, every little change to the DOM will result in dozens of broken tests. Test Studio includes a hybrid element-detection logic that can find elements based on complex selector queries and, when needed, images. That is why your tests are less likely to break when you update your page’s hierarchy. This takes a considerable burden off your team and reduces the test maintenance to a minimum, allowing you to focus on more important tasks. What is the difference between web testing and desktop testing? Web apps are hosted on a remote server and run in a web browser, allowing users with internet connection to access them from anywhere. Desktop applications run locally on a desktop (Windows) operating system and can be accessed on personal or remote machines. Based on that, there are several differences in the tools and techniques required to test a web vs. desktop app: Testing environment setup: In desktop testing, the number of clients and servers is specified, while for web apps it is critical to test the application’s behavior, performance and cross browser compatibility under different operating systems. Test results monitoring: Test monitoring complexity is different for desktop vs. web application testing. In web testing, it is critical to monitor how your web tests perform across a variety of browsers, browser versions, mobile devices, form factors, etc., while in desktop testing you only need visibility into how the app behaves under a specific operating system when used by a single user or a limited number of users. Security and access authentication: Desktop applications run as part of closed and secured environments while web apps are exposed to higher security risks. Due to the use of various authentication methods and protocols, an important aspect of end-to-end web testing is to make sure that users can access the application. Which web applications can be automated with Test Studio? Test Studio can be used to automate practically anything that runs on the web, regardless if it is .NET or JavaScript based. It is also a good choice if you are looking for a tool to automate component-based applications as it supports all third-party commercial UI component libraries, such as DevExpress, Infragistics and Syncfusion. Test Studio plays particularly well with your favorite Telerik and Kendo UI components thanks to its built-in, ready-to-use translators. These are wrappers that open the element and expose the specific and custom properties, allowing you to add action and verification steps on the go. This genuinely native technology significantly cuts down testing time in component-based applications. Industry-Leading Support Expert and Timely Support Get answers to your questions directly from the developers who build this UI suite, even during your trial period. Contact support Need Evaluation Help? If you are not a developer or don't have time to evaluate our product, send us your project requirements. We will evaluate your required features and let you know how our products fit your needs. Send us your project requirements Ready to See Test Studio in Action ? Contact Us Complete .NET Toolbox Telerik DevCraft Complete JavaScript Toolbox Kendo UI Get Products Free Trials Pricing Resources DX Hub Demos Documentation Release History Forums Blogs Webinars Videos Professional Services Partners Virtual Classroom Events FAQs Recognition Success Stories Testimonials Get in touch Contact Us USA: +1 888 679 0442 UK: +44 13 4483 8186 India: +91 406 9019447 Bulgaria: +359 2 8099850 Australia: +61 3 7068 8610 165k+ 50k+ 17k+ 4k+ 14k+ Contact Us 165k+ 50k+ 17k+ 4k+ 14k+ Telerik and Kendo UI are part of Progress product portfolio. Progress is the leading provider of application development and digital experience technologies. Company Technology Awards Press Releases Media Coverage Careers Offices Company Technology Awards Press Releases Media Coverage Careers Offices Copyright © 2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved. Progress and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings. All rights in any other trademarks contained herein are reserved by their respective owners and their inclusion does not imply an endorsement, affiliation, or sponsorship as between Progress and the respective owners. Terms of Use Site Feedback Privacy Center Trust Center Do Not Sell or Share My Personal Information Powered by Progress Sitefinity Overview Definition Features Testing Solutions Resources FAQ Support Try now | 2026-01-13T09:30:04 |
https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/reviews/2127074/#login | Reviews for 1Password: Password Manager – Add-ons for Firefox (en-US) To use these add-ons, you'll need to download Firefox . Dismiss this notice Firefox Browser Add-ons Extensions Themes More… for Firefox Dictionaries & Language Packs Other Browser Sites Add-ons for Android Log in Search Search Reviews for 1Password: Password Manager 1Password: Password Manager by 1Password Rated 3.8 out of 5 3.8 Stars out of 5 5 1,033 4 182 3 108 2 106 1 342 Review by Firefox user 18646596 Rated 4 out of 5 by Firefox user 18646596 , a year ago Show all reviews Show only five-star reviews Show only four-star reviews Show only three-star reviews Show only two-star reviews Show only one-star reviews Go to Mozilla's homepage Add-ons About Firefox Add-ons Blog Extension Workshop Developer Hub Developer Policies Community Blog Forum Report a bug Review Guide Browsers Desktop Mobile Enterprise Products Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Privacy Cookies Legal Except where otherwise noted , content on this site is licensed under the Creative Commons Attribution Share-Alike License v3.0 or any later version. Change language Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T09:30:04 |
https://snyk.io/de/platform/deepcode-ai/ | DeepCode AI | KI-gestützte Code-Reviews | KI-gestützte Sicherheit für SAST | Snyk AI | Snyk You need to enable JavaScript to run this app. Skip to main content Plattform Plattform Snyk AI Trust Platform Modernste Security für alle Dev-Teams Snyk AI Workflow AppSec-Workflows mit der Power von KI DeepCode AI KI speziell für Security Integrationen Sicherheit für das gesamte SDLC Snyk Learn Learning-Inhalte zu Developer Security Preise Produkte Snyk Code Sicherheit beginnt in der IDE Snyk Open Source Keine Chance für anfällige Abhängigkeiten Snyk Container Sicherheit für Ihre Base-Images Snyk IaC In-Code-Fixing von IaC-Konfigurationsfehlern Snyk API & Web Discovery und Testing für APIs und Web-Apps Snyk Studio Fix and secure AI-generated code Lösungen Sicherheit für KI-generierten Code Unterstützung durch KI, Absicherung mit Snyk Anwendungssicherheit Sicher vom Design bis zur Delivery Sicherheit für die Software-Lieferkette Risikomitigierung in der Lieferkette Zero-Day-Schwachstellen Fixing noch am ersten Tag Security Intelligence Umfassende Insights zu Schwachstellen Code Checker Ihr Code. Kostenlos perfektioniert. Risk-Based Prioritization Fix what matters most Snyk gibt Einführung der ersten AI Trust Platform bekannt Zur On-Demand-Session Ressourcen Snyk Ressourcen Alle Ressourcen Mehr lesen in der Content-Datenbank Ressourcen für Kunden Alles zum Start mit Snyk Ethisches Hacking Chancen und Potenziale mit ethischem Hacking Vulnerability Top 10 Die wichtigsten Schwachstellen im Überblick Snyk Blog Podcast Snyk auf YouTube AI Glossary Security-Know-how & Docs Snyk Labs R&D zu KI, Schwachstellen und DevSecOps Snyk Learn Learning-Inhalte zu Security Snyk Docs Jetzt starten mit Snyk Snyk Support Unterstützung jederzeit Snyk Schwachstellen-Datenbank Aufspüren und beheben Snyk Updates Immer am Security-Puls Snyk Partner Solutions Directory Tech-Integrationen unserer Partner Snyk Community & Games Events & Webinare Snyk Ambassadors DevSecCon Community VulnVortex Zielgruppe Snyk für Developer Der Info Drop für Developer Technologien für die öffentliche Hand AppSec-Schutz für Behörden und Bürger Snyk für Security-Leader Insights von Security-Leadern Neu am Start: Snyk Labs Zur Website Unternehmen Unternehmen Snyk: Die Plattform für Developer Security Mit Snyk erhalten Sie die Transparenz, Präzision und Kontrolle, die Sie und Ihre Entwickler zur Minimierung von Anwendungsrisiken benötigen. Subscribe to our newsletter Unsere Services Konsequent mehr AppSec-ROI Unsere Kunden Das erreichen unsere Kunden mit Snyk Unsere Partner Noch besser dank starker Kooperationen Case Studies Eine Auswahl unserer Erfolgsstories Newsroom Aktuelle Pressemitteilungen Kontakt Feedback oder Fragen? Jederzeit! Karriere und Kultur Snyk als Arbeitgeber Snyk Masterclass Series Security-Insights live und on-demand Preise Evo New DE Sprache auswählen English Deutsch Español Français 日本語 Português (BR) Anmeldung Nutzer von Snyk Free oder Team Snyk app.snyk.io Nutzer von Snyk Enterprise 🇺🇸 Snyk US - 1 app.snyk.io 🇺🇸 Snyk US - 2 app.us.snyk.io 🇪🇺 Snyk EU app.eu.snyk.io 🇦🇺 Snyk AU app.au.snyk.io Hosting-Region für Ihre Daten basierend auf lokalen Vereinbarungen; kann sich von Ihrem Standort unterscheiden Mehr erfahren . Snyk API & Web - Alle Nutzer Snyk API & Web (DAST) plus.probely.app Registrieren Live-Demo buchen Snyk Plattform Plattform DeepCode AI Snyk CLI IDE-Plug-ins Sicherheit und Governance Deployment-Optionen Compliance Select Plattform DeepCode AI Snyk CLI IDE-Plug-ins Sicherheit und Governance Deployment-Optionen Compliance Snyk Agent Fix: Code-Autofixing in Sekunden mit einer Genauigkeit von 80 % – jetzt frei verfügbar. DeepCode AI: Künstliche Intelligenz von Snyk DeepCode AI ist das Ergebnis von 8 Jahren Entwicklung und wichtige Säule unserer Technologien. So entsteht das schnellste, präziseste und umfassendste Toolset für AppSec-Testing auf dem Markt. Live-Demo buchen Play Video KI konzipiert speziell für sichere Entwicklung Als Herzstück der Snyk AI Trust Plattform kombiniert DeepCode AI verschiedene Modelle künstlicher Intelligenz, die ausschließlich mit Daten aus dem Security-Bereich trainiert und von unseren Security-Experten kuratiert werden. Hierdurch entsteht eine einzigartige KI – ohne die klassischen Schwächen der Technologie. KI-generierten Code jetzt absichern KI mit Code-Security-Fokus 25 Millionen Daten-Flows, Unterstützung für mehr als 19 Programmiersprachen und einen Verbund aus mehreren KI-Modellen vereinen wir in DeepCode AI für drei klare Ziele: Schwachstellen erkennen und priorisieren, Fixes automatisch einspielen und technische Schuld abbauen. KI für mehr Produktivität DeepCode AI bildet die Grundlage für Security-Autofixing mit 80 % Genauigkeit und umfassende App-Abdeckung. Und damit für zwei der wichtigsten Tragsäulen unserer Plattform für schnelle und sichere Software-Entwicklung. KI mit Datenschutz als Kernprämisse Entwickelt wurde DeepCode AI von KI-Vordenkern bei Snyk. Verfeinert wird die Technologie fortlaufend anhand von Millionen permissiv lizenzierten Open-Source-Projekten mit verifizierten Code-Fixes – Daten unserer Kunden bleiben strikt außen vor. DeepCode AI: Die KI für Anwendungssicherheit KI auf Basis eines einzelnen Modells wie etwa im Falle von ChatGPT-4 ist durchaus beachtlich, weist jedoch Datenschutzrisiken auf und unterliegt einigen Einschränkungen. So beginnt sie etwa zu „halluzinieren“, produziert also schlicht unwahre, falsche Ergebnisse. DeepCode AI bietet KI-Code-Analysen und -Fixes und wird lokal gehostet. Es setzt auf mehrere Modelle und security-spezifische Trainingsdatensätze, die speziell für ein Ziel trainiert werden: die Absicherung von Anwendungen. Hybride KI für Security-Scans mit unerreichter Präzision Die Power von Snyk fußt auf der Knowledge Base hinter DeepCode AI, die wir nach einer branchenweit einzigartigen Methodik aufbauen: Symbolische und generative KI wird unter Anwendung verschiedener Verfahren für maschinelles Lernen kombiniert und mit dem Know-how unserer Security-Experten angereichert. Für höchste Scan-Genauigkeit ganz ohne das Risiko von Halluzinationen. Risikobasierte Priorisierung gestützt auf KI DeepCode AI sorgt für kontextgenaueres Risiko-Scoring in Snyk, indem die KI Details sowohl zur Verbreitung des betroffenen Pakets als auch zur Angreifbarkeit von anfälligem Code auswertet. Parallel dazu behält sie den Reifegrad verfügbarer Exploits fortlaufend im Blick. Nahtlose Regeldefinition mit DeepCode AI Search Gestützt auf die Logik von DeepCode AI erstellen Sie Custom-Abfragen mit Auto-Complete-Feature. Die hybride KI gibt dabei direkt Übereinstimmungen im Code aus und erleichtert so Einrichtung, Testing, Ausführung und Speicherung von Regeln umfassend. Nutzen Sie jetzt kostenlos die KI-gestützten Code-Security-Tools von Snyk Unverbindlich und ohne Kreditkarte. Kostenlos starten mit GitHub Kostenlos starten mit Google Kontoregistrierung mit BitBucket und weiteren Optionen Durch die Nutzung von Snyk stimmen Sie automatisch unseren Richtlinien zu, so etwa unseren Nutzungsbedingungen und unserer Datenschutzerklärung . „Die Welle an Innovationen, die wir derzeit rund um generative KI erleben, trifft ob ihrer Potenziale für Produktivitätssteigerungen in der Software-Entwicklung bei vielen auf Euphorie. Von meiner Security-Warte aus betrachte ich das Ganze etwas nüchterner: Ob KI-generiert oder von Entwicklern geschrieben, Code muss vor allem sicher sein. Umso wichtiger ist für mich daher die KI, die Snyk uns mit Snyk Agent Fix an die Hand gibt. Denn damit entwickeln wir Software nicht nur schneller, sondern machen sie auch sicherer.“ Steve Pugh CISO , ICE/NYSE Fokusthemen Blog DeepCode AI: Wissenschaftlicher Background Ein Blick auf symbolische und hybride KI sowie Referenzen zu Publikationen und Forschungsarbeiten für tiefergehende Einblicke. Blog lesen Blog Snyk Code ab sofort mit KI-generierten Security-Fixes Erfahren Sie mehr über die Autofix-Vorschläge für sicheren Code von Snyk Agent Fix. Blog lesen Blog KI-gestützt zu sicherer KI KI-Modelle zur Verarbeitung natürlicher Sprache wie das von ChatGPT-4 beeindrucken durchaus. Für Security sind jedoch hybride KI-Ansätze gefragt. Blog lesen Dokumentation Snyk IDE-Plug-in für Auto-Fixing direkt am Code Code-Scans und Autofixing in Sekunden – ohne negativen Einfluss auf den Developer Flow. Mehr erfahren Anwendungssicherheit für das KI-Zeitalter Mit DeepCode AI, dem KI-Tooling der Snyk Plattform, steigern Sie sowohl Developer-Produktivität als auch Sicherheit und beheben Fehler in 16 % der Zeit. Kostenlos starten Live-Demo buchen Plattform Snyk AI Trust Platform Snyk AI Workflow DeepCode AI Integrationen Snyk Ressourcen Alle Ressourcen Blog Podcast Security-Know-how & Docs Snyk Labs Snyk Learn Snyk Docs Snyk Support Snyk Schwachstellen-Datenbank Snyk Updates Snyk Trust Center Unternehmen & Community Über Snyk Kontakt Demo buchen Karriere und Kultur Events & Webinare Snyk Ambassadors Warum Snyk? Snyk vs. GitHub Advanced Security Snyk vs. Veracode Snyk vs. Checkmarx Snyk vs. Black Duck Snyk vs. Wiz Snyk: Die Plattform für Developer Security Mit Snyk erhalten Sie die Transparenz, Präzision und Kontrolle, die Sie und Ihre Entwickler zur Minimierung von Anwendungsrisiken benötigen. Subscribe to our newsletter © 2025 Snyk Limited Alle Rechte vorbehalten Nutzungsbedingungen Datenschutzhinweis Nutzungsbedingungen Für Einwohner Kaliforniens: Meine persönliche Daten dürfen nicht weiterverkauft werden. | 2026-01-13T09:30:04 |
https://play.google.com/store/apps/details?id=com.cron.calendar&hl=de_AT | Notion Calendar - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Notion Calendar Notion Labs, Inc. 4.6 star 13.7K reviews 1M+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Notion Calendar lets you schedule meetings and control your time like never before. It deeply integrates with Google Calendar accounts so that all your events are synced. Along with speed, beauty, and light/dark modes, Notion Calendar includes powerful features: - CONNECTED TO NOTION — add Notion docs, projects, and timelines. - MULTIPLE TIME ZONES — pull the time zone column to the right to “travel to any city” and add more time zones. - ALL IN ONE PLACE — see one unified view across multiple calendars and auto-sync events between them. WIDGETS — featuring multiple sizes, rich previews of upcoming events, and a quick-add event button. - AVAILABLE IN 12 LANGUAGES — Japanese, Korean, French, German, Spanish, Portuguese, Danish, Dutch, Finnish, Norwegian, and Swedish. It’s time. Updated on Jul 11, 2025 Productivity Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. This app may share these data types with third parties Personal info, App activity and 2 others This app may collect these data types Personal info, App activity and 2 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.6 13.3K reviews 5 4 3 2 1 Han more_vert Flag inappropriate January 4, 2025 The app is extremely buggy and often shuts down upon being opened so I find it hard to register new events from my phone, and I also wish we had as much ability to customize reminders like we do on desktop. That being said, I love the desktop app, and I appreciate the notifications coming thru on my phone. If I could ask for one thing, I'd love to be able to save things natively to Notion Calendar without it having to link back to a database on my notion account or my google account. 11 people found this review helpful Did you find this helpful? Yes No Isaac Connor more_vert Flag inappropriate March 15, 2025 Very nice calendar app, easy to use, nice appearance. Just a couple of issues. First, the app doesn't include all the colours that Google Calendar does, which is annoying. Also, the max days you can see at once is 3, which is far too low. A week view is a basic feature of a calendar app, not to mention a month view. 110 people found this review helpful Did you find this helpful? Yes No Jose Sierra more_vert <ul class="VfPpkd-StrnGf-rymPhb DMZ54e" jsname="rymPhb" | 2026-01-13T09:30:04 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1w9T5h4SFIM-3PmCUHPrcl-t1jb-segjkGEn4zpU67vWNthY4RTydxRIQCc8JgYepeq7aDBl0HymBVlYUfdIe8WqUBykPipderUBMoNtpsjiPXCEhOEQ5bn0VuDhbm4hgo8yTdvk4h2QfH | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:30:04 |
https://extensionworkshop.com/documentation/develop/firefox-builtin-data-consent/ | Firefox built-in consent for data collection and transmission | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Firefox built-in consent for data collection and transmission Firefox supports built-in consent for data collection and transmission in Firefox for desktop 140 and later, and Firefox for Android 142 and later. From November 3, 2025, all new extensions must adopt the Firefox built-in data collection consent system. Extensions must state if and what data they collect or transmit. New versions and updates for add-ons created before November 3 don’t need to use this feature, but will have to at a later date. For updates on the rollout and the timeline for AMO accepting submissions using this feature and for tips on how to take advantage of it, see the community blog . To use Firefox's built-in consent experience, you have to specify what data your extension collects or transmits in the extension’s manifest.json file. This information is shown to the user when they first install the extension. A user can then choose to accept or reject the data collection, just as they do with extension permissions. You can also specify that the extension collects no data. Contents Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Taxonomy Firefox uses categories to standardize data collection information for developers and users. In line with the policies , there are two types of data: Personal data and Technical and Interaction data . Personal data Personally identifiable information can be actively provided by the user or obtained through extension APIs. It includes, but isn’t limited to, names, email addresses, search terms, and browsing activity data, as well as access to and placement of cookies. Data type visible during install Data collection permission used in the manifest Definition and examples Eligible for implicit consent ? Personally identifying information personallyIdentifyingInfo Examples: contact information such as name and address, email, and phone number, as well as other identifying data such as ID numbers, voice or video recordings, age, demographic information, or biometric data. no Health information healthInfo Examples: medical history, symptoms, diagnoses, treatments, procedures, or heart rate data. no Financial and payment information financialAndPaymentInfo Examples: credit card numbers, transactions, credit ratings, financial statements, or payment history. no Authentication information authenticationInfo Examples: passwords, usernames, personal identification numbers (PINs), security questions, and registration information for extensions that offer account-based services. no Personal communications personalCommunications Examples: emails, text or chat messages, social media posts, and data from phone calls and conference calls. no Location locationInfo Examples: region, GPS coordinates, or information about things near a user’s device. yes Browsing activity browsingActivity Information about the websites users visit, such as specific URLs, domains, or categories of pages users view. yes Website content websiteContent Covers anything visible on a website — such as text, images, videos, and links — and anything embedded, such as cookies, audio, page headers, and request and response information. yes Website activity websiteActivity Examples: interactions and mouse and keyboard activity, such as scrolling, clicking, typing, and actions, such as saving and downloading. yes Search terms searchTerms Search terms entered into search engines or the browser. yes Bookmarks bookmarksInfo Information about Firefox bookmarks, including specific websites, bookmark names, and folder names. yes Technical and interaction data Technical data describes the environment the user is running, such as browser settings, platform information, and hardware properties. User interaction data includes how the user interacts with Firefox and the installed add-on, metrics for product improvement, and error information. Data type visible during install Data collection permission used in the manifest Definition and examples Technical and interaction data technicalAndInteraction Examples: Device and browser info, extension usage and settings data, crash and error reports. Specifying data types You specify the data types your extension transmits in the browser_specific_settings.gecko.data_collection_permissions key in the manifest.json file. As a reminder, the policies state that data transmission refers to any data collected, used, transferred, shared, or handled outside the add-on or the local browser. Personal data Personal data permissions can be required or optional, except for technicalAndInteraction that cannot be required: "browser_specific_settings" : { "gecko" : { "data_collection_permissions" : { "required" : [ ... ] , "optional" : [ ... ] } } } The rest of this section describes each key in the data_collection_permissions object. Required data When you specify data types in the required list, users must accept this data collection to use the extension; they cannot opt out. So the user can review the data-collection requirements of an extension before installing it, data collection information is presented to the user in the installation prompt, like this: If the user doesn’t agree to data collection, they can cancel the extension installation. This installation prompt is the result of a manifest.json file that specifies one required data type, locationInfo , and one optional data type, technicalAndInteraction . { "manifest_version" : 2 , "name" : "Example - Data collection with fallback" , "version" : "1.0.0" , "permissions" : [ "storage" , "management" ] , "browser_specific_settings" : { "gecko" : { "id" : "@example-data-collection-with-fallback" , "data_collection_permissions" : { "required" : [ "locationInfo" ] , "optional" : [ "technicalAndInteraction" ] } } } , "background" : { "scripts" : [ "background.js" ] } , "browser_action" : { } , "options_ui" : { "page" : "options/page.html" } } This adds the "required" data collection paragraph to the installation prompt. The data permissions are also listed in about:addons like this: Optional data Optional data collection permissions are specified using the optional list. These aren’t presented during installation (except for technicalAndInteraction ), and they aren’t granted by default. The extension can request that the user opts in to this data collection after installation by calling permissions.request() in a user-activated event handler, and the user can turn this optional data collection on or off in about:addons in the Permissions and data section of the extension settings. Technical and interaction data The technicalAndInteraction data type behaves differently from all other data types. This data permission must be optional, but unlike other optional data collection options, the user can turn this permission on or off during the installation flow. This choice is available in the optional settings section of the extension installation prompt. No data collection If your extension doesn’t collect or transmit any data, you indicate that by specifying the none required permission in the manifest, as follows: { "manifest_version" : 2 , "name" : "extension without data collection" , "version" : "1.0.0" , "browser_specific_settings" : { "gecko" : { "id" : "@extension-without-data-collection" , "data_collection_permissions" : { "required" : [ "none" ] } } } , "permissions" : [ "bookmarks" , "<all_urls>" ] } When a user attempts to install this extension, Firefox shows the usual installation prompt with the description of the required (API) permissions and a description to indicate that the extension doesn’t collect any data, like this: The "no data collected" type is also listed in the Permissions and data tab of the extension in about:addons , like this: Accessing the data collection permissions programmatically You use the browser.permissions API to interact with the optional data permissions. Specifically, the getAll() method returns the list of granted optional data permissions, as follows: await browser . permissions . getAll ( ) { origins : [ "<all_urls>" ] , permissions : [ "bookmarks" ] , // In this case, the permission is granted. data_collection : [ "technicalAndInteraction" ] } You use the presence or absence of the data_collection key in the getAll() method’s response to feature-detect the built-in data collection consent experience in Firefox at runtime. const perms = await browser . permissions . getAll ( ) ; if ( ! perms . data_collection ) { // no built-in data consent in Firefox } You use the browser.permissions.request() API method to get consent from users for ancillary data collection (defined in the optional list): await browser . permissions . request ( { data_collection : [ "healthInfo" ] } ) ; This call displays a message to the user, giving them the choice to opt in to this data collection, like this: Updates When an extension is updated, Firefox only shows the added required data permissions, unless it’s the special none data type, because when the extension doesn’t collect any data, that doesn’t need to be notified to the user. Testing To see how the data collection prompts appear to a user for a new install or upgrade, follow the process described in Test permission requests . Tags: data-collection data-transmission api permissions firefox guide Contributors: abyrne-moz wagnerand willdurand Last update: wagnerand Aug 04, 2025 Up Next Develop Best practices for collecting user data consents Develop Build an accessible extension Develop Onboard, upboard, offboard users Documentation Topics Develop Publish Manage Enterprise Themes Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:04 |
https://www.telerik.com/blogs/productivity-testing#skip-to-content | Testing - Productivity News for .NET & JS Developer Tooling - Telerik Blogs skip navigation Telerik Test Studio Product Bundles DevCraft All Telerik .NET tools and Kendo UI JavaScript components in one package. Now enhanced with: MCP Servers Embedded Reporting Document Processing Libraries SSO Account Sign-in Web Kendo UI UI for Angular UI for Vue UI for jQuery KendoReact UI for Blazor UI for ASP.NET Core UI for ASP.NET MVC UI for ASP.NET AJAX Mobile UI for .NET MAUI Document Management Telerik Document Processing Desktop UI for .NET MAUI UI for WinUI UI for WinForms UI for WPF Reporting Telerik Reporting Telerik Report Server Testing & Mocking Test Studio Telerik JustMock CMS Sitefinity AI Productivity Tools MCP Servers UI/UX Tools ThemeBuilder Design System Kit Templates and Building Blocks Debugging Fiddler Fiddler Everywhere Fiddler Classic Fiddler Everywhere Reporter FiddlerCore Free Tools KendoReact Free VB.NET to C# Converter Testing Framework View all products Overview Solutions Functional UI Testing RESTful API Testing Load Testing Remote Test Execution Agile Teams Web Test Automation Desktop Test Automation Responsive UI Testing Continuous Testing Training Resources Docs and Support Documentation Virtual Classroom Videos Blogs Webinars Whitepapers Case Studies Feedback Portal Technical Support What’s New Roadmap Release Notes Trust Center FAQs Pricing Shopping cart Your Account Account Overview Your Licenses Downloads Support Center Forum Profile Payment Methods Edit Profile Log out Login Contact Us Request a demo Try now close mobile menu Productivity: Testing The AI-Forward Telerik & Kendo UI 2025 Q4 Release Is Here by Iva Borisova November 19, 2025 Latest For the latest product updates, please visit Release . Web Angular Productivity Testing Unit Testing in Angular: Modern Testing with Vitest See how to use Vitest in Angular as the more modern alternative to Jasmine, Web Test Runner and Karma. by Dany Paredes June 24, 2025 7 min read Share Productivity Testing Collaborative Testing’s Impact on Application Quality Software testing teams can pack the most power when manual and automated testers work in coordination. See some tips for this. by Amy Reichert December 20, 2024 4 min read Share Productivity Testing 5 Ways to Make Your Test Automation Faster Sluggish automated test runs can significantly slow down your entire team. This article teaches you five ways you can speed up your test automation. by Dennis Martinez December 05, 2024 7 min read Share Productivity Testing Speed vs. Quality in Software Testing How does test quality affect speed, and vice versa, and could finding the balance between the two be the key to keeping customers and the business happy? by Amy Reichert November 22, 2024 6 min read Share Productivity Testing Shift-Left to Make Testing Faster Without Impacting Quality Understand the concept of shift-left testing in an Agile development process and how it helps speed up testing without reducing application quality. by Amy Reichert November 06, 2024 6 min read Share 1 2 3 4 5 6 7 8 9 10 ... Next All articles Topics Web Web Blazor ASP.NET Core ASP.NET MVC ASP.NET AJAX Angular React jQuery Vue Mobile Mobile .NET MAUI/Hybrid Desktop Desktop .NET MAUI/Blazor Hybrid WPF WinForms WinUI Design Design UX Design Systems Productivity Productivity Reporting Testing Debugging Document Processing People People Accessibility Humanity Release AI Follow us Latest Stories in Your Inbox Subscribe to be the first to get our expert-written articles and tutorials for developers! All fields are required Email Country/Territory Select country/territory United States Afghanistan Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belgium Belize Benin Bermuda Bhutan Bolivia Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Terr. Brunei Darussalam Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos (Keeling) Islands Colombia Comoros Congo (Brazzaville) Congo, the democratic republic of the Cook Islands Costa Rica Cote d'Ivoire Croatia (Hrvatska) Curacao Cyprus Czech Republic Denmark Djibouti Dominica Dominican Republic Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Eswatini Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Terr. Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard and McDonald Is. Honduras Hong Kong Hungary Iceland India Indonesia Iraq Ireland Israel Italy Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Kuwait Kyrgyzstan Lao People's Dem. Rep. Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macao Madagascar Malawi Malaysia Maldives Mali Malta Man, Isle of Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Macedonia Northern Mariana Is. Norway Oman Pakistan Palau Palestine, State Of Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Republic of Korea (South Korea) Reunion Romania Rwanda S.Georgia and S.Sandwich Is. Saint Kitts and Nevis Saint Lucia Samoa San Marino Sao Tome and Principe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Slovakia Slovenia Solomon Islands Somalia South Africa South Sudan Spain Sri Lanka St. Helena St. Pierre and Miquelon St. Vincent and Grenadines Sudan Suriname Svalbard and Jan Mayen Is. Sweden Switzerland Taiwan Tajikistan Tanzania Thailand Timor-Leste Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu U.S. Minor Outlying Is. Uganda Ukraine United Arab Emirates United Kingdom Uruguay Uzbekistan Vanuatu Vatican (Holy See) Venezuela Viet Nam Virgin Islands (British) Virgin Islands (U.S.) Wallis and Futuna Is. Western Sahara Yemen Zambia Zimbabwe State/Province Select Progress collects the Personal Information set out in our Privacy Policy and the Supplemental Privacy notice for residents of California and other US States and uses it for the purposes stated in that policy. You can also ask us not to share your Personal Information to third parties here: Do Not Sell or Share My Info Blog By submitting this form, I understand and acknowledge my data will be processed in accordance with Progress' Privacy Policy . I agree to receive marketing communications from Progress Software or its Partners , containing information about Progress Software’s products, services and/or events. I understand I may opt out from marketing communication at any time. By submitting this form, you understand and agree that your personal data will be processed by Progress Software or its Partners as described in our Privacy Policy . You may opt out from marketing communication at any time here or through the opt out option placed in the e-mail communication sent by us or our Partners. We see that you have already chosen to receive marketing materials from us. If you wish to change this at any time you may do so by clicking here . Thank you for your continued interest in Progress. Based on either your previous activity on our websites or our ongoing relationship, we will keep you updated on our products, solutions, services, company news and events. If you decide that you want to be removed from our mailing lists at any time, you can change your contact preferences by clicking here . Subscribe Complete .NET Toolbox Telerik DevCraft Complete JavaScript Toolbox Kendo UI Get Products Free Trials Pricing Resources DX Hub Demos Documentation Release History Forums Blogs Webinars Videos Professional Services Partners Virtual Classroom Events FAQs Recognition Success Stories Testimonials Get in touch Contact Us USA: +1 888 679 0442 UK: +44 13 4483 8186 India: +91 406 9019447 Bulgaria: +359 2 8099850 Australia: +61 3 7068 8610 165k+ 50k+ 17k+ 4k+ 14k+ Contact Us 165k+ 50k+ 17k+ 4k+ 14k+ Telerik and Kendo UI are part of Progress product portfolio. Progress is the leading provider of application development and digital experience technologies. Company Technology Awards Press Releases Media Coverage Careers Offices Company Technology Awards Press Releases Media Coverage Careers Offices Copyright © 2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved. Progress and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings. All rights in any other trademarks contained herein are reserved by their respective owners and their inclusion does not imply an endorsement, affiliation, or sponsorship as between Progress and the respective owners. Terms of Use Site Feedback Privacy Center Trust Center Do Not Sell or Share My Personal Information Powered by Progress Sitefinity | 2026-01-13T09:30:04 |
https://extensionworkshop.com/extension-basics/#use-the-configuration-file | Extension Basics | Firefox Extension Workshop Extension Workshop Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Submit or Manage Extensions Search Submit or Manage Extensions Search Select a section Page Name Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Extension Basics Getting started Mozilla Developer Network Documentation Topics Develop Firefox Tools User Experience Firefox for Android Port to Firefox Test and debug Getting Started Unique Firefox Capabilities Firefox Workflow Overview About the WebExtensions API Manifest V3 Manifest V3 migration guide What is Manifest V3? Manifest V3 changes Migration checklist Cross-Browser Development Browser Compatibility Namespace Asynchronous API Coverage Manifest keys More information Build cross-browser extensions Firefox Tools Build an extension in 5 minutes Browser Extension Development Tools Boilerplating tools Coding tools Testing and debugging tools Translation tools Tools for Firefox for Android Choosing a Firefox version for extension development Firefox editions Firefox version and their web extension development capabilities Getting started with web-ext Installation Update Using web-ext Check your code Test and debug Package, sign, and publish Use the configuration file Advanced topics See also web-ext v8 command reference What's new Commands web-ext build web-ext docs web-ext dump-config web-ext lint web-ext run web-ext sign Global options Setting option environment variables See also web-ext v7 command reference Commands Global options Setting option environment variables See also Web-ext Webpack plug-in Browser API Polyfill Extensions and the Add-on ID Basic workflow with no add-on ID When do you need an add-on ID? User Experience Build a secure extension Request the right permissions Introduction Advised permissions Avoid unnecessary permissions Request permissions at runtime Add information about permissions to your extensions AMO page Firefox built-in consent for data collection and transmission Taxonomy Specifying data types Accessing the data collection permissions programmatically Updates Best practices for collecting user data consents Know your privacy settings Get prepared Prompt after install Determine your consent flow Your consent dialogs Build an accessible extension Onboard, upboard, offboard users Onboarding Upboarding Offboarding User experience best practices 1. Keep it focused 2. Give users what they need, where they need it 3. Keep the user informed 4. Be Firefoxy in look and feel 5. Great onboarding experience 6. Test, test, and then test again Mobile Differences between desktop and Android extensions Introduction User interface Native application interaction Permissions Storage User experience guidelines for mobile extensions Introduction The basics The extra mile The last mile Developing extensions for Firefox for Android Set up your computer and Android emulator or device Check for Firefox for Android compatibility Install and run your extension in Firefox for Android Debug your extension Manifest V3 compatibility GeckoView Extensions (Android library) Port Your Extension Porting a Google Chrome Extension Debug and Test Debugging Developer tools toolbox Debugging background scripts Debugging options pages Debugging popups Debugging content scripts Debugging sidebars Debugging storage Debugging developer tools pages and panels Debug permission requests Debugging browser restarts Temporary Installation in Firefox Reloading a temporary extension Using the command line Detecting temporary installation Limitations Testing persistent and restart features What is an add-on ID? What is a Firefox profile? Extension behavior in Firefox What do I do to ensure I can test my extension? Test permission requests Permission grant behavior during testing Observe or verify install time permission requests Retest runtime permission grants Testing localizations Known issues Content scripts don't appear in DevTools Extension source don't update in DevTools "Destroyed actor" errors when debugging Android Publish Get your extension signed Distribute your signed extension Promote your extension Policies Add-on Policies No Surprises Content Submission Guidelines Development Practices User Scripts Data Collection and Transmission Disclosure and Control Monetization Security, Compliance and Blocking Add-on Policies FAQ No Surprises Content Submission Guidelines Data Collection and Transmission Disclosure and Control Security, Compliance and Blocking Firefox Add-on Distribution Agreement 1. Introduction 2. Accounts 3. Privacy Policy 4. Distribution, certificates, & review process 5. Your obligations 6. Licenses; proprietary rights 7. Content removal 8. Disclaimer of warranties 9. Limitation of liability 10. Release; indemnification 11. General legal terms Add-ons Blocking Process Security Over Choice Blocking Criteria Developer Outreach Requesting a Block Blocking Other Types of Third Party Software Third Party Library Usage When must links for third-party libraries be provided? How to determine the third-party library link Communicating third-party library links to reviewers What does review rejection mean to users? Review overview Impact of review rejection Blocklisting Sign Signing and distribution overview Signing your add-ons Distributing your add-on Post-submission review More information about AMO Package your extension Windows Mac OSX Linux / Mac OSX Terminal Distribute Distribute Manifest V2 and V3 extensions Distribute pre-release versions Submitting an add-on Listing on AMO Self-distribution Get help Version Rollback Eligibility Roll back using Developer Hub Roll back using the Add-on Submission API Source code submission Provide your extension source code Default reviewer build environment Use of obfuscated code Source code checklist Firefox version compatibility Version compatibility The `browser_specific_settings` key AMO compatibility setting Recommendations Add-on ownership Transfer ownership Code disputes Developer accounts Setting a display name Blocked accounts Issues receiving emails from AMO Self-distribution Self-distribution options Installing self-distributed extensions Preparing your add-on Install from file on a computer Install from file on Android For desktop apps Promote Create an appealing listing Your add-on’s name Create a captivating icon Create a meaningful set of keywords Make sure your summary is just long enough Focus on key features in your screenshots The add-on description can be longer, but not too long Make it local Make it experimental Select the right platforms and versions Categorize well Be prepared to provide support Set up a developer profile Use plain language in any privacy policy or license agreement Gently ask for a review Make use of Markdown Some other points What’s great content and design? Promoting your extension Promote your add-on from your website Friends, family, and colleagues Events and meetups Current users Social media Engage with your users Create a forum, user group, or similar Engage with bloggers and news media Advertising Make money from browser extensions Will I ever be able to sell through AMO? What can't you do What can you do Unsolicited offers How can I maximize my income? Recommended extensions Overview Criteria for Recommended extensions Developer partnership Selection process Manage Stay informed when Firefox changes Publish extension updates Manage authors of your extension Promote your extension Removing your extension from distribution Resources Updating your extension Enabling updates to your extension Manifest structure Testing automatic updating Best practices for updating your extension Monitoring extension usage statistics Accessing the statistics dashboard Tracking external sources Add-on listing example Resources for publishers Retiring your extension Reasons for withdrawing your extension Steps to retiring an extension Suggested retirement timetable Enterprise Developing your enterprise extension Distributing your enterprise extension Enterprise support Manage add-ons for Firefox for Enterprise Install system add-ons for Firefox for Enterprise Enterprise resources Enterprise development Data collection disclosure and consent for enterprise extensions How to add policy support Distributing your policy Enterprise policies that impact extensions Relevant policies Other relevant policies Enterprise distribution Signed vs. unsigned extensions Using an ExtensionSettings policy Bundling add-ons with a custom Firefox Themes Creating themes Using the AMO theme generator Getting started Submitting your theme Updating your theme Static themes Introduction Create a simple static theme Updating static themes Single image themes Multiple image themes Static animated themes Dynamic themes Introduction Creating dynamic themes Publishing dynamic themes Cross-browser compatibility Community Who is part of the community? Connect with the community Get involved in the community Get in touch Community Forum Add-ons Blog Office Hours Stack Overflow Communication Calendar Dev Mailing List Contribute Contribution opportunities Onboard to the WebExtensions codebase Hacking guide for WebExtensions code contributions WebExtensions Experiments Find or create a bug Bring your extension to life Get how-tos, resources, and information to successfully build and ship your extension for Firefox. Contents Getting started Mozilla Developer Network Getting started The Firefox Extension Workshop can help you develop extensions for Firefox and give your users simple, yet powerful ways to customize their browsing experience. You’ll find: Overview of the Firefox extension features Tools and processes for developing and testing How to publish your extension on addons.mozilla.org or distribute it yourself How to manage your published extension An enterprise guide for developing and using extensions How to develop themes for Firefox Firefox developer communities Mozilla Developer Network Documentation for the WebExtensions API can be found on the Mozilla Developer Network (MDN). On MDN, you’ll find: Tutorials to help you start Explanations of key extension development concepts A guide to extension UI components How to use the extension Javascript APIs. A reference guide for the extension Javascript APIs, including compatibility tables for other popular browsers. A reference guide for the manifest.json file and its keys. Contributors: caitmuenster rbrishabh Last update: rbrishabh Sep 25, 2019 Up Next Create extensions for Firefox and Firefox for Android Develop Unique Firefox Capabilities Develop Firefox workflow overview Connect With Us Twitter For developers: @mozamo For end users: @rockyourfirefox More Matrix Community forum Extensions Developer Newsletter Stay up-to-date on news and events for Firefox extension developers. Email Address I’m okay with Mozilla handling my info as explained in this Privacy Notice . Sign up Thanks! Please check your inbox to confirm your subscription. If you haven’t previously confirmed a subscription to a Mozilla-related newsletter you may have to do so. Please check your inbox or your spam filter for an email from us. Mozilla Add-ons About Blog Developer Hub Developer Policies Forum Firefox Download Firefox Desktop Mobile Features Beta, Nightly, Developer Edition Twitter (@firefox) YouTube (firefoxchannel) Github (mozilla) Website Privacy Notice Cookies Legal Edit this page on GitHub Portions of this content are ©1998–2025 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T09:30:04 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.