First, I decided to learn about the general development process for Microsoft Edge extensions, which is the type of app I want to develop.
References
Overview of Microsoft Edge Extensions
Microsoft Edge Add-ons Developer
General development process
The general process from development to publishing for Microsoft Edge extensions is as follows. I’ve learned that development involves using HTML, JavaScript, and CSS. However, I don’t have experience with any of these…
- Creating a manifest file
- JSON file
- A file that contains the app’s information
- JSON file
- Implementation
- JavaScript file
- A file defining the app’s features and functions
- HTML and CSS files
- A file defining the user interface
- JavaScript file
- Test
- It seems I can side-load the extension into my browser to test its functionality.
- Publish my extension to browser stores
- Register for a developer account
- Submitting the complete set of the extension files for review and approval

Things to search next
This is where I encountered some parts that are still unclear.
- What should I test for Microsoft Edge extensions?
- It mentioned testing in various environments, but what specific environments or conditions should I consider for testing?
- Which web browsers should I target?
- Which web browser is the most commonly used? (Microsoft Edge, Safari, Firefox, Chrome, Opera or Brave)
- What is Chromium
- How to receive recommended badges
- Is it checked during the application process?
- If it’s not approved, can I reapply?
Leave a comment