Webreakstuff's blog on design, development and strategy. Click here to subscribe.

Stop using the “beta” label

Fred Oliveira on September 11, 2006 Comments (32)

As you’ve probably noticed if you read the previous post, Goplan launched a while ago. If you look closely however, you may notice we didn’t call the launch a beta like it seems most people would assume (this is web 2.0, right?). Here’s the reasoning behind that decision:

Beta software has been labeled that way in the past few months because it’s a trend. You launch something you feel isn’t quite “ready” so you tag it as something that gives the user the idea that it may fail. This is mistake number 1: if you launch software and are passionate about it, avoid having it boil down in the hands of the user. You should focus on making it work, not excuse yourself using by using the “b” word if it doesn’t.

Launching web applications is a risk – a risk you have to take, as the developer. Calling the product a beta doesn’t alleviate that. Fact is, if it involves people’s assets or (even) a small part of their lives, the risk is on you. Launch it if it solves a problem, not if it creates several. Any other decision would be mistake number 2.

If its a test, call it a test, and a beta isn’t a test. Lets face it, we’re never sure something will work right. We’re never sure the way we thought about something is the way most people would – and that makes testing a necessity. But make it clear that you are still unsure about certain things, that people can trust you’ll listen, and that you’ll avoid whatever mistake number 3 might be.

Just don’t label your web applications beta.

View/add comments on this entry

Comments on this post

Luke Redpath

Couldn’t agree more!

Jeremiah

I’ confused – we should take care to label things accurately, unless it’s an actual beta, because then we’d just be trendy?

I don’t know how many web apps call themselves “beta” because they think it’s cool. GMail’s been “beta” for some time, but because it’s actually in a beta phase – similarly with Flickr (although, Gamma!??).

I think if you’re a beta product, call yourself that and leave trend worrying to your marketing flacks.

JacksonLatka.com - Blog - Jacksonian Theory » Don’t Label Your Web App “beta”

[...] In the web world, the “beta” trend, or more specifically the usage of the “beta” tag on a web application logo (see my post on web 2.0 logos) started somewhere and seems to be nearing its end now (or at least it should be according to the web app team Webreakstuff). They bring up some good points in their post about why developers should stop marketing their applications as “beta” (or stop releasing them if they really are not ready). Stop using the “beta” label. [...]

Mack D. Male

I don’t think there’s anything wrong with the term “beta”, except that thanks to Google et al, you now have to qualify that you mean a “classical beta” in which you get users to test out the product before launching it.

You’re right, it’s probably easier to just avoid the beta label altogether.

Terry

That’s a good thought! O well, maybe I should mark my site as “failing”…lol

geniusleft

This is a interesting discussion. I post related blog for this :D

http://geniusleft.blogspot.com/2006/09/is-beta-equals-web-20.html
Is “beta” equals Web 2.0?

I thought you can labeled your site “beta” early if your site meet the web 2.0 principles especially “update frequently”.

kahfei

The ‘Beta’ tag might really soon look like those hair bands being wear in the 80’s.

knowologist

i have commented on this before, and here’s what i think: beta tag in web world doesn’t mean necessarily the app is buggy or is likely to fail in users hand. I realy like to think that beta tag means the app is still evolving, or updates frequently like geniusleft said. So in web, beta doesn’t mean buggy apps, just apps giving users limited services.

I have used gmail while still in beta and i don’t remember it to crash, but i remember existing services becoming better and new services being added. :)

Remember your last article about the necessity of failure and natural selection in web20. In web nowadays, if something doesn’t evolve it’s likely to fail and fade sooner or later.

Conlusion: that leads us to have two definitions for beta: the classic-desktop-buggy-beta-testing application and the new-web-evolving-but-stable-beta application.

PS.: I’m not in favor of the (ab)use of beta tag in web. In fact, i don’t like it that much. Due to their nature, it’s kinda obvious that web apps can (and should) update frequently and evolve. At least for us, developers, isn’t it guys? :)

Mind Booster Noori

> GMail’s been “beta” for some time, but because it’s actually in a beta
> phase

No, sorry but I can’t agree. Google started this trend of calling “beta” to apps that aren’t. Not that I completely agree with Fred: I understand his points but still I think that there’s a difference between beta software and it’s Gold/general availability release, and if some software is _really_ in a beta stage, then it’s users should know about it (either if you call it plain “beta” or something else). The problem is that many developers, like Fred said, chose to think about the “beta” tag as “a web 2.0 thing”, something nice to have, just like rounded corners and preety large characters. You talk about the sequence of versions on Flickr, I plead you to consider what’s happening right now with Google’s Blogger: they’re swapping the standard versioning scheme!

So, while I’m not a completely fan of the “give away from beta tags” message Fred tells us, it would certainly be better that way than to see people using that tag as they do now. But the best scenario would be seeing the “beta” tag being used as it was allways – before Web 2.0.

Goplan offers competition to bellwether Basecamp at FactoryCity

[...] I got an invite from the good folks at WebBreakStuff today to check out Goplan, their latest product beta (but it’s apparently not a beta). [...]

Terence Pua

For paid software, I would agree that using the beta tag should NOT be used, including freeium SaaS.

But for “free” software, I don’t think this is necessarily true. If a user doesn’t want to use it because of the beta tag, move on but developers should not be penalized for using the beta tag in this particular case.

Matt Robin

I completely agree (although with some sites – isn’t it the use of ‘beta’ as a tongue-in-cheek reference only – not given with any seriousness?)
It is getting over-used and it has already become a trend associated with web 2.0 sites (web 2.0 being a buzzword itself – there wasn’t a web 1.0 talked about before web 2.0 was mentioned). I think ‘beta’ can still be used legitimately for applications/web-apps that are in a test stage of development – but shouln’t be labelled on websites that are actually LIVE, complete projects. Hmm…that’s sort of what you’ve said anyway – ha! So, I agree with this article on principle – but the trend will continue regardless.

Mic

I find it hilarious that every site that gets built these days have the word beta on the logo.

Also, the amount of sites that flickr has inspired is ridiculous! fastr, delivr, socializr

anyone else find thse funny? =)

Jason Sanzone

If beta means the site is still evolving, there would be no point in it, all sites are evolving. Google is updating its algorithm’s constantly; Google Beta. Sites are adding to their functionality all the time. I could see it being useful to let people know that the majority of the site is still under construction, or that the site is in the very early stages of its development and still may be majorly buggy etc. But sites like Gmail that keep it on there for years, are just ridiculous. We all know Gmail works almost flawlessly and it’s not in early stages of development. The beta tag could be useful, but its become a pointless buzz word.

To beta or not to beta « Ben’s Blog

[...] The team of individuals from Webreakstuff have answered this question quite nicely in their blog post “Stop using the ‘beta’ label”. [...]

Beverly Trayner

hum

beta, for me is a mindset. one that says – nothing is finished, nothing is perfect, everything is in process. and, what’s more, we want to hear even the smallest opinion in that conversation towards finishing.

i like the way developers of applications in beta respond so quickly and with an interest to know more about my teeny tiny niche in the market.

anyone who calls themself beta but isn’t tuning in to the quiet voice isn’t interesting to me. but for the rest – I HEART BETA!

Tekno Seyir » Blog ArÅŸivi » Proje yönetimi için alternatifler

[...] Ve bir not, yeni web 2.0 servislerinde görmeye alıştığımız beta ifadesi Goplan’da yok, kullanıcılara sunulan ürünlere beta demenin yanlış olduÄŸunu ifade etmiÅŸler. [...]

Brian

In software development, software achieves alpha stage after it reaches of set of milestones where features are frozen (no more features to be added), but internal testing still needs to be done to make sure those features work properly. After it passes internal testing (alpha), it then goes to beta testing where it is exposed to external testing (by those outside the company or group).

The fact that so many websites are using beta is a sign that people are starting to treat their websites as applications. That is one of the core elements of this whole Web 2.0 movement. It is more a difference of mentality than anything else.

In my opinion, this movement is a good thing. However, they should be treating the beta testing as beta testing, and many websites do not do that. An example of proper beta testing is what Krugle.com did for their code search engine. You had to sign up with a beta testing account and they emailed you the correct link to login and test. In theory, they would have a cutoff limit (although, I don’t think Krugle did have one).

Beta should not be a finished product/service open to everyone. It should also not be a sign for constantly evolving software, because, as someone stated earlier, most software is constantly evolving. That is why version numbers are used.

Brian

Correction… Beta is where the features are frozen. Alpha is where a majority of features are implemented.

http://en.wikipedia.org/wiki/Development_stage

Oskar Syahbana

Well, the GoPlan site isn’t fully accessible yet (I think it’s invitation based?). So although it isn’t a beta, I wouldn’t call it a non-beta product either.

Fred

We’re doing user testing, it’s definitely not something we’d call a beta.

Dan

go GAMMA!

adaptive path » blog » blog archive » Signposts for the Week ending October 6, 2006

[...] Michael Beirut writes a moving tribute to Alan Fletcher, for whom “design was not a profession or a craft, but a life.” Enough with the Beta label already begs WeBreakStuff. We agree. [...]

harwin

Marvelous. Thanks, will spread this among my friends!

hermes

Marvelous. Thanks, will spread this among my friends!

hashbat

Marvelous. Thanks, will spread this among my friends!

helle

Marvelous. Thanks, will spread this among my friends!

Sten84025

I’ve just been staying at home not getting anything done. I guess it doesn’t bother me. Shrug. I haven’t been up to anything. I haven’t gotten much done today.

Antonio

Very nice site! Good work.

trama

Ich erklare meinen Freunden uber diese Seite. Interessieren!

imparare

Interesting comments.. :D

Proje yönetimi için alternatifler | Rasim Coşkun | Web Tasarım | Web Design

[...] Ve bir not, yeni web 2.0 servislerinde görmeye alıştığımız beta ifadesi Goplan’da yok, kullanıcılara sunulan ürünlere beta demenin yanlış olduğunu ifade etmişler. [...]

Something to say?