Always Be Releasing (ABR) approach to software development

Something I have been noticing with software development and the software's user base is that more and more users expect software to be in a constant release mode (which I call Always-Be-Releasing approach). That is, they really don't like the older, more traditional methods (very much like what Microsoft does) where a version is released and any fixes are passed down through patches with new version coming every year or more. It appears that the software release approach used by Open Source where the developers are constantly and consistently releasing new versions (even if its just a dev/snapshot build) is a much more desirable, and in some ways, an expected approach.

If you were to release updates to your application(s) on a daily/weekly basis, even with just minor changes, your users will think the application is always being worked and gain a level of confidence that is hard to come by now. There are just too many dead-applications cluttering the software database websites, the search engines and the software review websites. Users want to make sure the time they invest in learning an application is not going to waste.

The days of a software title release every year or 6 months just doesn't cut it anymore and only upsets your users. Stay in an Always-Be-Releasing state and you will find you users are much happier, contribute more with suggestions and develop a stronger loyalty to your company and software.

Thoughts, leave a comment...