The changes you have read about affect us just a bit. It is important to recognize that we are “Social CRM,” and as such, an industry participant that Twitter wants and needs to support – especially since we are a potential source of significant advertising revenue. And, applications like Engage121 are really not part of the problem(s) that Twitter is trying to solve.
To be more specific:
• There will be no impact on our source(s) of Twitter data; and the content available to you will remain unchanged. We access (now and in the future) the Twitter API to support our ad hoc searches, and we connect to Twitter firehose re-seller(s) for background tasks such as measurement and analysis. That will not change.
• However, as a participant in the Twitter ecosystem we are obligated to slightly change the presentation of Tweets in our application to more closely comport with Twitter’s new standard. These changes are already in our development pipeline and you should notice changes over the coming month or so.
It seems to me that Twitter’s primary intent is:
(i) to control the user experience (look and feel) of its product – Tweets;
(ii) guide consumers who do want a platform to the Twitter-owned Tweetdeck, which, again, provides Twitter more direct control over the user experience, and
(iii) eliminate superfluous middleware that stand between native Twitter and its users.
If there is one thing we have learned about social media, it is to expect change. Today, Twitter is trying to gain more control over the product it delivers to users, but without adversely the ecosystem that is vital to its developing revenue model. Tomorrow, expect radical changes from Facebook as its users increasingly access the platform through mobile devices that are far less able to carry advertising. And the day after, who knows. We will do our best to stay on top of the changes – that’s a promise.