My goal with this blog

I write about relevant changes in the way that people use the web and how startups are built to provide services and products for this ever changing wonderful thing we still know as "the web." As a former entrepreneur turned early-stage investor, my greatest hope is for this to be useful to other folks that are like me in the hopes that they can avoid some of the mistakes I've made.

Why custom browsers suck

Chris Mesinna (who I don't know but who I gather spent some time at social browser company Flock) had a thought-provoking piece on content-creation tools for the web and the future of rich browsers. I suspect Flock folks are none too pleased that he disses their efforts but I was much more interested in his conclusion that there might really be a future in innovative rich Internet applications built with Webkit which is Apple's equivalent of Microsoft's 8 year-old embedable IE browser control. Using it, a developer can write a rich client application that functions largely like a web-browser but with hooks into the OS for key actions that browsers have traditionally sucked at.

I am all for making better tools for content creators, but this seems like a risky approach to take mostly because of the fact that I don't think it's a tenable strategy to expect a regular user to take an 18.2MB download of a custom web-browser in this day and age (I am in fact trying to write this blog post on the OSX machine in the time that it takes me to download Flock and might just make it). Plus even if the Flocks of the world were to get past the download hurdle, people just don't want more clients– if RSS readers couldn't make it as standalone applications in large numbers given how much value they add over all of the web-based experiences I have seen for consuming RSS, I seriously doubt that custom browsers will.

However 10 years into this web thing, it's not too much to ask that the existing browser vendors address a couple of critical things, namely better upload, rich text editing, and some sort of canvas for drawing (that actually works). That would be a great start, and notice that it doesn't include fancy things like offline use or drag-and-drop across applications. Given their client-side thick-headedness I very much doubt that Microsoft will address this, but I have great hopes that at least some of these issues will be tackled by the forthcoming Firefox 2.0 release.

And when that happens, if Apple has any sense whatsoever, they'll get WebKit in shape to support these things as well. In a future post I am going to write about all of the "dirty little Safari secrets" that we've learned about while developing Tabblo (there really are a couple of gems especially around performance that no one seems either aware of or willing to blog about). And if they Apple doesn't get its act together, well then we'll just continue to be glad to see all of those Mac users at conferences running the Fox on OSX despite its heinous widgets and it's fat footprint.

In the meanwhile, I'm not ready to give up on how far we've come in just about a year's time with interactivity in the browser and the kludge of technologies now known as AJAX. The Javascript libraries are getting quite good (you might even call them platformy) and there are a whole bunch of people coming at the problem from interactive design, engineering, QA, and a whole host of other perspectives which really do help to make a platform.

[As an aside, custom browsers as development tools are a great thing. I've used this trick in the past, and from Greasemonkey fittingly enough, the new Webkit Javascript debugger, there is a whole ton of sense in being able to instrument the browser when you're trying to make it to fancy tricks for users.]