3 reasons why I believe Google Buzz has already won
I am sure you ‘ve heard of the latest Google product named Buzz, right? I am still waiting to see the Buzz link inside my Gmail. What about you? I have already commented/liked a couple of Buzz(es) till now. And for the last hour or so I ‘ve been looking around for some Buzz^2. For the time being I can already give you 3 reasons why I believe Google Buzz has already won.
-
It uses Google Accounts
There is so little chance that you don’t have a Google Account these days. What about a Google Profile? With Google Buzz your Google Profile is now getting in action. Featuring followers/following, public Buzz timeline with likes, comments, maps and more. Have you been using OpenID lately? Which account provider do you use the most? I bet Google is your first choice (if applicable).
-
It’s not a first mover
As Robert (Scoble) has mentioned before “The problem is that first mover rarely wins“. The thing is, Google is not a first mover in this. Google Buzz takes advantage of some of the most intriguing and successful existing features in other web services like FriendFeed and Twitter. It has incuded the Followers/Following feature which has proved its popularity in the latest years (see Twitter, FriendFeed, etc.). It also uses Google Reader’s and FriendFeed’s Like feature. The appearance of Google Buzz is very FriendFeed-like. I am not sure if Google Buzz can succeed where FriendFeed couldn’t, but I bet this time Google’s social fight/attempt will turn out successful.
-
It is made of PubSubHubbub
It’s real-time. Enough said. :)
There are also a few other stuff that make Google Buzz stand out. For instance, have you tried editing you comment or removing your “like”? See what happens to that buzz mail in your inbox? ;)
Google Buzz is up and running

Google Buzz is live. It is still rolling out to everyone, so you should get your update soon. I am already seeing a Buzz tab in my Google Profile. Do you?
Google Buzz is a new way to start conversations about the things you find interesting. It’s built right into Gmail, so you don’t have to peck out an entirely new set of friends from scratch — it just works.
Although I still cannot see Buzz inside my Gmail or via my Phone I have to say that I am a little bit excited. Google Buzz APIs are already available here.
Nexus One: The Story

If you are into mobiles, gadgets and all the latest tech going on out there (especially Android), it’s almost inevitable you didn’t notice these series of short films, that came out lately, documenting the making of Nexus One. They are split up in five parts, each one containing a bit of the life cycle of a Nexus One ranging from basic concept and design details to everyday using of this superphone. The five parts can be summarized to this:
- Episode 1: Concept & Design
- Episode 2: Display & 3D Framework
- Episode 3: Testing
- Episode 4: Manufacturing
- Episode 5: Day One
Twitter: Project Code Swarm

Twitter Code Swarm is a very interesting visualization of the explosive growth of Twitter as a development platform. The video below illustrates the amount of work it takes to build something as seemingly simple as a website that lets you publish 140 character status updates.
The “recording” period starts in April 2006 and ends in January 2010. Enjoy!
Did you noticed the music playing? Have you played the Braid game?
P.S. Project code_swarm is also available on Google Code and github.
[ via - photo via Michael Ogawa ]
Google Tablet featuring Chrome OS coming soon?

Yes, this could be true. Although a Google-branded tablet is not even a rumor yet, Google engineers have been working on various concept User Interfaces for Google Chrome OS coming soon. Moreover, Chrome OS, will not only be available for netbooks, as we originally thought, but we will be able to use custom versions Chrome OS in various devices each having vastly different input methods, available screen space, and processing power.
While its primary focus is netbooks, Chrome OS could eventually scale to a wide variety of devices. Each would have vastly different input methods, available screen space, and processing power.
This is quite interesting, isn’t it?

Check out more Chrome OS concept designs for Tablets here.
Note to self: I think Google Wave, due to its nature (for the moment), fits best in a Tablet.
Mozilla Weave Sync API released! Plus a number of early prototypes and sample code.

A couple of days ago, Mozilla Labs released new Weave Sync APIs and resources for developers. If you have no idea what Weave is you should check it out here. Weave aims to seamlessly bridge your desktop and mobile Firefox experiences, by syncing bookmarks, saved passwords, browsing history, and open browser tabs across your platforms. So, in short you can leave your home computer and access your, lets say, browsing history via your mobile phone.
For the time being such capabilities existed in the iPhone but only limited to the bookmark syncing via MobileMe features or via apps like Instapaper.
There is also Google Web History which merged with Google Bookmarks last summer and now has some great features like viewing your web activity, searching the full text of pages you’ve visited, getting personalized search results and more. However these features are only available if you install the latest Google Toolbar and there is no immediate access via your mobile phone.
So, Weave is here to change this. You don’t have to install any toolbar and now that there is an API out there the possibilities are numerous. Mozilla already released a number of early prototypes and sample code that have been developed alongside the Weave APIs including a web-based Weave client, an iPhone Weave client, a commandline Weave client and a WebOS Weave client.
Now that Weave API is out I would love to see a Weave client for my Android phone along with some import/export features in Weave or even better some Ubiquity commands to interact with the Weave.
By the way, does anyone know when the latest Ubiquity version will be available for Firefox 3.6?




0
Unless otherwise noted, all material is licensed under a