Is the use case something like taking screenshots?
I don't think $20 is bad here, I don't need it so $20 seems like a lot to me, for someone taking a lot of screen shots maybe $20 is no different than $2?
If I'm expensing something for say work, nobody cares if it is $2 or $20. In fact someone might look at me weird for expesning $2 rather than $20. The breakpoints are far higher than that as far as approvals.
$20 for a browser extension that blurs text on a page! Yikes! This strikes me as the sort of generic productivity tool that might be worth a buck or two, but for $20, it had better blur text AND file my taxes for me. I would be really surprised if there were not free extensions that did effectively the same thing. And if there are not, someone could probably whip it up in a day or two, and there goes your business.
Most people can't code. If you can hack it together in hour then you're not the target audience. This is priced well, or even a bit low given the probably-smallish market size.
We programmers should really learn to value our time and our skills better. Charge more.
I don't mean to be overly critical of your product, as I hate when people do that on HN However, you should know blurring is not a secure way of censoring information, as each character is still sort of recognisable, and programmatically reversing the blurring of known alphabets and typefaces is not that difficult (for numbers, you could blur each number from 0-9 and look at the resulting images) This is even more ob…
I agree, the blurring is not "strong" enough, too much information is retained. It's highly likely that it can be undone (I mean if blurred stuff gets passed around as a screenshot - it would be trivial to undo it right on the webpage ;-) )
Pricing is incredibly hard to get right. It's very, very likely that the market for a tool like this is small, so charging $2 would actually net the author far less than charging fewer people $20. In that regard it's correctly priced at $20. The apparent simplicity of some code has absolutely no impact whatsoever on the amount you should charge for it. What you charge for your product should be based on the value tha…
> What you charge for your product should be based on the value that the customer gets from it and not the amount work that you've put in to it. Go one level deeper. How much effort would a competitor have to put into building a competing product and undercutting you? If the answer is "one afternoon," then you either need to figure out a way to make competition less likely or set a more realistic price.
If it really takes the competition a whole afternoon to implement this, $20 is an incredible price. Even just an hour for any in-house SWE in America is going to cost the company at least $20.
If you price your weekend at $20, it is. Many devs would say $20 is 20 minutes billed time.
Well - frankly I price this at "free-fiddy" because I hammered this out in 5m (just drop it into your console): https://kopy.io/sAgzt Yes it's jQuery (and I know everyone on HN hates jQuery!) - a vanilla JS version would be just as trivial! Wrapping it in a Chrome manifest w/a simple "enable/disable" browser button-type interface would be about 20 minutes I guess.
And by the time you’ve wrapped it up, tested it, made the UI nicer (blur selected text, put a box around what will be blurred, allow for unblurring, etc.), don’t you think there’s something else you could have done for your company that would provide more than $20 value to them?