Is Twitter going to pull a bait-and-switch on developers?
econsultancy.com
econsultancy.com
If you develop for a platform, like Apple or Facebook or Twitter, you are basing your business on the whim of the platform owner.
Every change in development license for Facebook/Apple has killed off some company who got in their way.
Zynga is estimated to be worth $5 billion, but it is running on Facebook. At anytime, Facebook can kill Zynga or force it to pay a large tax to be on their platform. Otherwise, Zynga might have enough money to buy Facebook outright.
So the trick is to be a platform owner, instead of making one off applications.
> Twitter really should have had all of that when it launched or it should have built those services right into the Twitter experience.
Part of why the Twitter platform is so rich with services is that the company didn't insist on filling in all the holes itself. The more open model they followed is precisely what allowed such creativity in the services that run on top of the platform.
A glaring example of how little Twitter has done to support developers since their original API is this support ticket that has been open for about 15 months: http://code.google.com/p/twitter-api/issues/detail?id=214
Obviously, those 150 people have been working hard on something for the last year, and providing the best tools for developers (let alone filling huge holes in their API) doesn't seem to be the top priority.
I could be totally wrong on this and API V2 will be out in a few weeks and blow all of our socks off.
So Twitter is always in the need of new users. Let's say they do an Apple and kick out all of the various different add-ons that they make (while allowing ones that they don't make until they make one themselves).
Eventually Twitter will just be another memory because the critical mass, people advertising twitter, will fall away.