![]() We agreed with our friends at Tapbots, there is no reason to panic. It's good to know that management's decision to control the core Twitter experience hasn't affected their great API engineering.Īt this point in time, we also learned that we had plenty of user tokens for the upcoming version. ![]() Adapting our existing code to the new API took very little time and allowed us to simplify a lot of our internal code. There were a lot of improvements in the API and the new infrastructure was extremely robust. Since the early days of the project, we had been worried that third-party development might be eliminated completely.Īs more details about API 1.1 became available in September, we became even more upbeat about the changes. In spite of the new requirements and limitations, we were happy to know that our API access wasn't going to be revoked. In August, a posting on Twitter's developer blog announced that changes were coming. If you're at all interested in Twitter's development ecosystem, you know that approximately six months into our product development there were some major changes announced. You'll be able to enjoy this piece even if you don't know what an Xcode is. Since a lot of the people reading this aren't developers, I'm going to keep the jargon to a minimum. Here's one about the development of Twitterrific 5. I've always loved shows that take you behind the scenes of creative efforts: Project Runway and Classic Albums being two of my favorites.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |