eWeek Microsoft Watch
Advertisement
Advertisement
June 6, 2007 1:55 PM

Can Microsoft Be the Wrench in Google Gears?



Joe Wilcox
Joe Wilcox

Dare Obasanjo, a program manager for Microsoft, in a recent blog post raises concerns over Google Gears' synchronization capabilities. Microsoft should be very concerned that Google might do synch right.

Gears is Google's attempt to provide software developers with a means of offering offline access to just about any online content. Synchronization is essential to the whole concept, where content would automatically synch in either direction.

Obasanjo blogged last night that something is missing:

"It seems that without providing data synchronization out of the box, Google Gears leaves the most difficult and cumbersome aspect of building a disconnected Web app up to application developers. This may be OK for Google developers using Google Gears since the average Google coder is a Ph.D but the platform isn't terribly useful to Web application developers who want to use it for anything besides a super-sized HTTP cookie."

Gears is still at the beta stage and Google may yet improve its synch capabilities. Regardless, Microsoft should consider itself lucky, if Google soley focuses on Web content. Quite possibly, synchronization is the killer app that will determine whether desktop software maintains its relevance or the Web becomes the more popular platform.

Synchronization Hub
The natural place for synchronization services is as part of the operating system. Apple and Microsoft moved in the right direction but neither reached the destination.

Long ago, Apple made iSync part of Mac OS X and then failed to extend it—or .Mac synchronization—in any meaningful way. Apple had an early lead on Microsoft that wasn't exploited: synchronization as part of the operating system. The Mac maker should have made iSync a more pervasive service leveraged by its iLife software and extended to third-party applications and hardware. Instead, iTunes is the synchronization hub for Apple software and services. The approach lets the company bring products like iPod and Apple TV to Windows but blocks a natural place to really extend and differentiate Mac OS X.

Microsoft has done no better; in fact, it's done much worse. There was so much promise! During its 2003 developer conference, Microsoft promised synchronization as a core service of what was then called Windows "Longhorn." Windows Vista does ship with a feature called Synch Center, but it's not a unified, universal synchronization service. Windows Mobile devices need separate software to synch with Outlook, for example, and there is no real support for Web services.

Microsoft should worry lots more about universal synchronization than it does. Microsoft offers too many synchronization mechanisms that simply don't play well together, if at all. Take the so-called RSS platform introduced with Internet Explorer 7 and extended with Windows Vista. The service is its own silo, yet Microsoft promised tons of extensible functionality. But where is it and how does it work with other content?

Microsoft's MTP (Media Transport Protocol) has the makings of a universal synchronization process, but where has it truly been extended? Windows Media Player? It's odd enough to synch photos, movies, music and contacts with iTunes.

Next to security, synchronization should be Microsoft's top development priority. The company that solves synch—and so far Apple is way out in front—will rightly connect together the Web, the desktop, the server, consumer- and commercial-generated content, and data stores ranging from cell phones to the display on the refrigerator.

Risky Business
If Google gets synchronization right before Microsoft, it's game over. Google would be able to extend the relevancy of the Web platform back to the desktop on its terms; think invading army. If Microsoft gets synch right, it can drive desktop relevancy the other way, invading Google turf. Microsoft missed a huge opportunity by failing to deliver synchronization as a core Windows Vista service. Google could exploit this failure.

Google Gears is a much greater problem for Microsoft than all the fuss bloggers and news organizations make about Google apps' competition with Microsoft Office. Google may not have got synch right today, but there's always tomorrow. There are enough Web startups and established Web 2.0 players to make synchronization the possible killer application for the Internet. Everyone would want it.

The Web platform's promise is access to content anytime, anywhere and on anything—as long as the user has Internet access. Google Gears could bring some of that information offline, further extending that promise. Universal synchronization would be game-changing, however; it would be a paradigm shift for digital devices, desktop software and the Web.

Today's situation reminds me of the state of the PC 15 years ago, when competing formats and applications didn't work well together. Eventually, the market consolidated around products and file formats rather than universal synchronization mechanisms that would have allowed peaceful coexistence. Microsoft emerged the major victor from the bloodbath.

Today's situation is like a good game of "Risk," where rival camps gain territory. Microsoft obviously is one player, while Apple and Google are others. Apple is a player because the company got synchronization right with iTunes and the iPod. I contend that synch is perhaps the major foundation for the iPod's success. Apple got this fundamental process right and then extended it to other content types and Web services. Synchronization likely will be an iPhone hallmark, given Apple's record with the iPod and integration with AT&T services like voice mail.

Google has so much to lose but even more to gain if it could extend universal synchronization from the Web to the desktop and to devices. Content synch also could include advertising.

To be clear, Microsoft takes synchronization seriously. The concept is built into products as disparate as Vista, Windows Live and Xbox. But missing is universal synchronization—usable by software and hardware developers—across all platforms. In "Risk," there is one winner. Microsoft, play smart or you could be the game's biggest loser.

Related:


Create, Communicate, Collaborate with IT Professionals at Ziff Davis Enterprise IT Link.

TrackBack

TrackBack

http://www.microsoft-watch.com/cgi-bin/mte/mt-tb.cgi/11108

Comments (15)

Swashbuckler :

MS should be worried about Gears. It's all about moving the platform from the OS to the browser by making the browser having the necessary features to support real applications.

But, I would be surprised if Google does provide the sync capabilities as a part of Gears (or as open source in general). Gears advances the browser platform, which is what Google wants. Google doesn't want to make it too easy of a platform on which other companies can build competing applications.

However, MS will not stop Gears. Gears will continue to be a plugin for IE just like Flash is.

Joe :

Not a bad right-up. There is definitely a lot going on in this area. The question, will Microsoft's solution be cross platform?
There's really no point in baking this functionality into the platform, because Silverlight, Apollo and other RIAs won't be able to use it. This really *has* to be part of the 'reach' platform (e.g. Silverlight).


"It seems that without providing data synchronization out of the box, Google Gears leaves the most difficult and cumbersome aspect of building a disconnected Web app up to application developers. This may be OK for Google developers using Google Gears since the average Google coder is a Ph.D but the platform isn't terribly useful to Web application developers who want to use it for anything besides a super-sized HTTP cookie."

This is hugely misleading; the author implies that somewhere on this planet there exists some magical generalized method for "just synchronizing data" and handling conflicts, deletes, etc. automatically.

This of course isn't the case. Synchronization is highly domain-specific and trying to provide any sort of framework for building your own is probably pointless. Speaking as someone with no PhD, nor any form of higher education, I can say that synchronization is nowhere near as hard to implement as this quote maintains.

If instead the author simply said "synchronization" when he really meant "replication", then again this is such a simple task (implemented by as little as a 4-line for() loop in typical languages) that any "support" for it would be pointless.

Google is doing what it does best: providing extremely general solutions that provide room for building all sorts of things on top of (a giga-cookie is an incredibly useful thing).

David.

Sam :

Synch is the cornerstone, no doubt - but I think it needs to be looked at from a slightly different perspective. Synch from site to client is good, but what about synching between peers (P2P)? Last time I checked, Microsoft had this nailed with a nifty little acquisition called Groove!

Paul :

s/synch/sync/ig

What a load of rubbish.

Having attended the launch at Google Developer Day 2007, I can say that what Gears is accomplishing far outstrips an 'offline cache' system.

With Gears, Google can fix up GMail so that you can write new emails, or delete them without needing to be 'connected'.
When you then connect these 'offline' operations can then be published up to the actual main website.

PS. I have no PhD nor am I a teenager. Gears looks to be very promising.

Dateman :

"To be clear, Microsoft takes synchronization seriously."

Yes though why do they so seriously suck at it???

ActiveStink has been a joke for ages, and that is trying to get Microsoft products working together. Palm synch software was always way more reliable than anything MS could produce in this space.

I expect MS products and efforts on synch will always be behind the curve in this space. Google will eat them alive.

Michael,
Gears is currently an offline cache system. If a developer wants to use it to offline-enable their application (e.g. like RememberTheMilk.com just did), then they have to roll their own synchronization protocol by hand to handle conflicts between offline /online changes to the user's data.

The GMail developers are Ph.D's, I'm sure they can figure it out. My point was that the average Web developer probably can't and would benefit from more support from the platform for synchronization or replication.

john paul :

this is the time that microsoft has to make adcenter free for 2 years ,,, google is trying to make free charges for its web-based softwares ..

so microsoft has to make adcenter free then adsense will die eventually .. microsoft wins ..

microsoft dont need adcenter's money , so let it be free for 2 years or 5 years .. MS must play the google way ..

do this and MS wins ...

IvanLatysh :

Let's have a look at the real world.

Microsoft & synchronization is a sumo fighter dancing ballet, it is painful to watch.


"Apple is a player because the company got synchronization right with iTunes and the iPod. I contend that synch is perhaps the major foundation for the iPod's success."
Here is one problem, there is no synchronization in iTunes. And as everyone knows, iPod isn't a product it is a style or a part of outfit.

So let's compare apples to apples.

Mac :

MS has already released GROOVE for P2P data sharing and synchronization. It is an amazing application that I use with my coworkers almost every day. BTW, it only syncs the changes, so a 16K change to a 35MB file is synced among five users instantly.

=Mac=

Steve Morse :

There is more to synchronization than email and rss feeds. This is already possible. The next step is to synchronize application data. In this respect Google Gears is turning in the right direction. Put it in the developers hands so the developer can deploy applications that can work on-line and off-line for the system users.

Steve Morse, I think you're right. Synchronization of just files is pretty easy. But when applications need custom synchronization of data within files, the topic gets a lot more complex, and having synchronization built right into the OS (as Joe mentions in this blog) really isn't realistic. However, I do agree that Google (and others) can provide a basic starting point for us programmers to build on.

I decided to blog about this on my own blog from a programmer's perspective:

http://blogs.devsource.com/msdev

Jorit Hain :

You are a paranoid nut case.

Post a Comment

 
 


RSS Syndication
Advertisement
Advertisement
Microsoft Watch     Contact Us | Advertise | Site Map
Ziff Davis Enterprise

Ziff Davis Enterprise Home | Contact Us | Advertise | Link to Us | Reprints | Magazine Subscriptions | Newsletters
RSS Feeds | White Papers | ROI Calculators | Tech Podcasts | Tech Video |

Baseline | Careers | Channel Insider | CIO Insight | DesktopLinux | DeviceForge | DevSource | eSeminars |
eWEEK | LinuxDevices | Linux Watch | Microsoft Watch | Mid-market | Networking | PDF Zone |
Publish | eWeek Security | Strategic Partner | Web Buyer's Guide | Windows for Devices

Developer Shed | Dev Shed | ASP Free | Dev Articles | Dev Hardware | SEO Chat | Tutorialized | Scripts |
Code Walkers | Web Hosters | Dev Mechanic | Dev Archives | IT Marketplace | igrep

Use of this site is governed by our Terms of Use and Privacy Policy

Copyright ©1996-2007 Ziff Davis Enterprise Inc. All Rights Reserved. Microsoft Watch is a trademark of Ziff Davis Enterprise, Inc. Reproduction in whole or in part in any form or medium without express written permission of Ziff Davis Enterprise Inc. is prohibited.

Ziff Davis Enterprise