Browser extension development.
Put your tool where your users already work — in the browser.
Browser extensions are underrated for internal tooling. If your team spends the day inside a supplier portal, a marketplace back office or a system you cannot change, an extension can add the button that system lacks, capture data into your own system, or automate the sequence someone repeats fifty times a day.
What’s included
- Chrome, Edge and Firefox extensions from one codebase
- Data capture from pages your team already uses
- Workflow automation for repetitive sequences
- Integration with your own API and systems
- Authentication tied to your existing accounts
- Chrome Web Store submission and review handling
- Managed deployment for internal-only extensions
Manifest V3 changes what is possible
Chrome's current extension platform restricts background execution and remote code. Some older approaches no longer work. Building to the current platform correctly avoids an extension that gets rejected at review or breaks at the next browser update.
Internal extensions do not need the store
For an extension only your team uses, you can deploy privately without public review. That removes the review delay and keeps internal tooling out of public view.
Common questions
Will it work in all browsers?
Chrome, Edge and other Chromium browsers share a codebase. Firefox needs modest adaptation. Safari is a separate build and worth confirming you need.
Can it interact with a site we do not own?
Technically yes. Whether you should depends on that site's terms — I will raise it if it looks like a problem.
How long does store review take?
Usually days, occasionally longer. Extensions with broad permissions get more scrutiny, so requesting only what you need speeds it up.
Have a project in mind?
Tell me what you're building and roughly when you need it. I reply to every genuine enquiry within one working day.