Impressed with the availability of free 3G wireless on Kindle, I decided to buy one. And within the first few minutes of playing with it, I found myself on the Twitter web site, cringing while I loaded their heavy UI from this device.

So I did the only logical thing I could think of. I created a Kindle-friendly client for Twitter. KindleTwit.

I wrote the whole thing in the last few hours, so I’m sure there are some designn details I should work out. And in time, I will. But the important thing is that it works.

Go try it out!

An interesting thought just occurred to me… It seems quite reasonable to implement the Twitter API as a bug-tracking tool.

A software team could implement a Twitter account for bug tracking, and include the API into their projects within various try-catch blocks around potential points of failure. Then, all the members of that team would just follow that twitter account. For more critical applications, they could turn on device updates. It seems like a more available version of the old developer’s standby of programmatically emailing bug reports.

For sensitive applications, the tweets could be “protected”… but for less critical uses, the visibility of the public timeline would seem to be an added incentive for developers to fix bugs quickly.

It’s an interesting thought.