To better understand the value of internal browser extensions, we combed through the Chrome Extension store, searching for internal extensions with these keywords in the description: "internal, internal tool, internal company, corporate use, employees of, for * employees." Note: most companies don't publish their internal extensions publicly; their extensions are usually "unlisted."<p>Here is a summary of the top 100 most interesting internal extensions we found!<p>Excited to hear your thoughts, are you building internal extensions yourself?<p>------<p>What problems are developers trying to solve?<p>- Give employees better access to internal information to do their jobs (custom knowledge base, FAQ search, internal directory)<p>- Streamline a tedious and/or error-prone browser process<p>- SaaS doesn't easily surface information that my employees need<p>- Hosting a frontend for my internal tool is too cumbersome<p>- Having to context switch to use a certain type of internal tool is not preferable<p>- My devs need an ad hoc tool (dev tools)<p>------<p>Breakdown of 100 internal extensions by functionality
(Note: these categories are not mutually exclusive.)<p>knowledge sharing: exposing data in the right context (READ) to remove context switching<p>19 instances<p>frontend automations/form filling/take actions<p>9 instances<p>UI modification + additional functionality on existing tooling<p>17 instances<p>Scraping<p>3 instances<p>Integrations used in context (CRUD)<p>24 instances<p>developer focused tools: PR/debugging and etc.<p>14 instances<p>Internal productivity functionality (credential saving and etc., rather vague)<p>19 instances<p>Analytics and tracking<p>6 instances<p>------<p>Resources<p>Airtable of the 100 Chrome Extensions: https://airtable.com/shrz1b4O3lC3Osnj1/tblUrp8Pv1I2IDMpz<p>Same post with better formatting: https://dev.to/realkevinyang/what-i-learned-from-studying-100-internal-chrome-extensions-a7n