And we have another third party developer to add to our Twitter API Death Watch – Birdsong. Yes, Birdsong just sang its swan song.
But are Twitter’s new API restrictions to blame?
In its description, the Birdsong app offered a “quick, integrated and powerful” experience with:
- Live tile and push notifications
- Live in-app updates for direct messages and mentions
- Configurable timelines
- Multiple accounts
- Threaded conversations
- Geo-tag tweets
But reviews of the app are mixed on the its Windows Phone page. There are 293 reviews and they’re all over the map, with some calling it horrible and some saying it’s the best thing since sliced bread.
So retiring the app may not be entirely on account of Twitter’s API changes, as the developer, Red Badger, concedes (in a way) in its retirement announcement:
Windows Phone Marketplace has not proven itself, for us at least, to be a financially viable proposition at this moment in time. The revenue generated from Birdsong sales vs. the internal cost of development and push service hosting simply doesn’t add up.
But that reason was listed as the SECOND reason why they’re shutting down the app. The first reason? The next change in Twitter’s API would make Birdsong unusable.
Our decision is fuelled by two primary factors. Firstly Twitter has made it abundantly clear that they no longer wish to encourage the development of clients that emulate the core Twitter experience. Any developer who has built a client around the Twitter API will have always been aware that they were ultimately at the mercy of Twitter, but in recent months Twitter have had a distinct change of heart in regards to 3rd party developers that has been well documented and dissected elsewhere to the point there is no need to cover it further here.
They direct users to another Twitter app, Rowi - but as this appears to recreate “the core Twitter experience” as well – and that’s a big no-no according to Twitter’s new rules (as referenced above), so we wonder if users should bother following that advice?
What do you think? Is Twitter at fault here or is it the scapegoat?
(Goat image from Shutterstock)
- Two More Twitter API Casualties: TweetChat and TweetGrid
- Twitter Settles Suit With TweetAdder, Allowing Tool Once Labeled As Spam Continued Access
- Twitter Ads App Throws Its Neck On Chopping Block
- Breaking! PeopleBrowsr Reaches Firehose Settlement With Twitter