ExtraEight

How to release web applications — BETA, TEST, Pre-Release post

01.10.06

There’s a good post on TechCrunch about this whole “beta” fad that companies are partaking in to release web applications. It talks about the balance between making your site public too early and keeping it under wraps too long and going to market too late in the game.

It seems that when you distill the “beta” fad down to its elements, the purpose of it is purely for marketing. I doubt that any public beta has really benefited more from being public than private in terms of adding functionality and fixing bugs. A properly run private beta can be just as useful. But as far as marketing goes, TechCrunch provides some great pointers on how to use this marketing strategy.

The one thing I would add to this list is to write software for yourself. Create an application that you will use and then use it. You are your own best critic. If you don’t like it or don’t think it’s useful, then there’s a good chance that other people are going to feel the same way.

1 comment so far

Beta is such the fad right now, and it is totally understandable. When I was in college I loved getting beta software before it was generally available so I could tell my friends about all the new things. I think the marketting people are exploiting that, but the software engineers are just as guilty. Now they can leave bugs in a beta and still go to market, and just update later. These web services are interesting things since they tend to be server based, and changes can be made to a broad set of clients instantly. The new idea is: Get it out the door ASAP, then fix it. I think that’s great, but make sure you don’t leave yourself vulnerable to competition.



Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

(required)

(required but not displayed)