Twaddle

It’s funny, you test an application for several weeks and determine there’s no major bugs and go ahead and release it. Then on the day of release you experience a crashing bug didn’t occur previously resulting in egg on your face. Basically, when Twaddle gets updates from Twitter it looks at the list of tweets for any @replies. If it finds an @reply it checks who the target is and proceeds to download their information (if Twaddle does not already have it). Once this is done it can proceed to download that user’s avatar and create the schmick little overlays that you see in the various Twaddle views. Unfortunately there’s a slight problem… if an @reply is directed at a user who protects their updates, and you do not have access to those updates, Twaddle flails it’s arms in the air and crashes. Not cool, not cool all. Now that I’ve experienced the problem and know what it is I can fix it.

I also noticed that obtaining your friends list took way longer than it should. This will also be rectified in the next point release (0.1.2). As a result of this fix the first time you use 0.1.2 – or newer – you may notice that Twaddle takes a bit longer than usual to start up due to an update to the database used to store information. The upside of this is that Twaddle should update a lot quicker, resulting in better battery life, and generally a better user experience.

Expect the new version today or tomorrow.