Last night, Twitter blogged about upcoming changes to its API in version 1.1. It’s not the most communicative of posts, goes on for quite a bit and has incensed quite a lot of developers.
The fury is all about this diagram and paragraph:
In the upper right-hand quadrant are services that enable users to interact with Tweets, like the Tweet curation service Storify or the Tweet discovery site Favstar.fm.
That upper-right quadrant also includes, of course, “traditional” Twitter clients like Tweetbot andEchofon. Nearly eighteen months ago, we gave developers guidance that they should not build client apps that mimic or reproduce the mainstream Twitter consumer client experience.” And to reiterate what I wrote in my last post, that guidance continues to apply today.
So, apps like Tweetbot, Echofon and Tweetdeck are no longer wanted. But why would they do this, and what are the alternatives?
Because Twitter is changing, and it’s going to change rapidly. Twitter’s 1.0 API has been around for 6 years, which is an eternity in API terms. They need to move on and they want their applications to come with them in the same way that Apple wants to control their app ecosystem and user experience. The problem is that these rules haven’t existed before and the way it’s all been phrased is pretty hideous and very negative.
Well, they could have phrased it better. Anil Dash does a great job of re-writing the post and making the world seem right again.
Joe Stump makes some great suggestions as to how to control third party clients:
Why not run API like the App Store? 1. Require they use Twitter ads 2. Require they follow design rules 3. Require all clients be approved
I really like those ideas, and they seem implementable, but it will require a lot of effort on Twitter’s side to set up this ecosystem and encourage third party apps again.
But, from the blog post, it seems Twitter doesn’t want to encourage third party apps.
There’ll still be 6 months between v1.1 being turned on and 1.0 being turned off, which is plenty of time for developers to bring themselves into line with the new rules. Twitter will be listening to this discussion, and will probably respond in time. Hopefully this will clear up the confusion, and I hope they work directly with the developers that are affected by this, instead of just dictating the rules. We can always hope!
Just remember, it’s still a great service (via Jason Snell)
As the Twitter angst burns bright, let me say this: I think Twitter is the single best thing ever made on the Internet. Seriously.
Just a quick note about a new Twitter client – Destroy Twitter, that has quickly replaced Twhirl as my client of choice. It’s lightweight, very simple and very fast whilst being incredibly slick at the same time. Now, all they have to do is get rid of the rubbish Windows chrome at the top and they’re on to a winner!
iPhone development is the forefront of “cool” programming. Doing something with your latest toy and potentially selling it to millions of people, making a few bucks along the way. The main stumbling block (assuming you have a Mac) is the Objective-C language.
My experience in programming starts out with Java (university) -> PHP -> C# -> ASP .NET. Nowhere along the way have I ever delt with memory management or pointers. However, you can pick these things up quite quickly once you’ve had some things explained to you. So, here’s 10 great sites for starting out in your iPhone development.
Stanford Cocoa Programming Course
A full 20-lecture course with sample code, walkthrough assignments and guest lectures from Apple employees. If you’ve ever been through uni/college you’ll know what to expect, a bit of a challenge to the casual developer but you’ll learn amazingly quickly. Thoroughly recommended.
Apple Developer Documentation
The bible for iPhone developers. The whole SDK can be viewed from here along with some great exercises and videos on how the whole thing works. When you download the SDK you can download this whole library into XCode for viewing offline.
A Digg-esque site for bookmarking iPhone resources. Not a massive community at the moment but it’s getting there.
Jeff LaMarche’s Blog
Jeff has been an Objective-C programmer for the past 10 years and regularly blogs about iPhone development, whether it’s a new component or some funky OpenGL particle system. His posts are full of great code samples so go have a look!
Tim Haines’ Twitter List
If you’re in to Twitter (like I am) Tim Haines maintains a list of iPhone developers on Twitter. If you go and put your name on the spreadsheet there’s a ruby script you can run to follow all the developers on that list. You’ll get access to hundreds of people-worth of knowledge and help. The community is very friendly and always willing to help you out.
So, good luck making your shiny new app! If you have any good sites you want added to the list, leave a comment!
Just a short post to say you can now follow me on twitter. Just go to http://twitter.com/steveworkman and see what I’m doing (and where!)
A twitter widget shall shortly be appearing in my sidebar no doubt