- Twitter has introduced an API that gives third-party apps considerably more power.
- Conversation threads, poll results, spam filtering and other features are finally available elsewhere.
- These apps still wonâ€™t be as powerful as the official clients.
Third-party Twitter apps have usually missed on out key features of the official software, but that gap is about to close.
After a delay due to high-profile account hacks, Twitter has released a new v2 developer API that lets third-party apps on Android, iOS, and elsewhere use many of the features you might take for granted from the social network, including conversation threading, pinned tweets on profiles, poll results, stream filtering, and spam filtering.Â Unofficial apps and websites should behave more like you expect.
Twitter is also changing how it offers access to the toolkit. Instead of having three separate platforms, thereâ€™s one common framework â€” creators just choose the amount of access they need. A Standard track is meant for â€œgetting started,â€� teaching, or just for fun. The upcoming Academic Research path will provide advanced or even custom access to help study the â€œpublic conversation.â€� Companies, meanwhile, can use a Business track to develop full-featured apps or gather enterprise data.
Read more: The best Twitter apps for Android
This still doesnâ€™t put your favorite third-party app on par with the official Twitter client, though. Twitterificâ€™s Sean Heber noted that many of the new features donâ€™t involve posting tweets, and the stream features arenâ€™t true replacements for a streaming timeline. You might not see a preferred app deliver a live feed or push notifications like youâ€™d hope for.
Usage caps could also restrict many apps.
This is an initial release as part of an Early Access program, though, and the existing API isnâ€™t going away very soon. This hints at a future where you can have the advantages of a third-party app without making as many sacrifices. If nothing else, itâ€™s an acknowledgment that Twitterâ€™s war against developers may have hurt more than it helped.