My goal with this blog

I write about relevant changes in the way that people use the web and how startups are built to provide services and products for this ever changing wonderful thing we still know as "the web." As a former entrepreneur turned early-stage investor, my greatest hope is for this to be useful to other folks that are like me in the hopes that they can avoid some of the mistakes I've made.

Give us IMAP for the rest of our stuff cloud people!

The article in Monday's WSJ outing that the rumored Google storage service, where all of your files are stored on Google servers, initially rubbed me me the wrong way. The implication that we'd get all of our data stored in exchange for our eyeballs and our privacy (in light of all of the recent Facebook hoopla) must have struck me as a Faustian bargain that seems hard to extend much beyond email (and even that has been bothering me lately as Google seems to be misreading my email in the ads it is choosing to put inline).

But after thinking about it a little more, I realized that the irritation goes deeper than the business model to the dominant underlying assumption these days that all of personal computing is going to move to the server farm and that maybe, just maybe, we're finally getting ready to go back to the thin client model for computing. [If you see the irony in this given that I've just spent 3 years pushing content creation webapps as the end-all be-all, read on]

Let's review for a second why moving all of our personal computing to the cloud sucks:

1. Offline. Since HP bought us, I've upped the amount of time that I spend on planes crossing from east to west and it's beginning to really get to me that I can't use Gmail, Reader, or Tabblo during these six hour stretches. For instance, I have no problem keeping relatively current with my work email (thanks to the flying), but my personal Gmail account is usually 10 days behind. And even though the Reader team did a nice thing in integrating Google Gears for offline use, the offline experience still feels sort of bolted on with key command sequences not available.

2. CPUs are awesome and universally under-utilized these days. I've lost count of how many cores I have in my laptop but outside of spinning up for buggy Javascript goodness, they are only really ever taxed when I'm doing something to multimedia inside the rich client apps. Why does Flickr have to resize photos for me in a queue that takes 4 times the amount of time that iPhoto would? At Tabblo, we're offenders on this score as well; though the team has done a great job of making image transform operations tolerably fast, there are still operations that would benefit from a little CPU help, especially when the site is under load.

3. Uploading stuff over and over sucks. I've been obsessed with this one lately so here I'll only say that it's now not just about photos— on top of (re)uploading rich media, I've now also got profile picture-uploading fatigue and friend-finding ennui, and status-updating exasperation. And unless you're only going to ever use one company's "cloud," this is just a fact of life these days.

motled

These are all good reasons why cloud-based services are probably not the only model for moving personal computing forward, but this morning while reading Tim O'Reilly's update on the definition of software above the level of a single device, I went back to being exasperated by this mottled relationship we have with our devices and data where everything that we care about seems to be spreading across more devices, more websites, and in most cases more PCs.

Tim writes about what a good model the iPhone/iPod+iTunes+iTMS is for this concept of of allowing software spanning multiple devices to play in delivering a solution. To me this seems to be an opportunity for stuff to get lost in more places. In fact, I've found that having the device tethered to the PC for the sake of connecting to data from the cloud a pretty horrendous proposition. RIM's Blackberry showed us the power of over-the-air sync a decade ago, and with WIFI on more and more of these devices, it's time to extend the model across all types of data. It is great to use the PC's richer interface to configure these more interface-constrained devices (a great example of this being the way that I can now program my Tivo from my PC instead of being deafened the bouncy Tivo noise every time I need to schedule a new recording). And frankly I'm not all that good at actually remembering to sync my iPhone thus exposing myself to all sorts of data loss/sync issues.

Which is of course another way of saying that this cloud thing really does have legs if Google and others can see their way to a good implementation for getting around problems 1-4 described above. As I was racking my brain wondering how they might do that, I thought of my earlier example of being able to answer email on the plane, and realized that we've got a pretty good real world example for what needs to happen in IMAP today (which is partly why I was so excited to see Gmail implement it). A good IMAP server lets me work offline, can more-or-less reconcile changes across devices that need access the mesage store, supports the server pushing status changes to the client, enables rich CPU-intensive activities to take place locally (indexing the cache of my account contents), and provides folders for aggregating items as well as a timeline view of when items are stored.

What if we had a cloud-based service that supported an IMAP-like protocol for read/write? Couldn't I then use iPhoto to begin organizing pictures, Flickr for adding some from friends, and Tabblo for creating a different "view" of the collection? What would it take to get a few of the broadly distributed clients to support this via plug-ins, and a few of the services to support it as a backend store API? Ditto for video, or any other type of multimedia.

Of course this model could also be applied to metadata (addressbook, buddy lists, etc.) The key would be that unlike RSS or even the bidrectional APP (Atom Publishing Protocol), an IMAP-like protocol would start from the assumption of many clients of different shapes and sizes needing rich read/write capabilities first and foremost (as I think about it, APP and a proper RESTful API might get you there, but I wonder if you couldn't simply start by actually using IMAP).

So who knows? Maybe the cloud is the right place to manage data and some of our computing tasks, assuming that we managed to get IMAP going for the rest of our electronic lives.