Wanting to build good, useful software is a great goal, but one of the first questions raised in this quest is what to build. That is the question I wrestled with last year when contemplating starting Useful Fruit. As an avid Mac user, I was pretty set on the platform to target, but that didn’t help with figuring out the problem to address.
At first, I looked for problems in the security space, as that’s where much of my background is. This space is mired with “magic bullet” products that customers don’t understand and that don’t solve those customers’ problems at all. There were two problems with this space. The first was that security is hard, particularly to do in a general way for consumers. That’s one of the reasons that there are so many useless security products out there. The second reason security was a problem was that I was working a day job for a security company, and they felt it would be a conflict of interest for me to build a security product on the side.
So, a security product was not in the cards. I wasn’t really disappointed, as I was ready for a change of pace anyway. Of course, I still didn’t have a problem to solve. Thankfully, with no direction I fell back on the advice of I kept hearing over and over – solve your own problem. What problem was that? Let’s just say I’m the kind of guy that walks out of a meeting, looks at his notes, and realizes that I missed the last 20 minutes and I’m not sure what the notes I did take mean.