Earlier quoted context omitted.
I suppose you could post your project idea on there, and see if it takes off. Although it's not clear who makes the decision of who "officially" gets to tackle it, there's really nothing stopping you from tackling it anyway.
The whole point of this site is to find problems that are worth solving. Not, to build yet another useless yik yak app, that nobody needs, wants or isn't willing to pay for.
Show HN: Get Paid to Build Your Next Side Project
111–120 of 473 posts
Re: Show HN: Get Paid to Build Your Next Side Project
#112"Subscribe to news without paying $30/month per website" I don't think there is a legal way of actually doing this.
Re: Show HN: Get Paid to Build Your Next Side Project
#113Photoshop license costs $348 a year. If 1000 people get together and put $400 each, you'll get $400000. That money could be used to leverage a Gimp to be more Photoshop-users friendly. Then you don't have to keep with the subscription model. You have a great piece of open source software available for everyone to use as long as they want. You can do another round to get more features added. This solves the issue that…
Also, $400k is, like, nothing in developer time (compared to what Adobe puts into their software, at least).
Re: Show HN: Get Paid to Build Your Next Side Project
#114Re: Show HN: Get Paid to Build Your Next Side Project
#115Photoshop license costs $348 a year. If 1000 people get together and put $400 each, you'll get $400000. That money could be used to leverage a Gimp to be more Photoshop-users friendly. Then you don't have to keep with the subscription model. You have a great piece of open source software available for everyone to use as long as they want. You can do another round to get more features added. This solves the issue that…
The opportunity with Photoshop may not be to create another Photoshop clone, or add more features, but rather create smaller, specialized editing apps, that each target a subset of the Photoshop user-base, with perhaps less features.
Look at how Adobe Lightroom cherry picked a few Photoshop and Bridge components, to create a more specialized app that does a specialized job that Photoshop might have done in the past.
Or how Adobe's iPad Pro apps again deliver just a small subset of the total available features from their parent apps, making them more specialized for specific use-cases.
Photoshop's massive fragmented user base is ripe for the pickin' for sure. Could you tear down Gimp like that? Or would it be better to start from scratch?
Re: Show HN: Get Paid to Build Your Next Side Project
#116Isn't this exactly how Freelancer/odesk/whatever work now?
Good question. The big difference is you own the products you build here, and charge a monthly fee for access (for up to X customers). It's a bit like kickstarting a SaaS business. Versus with contracting/freelancing, you get paid 1x and the product is owned by the customer you work for.
For example, say I pick up one of the projects and the subscriber picks me to work on it. Okay, great. I go and work on it and consider it done. As it turns out, there was a lot of miscommunication and they wanted something different.
Do I still get paid? It seems like either way, there is a huge avenue for somebody to get screwed.
Re: Show HN: Get Paid to Build Your Next Side Project
#117> Identify location of text in an image ...for... $75 This is what my doctor charges for a flu vaccination. I guess I've chosen the wrong profession.
You don't pay your doctor $75 for sticking a needle in your arm, you pay him for his knowledge not to stick the needle in the wrong place. Looks like we've got full circle considering this same logic was applied to devs for ages.
Flu shots are generally intramuscular, you literally just jab it into your bicep. A layperson can do it with high probabilities of success just by reading the instructions on the box.
Indeed, pharmacists administer these all over the US.
Re: Show HN: Get Paid to Build Your Next Side Project
#118Re: Show HN: Get Paid to Build Your Next Side Project
#119Photoshop license costs $348 a year. If 1000 people get together and put $400 each, you'll get $400000. That money could be used to leverage a Gimp to be more Photoshop-users friendly. Then you don't have to keep with the subscription model. You have a great piece of open source software available for everyone to use as long as they want. You can do another round to get more features added. This solves the issue that…
The reason is a simple value estimation. It's open source (and so free to get) therefore its price is $0. Any product that is free signals that the product has correspondingly low value. I think it's simply unrealistic to expect people to put forward $400 for something with such low value perception and whose fair market price is $0.
This is especially true when Photoshop has such a high value perception (in part because it is better, and in part as a justification for shelling out the $400).
Ask yourself this - Have you, or will you, paid (donated, ...) $70 for using Vim (atom, neovim, emacs, VSC, ...) to support development? Have you paid $200 to Debian, Ubuntu, or Redhat for your Linux OS? $5,000 for (open|libre)ssl? $13,000 per core for PostgreSQL/MySQL?