Launching today
Got an idea for a Chrome extension? Describe it in plain English and PlugThis builds it. Real code, a real backend, ready for the Chrome Web Store. Refine it just by chatting. Connect Supabase for login and a database. Every change is saved as a version, so nothing is ever lost. When you're ready, we generate the icons, screenshots, and listing copy the store asks for. Everyone else builds web apps. We build Chrome extensions. That is the one thing we do.
Building a niche-focused SaaS myself, I love the "Lovable, but for X" positioning — going narrow lets you own the whole workflow. Curious: does PlugThis help with the Chrome Web Store review process too (manifest permissions, privacy disclosures)? That's usually the part that kills momentum for first-time extension builders.
PlugThis
Hi @kojimajunya Yes yes we do :D PlugThis tells you your extension's chrome webstore readiness, helps you generate assets and in one click push changes live to CWS.
Please do check out PlugThis and take it for a spin.
this is REALLY timely, i just built a feature spec for my app and a simple chrome extension was part of the design - I want an extension that will scrape monthly statements from accounts (banking, credit cards, etc) and send them to my app automatically....I am non-technical Lovable app builder so i was not looking forward to trying to figure this out on my own....sounds like you might just have the solution i need. Does this sound like a use case your tool can handle?
PlugThis
Hi @crystal_harrison PlugThis should be able to handle this, give it a shot on the platform if you run into challenges, please send me a email udaya@plugthis.ai I ll hop on a zoom call and troubleshoot it for you.
@nefer_ai will do that here when i get off this call!
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?
Congrats on the launch Udaya and team. 🥳
Building chrome extension is not trivial, you need to understand chrome APIs, manifest, permissions and what not. Just having a super easy way to create an extension with 3-4 prompts makes PlugThis worth it. I’ve created few extensions already and the experience was a breeze.
Wonder if the coverage for other browsers is in the roadmap
PlugThis
@cjgiridhar Hi Chetan! Thank you. Glad to have you as one our early users. Your feedback was the reason we built chrome store readiness, asset generation and one click connect to update extensions directly on chrome webstore. Take a bow 🙇 As of now we are focussed on chrome and edge browsers. May be later we might do Safari and Firefox.
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.
This is a great idea. Does the app publish to chrome store directly post building ?
PlugThis
@neosrix Thanks Srix. Yes, it does.
Once your extension is built, you connect your Chrome Web Store account once, and PlugThis uploads and publishes directly from inside the app. It also generates the listing description, permission justifications, and privacy disclosures the store asks for, so you are not filling that out by hand. After the first publish it remembers your Store item ID, so pushing an update later is basically one click.
The only parts that stay on Google's side are the one-time developer account registration and the review itself, since approval is always their call. Everything up to hitting submit, we handle for you.