(this is page 99 of 121)





Latest

Books rock!

I was sad to miss O'Reilly's Tools of Change conference last week if for no other reason than because I really wanted to see Manolis Kelaidis's presentation on connecting the analog to the digital on the future of books.

Ever since I read Neil Stephenson's The Diamond Age, I've been waiting for someone to crack the code on moving books into the digital age. Despite the false starts of local companies like E-Ink, it's clear that paper (or some form of it) is here to stay. The form factor is just perfect for some use cases and, more importantly, the emotional attachment that all of us nerds have to the page-flipping format is way too strong to be broken by even the most over-hyped and anticipated of gadgets.

Moreover, the history of print design is rich with a lot of smart people thinking very hard about the best way to present information to be consumed on the printed page, and it's not likely to be eclipsed by the world of web designers anytime soon. Even the guys at 37 signals are all about how online design may now be making a U-turn and heading back to the realm of print.

For me, the biggest challenge in understanding how the book will transform into a digital object is in creating a proper back channel so that users can continue interacting with content in the way that the web has enabled. Take Digg or Reddit as cannonical examples of how we are used to injecting feedback into the content consumption process: if I read something really awesome, I want people to know about it. I might even want to leave a comment if I think that I can help extend the argument.

Until the book form factor solves the back channel problem, we're stuck with their being static artifacts of the information explosion going on around us. Which is again, why I was sad to miss Manolis's presentation. Of all the work I've seen around e-books, his comes the closest to expressing what could be a very viable product roadmap for the venerable book.

Comments Permalink

Googing offline

A month ago I switched to Google Reader from NetNewsWire because I was tired of the cross computer synchronization problem. Reader is also one of those nice applications that doesn't just ape its desktop predecessors— perhaps because there isn't a real strong legacy of desktop RSS readers— but that instead tries to make the whole experience of consuming feeds more web native by weaving in social features around the sharing of posted items. I'll have a lot more to say about mixing together feed management and social features over the next few days (as I am on vacation and will have finally have a chance to write about friends, feed management, and the secret of Facebook's success) so for now I will just say that Reader is a good application that anyone interested in going beyond very basic feed consumption should definitely check out.

This post is not about Reader though, but about Google Gears, a new browser plug-in that was released recently around Google's first Developer Day to make it possible to take web applications offline. Basically Gears combines 3 things together in a local runtime: an RDBMS (SQLite), a local web server, and a multi-threading primitive in the form of a worker pool. The plug-in (which currently runs on IE and Firefox and sort of supports WebKit/Safari) provides these three services and leaves the rest to you, the developer.

I have to admit that when I first read about Gears, I was a bit disappointed that Google had chosen to bite off so little in order to solve what is probably the Achilles heel of all web applications, offline use. If solving this problem had fallen to me (which it did in a small way 7 years ago when we were building a bandwidth-enhancing service for the Memora Personal Server), I would also have used a local webserver but made it capable of running server code (in the form of Java/PHP/Python/Ruby plug-ins) and capable of transparently rewriting URLs so that the enduser was unaware of which server was actually handling the request while the developer had less work to do in building out hybrid applications. We pulled this trick off at Memora to serve big video files from a local webserver instead of across the network when the assets existed in both places with the best part being that outside of a bit of middleware which the developer had to be conscious of in certain cases, the rest of was completely transparent.

That said yesterday I got my first chance to test Gears via a synced version of Reader that went "offline" with 755 of my most recent posts for a long airplane ride. Holy smokes, that thing is fast! Though it could have quite a bit to do with the way that Reader itself is architected, the best part of using Reader offline is that you don't have to wait for the server loads as a new bunch of posts is loaded in. It just screams. By comparison, I've got a single user instance of the entire Tabblo website running on my machine for development purposes (MySQL, Apache C modules, Python, Django) and it is much much slower despite having no real server load, so much so, that I'm beginning to think that there may be quite a bit of connection setup/teardown overhead between a web browser and even just a local server, and that the Google guys may have been conscious of this in the design of Gears.

Gears is not without some enduser annoyances that are imposed on it by the browser, the biggest one being that you have to remember to leave the browser window open before you go offline or you're stuck despite the plug-in having all of the data anyway. There is also of course the nasty problem of distribution; despite the fact that it's provided as a smallish .xpi or ActiveX control, it would be a whole lot better if it could come pre-bundled with the browser, or at the very least with the Google Toolbar. There is zero doubt in my mind that Gmail is going to get a Gears life any day now, something which will likely remove the last obstacle for my going to it full time for all of my email needs, so perhaps there are plans to address both of these issues.

In the meanwhile, I can't wait to try using Gears for a project as it's clear that the Gears folks have done a very nice job of doing a UNIX (little small tools that can provide big leverage) to a key piece the "webapps all the time and everywhere" challenge we're all dealing with these days.

Comments Permalink

Three time rifters

I remember Seth Godin from the first Internet boom as the guy who wrote the smallish marketing pieces about colored cows that I never really paid attention to. But then I had his good friend, Lisa Gansky, on my board at Tabblo and heard all about how Seth was really one of the few Internet marketing folks who "gets it."

Which was why reading his recent blog post about John Heilemann's piece on Steve Jobs and the iPhone was such a pleasure. Better yet, in the blog post Seth points to this old Fast Company piece of his where he writes about Walt Disney as the ultimate three-time rifter:

What's a rift? It's a big tear in the fabric of the rules that we live by. It's a fundamental change in the game, one that creates a bunch of new losers -- and a handful of new winners.

I love this notion— that some people are just hard-wired to spot the real rifts— because it explains a lot about the best entrepreneurs that I know. Some people call it "pattern recognition," but for me it has always seemed more like good taste around what really constitutes new opportunities and not just hype and line noise.

As Seth tells it, most rifters wander into their first rift almost by accident and then go on to think that they are gifted enough to spot rifts even when they aren't there (I guess this would be the business equivalent of second system syndrome), but it is those rare few that can keep on spotting the rifts again and again despite position, age, or stature.

Comments Permalink

Roger von Oech has a nice short post comparing his behavior when he reads articles online versus in print that makes the basic point that his relationship the content differs depending on whether he is flipping the page or scrolling with the mouse. Expectations, time spent, even conclusions drawn can vary, despite the fact that it's the same exact content.

The post underscores the premise that presentation matters, the fundamental underpinning of the graphics design profession. However, Roger also gets to something more: the commitment that a reader makes to a particular bit of content when he decides to consume it on paper. It is almost as though the act of stepping outside of the natural flow of screen life implies that a different mode of thinking is going to be used a different part of the brain engaged.

When we all became employees of HP, we were given this really sweet All-in-one printer to help us start thinking about how a printer is used in the home. In my case, this was the first time I've had a consistently reliable printer outside of work since I left my college dorm so I've been overconsuming paper and ink quite a bit. In fact, I've got this new pattern of consuming content where I star all of the items in Google Reader that I want to go back and consume on paper at a later point (as a general rule they have to be about 500 words or more and particularly thought-provoking for me though in my "skim to star" mode, I often get the latter wrong). Then, when I'm ready, I'll print off a whole bunch of posts and go through them as I might have a newspaper 10 years ago or the latest issue of the Economist on a Saturday morning. Right now this mode of consumption has two big limitations:

  1. The presentation of your average printed blog post sucks (but we're working on fixing that)
  2. There is no backchannel for communicating feedback on the really good stuff back into my electronic life (I can't add it to del.icio.us for example or email it to a friend)

but outside of these two limitations, I find that I'm doing more careful consideration of the arguments presented in the pieces when I consume them on paper. This whole Facebook/F8 meme for instance, has been something that I've read about mostly on paper where I am more likely to focus on the longer more thoughtful pieces and less likely (frankly because I can't) to jump around from soundbite blog post to soundbite blog post.

Along a somewhat related vein: in anticipation of the most hyped product launch ever, I've been reading "Designing for Small Screens," a book about user interface/interaction design for display-constrained devices. The book is well worth reading if you are interested in this vein of different mediums/different modes of relating to content. It starts from the premise that the visual interface is the most high bandwidth way to consume content and then walks through a number of interface patterns that are useful in maximizing limited real estate. In light of the paper versus screen modalities, you can not help but wonder what mode of relating to content might emerge as these smartphone-like interfaces really do gain mass market traction over the next couple of years.

Comments Permalink

I spent this past week in Europe visiting HP sites, partners, and vendors and was taken aback by how much connectivity we now take for granted in our regular work here in the United States. The last time I was in Europe for work was 9 years ago (when we'd be amazed just to be able to dial up from the hotel room), but I guess with all the talk of broadband being much better overseas and the 3G cellphone networks being ubiquitous, I was sort of expecting at least parity with the setup I've got here. Boy was I surprised. Here are some of the things you can expect to go wrong:

  1. Power (this one was on me for being unprepared). Between Spain and England, I discovered 3 different plug types. What is more, if you travel with a laptop and a phone (more than one device to plug in) and check in late, good luck getting the hotels to have anything to lend you to plug your American appliances in.

  2. Consistent SMS/data on your cellphone. Having just switched to a GSM network, I was really excited by the prospect of 3G networks and zippy-fast mobile data. While voice worked everywhere, SMS and data did not. In fact, SMS was the flakiest of all of the services that I've come to rely on— I could receive messages almost everywhere, but I had at best 50% odds of being able to send them.

  3. EVDO and Wi-fi. I knew my EVDO card wouldn't work at all; I guess I just hadn't realized how much I rely on it to stay in touch with the team back in Boston while waiting at airports, in cabs, or in dead times between meetings. And as far as the wi-fi is concerned, it does seem to be fairly ubiquitous, but in 100% of the cases it was expensive and encumbered by either its billing mechanism or by some lame proxy server setup that blocked most of the useful Internet services you'd want to get access to.

  4. Overall Internet speed. Finally, the speed of "broadband" connections (especially in Spain) is painful. In this new world of rich Internet applications, it's easy to forget that we've only just been able to get to the point where we can use them in the US and that this is far from a given for other parts of the world. For instance, in Spain Tabblo.com was completely unusable, and even Gmail was severely hobbled by the dearth of bandwidth.

I'm not just writing this to gripe about my technical defficulties with the "old world," or even to warn other innocent travelers, but because I realized for the first time this week how much I've gotten used to filling the small cracks of free time when I am traveling with little bits of collaborative work and communication. It made me think that the macro effect productivity boost must finally be something that economists can measure as a positive impact of PCs and mobiles— always-on connections to the data and people that you need to get stuff done.

And yet at the same time, it was sort of nice to have a few cab rides and airport stays to do some disconnected work. Or even better, to just sit and think.

Comments Permalink