(this is page 47 of 121)





Latest

Last month I decided to find out what this netbook craze was all about and purchased an HP Mini 1000 running the HP/Canonical developed MIE (a stripped down Ubuntu 8.04 with an attractive coat of gloss on the surface). I gave it a fair shake, trying to use it at home, at work, and even on the road while on a trip to California last week.

And while I have to say that it is impressive that HP has managed to pack this much into a device which costs $400, the end result of my experiment was to conclude that netbooks are just cheap laptops and that all of the analyst/press/reviewer hoopla (Forrester recently called the Netbook the "third PC formfactor) is just marketing hype. What is more, unless your primary laptop is some huge boat which can't be moved around, or unless you've never been able to have a laptop— I can almost guarantee that the netbook performance will disappoint you to say nothing of the obvious screen/keyboard issues.

Prior to the popularization of smartphones, there might have been a role for these small machines as a new class of Internet access device. Unfortunately the space between the top of the smartphone range (or at least any smartphone that can run Webkit-derived browsers well) and a 12+ inch laptop that is portable is too small to squeeze a new product category into— especially one that doesn't deliver any new interface paradigms or real software innovation.

And on the subject of software (it always comes back to that), I am amazed that despite the apparent polish that HP and Canonical put into the MIE environment, they left such ridiculously obvious issues with the mobile experience unaddressed. The suspend/resume is still too slow and flakey (though this might be a Linux thing, I would imagine a customized kernel could have done a better job given that the hardware was known), and it still takes far too long for the machine to find and associate itself with a WIFI access point, even when it has been previously configured. In the world of 15-60 second "Internet snacking" these two bugs are deal killers.

[Come on guys, if you don't want to look as far as how quickly OSX latpops come out of sleep and on to the network, look no further than today's crop of smartphones and make that the target.]

gizmos from the sideFinally, back to the form factor issue for a second: though it is amazingly obvious in hindsight, unless you can put the device in a pocket (jacket or otherwise), its diminutive formfactor over other laptops just doesn't buy you anything other than a weaker battery that limits its use to about 2.5 hours (I got about a day of sporadic use assuming that the suspend cycle was working) and a screen which is bound to drive you to Advil after extended use.

[In this picture the devices top to bottom are: iPhone 3G, Nokia N800, HP 1000 Mini MIE, Macbook 13 inch]Macbook, HP Mini MIE, Nokia 800 & iPhone 3g

It's too bad— I was really looking forward to using this machine all the time. But until suspend/resume and time-to-network are resolved (along with a number of other interface annoyances that have more to do with MIE's Linux legacy than anything else), it is destined for my graveyard of cool but useless devices.

Comments Permalink

Why does sync still suck?

I remember the first time I synced a PalmPilot to a computer 12 years ago being amazed at the way in which all of my contacts and calendar entries seemed to stay in tune with each other across both devices. Like many others I spent the obligatory 5 minutes trying to trick the sync process and then an hour or so wondering what this brave new world of possibilities this new capability would offer us. True device independence as our metadata (contacts, calendars, bookmarks) and data (all sorts of files) would get intelligently squirted between devices and kept up to date no matter what we did on each of our devices.

Boy how wrong we all turned out to be. Even after a dozen years, sync still sucks. Yesterday Google announced iPhone-Google Contacts-Google Calendar sync which I was excited to try because of how bad Apple's for pay Mobile Me service has turned out to be for keeping 3 computers and an iPhone up to date with each other. And after a few hours of screwing with it, I'm ready to conclude that Google's sync doesn't seem all that much better.

It may have seemed like magic a dozen years ago, but it's just not that hard of a problem to solve. What confuses me most is why the OS vendors haven't solved this problem all the way from metadata to data and offered it as a part of the OS. It's clear that Apple sort of tried (they still don't have a good story for keeping files current across computers— and using a WebDAV server is not adequate), but initial scaling issues and and to much of a focus on the Jobsian "one man, one shiny box" dictum seems to have kept them from truly embracing the cloud as a viable canonical store for the original copy of everything. And while I hear Microsoft has a nifty utility with Folder Share, true sync has only ever worked well in Outlook/Exchange environments (it's no surprise that Google emulates the Exchange protocol for its iPhone calendar/contact sync). Perhaps Mr Notes Ozzie can change this, but the evidence is not there today.

And so we're all left patching our own solutions out of offerings from vendors big and small: Dropbox for files, Foxmarks for bookmarks, and then some hodge-podge of MobileMe and Google for the rest. Until someone steps up and acquires a bunch of these point solutions (which should be cheap these days) and integrates the whole thing into a cohesive whole (maybe this is the GDrive promise), we'll continue the bad habit of confusing a long view for a short distance in the world of sync.

Comments Permalink

One take Frank

An artist friend once told me that in painting class you learn to trust yourself with the mantra: "first stroke, best stroke" which is a paraphrase of something that Picasso apparently used to say. This blog post reminded me of that today— after a long week of reviewing "vintage charts" at work (multi-year masturbatory exercises in predicting the future)— and made me reconsider something I've learned about building products on the web.

At one end of the product development spectrum you've got what I'd call the "Apple myth:" a long slow slog to get every pixel perfect, every swipe just so, every transition amusing. At the other you've got the "build it quick, iterate like a madman and hope that they never catch you" attitude that has dominated Web 2.0 world since the launch of Flickr. This failed many a me-too startup, but the approach had its merits. The piece above reminds you that after enough experience, you too can become like "one take Frank," belting it out just so on the first try, especially in mediums that allow for that kind of pliability (like the web as opposed to say hardware).

Making stuff is hard, and no matter how much we may try to disguise the in-predictability of getting it right behind things like "ethnographic studies," or even— dare I say it— "usability tests," it's good to be reminded that sometimes it just pays to go with your gut. Oh yeah, and build up a lot of experience along the way.

Comments Permalink

Henry Ford once famously said that his customers could have any color car they liked as long as it was black. When playing with the various emerging "mass customized" versions of already popular products, I am often reminded of his statement. Thus far I've tried custom Nike running shoes, a custom bag from Timbuk2, and jusCustom lego boxt this weekend, Lego's "Factory" product. In all three cases, I've been disappointed.

The reason is simple: for a mass customized/personalized product (by which I mean on that can be manufactured according to the enduser's design specifications) to justify its premium, it has to be measurably better than its off-the-shelf cousin. And note that when I say premium I don't just mean price (in fact one of the mistakes I think companies experimenting in this space are making is not charging a price premium), but also the cost in time as anything made-to-order is bound to take longer.

The case of Lego Factory is a good example of how a company can almost get it right. The idea is simple: after downloading a Legoized CAD program, users can design their own Lego set by picking from a catalog of bricks. After this design step Lego will custom build your un-assembled set and ship it directly to you from overseas in about 2 weeks. You can even customize the cover of the box with an image of your model set against a number of canned backgrounds. Overall the price is fairly decent (I paid $25 shipped for a set with 110 pieces) and the basic experience delivers on the promise of "making your own Lego set." However far too many edges are too rough for this to ever become a mass market experience.

The configurator: In the photo creative world this is what we call the online service/software that lets you assemble the photo book/card/product. In Lego's case, the downloadable CAD Lego Factory program is B-grade software at best, and that is for a truly committed user. There are plenty of bugs that riddle the experience, the catalog is tough to navigate, and the physics of snapping the virtual pieces together doesn't work consistently. But most importantly, the company forgets to provide enough partial starting points towards building a compelling model and offers little in the way of guided help to get people to feel creative. True you can start from a car or a plane, but these are finished products at different scales that don't even manage to combine well with each other. Partially finished consistently scaled models or better yet, the ability to "draw" out shapes and have the tool fill in with bricks would go a long way toward fixing most of the heinous issues.

The out-of-the-box experience: It turns out that after messaging that you could "customize the box" what actually comes with the set is a cheap generic box with an inkjet printed version of your model stuck behind a cellophane cover. I doubt that Lego would actually ship a product to a store with such a poor box. Similarly instead of the choke-proof sealed plastic bags, the bricks come jumbled together in what looks like the ziploc bag grandma used to give you cookies to take home with.

And worst of all, there is no manual! Instead there is a lame letter stating that the Factory kits don't come with manuals suggesting instead that you use the software to step through an arbitrary assembly process while the CAD program reverse-explodes the model you've built one step at a time in what seems like a truly random process.

Until my experience with Factory, I had no idea how much human editing went into making Lego build instructions (I had naively thought that most of it was automated by computer). And as it turns out, these highly edited guides are an integral part of the experience, especially if you are a kid who has been trained in the 3 rules of Lego (1. Never lose pieces, 2. The manual is always right, 3. Don't ever force it).

As with Nike and Timbuk2, I think Lego deserves praise for the Factory experiment. But unless they remember that mass customized goods need to be that much better and not actually worse than their factory-churned relatives, it's going to remain an interesting side project.

If I were in charge of that team, I'd work hard on the software— both during the design phase, and in the creation of a compelling and usable guide (two software problems which appear to me immanently more solvable than some of the others the team has already solved in the end-to-end experience)— in order to move this experience into the mainstream.

Comments Permalink

Towards real value

Engineers, scientists, and artists create value. Everyone else just moves it around.
—Robert Noyce, co-founder Intel

Thus begins Steve Hamm's light and fun read, "The Race for perfect: Inside the quest to design the ultimate portable computer." The story starts with Alan Kay's vision of the Dynabook (incidentally inspired by a visit to our very own Seymour Papert here in Lexington) and traces first the development of the clamshell laptop and then the pda-turned-smartphone. Throughout it all we get to know a bunch of cowboy-entrepreneur engineers that spend many cycles cramming ever more powerful components into ever shrinking cases trying desperately the whole time to catch up with the hype that the vision of truly mobile computing had unleashed.

I loved this story. And to boot, I can't think of a better time to have read it.

It's been over a week, so I figure the presidential inauguration hype has died down enough for me to quote my absolute favorite part of the speech:

Rather, it has been the risk-takers, the doers, the makers of things - some celebrated but more often men and women obscure in their labour, who have carried us up the long, rugged path towards prosperity and freedom.

I was surprised that this one line was not picked up by more of the media, especially because $850 billion stimulus package or not, it is these kinds of folks that we are in desperate need of to pull us out of this financial bubble hangover we're suffering from.

We need more of those crazy entrepreneur-engineers that Hamm chronicles in The Race for Perfect. Folks like Edwin Land who invented instant photography by rolling up his shirtsleeves and getting to work. Or more importantly, as the man in the big white house says, all of those folks "obscure in their labour" but chronicled by Hamm in his book that spend countless years building real value.

Comments Permalink