Ask HN: Does anyone else have a hard time coming up with ideas for projects?
Here are some examples of my ideas and justifications for tossing them out:
* Something for managing my bookmarks - nah, Chrome's built-in Bookmark Manager is fine for my purposes
* Trello allows people to make lists of lists. What other data structure could I draw from as inspiration for a web app? - nah, can't think of anything
* Make some software that makes chiptunes - nah, this exists already, and all the Michael Jackson chiptunes I want to make already exist (heh)
* Make a tiny dog food firing catapult - maybe, but I'd have to spend some time reading about Arduino or something
* Make an app that visualizes acne outbreaks over time - maybe, but the result isn't worth the effort. I don't want to look at my face anyway.
* Do some OCR - sounds boring
* Make a better DataTables - don't need it
* Write a GLSL parser and evaluate things in JavaScript for debugging purposes - would be cool, but don't really need it
* Make a web app to send yourself an email in the future - Google Calendar does this
* Write a program to control your laptop's fan speed - sounds boring
* What's this React nonsense - ehhh don't care, won't need it if I'm not making a single page app
And there's always game projects and procedural generation-ish stuff and graphics, but that's kinda it's own category of project and doesn't fit my criteria of being something useful.
Does anyone else have this problem? How do you go about getting ideas for projects? Please discuss.
10 comments
[ 2.9 ms ] story [ 43.0 ms ] threadSource: support engineer / operations folk who spent many years running enterprise software on a day to day basis
1. Are you building something for fun? Look at what you do for fun. Narrow down on these topics and then decide to build something. For e.g. spend a lot of time on HN? Build an HN Chrome/Firefox add-on that does things you want in HN.
2. Are you building something for learning a new technology? Narrow down on the technology that you want to learn about. Now think of apps to build using that technology.
3. Are you building something for additional revenue? Find pain points in your industry and create apps to solve them.
Without the right amount of motivation, even if you had started with any of the projects mentioned above, it is very likely that you would not be able to follow it through.
My motivation for projects has always been kinda screwy. On the one hand, I want to make an income on my side projects in order to someday move away from my rather boring job. On the other hand, I want to make fun and personal things like games, that aren't necessarily things that people would pay for. Most of the project ideas in my list reflect this split of motivation.
Wow, thanks for the insight. :)
Some people build things simply for the joy of building it.
In each idea you've discussed, you could easily carve out a special niche version you need for yourself.
If your goal is to make money from said project, well that is a different thing altogether.
I personally suggest you abandon punching keys into a keyboard and get into something like hardware-hacking.
In the past few years, however, I've accumulated a pretty substantial stockpile of what I think are truly legit ideas that I am not in a position (without funding) to do justice to. To make things worse I'm not really seeking funding so I may never find out. Eventually I'll probably revisit the list and start putting them out there if the time that has passed hasn't made them irrelevant, or someone else hasn't already done it.
I think choosing the ideas you will pursue really needs to be tied closely to your goals / objectives.
[EDIT: After reading through some other comments it appears one in this thread is quite similar to the content that follows, but in my estimation different enough that it may be worth posting anyway]
Just interested in learning? Do a project that will allow you to learn about what interests you.
Just interested in making money? For starters my suggestion would be take an existing product / service (not patented) and make it better, or maybe tweak it slightly. The tougher / far riskier objective would be to take an untested idea to market and try to make money with it. Extrapolating that a solution to a pain point I experience is likely a viable business, or that just because a few people I know have an interest in an idea it must mean that many other people in the industry would likely pay for a packaged solution IMO is risky.
Want to do something to help make the world a better place? This, IMO, is probably the hardest type of idea to really turn into something worthwhile. Perhaps one of the easiest ways to chip away at this type of objective is take something you know well and share it with the world. Make an open source project out of it and license it with a nonrestrictive license such as MIT, BSD, etc.
Work on something that you will use. Something that you really want to exist and there are only sub-par or no alternatives out there. Whether this is something that will entertain you or fix a problem of yours.
It is most likely that if you find this product of use then someone out there in the world will think the same as well. However, this could be five people or thousands of people, it is hard to predict.
If it is really good then the money will follow, but instead of money, take satisfaction that you have created something from an idea and that there's at least one person other than you that is using it.