Share your feedback...
Add the ability to opt-in notifications for specific templates so you can be easily notified when a certain template has been updated.
Conversion script for other browsers
Create a conversion script that allows you to easily convert your template to support other browsers such as Firefox or Safari, where possible.
Add a community showcase that displays extension projects built by devs within the community
Template for communicating with desktop apps
Tauri and Electron are popular ways to create desktop applications. A template demonstrating how to communicate with these apps from a browser extension would be very helpful. From what I’ve read, the Native Messaging API is the best way to do that (avoids communicating with a server or spinning up an insecure localhost port). A bonus would be a website talking to the chrome extension, which talks to the desktop app. TypeSafety using something like Comlink would be nice too.
Blog post explaining popular web framework integrations
Next.js, Astro.build , Vite, and other frameworks are popular these days. They are usually “batteries included”, and support features like routing, bundling, and more right out of the box. Plus, they are easier to keep updated, compared to when I was rolling my own webpack configs a few years ago. Many frameworks support exporting to static sites. A blog post explaining how to hook these static exports up would be nice. My initial impression is that it just has to do with linking up exported pages with the manifest.json Of course, you could make Popup full page & new tab starters for each framework. It seems like the Content scripts starter would be harder (maybe iframes with comlink?)
Launch a community that allows devs that purchased ExtensionKit to discuss all things related to extension development and growth