What’s the Browser Matter?

I’ve been pondering a redesign of this website for a while now. As it should be, it’s way down the bottom of my Things To Do, but it’s there.

I’m writing this in MarsEdit, I’ll read it in NetNewsWire. According to my server logs, some of you are reading this within your Google homepage, Newsgator account, email client, or something altogether different.

So, who would I be redesigning the site for?

Robots? They don’t appreciate interesting typography or color choices.

This is why the default WordPress theme is so popular – the value isn’t in the CSS. The value of a website is in it’s reception.

I’ve half-joked about rebuilding Amazon.com to make it friendlier to my Treo. Using their E-Commerce Service – it’d be a decent effort, but not outrageous. Completely do-able.

37Signals recently opened up the Basecamp API to developers.

ProgrammableWeb’s Mashup Matrix says there are 89 other APIs available.

If I can get the data from those services within applications I’m already using and comfortable with – what does it matter what their website looks like? I won’t see it.

Let’s say, you loaded up this page and found just a link to the RSS feed. Let’s say we got really real and just released the API of a web application. Leaving the interface design to the customers.

UPDATE 11 May 2006:

“The browser will explode into a thousand fragments, will spawn a thousand specialized offspring” – Stowe Boyd