Web 2.0 Applications



Pattern 3: Innovation in Assembly

Innovation in Assembly is about using a platform strategy for your web 2.0 application. Okey, what does that mean? It means that in addition to the fact that the Web is about to replace desktop operating systems, web sites are doing the same. What is the benefits with this? Well, platforms gives you a more measurable growth, third party innovation, they build trust and community, you get a better idea of how your services are used and income can easily be attached to a platform. (J. Watson, 8. March 10)

This weeks example is Google Wave. “Google Wave is a product that helps users communicate and collaborate on the web. A “wave” is equal parts conversation and document, where users can almost instantly communicate and work together with richly formatted text, photos, videos, maps, and more. Google Wave is also a platform with a rich set of open APIs that allow developers to embed waves in other web services and to build extensions that work inside waves.”

When do you use Google Wave? Some of Googles suggetions are; organizing events, meeting notes, group reports and writing projects, brainstorming and sharing photos. And thats just a few examples. The application is still in the development stage, so its currently only available in a limited prewiew. It is going to be exiting to see how popular it will get when it opens for the public, but I believe its going to be the next big thing. Google Wave is all about communication, and here you can communicate with everyone, no matter what you are communication about.

One of the issues with the platform stategy is the Terms of Service. Services are often provided “as is”,  finding the right level of support as a provider and for the consumer to understand the limitations are often debated. After reading through Google Wave’s Terms of Service its two points that I wish to comment on;

4.4 You acknowledge and agree that if Google disables access to your account, you may be prevented from accessing the Services, your account details or any files or other content which is contained in your account.
14.2 You expressly understand and agree that your use of the services is at your sole risk and that the services are provided “as is” and “as available”.

As I mentioned before, many applications provide the service “as is”, and as you can see, Google Wave does the same. They also state that if they decide to disable your account, you loose everything. This is a problem with many applications, you have no guarantee that the service wont get shut down, or that they decide to for some reason to shut down your account.

There is also one other issue with platforms, and that is the technology gap. Transaction support, security and localization are often not complete solutions. And with a application like Google Wave, where you will be sharing so much information, it could be easy to do for example a identity theft if the security is lacking.

I believe that Google will do what it takes to take care of the technology gaps, wherever it is possible. They have a staff of experienced developers, and its not the first time they are making an application. They know what they are doing. They also have many people that helps them with testing the product, inculding me. And they dont have a date for when it has to be finished, that is something I believe is a crucial factor. They dont have to rush anything, they can take their time to make it right.

Advertisements

Trackbacks & Pingbacks

Comments

  1. * jrsketcher says:

    Interesting choice of Web 2.0 application and nice job on explaining what it’s about. I’d like to hear a bit more about what specific APIs have been used for. You’ve obviously read the lecture notes and maybe you could show a few examples of those points you mentioned as they apply to Google Wave? Short and sweet blog. 🙂

    | Reply Posted 7 years, 4 months ago
    • * nymphad says:

      Hi! Thanks for the comment! You where a bit to fast though, I managed to copy the wrong version. You should read it again! I believe I at least have answered a bit better about the examples from the lecture notes:)
      At the Google Wave API Lab they explain:
      The Google Wave API allows developers to use and enhance Google Wave through two primary types of development:
      * Extensions: Build robot extensions to automate common tasks or build gadget extensions to provide a new way for users to interact
      * Embed: Make your site more collaborative by dropping in a Wave
      I hope that answeres your question!

      | Reply Posted 7 years, 4 months ago


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: