We have received some good news from the Chrome extension developer relations team today. All previously communicated Manifest V2 phase out dates are put on-hold. The Chrome extensions team is reacting to mounting developer dissatisfaction with the Manifest V3 model and non-existent workarounds for common V2 capabilities. Chrome team’s current plan is to iteratively ship features that unblock migration to V3 manifest and then resume V2 phase out plan. Continue reading...

“Established Publisher” badge is another new way introduced by the Chrome Web Store team to distinguish publishers with good track record and adherence to store guidelines. This badge should give more peace of mind to users and increase chances that users chose your extensions instead of low quality competitors. You also get your website address shown more prominently in the Web Store listing page. So, how do you get this badge? Continue reading...

The new featured extension badge in Chrome Web Store is a way to differentiate your extension from competition. It’s a signal of trustworthiness to users visiting your extension listing page and can help to boost installation rate for your extension. Let’s take a look at how you can earn the featured badge for your extension. Continue reading...

Chrome browser extension development journey starts by learning how to load your extension without first publishing it to Chrome Web Store. Luckily, it’s very easy to begin and anyone can do it without paying any developer license fees. You just need to do a couple easy steps. Continue reading...

I previously wrote that Mozilla still has no clear timeline when Manifest v3 will get mainstream support in Firefox. But it does not mean you can’t start experimenting and preparing for the inevitable MV3 migration in the Firefox browser right now. Continue reading...