31–39 of 39 posts
Earlier quoted context omitted.
Can you point to one extension that is making 7 figures?
I imagine Grammarly is. And then they spend all that revenue on YouTube ads... https://www.grammarly.com/browser/chrome
Very well priced but.... I think I get what you were trying to do with the pricing "per hacker". But really it's just confusing. Say it's $30/users/month The price is good. I just find the hacker term unnecessary
I found making Chrome extensions with Sveltekit was very easy thanks in part to its use of Vite. Any plans to support anything other than React?
Do you have any references that you could point me to on how to get Sveltekit running to build Chrome extensions?
Sorry for the digression, but this has been a bit of a bugbear for the past month and would dearly love to know how to get around it.
Earlier quoted context omitted.
Can you point to one extension that is making 7 figures?
Are you looking very specifically for “ONLY 7 figures”? Revenue, or profit? Not hard to think of a handful of big players in revenue; 1Password and Honey spring instantly to mind as 9-figure revenue players.
Earlier quoted context omitted.
Are you looking very specifically for “ONLY 7 figures”? Revenue, or profit? Not hard to think of a handful of big players in revenue; 1Password and Honey spring instantly to mind as 9-figure revenue players.
I am interesting to know if a solo developer can make a living, 6/7 figures, producing and monetizing extensions.
Earlier quoted context omitted.
> Our tooling is written in Node.js. Sure. My question is why.
It’s a norm for frontend devs to build CLI tools in the language/evironments/ecosystems they’re most familiar with.
Earlier quoted context omitted.
> Our tooling is written in Node.js. Sure. My question is why.
Surely you are trolling? That's a very, very common setup. Nothing complicated or out of the ordinary requiring specific tooling for the dev environment. The output that runs in the browser at runtime has its own set of same constraints. Modern browser version, etc.
First of all, don't do that. It's obnoxious. Secondly:
> That's a very, very common setup.
So? Falling back on the argument that, essentially, "lots of people do this" is about as worthy as attempting to counter by saying that the other person/what they are doing is weird[1]. (It's actually slightly more respectable, but that's only because of how unrespectable the call-them-a-weirdo path is.) You either have an argument for $THING that will hold up under scrutiny without appealing to how weird/anti-weird $THING is, or you don't.
Thirdly, you are not compelled to comment. (What makes your decision to join in even more mystifying is that you were not the person being addressed—at least their impulse to do so would have made sense, even if the argument was still a bad one.) If you don't actually have an answer, why bother commenting at all?
I found making Chrome extensions with Sveltekit was very easy thanks in part to its use of Vite. Any plans to support anything other than React?
Svelte or Sveltekit specifically? I've had issues with getting the webextensions polyfill working with Sveltekit but Svelte works without any issues. Do you have any references that you could point me to on how to get Sveltekit running to build Chrome extensions? Sorry for the digression, but this has been a bit of a bugbear for the past month and would dearly love to know how to get around it.
[0] https://github.com/antony/sveltekit-adapter-browser-extensio...