Making Websites Beta
Posted by Andrew Faulkner on January 11th, 2007.
Andrew Faulkner has posted 211 articles.
RSS Feed for Andrew Faulkner
OK. It’s only January and the award for ‘worst pun in title’ has a clear winner.
It had occurred to me that many sites bear the word ‘beta’ in their logo or banner. But today I stumbled across three maybe four in a row. This got me thinking and inspired me to comment on the concept of beta.
First of all, let’s define beta in the context of websites, web-apps and of course software development. From wikipedia:
A beta version or beta release usually represents the first version of a computer program that implements all features in the initial requirements analysis. It is likely to be useful for internal demonstrations and previews to select customers, but unstable and not yet ready for release. Some developers refer to this stage as a preview, as a technical preview (TP) or as an early access. As the second major stage in the release lifecycle, following the alpha stage, it is named after the Greek letter beta, the second letter in the Greek alphabet.
Often this stage begins when the developers announce a feature freeze on the product, indicating that no more feature requirements will be accepted for this version of the product. Only software issues, or bugs and unimplemented features will be addressed.
Summarising, beta refers to a website or web-app that has the required features in place but has not yet undergone full testing and feedback. Now, with this in mind, think back to the many websites with that little word ‘beta’ shown. And this is the bit that irks me a little…
Why is that ‘beta’ there?
When viewing the majority of sites apparently in beta, I see no reason how they could be in beta. The functionality is there and the design looks complete. I’d expect a site/app in beta to actually have some information about the beta process. For example:
- Some indication of the features (and a small specification for each feature if this is relevant and secure)
- How will we know if it’s working if it isn’t clear what it should do?
- A list of reported bugs alongside a changelog if constant improvements are being made
- Why report bugs that have already been reported many times?
- A clear indication on how to report bugs or other issues
- Why find issues if you can’t report them? If you can find a way, wouldn’t it be sensible if everyone reported them to best aid the developer?
Reasons for ‘incorrect usage’
So why do people place a website in beta for no apparent reason?
- It’s cool. (Complete misunderstanding of ‘beta’)
- “All the cool kids do it so it must be a good thing to do.” ~ I think this is the most common reason for putting something into beta. It’s also the most pointless. There isn’t a goal in this.
- Lazyness
- “I’ll never finish this so I’ll put it into beta for now.” ~ A little better. At least there’s a finish-line defined. Still not the right attitude in my opinion though.
- Instant Feedback
- “If I put the word ‘beta’ on my site, then I’ll get lots of free, quick feedback.” Only works if you put the effort into the beta process. Again, the wrong attitude in my view.
In Conclusion
But it’s not all a rant. The beta stage in a project can be very fruitful. Just don’t expect to do no work and get miracle results. Inform the visitor of your beta project and how you’re working it.
I’d love to hear your thoughts on this issue. Plus any advice you have for the beta stage of website/app development.
Make A Comment
( 21 so far )
21 Responses to Making Websites Beta
It seems like a lot of sites are labeling their product/page as “Beta” because they’ve seen it being done on some of the Web2.0 giants. In fact, quite a lot of “2.0″ features are being mimicked by smaller sites that just don’t need them (ie Javascript effects, unnecessary AJAX etc).
Personally, I think it’s just a nuisance.
HAHA, so is it OK for me to make put a BETA icon on my site?? http://trevordavis.net
I’m trying to do all of the content for my site first and get the whole structure setup. Then I am going to work on the design.
That damn beta icon irritates me too.
beta in webdesignland here is synonym to a broken link, broken content, broken presentation. It scares users.
I think I am guilty for some of this “beta” stuff, but by the same token - when I use the term I actually have a design/site that is unfinished (AND still being worked on).
But, I guess I fail in letting users know WHAT is beta in it. :)
Trevor, I wish more people were as smart as you are.
Just coming up with reasons, one reason can be that it is difficult for the sites to come up with traffic prediction, and hence requirements to handle it. The beta stage can be used to get a feel of it and then incorporate that.
Of course, the beta also justifies if the site goes down unexpectedly ;-)
I studied software engineering and in those terms ‘beta’ means non public. I always have found it odd to apply the word beta to something ‘live’ and never advise a client to do it. To me beta always will be a testing process NOT a live site. The beta fad is really just that to me. It always makes me think of things like ‘too lazy to full test’. There are arguments saying it’s useful for testing and trying - why not have a private beta - much more elegant in my thoughts.
I saw a gamma site the other day… ah yes… it’s flickr! Web2.0 giants are evolving. Soon we will get to the web 3.0 fase!!
I personally have always interpreted “beta” to mean a sort of testing phase. To me its where you have mainly what you set out to do, but there still needs to be some adjusting to get it just right. Maybe more features, maybe tweaking some, but not things you knew before the release.
Tammie: I think the Web and and Software Engineering are on two totally separate wave lengths when it comes to “beta testing.” With software you can’t sell it and then take it back and fix it, however with a website (granted its not an e-commerce site or anything like that) you can always change things along the way without effecting much, especially blogs.
Either way I don’t necessarily think it means an unfinished stage, more of a way to improve through the comments and evaluation of others.
The thing is web = development at the core. So why should you be any less professional about it if you are in any form serious? If it doesn’t work why call it beta and make live? I think it only taints the quality. The difference is when it comes to the use of websites or just a few non functional errors? Change does not equal putting something in beta. Beta is a borrowed term with marketing spin that is now often (sadly) used as an excuse to not go through testing and just release and hope - only removing the beta when either web 2.0 unicorns have left the building OR when you get venture funding. Software engineering and web aren’t seperate wave lengths one is part of the other to a huge extent now in both methodology and process - mainly because of the shift towards web as application. It is also a point that Software Engineering even when I studied it didn’t mean just software it actually is an educational term for programming in many organisations. I majored in web development through it so the processes are real world.
I’m okay with something being beta and public, but what drives me nuts is when something seems to stay in perpetual beta - or even Alpha.
* “All the cool kids do it so it must be a good thing to do.” ~ I think this is the most common reason for putting something into beta. It’s also the most pointless. There isn’t a goal in this.
you could say this for everything associated with the buzz word “web 2.0″ haha
In my opinion, I think a website that’s been launched for the public eye should be past the ‘beta’ version. After beta is when when the site goes live and have been properly tested with a small group of users. If a site absolutely must be released prior to full bug testing then the current bugs should be acknowledged.
I’m making my site much the same as Trevor from response 2.
The content was created first without CSS and all along, displayed a large message telling users what’s going on and when the site will be launched. It’s always a good thing to let your users know what’s happening :)
The content was created first without CSS and all along, displayed a large message telling users what’s going on and when the site will be launched.
Why not apply already basic font styling for links, headings and text?
Why not apply already basic font styling for links, headings and text?
It’s a plain site that is built up over time. But yes, I got around to the typography fairly early in the design.
[…] The site’s pretty barren currently — I think I might be among the first dozen or so people to have signed up. It’s also in beta, like everything else these days, so I don’t want to be too judgmental. Nonetheless, a precursory glance leaves me skeptical about the site’s value — and, I swear, not just because I’m working on a social networking project of my own. […]
[…] In all honesty, I’ve only tested out the script in Firefox 2.0, IE 6, and Opera 9. I should have labeled the script as a beta, but I’m taking Andrew Faulkner’s advice and leaving the beta out of it. […]
Regarding the Beta argument…My website was originally launched in 2006. For the last few months I have been redesigning it for a relaunch this year. It has reached a certain phase in the design where the functionality is almost there and needs testing in its web environment. I have tested it as far as I can. I have launched the site in its ‘beta’ state and expect people to use it and understand its in its testing state. I have also placed a ‘Report a Problem’ link on all the pages including the homepage for users to use and identify and errors. And people have used it.This is what beta means to me. A prelaunch testing phase to try it out with real users. You’d be amazed at what people will point out in the testing phases. It can be a real eye opener. This makes sure that the actual launch is tried and trusted by your users with all their requirements met.I love live Beta testing. It benefits everybody.http://www.publicangel.com
I’m looking for people to test my beta websitehttp://www.hellosanta.org/ Send feedback to randy@kbcafe.com
Our site is currently in what should have been beta. Now we are working on a new and improved site that will go live without all final features. I think it will be useful to term in beta and get visitor feedback. Is it too late? Good tips on what to do to inform users!
Related In Some Way, Shape Or Form
The above post has obviously kept you amused. Why not discover similar material:
The posts Apple - Safari 3 Public Beta, TrendWatch Test, “Beta”, Does Anyone Care Any More?, A Darker Web?, Re-design announcement!, are related to this post.
Or why not take time out to find out about the author of the post.
Sponsors
Recent Comments
- Successful Facebook Applications Use Calls to Action:
[…] developers are using CTA’s in other ways within their applications. Matt Davies of Fadtastic... - Maria Rogers:
i hear that SEO experts earn thousands of bucks just optimising some large high traffic... - Paige Price:
my father practices Reiki and it is helpful for the general health.’`,
Search
Topics
Authors
- Abhijit Nadgouda
- Al Newkirk
- Andrew Faulkner
- Andrew Whitacre
- Anshul
- Chris Moseley
- Darren Hoyt
- Dean Hunt
- Derek Brown
- Ezekiel Bruni
- Gavin McFarland
- Jason Spector
- Johan
- Terry Ng
- Marc Bernstein
- Matt Davies
- Michael Murphy
- Mike Bishop
- Phil Renaud
- P.J. Onori
- Ron Scott
- Steve Rose
- Steven Teskey
- Tadeusz Szewczyk
- Tammie Lister
- Ted Goas
RSS Feeds
- Complete Feed
Everything from fadtastic. - Articles
Just the articles. No news/blog. - Reviews
Our book, brand and service reviews. - Blog/Site News
The 'FadBlog.' Site updates and news.
9rules
