(this is page 80 of 121)





Latest

So we've got Adobe Air that just went 1.0 this week. Microsoft is coming on from a copy-come-from-behind strategy with Silverlight. Mozilla has got something going on, and Apple has got Webkit at the center of their whole device strategy.

So who wins in the web development platform war for the next decade? Which of these rich runtimes suck the oxygen out of the rich client world and give a nice evolutionary twist to what's been going on with the AJAX spruced applications? Or are Win32 and Cocoa here to stay?

I'm not a betting man, but if I were, it'd be DHTML all the way.

Why? Because at the end of the day we've got to think in terms of access devices. At HP we're living as primary beneficiaries of the move to laptops these days, but just as we've moved there from the desktops, I'm sure we're going to move to the portable devices (iPhones and others) from laptops. And in the case of these portable devices, why would you care about a really rich runtime? What matters is the data and how quickly you can get to it. Sure Air and Silverlight can run in these mobile devices, but the real question is: at what battery cost? And to what benefit?

I'm guessing that the DHTML model has got long legs to it— especially as the world comes to standardize on Webkit and all of the good stuff that comes with it. At Tabblo we've been totally biased towards it; at first because it was the only way to remain truly "platform neutral," and later because of the advantages it has given us in terms of embed-ability within other websites, other online experiences.

If I had to guess I'd say we've got a lot to squeeze from the web browser especially now that we've got a great canvas like Webkit. Even Firefox 3 with its much improved performance gives most of us room for pause as we think about the browser of the future and the world of mobile platforms.

Comments Permalink

ReadWriteWeb has an astonishing roundup of the multitude of sites playing in the "stream your life" space— a category which essentially amounts to rolling the feeds from the various different sites you participate into one activity stream that your friends can then use to keep tabs on you. Since this is a specialized feed reader application, and since I've had feed readers on the brain lately, I spent some time checking a few of the services.

My conclusion: I remain unconvinced that these services can exist as standalone destinations, though I now see an important task they fulfill that a more general purpose feed reader (a la Google Reader) does not. The best of them provide a nice feature in managing distributed identity across a whole variety of sites. FriendFeed does this the best; you subscribe to individual people and then get all of their various different activities in one stream. Where this comes in most helpful is with people who have blogs but who also do a lot of twittering, flickering, and deliciousing (though it bears mention that in some cases those other activities are of a completely different modality). I realize that this seems like a sort of trivial feature that could easily be added on to a mainstream blogging engine (and probably should), but it is worth pointing out nonetheless.

Where I'm fairly sure these sites are not going to win is in providing yet another way to author a similar but distinct type of micro content. Back to FriendFeed for a moment: outside of aggregating my own content, I can also write quick posts (a la Tumblr) that live only inside of my FriendFeed feed for my FriendFeed friends to look at. Do we really need this in the age of blogger and Wordpress and Twitter and a whole bunch of other very similar content creation engines?

What I'd prefer to see is the folks from the 35 different startups profiled here picking up a copy of "Programming Collective Intelligence" by Toby Segaran— O'Reilly's wonderful new book on the data processing algorithms that will power the next wave of social computing. It's taken me more than 10 years to get a much more superficial understanding of some of the core filtering, grouping, indexing, and ranking algorithms that Segaran covers with an extremely lucid style and concrete code samples in this book. More importantly however, this is the kind of experimentation we should be doing, instead of having people just jamming Wordpress and Twitter or Jaiku and Flickr in the transporter and hoping that what comes out the other end doesn't have a fly's head.

Comments Permalink

Continuing along the theme of custom readers for RSS streams, I can't help but notice that there has been a recent explosion in sites that do nothing other than aggregate the feeds of content that you (and others) create across various activities. It was a neat idea back when Jaiku implemented "add RSS feed" to their version of the Twitter timeline, but since then we've gotten Spokeo, FriendFeed, and now Second Brain to name but a few of the new entrants into this most meta of categories.

Given the ease and cost of starting an Internet property these days, all good ideas on the Internet automatically get a half dozen good implementations right away. In this case, everyone is trying to generalize the Facebook Activity Stream to work across all of the Internet (with "all of the Internet" being the top 10 user generated content sites of the Web 2.0 world). Having tried a couple of these, I'm not sure that they're going to work for two important reasons:

1. They feel too spare to work as places that people will actually log into. I can maybe see bunching up a load of feeds into one of these services for the sake of de-duplication and then putting the RSS feed directly into a regular reader, but I have a hard time imagining that I'd go to any of these aggregation sites as destinations in and of themselves.

2. It's not clear to me that even at scale, these utility sites will find business models that work for them. If Facebook can't monetize well with all of its supporting structure, why would a site that trades in just one element (albeit an addictive one) do any better?

If I owned one of these sites, I'd be thinking about repackaging these aggregate feed streams in formats that are not for consumption via a web browser, or even a standard feed reader. And the more heavy lifting required to shoehorn this content into some other format, the better. Where are the custom printed newspapers of feed aggregates? The photo frame slideshows that are actually compelling and not just teeny type doing the rumba on a screen that is 6 feet away? The spoken versions (read by the computer equivalent of Jeremy Irons) for consumption as podcasts? I have no idea how many different formats might actually work, but it's worth thinking about if entrepreneurs really aim to make stand-alone businesses here.

Comments Permalink

Why RSS readers don't work

Why don't people like RSS readers? I can't imagine how anyone could stay on top of the blogosphere without the use of one; yet even Big Kahuna Bloggers like Doc don't use them, preferring instead to troll through their bookmarks and rely on pointers sent by email or Twitter.

Perhaps it is all about the fact that most RSS reader developers chose to ape the 3-pane interface of the traditional email client (in the hopes of conceptual synergy) and most people just don't want another inbox. That said, this would not explain why even the mail program plug-in readers that put the feeds right into your regular inbox (FeedDemon and Thunderbird) have failed to catch on. Hell even when Microsoft baked RSS reading into Outlook, people barely took notice.

On the other hand, the famous Facebook "Activity Stream" is nothing more than an internal news reader (and as of yesterday, it would seem that it is also an external one). And sites like Techmeme and Tailrank are aggregated newsreaders with a slightly more complex sorting algorithm.

When I think of what works about both of these alternative newsreaders, the conclusion that I come to is that the "add to reader" step (actively subscribing to a feed of content) must deter most folks. If this is indeed the case, then crowdsourcing this step in the process seems like an interesting possibility. Or at the very least, baking the reader into the web browser (which all of the browser vendors have done, albeit in a "one feed, one website" model that seems borked from the start) and then relying on browsing patterns to subscribe and unsubscribe folks from particular feeds.

As I continue to think through "web as movement," I can't help but feel that we've got tons more innovation to do on the reader front, and that we're only now just getting started.

Comments Permalink

The web as movement

Driving up to New Hampshire in the midst of a blizzard tonight, I was captivated by the swirling snow and thoughts of how the web is quietly turning into a series of flows (blog posts, Flickr streams, Twitters, etc.). It has take many more years than I would have thought: after all, RSS first entered my life back in 2002 on a hot summer day when I made a stupid bet that everyone would be consuming their content via readers inside of 5 years. The two trends driving this evolution of the web: 1. the web as a communications/publishing platform and 2. the atomization of web content such that we care less about "page loads" of information and more about individual atoms (for instance, did you know that every tweet has its own permalink?)

Perhaps the most thought-provoking piece of work on this whole transformation as of late has been Matt Webb's presentation "Movement" where he makes this point and more in describing a new interaction pattern for information (think interactive RSS feeds). His argument stimulates the grey matter because of the way that it makes you think about how the metaphor of the "web as movement" versus the "web as place" changes your expectations for the medium.

There are loads of other folks sniffing around this notion from different starting points. Some see web services as programmable data sources that the elusive mashup serves to recombine in new and interesting ways (Tom Coates did this one best in his presentation "A Web of Data.") Others see the new web being born out of the micropublishing boom (Twitter, Jaiku, Tumblr) where the constant update combined with the lightweight social network drives the main pattern of interaction. In both of these cases though, we are leaving behind the Geocities/Homestead/etc. view of webpages as static (or even semi-static blogs) and jumping on to the moving web, be whatever may.

It's a big shift— about as big as the one to cloud computing— so I'm not really sure of where it will take us. One thing I do hope however is that it lays to rest the notion of the "destination site" with its registration-based walled garden and constrained experience designed to chases money in the form of shifting ad dollars. Maybe Techcrunch's report of the stagnating Facebook traffic is a harbinger of things to come (though seen from the best possible light all Facebook is is one giant web-as-movement-reader).

I'm just kicking off the thinking about this, which is to say there is tons more thinking to do. At the end of the day this is likely to touch everything we do online: from how we communicate to how search engines index the web, from how we buy and sell to how we look for recommendations. All coming from billions of loosely joined little pieces moving...

Comments Permalink