Browser extensions are big business in 2020
December 08, 2019 • 🥤 4 min read
Browser extensions are all the rage nowadays. In fact, some companies build their entire businesses on browser extensions. Honey, the Chrome extension that applies promo codes at checkout online, was recently bought out by PayPal for a whopping $4 billion. That’s right, billion with a B.
What does this mean for developers and businesses? Should you build a browser extension? Let’s break it down.
Brief history of modern browser extensions
- The first browser extension was made for Internet Explorer in 1999.
- Firefox launched and shipped with extension support in 2004.
- Chrome and Safari started supporting extensions in 2009.
- In 2010, Chrome opened the Chrome Web Store to install extensions. Chrome surpassed Internet Explorer in usage in 2012.
- Microsoft Edge launched in 2015, replaced Internet Explorer on Windows 10 and added extension support in 2016.
- In 2015, a browser extension API standard initiative was created by a W3C community group with a goal to standardize browser extensions API’s.
According to Stat Counter, Chrome currently owns 65% of the browser market share, with claims from Google of over 2 billion active Chrome browsers in 2016. Currently, there are almost 200,000 extensions on the Chrome Web Store. By comparison, there are more than 2 million apps in the Apple App Store and almost 3 million apps in the Google Play Store.
Is a browser extension a good move for your product?
Now that you have an idea of the modern browser extension landscape, it’s natural for you to ask – is building an extension the right move to build and ship a new product idea?
The answer is a resounding… YES.
Due to the immense popularity of Chrome, quick development leveraging Chrome’s extension API, and the ease of publishing to the Chrome Web Store, it has never been easier or cheaper getting a valuable shipped product to the most users.
Doing some ratio math, you can figure out the relative competition with other products:
In the Chrome Web Store, you have 2 billion Chrome users : 200,000 Chrome extensions = 10,000 users : 1 Chrome extension.
In the Apple App Store, you have 100 million iPhone users : 2 million iOS apps = 50 users : 1 iOS app.
In the Google Play Store, you have 2 billion Android users : 3 million Android apps = 667 users : 1 Android app.
Clearly, you can see there’s a competitive advantage of launching a browser extension (especially a Chrome extension) over launching on other platforms. This is especially true if you want to get the most people using your product right away. By sheer numbers alone, launching a Chrome extension gives you 200 times more potential users than an iOS app. If you also consider development costs of a Chrome extension over an iOS app, the advantage grows even more.
Now, of course, browser extensions aren’t magic. They fall victim to the same problems new software products face, which is that no one downloads or installs new software anymore. You will still have to do the hard work to get users. In addition, browser extensions can only solve a specific set of problems on websites, and you are limited by the extension API.
With these 2 points in mind, after fitting your product’s scope for an extension, getting enough dedicated users, you can grow your product’s services by expanding to other platforms.
Getting started and essential knowledge for developers
My recommended flow to developing extensions is to go Chrome > Firefox > Safari. I launched the Chrome extension first by sharing it on Twitter, and decided to go ahead and port to Firefox and Safari after receiving a lot of positive reception.
With these 3 browsers alone, you will have about 90% coverage of the browser market. Since many other modern browsers are Chromium-based, taking those into account you will likely have close to 100% coverage.
Recommended development steps
1. Chrome Extension
The Chrome Developer Extensions website has everything you need to make a new extension – tutorials, documentation, and instructions on publishing to the Chrome Web Store.
2. Port to Firefox
3) Port to Safari
There are key differences in Safari extensions, and depending on the complexity of your Chrome extension, it may be more work to port. Apple has a documentation page called Converting Chrome Extensions.
Tip: Use Safari Extension Builder to avoid configuring things by hand in XCode.
What all this means for the future of the web
Believe it or not, the web as a platform is only 30 years old. It might be more crowded than ever before with almost 2 billion websites, but the web platform has been given new life with browser extensions.
The emergence of Chrome has brought along exciting new ways to create useful products. However, there are issues with Chrome’s market dominance, as seen when Google recently restricted modern ad blocking extensions, or privacy issues like Gmail forcing logging into Chrome. It’ll be interesting to see if Chrome can keep its grips on the market in the next decade. Still, we have Google Chrome to thank for democratizing the browser extension space, and it should only get better from here.
This space evolves quickly, and it can be sometimes hard to keep up with all the changes with browsers. To help myself keep up to date, I made a Twitter bot @experimentalweb. I’ve found it to be a good way to passively keep track of updates from browsers and Internet organizations like W3C.
I intend on expanding the microsite experimentalweb.net into a digital magazine to showcase new developments on the web and browser features.
By Thomas Wang, who occasionally has useful things to share.