In the last two days, a couple of users noticed a new, Ajax-based interface on their Twitter home pages. Apparently, this new interface will allow users to scroll through their timelines without having to refresh the page. This, by itself, would not be a major new feature, but it hints at a larger refresh of Twitter's user interface.
One of the advantages of using Ajax to display updates on users' profile pages is that this could also allow for pushing real-time updates to your Twitter stream in the near future. Currently, you have to reload the pages manually.
As Kristen Nicole points out on SocialTimes, the increased (or at least perceived) competition from Facebook might be pushing Twitter to release new features on its own, instead of almost solely relying on third-party developers. While there are distinct differences between the cultures on Twitter and Facebook, Facebook's new API could open the way to more competition between the two services.
Also, while Twitter's strategy of opening up its API and encouraging innovation by third-party developers has made the service the success it is today, it has also made monetizing Twitter even harder. The standard Twitter profile home page is very basic, and anybody who wants more features has to use a third-party application. The most active Twitter users hardly ever visit the site, as the interface is too basic. Instead, they rely on tools like Tweetdeck or Twhirl to interact with the Twitter API.
Have you seen Twitter's new Ajax updates in action? If so, let us know in the comments.
Comments
Subscribe to comments for this post OR Subscribe to comments for all ReadWriteWeb posts
The AJAX More button shows up when you click on the same tab twice in the sidebar on the right side.
The free and open source microbloggingservice identi.ca (at http://identi.ca) already posts new updates with Ajax, and it let's third party clients and services use XMPP to make the timeline update in real time.
Twitter originally had AJAX loading for updates but the feature was removed early on as a means to reduce load on the service. It will certainly be a welcome feature to have again, I wonder though if the frequency of call required for AJAX calls will be acceptable for use by apps using the API? It's kind of like the difference between using push email and regular pop email!
At the same time the Twitter API limits make some applications untenable... http://particls.uservoice.com/pages/general/suggestions/120914-twitter-has-a-5000msg-limit-on-dms-from-whitelisted-accounts
Am I the only one wondering who will really benefit from this? 80% of Twitter users go through a third party to tweet, so few people will actually see this tuff -- GUI enhancements on the Twitter site mean nothing if you're already using someone elses GUI (most of which enable this stuff to be done already anyway).
A more useful addition to the Twitter website would be some bringing together of tools and tips to make the thing much easier for new users to start to use effectively.
Ian Hendry
CEO, WeCanDo.BIZ
http://www.wecando.biz
That's right, Twitter has to decide whether it is a platform or a service before start making money.
Its nice, but having a ajax based twitter page will not be so great for SEO will it?
A more useful addition to the Twitter website would be some bringing together of tools and tips to make the thing much easier for new users to start to use effectively. muhabbet , mIRC
At the same time the Twitter API limits make some applications untenable...
thank you soo
I've been using the Autopagerize greasemonkey script for some time and that basically provides same functionality on twitter and most other pages. You might like it too.