What to Expect with the API Changes?

FernandoUpLogic · 2012-07-03T06:10:50.000Z

+1

apoll_oh · 2012-07-03T07:15:04.000Z

+1

peteconnolly · 2012-07-03T13:49:28.000Z

+1

ferenc · 2012-07-03T14:22:53.000Z

+1

DJGenerator · 2012-07-03T16:03:41.000Z

+1

rickumali · 2012-07-03T22:12:38.000Z

+1

jerrylthompson · 2012-07-06T12:45:34.000Z

Thanks everyone for the +1s on this post. Obviously the concern for us developers are valid and a courtesy response is being requested here.

rsarver · 2012-07-06T15:34:28.000Z

Jerry, thanks for the balanced and thoughtful post.

I wanted to chime in and let everyone know that we’re tracking all the conversations and listening to as much feedback as we can. While we can’t share any additional information at this point, we will as soon as we can and we will be as clear as possible at that time.

jerrylthompson · 2012-07-06T16:03:43.000Z

Hi Ryan, thanks for chiming in. It is the greatest fear of any developer, especially those who have invested hundreds+ of hours into their product, to have either little information or little time to react – both of which can have disasterous results for them. Thank you for following up and looking forward to learning more.

BradleyMarkham · 2012-07-06T17:49:29.000Z

As the CEO of a funded startup that is using the Twitter API (and consistently adhering to all of their developer rules), I don’t think this kind of veiled ‘something is coming that will affect you’ warning is helpful. I, like many others, make my living off of and feed my family by providing a unique experience for people that ties in with Twitter that people can’t get directly from Twitter itself. I have been proud to be part of the Twitter ecosystem, and we have put thousands of hours over 3 years into building our products. My investors and I agree that services like ours will provide valuable content to the Twitter ecosystem and that there is a great potential for synergistic partnerships among Twitter and its developers in which Twitter can monetize its content (some of which we help to provide) through various distribution endpoints.

For example, if part of the proposed crackdown is related to a monetization issue, my apps, along with many others I’m sure would be happy to include Twitter’s own ads into the tweet streams we display, etc. This would become like Adsense for Twitter and seems like a very potent revenue stream for you.

Regarding consistency, I agree and understand that providing a consistent user experience is important. In cases where creative 3rd party development provides an experience that users can’t find directly on Twitter’s core apps, I hope that Twitter will strive work with 3rd party developers in a way that facilitates open communication, encourages innovation, and seeks synergistic partnership opportunities.

jerrylthompson · 2012-07-06T18:09:45.000Z

+1

AyeYoDv · 2012-07-08T23:25:14.000Z

What ever the situation may be keep your head on and household stable as a man.

jerrylthompson · 2012-07-11T19:11:59.000Z

I’ve been getting a ton of direct responses regarding this thread. There are some really valid concerns from other developers that I’m hearing. While the high level view is that API changes only affect developers and/or their investors, the API relationship extends much further beyond that in my opinion and others I’ve spoken with.

Any major API change will ultimately affect the users of these products in very adverse ways. These users have developed trust and have adopted various applications as they fit their specific needs. Outside of the actual coding and support, developers are ultimately responsible in some ways to the people that use their apps. The same developers who support Twitter, also support their products.

pcorpp · 2012-07-11T19:18:14.000Z

may name is pezhe in usa alabama

AlecMontgomery · 2012-07-12T02:07:02.000Z

+1

140dev · 2012-07-12T14:12:06.000Z

What if we actually could build apps inside of tweets as @sippey believes? The result would be a paradigm shift of epic proportions. Suspend your disbelief long enough to read my take on this possibility: http://140dev.com/twitter-api-programming-blog/the-coming-twitter-land-rush/

orian · 2012-07-13T18:08:51.000Z

I’ve written up my thoughts on this here (yeah, it’s really long): http://bit.ly/NkAmOi

140dev · 2012-07-14T13:27:46.000Z

FUD, Day 15. Still no additional information from Twitter HQ on the FUD bomb. http://140dev.com/twitter-api-programming-blog/fud-day-15/

I’m feeling a little silly having to discuss this on Twitter’s forum. Anyone want to throw up a separate, independent Twitter developers forum? Maybe we can talk there.

deancollins · 2012-07-14T13:51:00.000Z

@Adam lol you expected something different?

Its day 33 since twitter broke ie8 with a scripting error - https://dev.twitter.com/discussions/9151 .Lets face it these guys are worth billions of dollars but still amateurs.

NAElGaza · 2014-01-30T00:33:40.000Z

Can we use Google Adsense for Twitter?
http://www.adsensebus.com/