Spent the last few months talking to founders and indie hackers who are quietly frustrated with subscription Chrome extensions.
The pattern I keep hearing: someone pays $20 to $50 a month for an extension that does one specific thing (usually an SEO checker, a research tool, a screenshot annotator, or an LinkedIn scraper). The extension itself is a few hundred lines of code, the underlying task is mechanical, and the monthly charge feels like rent on something that should be a one-time purchase.
I'm running growth for PlugThis (launching here on Product Hunt soon) and part of the pitch is that you can build or clone those tools yourself instead of renting them. But I want to stress-test the premise.
Two questions for this forum:
What happens when Chrome changes a manifest requirement?
PlugThis
@levi_mitchell1
@levi_mitchell1 The manifest isn't hardcoded into some template you download and own forever. Generation, validation, and sanitizing all happen on our side against the current Chrome rules. So when Google changes a manifest requirement, we update that logic in one place and every new extension people generate follows the new rule immediately.
You don't have to track the spec, learn what changed, or patch boilerplate yourself.
Being honest about the edge: an extension you already published stays as it was shipped, so if a change affects it, you would regenerate and re-publish.
But the "keep up with Chrome's moving target" burden sits with us, not you, which is exactly the part that usually makes people abandon extensions.
What made you ask? Have you been bitten by a manifest change breaking something before?
BYO API key means full ownership, but no free AI features out of the box. Real cost upfront.
PlugThis
Hi @aria_turner You don't bring your own key to use PlugThis itself. Generation runs on our AI with a free trial to start, then paid plans if you keep building, so there's no upfront API cost just to try it and ship your first extension.
The BYO-key part only comes in if the extension you generate needs to call an external API on its own at runtime (say it talks to an AI model or a third-party service). In that case the key lives inside your extension's own .env, which is where the "full ownership" bit is real: your extension, your key, your usage, no dependency on us to keep running.
So it's kind of the best of both. Zero-setup AI to build, and clean ownership for anything your extension calls once it's out in the world.
Good idea. It would be even better if your service somehow helped with the promotion and marketing of extensions, because this is much more difficult than development, especially in our time
PlugThis
@maxim100000 You bring up a really good point, our current focus is building the best chrome extension builder in the world. Helping our users move from idea to working extension, as soon as possible.
On the marketing front, we do assist with asset creation and deployment of updates to the chrome store.
We also help getting the extension ready for a chrome store listing.
On the distribution front, we havent made any plans yet, if you have any ideas please share.
I've had a few Chorme extension ideas setting in my notes because getting from an idea to working extensions always felt like too much work. i really like that you're focused on one problem instead of trying to build everything for everyone.
PlugThis
@tessa_lynch Thank you for appreciating exactly what we are doing. We just want to be the simplest way to build chrome extensions.
Please try out your ideas on Plugthis.ai Super excited to see your ideas to comes to life.
PlugThis
@hamza_afzal_butt Thank you, the types of extension being created are wide spread from scrapers to AI powered extensions that do customer research.
But my favourite so far was an interactive digital wellness BFF someone had created that acts as your buddy reminding you to do exercise, drink water every 20 minutes.
One other thing I have observed is people re-creating extensions that already exist and adding features they want on top of them.
I've noiced there are plenty of AI tools for websites but not many focused on broswer extensions. that focus alno makes Plug this stand out to me.
PlugThis
@_angelinaashley Thank you, we were clear from Day 1. We ll only focus on chrome extensions. There are plenty of web app and mobile builders but none of them build proper chrome extensions.
Please take PlugThis for a spin, would love to see what you are going to build.
@nefer_ai I like that this is built specifically for Chrome extensions instead of trying to cover every kind of app. Sometimes focusing on one problem is what makes a product really instead out.
PlugThis
@morgan__harriss Thank you, we want to do one thing, in our case building chrome extensions and be the best in the world at it.
Please take PlugThis for a spin, would love to see what ideas you were able to make into a chrome extension.