(this is page 90 of 121)





Latest

Doc has a characteristically thoughtful piece over at Linux Journal on the need for web service creators to be good members of the ecosystem and support APIs that allow data to be federated across services. He uses the example of his Flickr stream being usable at Tabblo (which is a testament to how good and ground-breaking Flickr has been in this regard), making the point that it benefits him as a user when all of us "vendors" play nice and respect both his data— and more importantly, his time. It is just plain silly to make him waste time with the asymmetry in broadband today, having to upload all of his stuff again.

I've written before on how business models that are at odds with this fundamental respect for the user are likely to be doomed (see all of the stuff on the roach motel), so here I'm going to take another angle. Data acquisition, whether it is importing contacts in a social network or uploading assets in a photo site, is just not something that we need to keep on re-inventing over and over again. Let me stick with the latter example for a moment: outside of the Flickr API, at Tabblo we have 7 other methods for ingesting digital photos. Each of these requires constant maintenance as its client environment/runtime changes, something that I think is just too much of a support problem for any small team to take on. And in fact, these days each of our rich uploaders is in some less-than-optimal state: from "outright busted" to "works most of the time."

Contrast this to Flickr which managed to solve the uploader maintenance problem by crowdsourcing it and letting passionate community members maintain all sorts of different clients with varying degrees of success. Not everyone can be a Flickr, but we should all be able to leverage their success, and instead spend out own cycles thinking about how to build the next layer of value.

That said, what I'm having trouble reconciling is how to build simple user experiences in this new layered and federated world. Imagine if we asked the average mainstream user who comes to Tabblo to go and register at Flickr, upload their photos there, authenticate Tabblo as a trusted service, only to then be able to get into their story-telling process. Nightmare, plain and simple.

One potential solution: I'd like to see a white-label services that could be wrapped by webapp builders for core pieces of functionality. To continue the upload example: why doesn't Amazon, or some enterprising entrepreneur looking to build on the cloud computing infrastructure at Amazon, build out a full suite of well-supported file uploaders, along with an associated S3-backed storage infrastructure for everything from photos to videos. By focusing on just the upload experience, this effort could just nail it for all the rest of us— building plug-ins for our favorite apps, clients for our favorite platforms, and even specialized hardware for events and community activities. In Doc's VRM world, such a company might even be able to charge the enduser a nominal fee for pipe and storage, so long as its service integrated easily with enough of the interesting webapps.

You listening lazy web?

Comments Permalink

Thanksgiving

marlboro skySo today is the day that we are supposed to give thanks in a general way for all of the things we appreciate about life. In my view as an immigrant this is a uniquely American type of holiday— so far as I know in fact, no other country has a holiday specifically dedicated to giving thanks to something that is not a person or an event. And in my own particular case (Venezuela), most of our holiday reasons come with epaulets and egos.

Given the crazy year that it's been, here are my thanks:

Thanks America for not being cynical

No matter what you think of politics or society today, the US is a pretty unique place in the way that it generally tends to eschew cynicism, preferring instead a sort of bounded optimism. I swear that when we look back on the "American Century" decades from now, it is this quality that folks will most associate with what made the US a great place for building Big Things out of nothing.

So thanks to all of the non-cynical investors who are always willing to write checks on the promise of building something out of nothing. Thanks to all of the non-cynical employees who are willing to get on the startup rollercoaster again even after they've been flipped out of it a few times before. Thanks to the big companies who keep buying innovation despite having been burned by it in the past. And most of all, thanks to all of the people out there from Boston to San Francisco who keep buying into the notion that the future is bright, and that we've got more opportunities ahead of us than have already passed.

Comments Permalink

Web apps that you can live in

Jeffrey Zeldman has the essay to ponder during the after-meal coma this year, "Understanding Web Design," on how web design is not about fancy bevels and cinematic effects but instead about creating extensible structures that others can inhabit. More like architecture and typography and less like traditional graphic design. Here is his definition:

Web design is the creation of digital environments that facilitate and encourage human activity; reflect or adapt to individual voices and content; and change gracefully over time while always retaining their identity.

His definition finally made me get to closure on the ambivalence that I've been feeling around Flash-based web applications. They sure are snazzy, but Flash webapps have this feel to them that has always felt "non-native" when it comes to how we relate to the web which goes beyond their relative heavyness.

With most Flash-based websites these days, you get exactly what the developers and designers wanted to give you and get to take it or leave it wholesale. This can be ok for applications that you use infrequently such as shoe configurators or stationery makers, but often gets overly cumbersome as soon as you start to layer in community or workflows that rely on collaboration of any sort, or more significantly when the users are supposed to help extend the environment. In those cases, thinking through building web applications that ring true to the definition above seems like a better bet to me.

The piece reminded me of Christopher Alexander's definition of "living structures" in architecture— places that are designed from the very beginning to be extended as their occupants learn how the want to relate to the space. As with the best architects in Alexander's world, the most interesting challenge for web designers these days is to figure out how to design for this kind of habitability.

Comments Permalink

On negative capability

Jeremy Liew points to a piece in Tech Review on Twitter and Ev Williams that covers the birth of the service in a well thought-out feel-good kind of way.

I think I am developing a man-crush for Ev as a product guy.

Though I suspect the ambling style portrayed in the piece may drive me nuts, I can't help but respect the way in which he seems to have pulled two infectious content/communication projects out of the ashes of mediocre ideas. This guy would be worth his weight in gold to any VC-backed company looking to restart its failed me-too consumer website.

My favorite quote in the piece:

Just like Blogger, Twitter was a simple communications product salvaged from the impending implosion of a more complex project. In both cases, Williams didn't really know what he was doing. With both ventures, his genius--if that is the word--derived from what the English poet John Keats, in a letter to his brothers, called "negative capability": "that is when man is capable of being in uncertainties, Mysteries, doubts without any irritable reaching after fact & reason."

Rings so true to being an entrepreneur and making things out of nothing that it almost makes me want to start reading poetry.

On another note, part of my fascination with Twitter (and all of the clones that it has inspired) is how it seems to have— in sitting at the intersection of communication and publishing— nailed what Jeremy refers to as "lightweight self expression for the general public." At Tabblo, I tried very hard to instill this discipline into our content creation experience, and failed repeatedly in the process. On good days I tell myself that this had to do with the fact that we were after a much more complex authoring experience (we wanted to make your stories to look like magazine layouts so you'd buy them as physical products), but I think deep down I've often wondered about my own acumen when it comes to "negative capability" and making key product decisions.

Comments Permalink

RIP Paper newspaper

Bye bye newspaper

At the local coffee shop this morning, I found myself in line reading a review of "Love in the Times of Cholera" from the SF Chronicle on my iPhone when I failed to notice that the line had inched forward ahead of me. As the old lady behind me made some "I'm annoyed" grunt noise, I apologized and explained that I had been reading a review in the newspaper. Which of course prompted her to point to the stack of Sunday newspapers behind us and inform me that I might prefer reading "the real thing."

I don't know if it's the recent prodding that I've been taking from friends to be more green or the fact that I'm less and less interested in other people picking my entire reading list, but these days I look at a stack of newspapers like this one and feel a mix of disinterest and revulsion. I love tire fires in the backyard as much as the next under-developed South American, but I'm still bothered by all of those trees getting chopped down for such a disposable form of content consumption.

Nothing super insightful here. I just wanted to mark the day on which the paper newspaper officially died for me. I still love reading parts of the NYTimes on Sunday, but from today on, I'm done buying the newspaper. Sort of reminds me of the day which I bought my last audio tape (a "metal TDK-90") back in 1998. The content lives on but the means of distribution dies.

[Interestingly, I most definitely do not feel that way about magazines, but that is for a different post]

Comments Permalink