I believe that's what a Beta used to be before the 2.0's started tagging everything with it and making incremental changes to their work based on incessant user

I believe that's what a Beta used to be before the 2.0's started tagging everything with it and making incremental changes to their work based on incessant user feedback. The problem today is that an entire plethora of applications target the many pieces required to solve your problem if not the core problem itself, so you either have to include a baseline of functionality expected in todays's app and risk being flushed away or you actually revolutionize the space from the ground up at the risk of total failure. It's a choice you have to make and with the speed of today's releases and the reactions of social media (see: Color) you need to strike a balance between vision and feedback instead of focusing on point releases, which are in themselves kind of pointless. tl;dr: this article addresses software as it was developed ten years ago and includes a most horrid blog theme to boot.