Week 8: Perpetual Beta

This week, our Web 2.0 pattern is the "Perpetual Beta".  Providing a service on the internet removes much of the costs and problems once associated with software releases: you no longer have to prepare such-and-such a number of physical CDs, and prepare them in boxes to be shipped on certain dates to certain stores in certain countries to be put on sale at certain times.  The producers need only publish their work to a given web space, and the service is thenceforth immediately available to all users.

This allows for a great deal of flexibility in release schedules.  You don't need to release everything straight away.  You don't need to do a great deal of internal testing (the users can do this for you, for free)!  The result has been the "Perpetual Beta".  Release early, so your users get some of the functionality immediately.  Release often, because there is always an improvement to be made or a feature to add.

What example can I possible use this week?  The "Perpetual Beta" is applied, implicitly, to all Web 2.0 applications; it is a consequence of the development environment, the platform, and the user's demands.  So why not talk about Facebook?

You can use the Facebook Blog to get a reading on how many updates are made to Facebook's functionality over time.  The last post made on the Blog is dated 19 January 2012 at the time of writing, but in January alone of this year the Blog announced more than 10 new Apps based around Facebook's new "Timeline" feature, and the ability to listen to music with your friends.  December of 2011 including the release of the Timeline feature itself, and many improvements for Facebook on Android devices.  It seems like every month they're releasing some extra feature or improvement, and this is without people designing all kinds of apps and games for Facebook in their own time!

Facebook might have been good enough had it stayed the way it was a couple of years ago, but by taking full advantage of Perpetual Beta, Facebook is always being tested by its users, and improved by the developers.  Facebook gets better every month because of this, and therefore is an excellent service for displaying the power of the principles of the Perpetual Beta!

Week 7: Software Above the Level of a Single Device

This week's Web.20 pattern is called "Software Above the Level of a Single Device".  The PC is not longer the only device that can be used to access the internet (and, therefore, all the useful and interesting applications thereon).  It therefore behoves the developer of a Web 2.0 application to consider which devices will users want to use when accessing this service, where (geographically) they could access this service, and what extra opportunities we can explore given this information.

Our interactions on the web are increasingly spanning all devices and methods of communication.  A photo taken on a mobile phone can be sent by email to a friend who turns it in to a satirical motivational poster using a  free web application, which is in turn uploaded to Facebook where it is now accessible to all his friends.  Each of these services (email, de-motivator, and Facebook) are now accessible anywhere because they are increasingly being designed to work on as many devices as possible, especially mobile devices.

Twitter and Facebook

Twitter and Facebook are two of the most successful Web 2.0 applications.  A huge part of that success is due to their being designed for use on mobile devices.

Today, smart phone developers explicitly advertise that Facebook and Twitter are accessible from the device as part of the devices services.  This Android, actually has a Facebook button under the regular QWERTY keyboard: simply press it, and you can be connected.

That's not all.  Twitter and Facebook are connected to each other such that any post made on twitter can be automatically  shared on Facebook as well (where it's easier to have an in depth discussion, if such a thing is warranted).

Twitter:

Automatically on Facebook: