(this is page 89 of 121)





Latest

Last year, a couple of us at Tabblo got a chance to get on the beta program of this really neat wireless camera card called Eye-Fi that automatically uploaded your pictures from your camera to your favorite photo site. The idea was very cute, and even as a beta, the implementation was very nice, so it was a fun surprise last week to receive the 1.0 version of the card in the mail. In the intervening year, the Eye-Fi guys seem to have polished their packaging and found great distribution for their product (Amazon, Walmart), while settling on a very sensible business model (sell the card at a slight premium to regular memory cards).

I like the Eye-Fi concept a lot and intend to give a couple of the cards out as Christmas presents this year. But after a week of constant use, I've been forced to rethink some of my assumptions about getting all of your content up into the cloud as quickly as possible, bypassing the PC at all costs.

While it is fun and sort of magical to see pictures just appear on your favorite Internet photo site (though arguably less now now that camera phones are so prevalent, especially those armed with awesome applications like Shozu), but the problem with getting your regular camera pictures sent automatically is that the mode of use for a typical digital camera these days is very much "ready, fire, aim" with most casual photographers using brute force as a substitute for innate skill, knowing that there is a nice editing step waiting inside of Picasa or iPhoto. When photos go straight to the cloud and into a service like Flickr (which is what I've been using with the Eye-Fi), that editing step disappears, which means one of two things happen:

1. you really frustrate people who might be following your picture stream on Flickr with twelve slightly different shots of the same subject in the same composition

2. you frustrate the hell out of yourself using a web interface to take on that first editing pass

Of course, #2 could all be fixed if Flickr were to support an IMAP-like protocol that iPhoto and Picasa could implement as rich clients to help you manipulate the photos and do the editing later (I have to admit that Flickr almost does this with their API today, but no mainstream clients have taken advantage of it). And in that case, having the data resident in the cloud where other applications could use it might justify someone using some basic algorithms around finding good unique pictures to solve #1 (I've seen a bunch of algorithms that do this very well with date-clustering and object detection inside of HP Labs, so this part is not science fiction).

In the meanwhile, it is worthwhile pausing for a moment as we all race to cut the venerable PC out of the content-device-Internet loop, and thinking about what we might be giving up.

Comments Permalink

Get nimble quick

Fred Wilson (VC/blogger extraordinaire) wrote up an interesting analysis of his own investment career viewed from the perspective of startup nimbleness. His main conclusion is that the majority of startups that succeed in achieving superb returns at some point in their history "transform" by being flexible enough to experiment. I love pieces like this because they help to pop the myth of entrepreneur-as-visionary who just seems to know at every decision what needs to be done.

To Fred's point, all of the best entrepreneurs I've seen combine two key abilities: a set of lightweight planning capabilities (to set up measures for success and gates that determine failure), and an unrelenting ability to execute quickly over repeated iterations without the rest of the company getting completely demoralized. In the software space in particular, another key skill is being able to build enough platform assets that can be re-used across experiments. Even in the fast and cheap world of web development, this is a key part of being able to iterate quickly and with as little technical debt as possible, which is why getting some hackers with experience on board can mean the difference between Facebook (iterated well) and Friendster (crapped out).

Finally, the article is also interesting because it applies well outside the context of the traditional startup. I'd say that about 50% of what I've been focused on since the HP acquisition has been on setting up the right execution context for maintaining this nimble experimental capability. Some of that involves figuring out how to work around big corporate process that exist for very good reasons in other contexts, and some of it involves cultural changes that reset the definition of success on the part of key contributors. But most of it— the really challenging bit— involves managing the impedance mismatch between what a big company needs to be successful (predictable success), and what a little startup relies on to make a dent in the world (huge risk-taking and nimble execution that may or may not work).

Comments Permalink

It must be a slow end-of-the-month press cycle because the press seems intent on proving to the world that Apple's OS X 10.5 (Leopard) was just too buggy to put out there, joining its Redmond cousin in the land of crappy desktop OS releases.

Personally, I've only been dealing with small annoyances (keyboard locking up, Desktop files flickering incessantly, Spaces not working, the Finder losing its handle to certain running apps) and not the really big stuff (network not working, data loss), but I am somewhat underwhelmed by what Apple delivered with this release both from a polish perspective and in terms of new capabilities.

Maybe what is happening now with OSX is that it has reached that level of maturity that most big software projects get to where it is very hard to make forward progress without noticeable regressions. This would be ok though because I'm fairly certain that better processes (Apple bring back the public beta please?) would take care of this.

sunset from delta shuttle

But maybe, this is about the fact that all of the big brains in Cupertino are now enamored with Apple's next platform, the iPhone.

Listening to the newly (re)launched Gillmor Group on the airplane a couple of days ago (this show is definitely an acquired taste, but one which I would recommend for nuggets such as this one), I heard Steve Gillmor defend Apple by saying that the iPhone was "the center of Apple's universe now" and that everything else including the computers and Leopard were just "peripherals." Sad as this may be to admit, it sounded somewhat right to me in that there seems to be a lot more "denting the world" potential in putting very capable portable multimedia computers in the hands of tens of millions of folks than in continuing to polish the desktop platform of yesteryear.

I'll be sad though; as the sun sets of the PC platform as the most innovative place to be developing, all of us who were introduced to computers through it will go through our own little pangs of nostalgia.

[Postnote: After writing/before posting, it occurred to me that projects like OLPC may have quite a bit of innovative growth in them... we will have to see]

Comments Permalink

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.

Comments Permalink

I've had occasion over the last week to use both Evite and eBay and I've got to say that no matter what all of the Internet pundits claim about how much fluff instead of stuff Web 2.0 is about, one thing we've learned is the last 10 years is how to make websites more usable. My god are these two sites horrendous to use! It is a true credit to Amazon and Yahoo that they managed to avoid the absolute stagnation that the eBays of the world seemed to have suffered from.

Ebay is a particular peeve of mine, both because it pioneered the world's best business model (as a market-maker for otherwise illiquid goods), and because it is still the greatest mainstream stealth success out there. When I ask people who I trust to be smart members of the mainstream what they love about their net-connected lives that they didn't have last decade, eBay is what most often comes up as the example of why the Internet is great. That the company has managed to remain in control of the auction market despite a truly horrendous user-experience speaks volumes to the power of positive feedback loops and network effects.

If I were in charge of one of these big winner-take-all Web 1.0 companies that hasn't yet understood that the web application space is going to be won and lost on usability over the next 5 years (and mobile platform support, though that is for a different post), I'd set up a Yahoo Brickhouse style R&D lab for innovating on user experience alone. Combined with proper A-B testing infrastructure (which I happen to know both of the companies mentioned here invested in heavily during the last decade), you'd have a real opportunity to bring user experiences forward to where they ought to be in this day and age.

Comments Permalink