There's something to be said for having a pet side project that adds some value to your life in the form of a warm-fuzzy / proud-papa / glad-I-did-that feeling. But that feeling subsides after a few years when your pet is starting to throw tantrums and rip up the carpet. At that point, you start to realize that the fleeting "value" most of those efforts created is long gone and all you are left with is a drooling, malfunctioning beast.
I spent 5 years from late 2005-2011 building applications that created little slices of value for people in return for nothing: CalendarHub, DryRunner, WoodenCube, Rezzible, BibleApps, Blogger Plugins, Chrome Extensions. It was a great run, and had I done all of these in school rather than side projects during a taxing career, I'd probably still be proud of them. But in the end, they made no money, and for the free-to-play projects still clinging to life, there is little incentive for me to go back and do something with them.
I am purposefully being a bit reflective on what I've done and the results they've given me, because I'm getting primed to go on a tear in mobile apps. I'm trying to distill some lessons from those bad choices and apply them to the mobile space, and what I know about mobile apps in the App Store and marketing in general is that All Apps Decline... which makes mobile seem like another mistake if not approached carefully.
To contrast my previous efforts, I've had one success in monetary terms: Appointron. It makes more than enough for me to justify continued work on it, and the market is huge, so it gets love all the time. That brings me to a couple of stark conclusions, one of which I've already tipped my hat to:
1) All products that you build need ongoing maintenance... so they better pay you something for the effort, else it will always be a drudgery to go back and fix the brokeness over time.
I'm not saying that a free project that never pays you cannot be fulfilling, I just think there is a drop-off in that fulfillment that is unexpected and you must factor that in when you start something.
2) You need to be willing to kill projects that don't go anywhere.
This one hits close to home. The reality is that there is a % of your time/brain that you can use to care about those products, and if you keep them around without receiving benefits at all, then they are simply a drain on your time and talent. Cleaning house is hard many times because you still believe there is some value locked away in those auto-pilot projects that you can somehow harvest. You are probably fooling yourself here.
Focus on things that create real, long-term value for 3rd parties, and make sure they pay you.
Wednesday, February 13, 2013
This morning I opened a work-item with a vague description of the work to be done. Since I don't know much about this particular project...
Google's recent announcement of algorithm changes that involve preferring secure sites over non-secure ones certainly created a collect...
Ad copy can sometimes border on the insensitive, especially when you're in objection-killing mode. To some people the BATNA is way too s...
The Customer First-Run Experience That Is Taking Over the SaaS World There is a type of non-scalable conversion tactic for new customers ...