For web applications and services, this problem was less of an issue: only the internet application itself would need to be updated. Everyone who utilised the application was using the latest software. However, the service would need to deny access to users whilst updating. But then, there's cases where an application provides its services, but still updates behind the scenes. This is where the Perpetual Beta is most recognised; an online service or application that incrementally improving itself to suit its customers, possibly without denying them the service.
"Perpetual Beta" implies software that isn't quite ever finished, but it would be more accurate to say it's about updating software in small but often bursts, as opposed to large patches. A website that continually improves itself gives the illusion of being alive as it evolves. There are several advantages to updating often and online over the traditional monthly patch:
- Gradual Changes ease new features into the system
- Lower risk of implementing bugs
- Increased response to errors and feedback
One site which has taken advantage of this pattern is Kongregate, a website dedicated towards flash games. Originally starting with the simple ability to play (and upload) flash games, record user profiles and record the games they play, Kongregate has slowly implemented features such as achievements, forums, contests and a "beta" section (where developers can test their games online and see how they look in the browser). When it began in 2006, updates for the website itself would only be made once every few months, but developers quickly adopted the "Perpetual Beta" format, adding new features and providing a better service for their users.
Kongregate's beginning was slow because there weren't many features or problems to patch, allowing its developers to cover all its primary functionality. When the core essentials were set up, Kongregate reaped the benefits of the developer pattern. The service was able to expand gradually with new features, services, and developers to focus on issues (usually because they were related to said features).
The flash game website has been fleshed out over the years and continues to look for ways to improve its user experience, but it is never quite "finished."
References:
Steve Matthews, (10 August 2011), Perpetual Beta – The Real 21st Century Library Model?
Wikipedia, Perpetual Beta article, retrieved 28 April 2012
Bill (Praxis101), (17 May 2006), "Perpetual beta" means never having to say you're sorry
Caroline McCarthy, (18 January 2007), Perspective: Beta--the four-letter word of Web 2.0
Kongregate Website
I hadn't heard of Kongregate, just checked it out. Very cool site, will have to spend some time exploring the games. It never ceases to amaze me the variation in websites that are Web 2.0 platforms, often sites I would not have stopped to think about as possible examples. I think you have tied the pattern and Kongregate together well.
ReplyDeleteThanks, I've wasted plenty of time playing various games on that website. It's just too bad flash games can easily lose save data!
DeleteI think this is one of the harder design patterns to identify simply because most websites have had plenty of time to develop. I also believe the only ways to know of prior iterations would be either interact closely with the website in its early stages or somehow find an extensive version history of the website.
Great find Courts. I had never heard of this site before either. Do you know if there are any other sites doing the same thing? It looks like a great platform for people to develop their games on and a lot of fun!
ReplyDeleteHm, well if you simply want to play flash-based games, Nitrome hosts a wide array of unique games, while Miniclip focuses on socialising while playing.
DeleteThen there's the website giant Newgrounds, which adopted the perpetual beta pattern too. That is to say, it started from just flash games and movies in 1991, to music and art whilst adding key features like a robust ranking system and forums.
I also have never heard of Kongregate, it is actually very cool!! I have a pretty good knowledge of the benefits of Perpetual Beta now, but I'm not aware of the drawbacks to using this method , do you know of any?
ReplyDeleteThe biggest issue with updating often is that maintenance costs time and money. A business can't benefit from a service while it is denied to its audience. Therefore (possible expensive) precautions must be taken in order to minimise the impact. These can be from hosting an alternate address while the official is under maintenance, to locking off only the parts of the service that were affected.
DeleteAlso, the "Beta" label can discourage potential users from using the service, as it implies "not finished" which is usually synonymous with "unstable". Likewise, sometimes businesses use the word as a scapegoat: "A feature isn't working? We're still in beta!"
The Perpetual Beta pattern isn't automatically an improvement, nor do these problems always arise when utilised. A service which has all the core functionality in place can benefit greatly from gradual expansion. On the other hand, a poor service may be wasting resources trying to cover up all its errors.
great post that introduced a simple process of development of Kongregate. from that, i can clear see that they implement "Perpetual Beta".I really agree that web application still need detailed test before it be released. Even user become co-tester for web application, as the client of web application, web application require should supple good user experience. regularly bugs will lead to customer drain. common internal test is still important！
ReplyDeleteAgreed, customers are not the same as a quality assurance team. The former usually want to use an application for themselves, the latter thoroughly try to find every hole and exploit in the system. Issues that are found from the public are bad for a business. The least that could happen is bad publicity, but the worst can include stolen goods and information.
Delete