Twitter's disdain for third-party clients gets real

There are a huge range of Twitter clients out there offering alternative ways to access Twitter. For many users, these provide a better experience. They provide a level of functionality that Twitter's own suite of applications don't. However, Twitter has revealed that this August it will be bringing in new restrictions and limitations on how these applications are built. Of course, for Twitter these restrictions aren't restrictions as such; it's actually a new developer API called 'Account Activity API'. The reason for the change is that it will give Twitter more power and control over what developers build - it also allows them to monetize the developer API in a different way too.

[caption id="attachment_19298" align="aligncenter" width="300"] twitter-disdain-for-third-party-clients-gets-real-img-0 From blog.twitter.com[/caption]

This is undoubtedly going to make applications like Twitterific significantly worse. For Twitter, that might make some sense. It goes without saying that the platform would prefer users to use its own applications to access the service. But for developers and users of these applications, it might make life a little more difficult.

What restrictions will third party Twitter clients face?

Twitter will be changing the way developers of third party Twitter clients access Twitter. Back in April, Twitter explained the changes it planned to make to it's developer API in a Twitter thread:

https://twitter.com/TwitterDev/status/982346370882461696

Because of the delay, the date that this change will come into effect is now August 16 2018. Essentially, on that date Twitter will turn off a number of legacy services including Site Streams and User Streams. Developers will then have to migrate to the new Account Activity API.

Learn more about migrating to Account Activity API here.

What impact will Twitter's change have?

As already mentioned, this is going to have a big impact on the way developers build third party Twitter clients. The knock-on effect on users will be substantial. Essentially the 'real-time' experience of Twitter that you get in Twitter's own applications will be missing. Users will have to refresh their Twitter feed; push notifications are unlikely to work, and Direct Messages may be hampered too, especially on mobile.

A lot of people are very unhappy about the changes Twitter is making. On Twitter the response was incredibly negative:

https://twitter.com/objectivechad/status/982353715708362752

https://twitter.com/merrickluo/status/983001459078742021

https://twitter.com/DanDuivel/status/982806945772912641

However, there was some support, or awareness for the change when it was announced...

https://twitter.com/trisweb/status/984005164372779010

Of course, this is one step in Twitter trying to give itself a boost - the company has been struggling for some time.

However, you do wonder how successful this change will be for Twitter. Although the premium Account Activity API costs around $11.60 a month, this is only open to applications with less than 250 users. Clearly, this isn't going to be feasible for many of the leading Twitter clients with thousands of users.

Read next: