Would it be beneficial or harmful for language learning? I would appreciate it if you shared your opinions.

A year ago today I uploaded my first extension — ChatGPT Pro Tools — to the Chrome Web Store, and then spent ten months not asking anyone for money. It launched with one tiny feature: pinning chats in ChatGPT. Funny detail: five months later that exact feature shipped natively in ChatGPT itself, so I deleted my own launch feature and kept going.

On day 295 I finally added a $4.99/month tier. Nineteen days later a stranger paid — and that first customer is still subscribed.
Year one in honest numbers:
• $574.39 collected in two months of charging, $209.65 MRR
• 44 active subscribers
• 2,144 installs currently enabled, 4.7 rating
• 47 Google clicks to my site in the first three months → 862 in the last 28 days
• $0 spent on ads

The biggest lesson was about reading the stats page, and the first screenshot shows why. In July the weekly-users graph climbed toward 16,000 and I honestly thought I’d caught a trend — I refreshed that chart like a slot machine. Then over two days the public counter settled from 10,000+ down to 2,000+, and when I decomposed the data, the whole spike was auto-update pulses re-counting dormant installs. The tell was in the second screenshot: installs per day didn’t react at all — no matching spike, just the same gradual climb as the months before. The real, boring number: 2,144 people who actually keep it enabled. So now I treat weekly-users as a mood ring and judge everything by installs, uninstalls and the enabled count.

What actually brought users in surprised me. Early on I generated a dozen long-tail blog articles — one prompt each, honestly — hit publish and forgot they existed. Months later I opened Search Console and realized nearly all of my traffic was landing on exactly those forgotten pages. That’s the third screenshot. One-prompt articles had been quietly carrying the whole funnel. Plan for year two: write them properly this time — because if the throwaway versions rank, better ones should rank higher.

One question for anyone further along: if you were in my position right now, what would you do on the marketing side?

I recently shipped a Chrome extension for free on the Chrome Web Store, and I'm honestly surprised by the growth so far. I kept it completely free because my main goal was to get users and see whether people actually found it useful. Now I'm seeing around 1.2K weekly users, with a pretty sharp growth curve over the last couple of weeks. The screenshot is from the Chrome Web Store analytics. Now I'm wondering, is there a good way to start earning from the extension without hurting user growth? I don't want to put the core functionality behind a paywall, bombard users with ads, or do anything that makes people uninstall it. I'm considering optional premium features, a one-time payment for advanced features, donations/support, sponsorships, or maybe a Pro version while keeping the core extension free. For people who have actually built and monetized Chrome extensions, what worked for you? I would especially like to hear about models that allowed you to monetize while keeping the free user base growing. Would really appreciate some practical advice from developers who have been through this.

Hi all,

As i'm working on growing launchpact.io i'm seeing a lot of unprepped launches and as the day unfold they don't get much visibility and end up with a failed launch.

This is one of the reasons i build launchpact.io, if you have an upcoming launch do check it out and prep ahead of time, i also added this checklist that can give some hints too, have a read.

Good luck everyone!

I kept running into the same problem: screenshots often contain information you didn't realize you were sharing.

An API key. An email address. A phone number. A password field. Customer information.

Usually, you take the screenshot first and then manually look for things to hide.

I built Blackbar to reverse that workflow.

It reads the page before capturing it and automatically detects and redacts sensitive-looking information. The screenshot you get is already the safer version.

The part I cared most about was privacy.

Blackbar runs entirely on the device. It declares connect-src 'none', so Chrome itself blocks the extension from making network connections. It still works with Wi-Fi turned off.

It's also open source, has no account requirement, and is free.

I'd genuinely like feedback from other Chrome extension users/builders, especially on:

• detection accuracy
• false positives/negatives
• the capture workflow
• anything that would make you hesitate to trust it

Chrome Web Store Link

Source

I've been following this community since before I launched and got a lot of inspiration from the milestone posts here, so here's mine, plus a question.

The extension is called Bulk Edit, Delete & Download Google Photos. Google Photos has no bulk editing, so everything is one photo at a time. Batch lets you select photos (or a date range, or an album) and enhance, filter, crop, caption, watermark, convert, delete, or download all of them in one run.

Launched publicly about 3 months ago. This week I crossed $1,000 gross revenue and $500 MRR. Screenshot attached.

What's gotten me here so far: the Chrome Web Store listing is my biggest organic channel by far, translating it into 9 languages helped, and answering questions in forums works way better than announcing.

Now the real question: for those of you who've gone past this point, what actually moved you from $1k to $10k? More features, more SEO content, YouTube, partnerships, raising prices? I have a free tier with a monthly quota and paid tiers at $6.99 and $24.99.

Happy to answer anything about the CWS review process or how the automation works in return.

It bothered me that despite all the space on my laptop screen or desktop monitor, reading web articles felt like breathing through a straw. Horizontal space is poorly used and vertical space is in short supply, leaving only a few paragraphs on screen at once.

So I made Columnary, a Chrome extension that makes full use of your screen real estate, whether it's a small screen laptop or a 5K monitor. It strips ads and formatting, and puts everything into columns in a horizontally scrolling format. This way, articles can fill 100% of your screen while keeping line lengths readable.

This transforms the way your brain processes articles. When you can see the whole thing at once, you can utilise your natural spatial processing ability to make sense of where you are.

Columnary also includes a bookmark feature so you can mark your place when stepping away from long articles, and various typography settings and a full screen mode, as well as keyboard shortcuts to help you scroll by column.

Install Columnary extension · Source code

I kept doing this thing where I'd find something I wanted to deal with later — an article, a product restock, a ticket sale, a deadline, some documentation, whatever — and I'd leave the tab open.

Then 3 days later I'd have 30 tabs open and no idea why half of them were there.

Bookmarks didn't really solve it either, because they remember where something is, but not when I need to come back to it. And setting a reminder on my phone meant getting an alert on the wrong device and then having to find the page again.

So I built Latr.

The idea is pretty simple:

Find something → remind yourself about it → forget about it → Latr brings the exact page back when you need it.

For example, if I'm looking at a page about a ticket sale starting Friday at 10 AM, I can highlight the date, right-click and tell Latr to remind me about it. It saves the page along with the reminder.

When the time comes, I get a notification and clicking it takes me straight back to that exact page.

There's also a keyboard shortcut (Alt + Shift + Y) if I just want to save the current page quickly.

I built a bunch of other things around the same idea too — recurring reminders, snoozing, notes, folders/tags, calendar handoff, importing existing links, etc.

One thing I was particularly intentional about is privacy: there's no account, no backend, no analytics, and no telemetry. The reminders stay in the browser.

It's completely free right now.

🔗 Chrome: https://chromewebstore.google.com/detail/latr-%E2%80%94-remind-me-about-th/lcceeepfhggkninbfbifkpalkdoinjli

🌐 Website: https://latr.page/

I'm sharing a short video showing how it works too.

This is my first time putting something I've built out there publicly, so I'd genuinely love some feedback.

Does this solve a problem you actually have?

And if you've tried it, I'd especially like to know:

• What's confusing?
• What feels unnecessary?
• What's missing?
• Would you actually keep using something like this?

I'm much more interested in hearing what sucks about it than hearing that it's great 😅

AskYouTube lets you ask questions directly about the video you're watching.

Instead of scrubbing through a 1-hour tutorial, podcast, lecture, or review, you can just ask:

• “What does he recommend?”
• “When does she explain pricing?”
• “What are the main arguments?”
• “Which tool does he use?”
• “Summarize the part about X.”

And get the answer without hunting through the entire video.

YouTube does have some AI functionality for this already, but it relies on Gemini, and in my experience, it’s pretty limited.

With this extension, you can choose the AI model you prefer, instead of being locked into one.

It works directly from YouTube as a browser extension, and it's free to use.

I originally built it because I watch a ridiculous amount of long-form YouTube content and kept thinking: why can't I just ask the video what I need to know?

So now you can.

Try it here: https://lappice.com/

Would love to know what you think, especially which AI you prefer and what kind of videos you'd use it for.

AskYouTube, ask the video instead of searching through it.

I kept running into a small but annoying problem:

I would be reading a long article, documentation page, research paper, or Reddit thread, close the tab, come back later — and have to find where I stopped again.

So I built Scroll Memory, a small Chrome extension that remembers your scroll position and brings you back to where you left off.

The idea is intentionally simple:

• Remembers where you stopped on a page
• Restores your position when you return
• Useful for long articles, documentation, papers, tutorials, etc.
• First 5 restores each month are free
• $1/month if you actually find it useful

I’m experimenting with a simple idea:

Can very small software solve problems that are annoying enough to be worth $1?

I’d especially like to know:

Would you actually use something like this?

And if not, what would make it useful enough for you?

Chrome Web Store:
https://chromewebstore.google.com/detail/jhademdbhjggiodhadfifkpcnpalejoj?utm_source=item-share-cb

I build KeywordAxe, a Chrome extension for Google Ads users (keyboard shortcuts, spend-anomaly alerts, bulk negative keywords). It has opt-in telemetry, and for months that telemetry quietly showed a core feature running but finding nothing — for everyone.


The cause was a good lesson in the fragility of DOM scraping. The extension read the campaigns table by column position. Google reshuffled that table in 2026: each row now starts with a checkbox and an expand-chevron cell, and the chevron is a Material icon rendered as *ligature text* — the literal string
"expand_more". So my extractor read every campaign's name as "expand_more" and
they all collapsed into one junk record. "Found nothing" and "silently broken"
produce identical output, so nobody noticed — including me — until the telemetry pattern gave it away.


I patched the scraper (read the header row, map columns by name, strip the icon
ligatures), then decided scraping a UI Google can reshuffle anytime was a losing game and rebuilt the data layer on the official Google Ads API — read-only OAuth (PKCE) from an MV3 service worker, with the developer token + client secret in a stateless Cloudflare Worker relay so nothing sensitive ships in the extension.


Stack: vanilla JS, no bundler, MV3, Cloudflare Workers, IndexedDB for the local
fallback. Happy to talk about the scraping→API migration, the MV3 OAuth flow, or the relay design.


Chrome Web Store: https://chromewebstore.google.com/detail/gcgpkjmlpfppmejefedicclpbdfncdfp

I built Wapes AI, a Chrome extension for WhatsApp Web (bulk messaging + AI CRM). Launched it 7 days ago with zero ads, just cold outreach and posting in relevant communities.

Results so far:

• 10 successful payments, $217 total, only 2 failed charges
• Revenue split across Argentina ($127.49), Peru ($44.99), Colombia ($15), Mexico ($14.99), and Chile ($10)

What surprised me most: as a solo dev with no big following, having paying users across 5 countries in week one proved people will pay for a Chrome extension that solves a real problem — even without brand recognition.

What worked:

• Talking to potential users before building anything
• Charging from day one instead of "polishing" first
• Posting in communities where WhatsApp/small-business users already are

Happy to answer questions about building and monetizing a Chrome extension, the tech stack, or how I got early users.

The idea was pretty simple: instead of treating a new tab as a blank page, make it a lightweight workspace.

I'm particularly interested in the UX right now.

The current version has:

• App shortcuts

• Bookmark collections

• Quick notes

• Tasks

• Focus timer

• Wallpapers

• Weather

• Designer/developer-focused widgets

One thing I deliberately tried to avoid was turning it into a giant widget dashboard. I want the interface to stay calm and useful.

For people who use New Tab extensions:

What feature makes you actually keep one installed?

And what usually makes you uninstall one?

I'm looking for criticism as much as compliments.

👉 Check Cosmos