I agree, for the most part. More and more webapps are providing APIs for 3rd party developer. And why not, right? It benefits everyone. But I think Twitter und

I agree, for the most part. More and more webapps are providing APIs for 3rd party developer. And why not, right? It benefits everyone. But I think Twitter understood from the beginning that they didn't need a super awesome native client. Why would they? We were blasting 140 character messages around, mimicking the way we text from our phones. Their core client device was, and still is, the mobile phone. But consider Facebook, which is generally more complicated than Twitter. If we had to deal with competing, unpolished 3rd party clients from the beginning of Facebook, I don't think Facebook would have taken off. In this case, it's good that Facebook controls the experience; it's a complicated one.