Birdfeed 1.1 Change Log
As I indicated on Twitter, Birdfeed 1.1 was primarily intended as a bug fix release. In time honored Apple fashion, I worked very hard in the month after Birdfeed’s release to smooth out the rough edges every software developer has to accept to ship a 1.0. Consequently, 1.1 is heavy on Snow Leopard-style “refinements” and light on out-and-out marquee features. Still, I think it sports some very nice improvements, and, more importantly, it lays a strong foundation for some more ambitious plans I’ve already been working on for 1.2.
Here’s what’s new:
Improvements
- Added support for the iPhone OS 3.0 in-app Mail sheet when forwarding a tweet or a link (the Mail app will still open if you are still using 2.2).
- Implemented a URL scheme and posting bookmarklet.
- Added support for nearby searches with no search term.
- Added a refresh button in the search view, and implemented “scroll to first new tweet” behavior for search refreshes.
- Added support for the Bit.ly URL shortening service.
- Added Posterous as a photo upload service.
- Addressed compatibility issues with the upcoming iPhone 3.1 OS.
- Slightly increased tweet font size.
Bug Fixes
- Overhauled the multiple account system to completely address the Account Amnesia problem.
- Overhauled the posting interface code to address a number of problems related to low memory conditions (existing post text being overwritten after returning from the camera interface, for example).
- Fixed bug that caused a zero follower count to be displayed for users with large followings.
- Made sure mentions count doesn’t update if you’re in the Mentions view.
- Compensated for a Twitter API bug that caused fewer than the requested number of tweets to be downloaded, resulting in a gap between the new tweets and the older, cached tweets.
- Addressed problems with using browser URLs for Instapaper or URL shortening before the page finishes loading.
- Worked on memory efficiency and performance throughout the app.
- Fixed a number of crashes that could happen as a result of invalid search queries.
Posted by buzzandersen on August 28, 2009


