About Me

My photo
Brisbane, Queensland, Australia
I am a full time computer consultant for a small firm, focusing on the small to medium business sector. I am also a student completing a Double Degree in Business and an Information Technology at Queensland University of Technology. This has created a hectic schedule and, as a result I am always busy working on something.

I do however have interests that are outside of work and University, including active involvement in the scouting movement and regular games of indoor soccer at Brisbane City Indoor Sports. My passion however, has always been in computing. This is shown by my active participation in the computer club at high school. I joined the school computer club in grade eight and continued right through to grade twelve. I was also a member of the computer club executive from grade ten.

I intend to use this blog to discuss a variety web 2.0 applications and how they relate to the web 2.0 patterns. I encourage you to read my posts and make comments below.

Thursday, May 12, 2011

Perpetual Beta

Running an application as a web service allows software developers to change the development life cycle they follow. The 6th web 2.0 Pattern, Perpetual Beta, deals with this change and its effects for users.

Software developed for using the traditional development life cycle, such as Microsoft Windows or Adobe PhotoShop, are developed and deployed on the system of the user who is running the software. In contrast, Web 2.0 applications run on the server which the developers control. Compared to the traditional method of deploying software on users’ systems, new Web 2.0 methods of providing users with software have several advantages for developers.

When traditional software has been developed, users will install the software on their device. When this software needs to be updated, the developer can provide the users with the update but has no means of ensuring that the user applies or installs these updates. Google has developed many applications which fit under the perpetual beta banner. As an example, today I will examine Google Docs.

The large majority of Google products and services, as shown on their product listing page, fit the model of the perpetual beta. Google docs is a office suite of applications (similar to Microsoft office) accessed on the cloud. This service is designed to allow users to share files: the documents are stored online, and this enables any user to view the most recent version of the document. This Web 2.0 application is also a good example of the perpetual beta model.



As a regular user of the google docs service, I have received the benefits of the self-updating application, as new improvements are installed without my having any imput from myself. I was not presented with an option to download or install the new version, only a small text notification box briefly explaining the changes that had been implemented in the new version, There was also a bright red link, which took the user to a page with details about the new features.

3 comments:

  1. One thing that caught my attention is that most of the collaborative tools you find on the web today be it diagramming (processwave, gliffy) or word doc(google docs) as mentioned in your post are always on beta. I guess this is the way to go forward now and also in the future.

    ReplyDelete
  2. Google docs doesn't need an introduction, most IT professions or anyone who is tech savy should be well aware of the reaping benefits it provides to its users.

    You have chosen a good application. Google Corporation certainly utilises the beta system towards their current and upcoming products. I can note one product that I have used in the past, it is called Google Wave, which Google has already announced that they will not be continuing developing this service due to the application's low transition rate.

    I am heavily relying on Google docs for my group assignments but am still in love with MS Office. I must be honest, MS Office still has better user experience compared to Google doc. Maybe Google docs should start delivering people's feedback about trying to replicate similar tools to MS Office as an online service and provide better user experience. Could be breaching copyright or cost Google pots of money to develop something? Where do you think the future of Google docs is heading? Better improved user experience?

    ReplyDelete
  3. I agree that Google do have a long way to go before they can completely compete with Microsoft office. For me, the big difference is with formatting and presenting the work. I am hopeful that these features will soon be added to and improved upon on the docs platform.

    When the Google docs service launched, they did not offer any way to insert tables into their documents. I found this to be very limiting but they have since added this feature.

    Hopefully Google will continue to add these kinds of features to eventually make their free web 2.0 application just as useful for creating professional documents as it currently is for collaborating on a document.

    ReplyDelete