Comments on: Top 10 Twitter Feature Requests http://developingux.com/2008/06/24/top-10-twitter-feature-requests/ .NET | Design | Architecture | Community Sat, 22 Nov 2008 02:52:52 +0000 http://wordpress.org/?v=2.6.3 By: Caleb Jenkins http://developingux.com/2008/06/24/top-10-twitter-feature-requests/#comment-352 Caleb Jenkins Wed, 25 Jun 2008 04:07:59 +0000 http://developingux.com/2008/06/24/top-10-twitter-feature-requests/#comment-352 @Alan - That's true, but some things (like Jabber support, multi-feeds) would help relieve the stress on the system while other features (tracking specifically) will add to it... most of these, I think, would be pretty neutral or at least minimal to the system. Either way, I think that twitter (more than anything else) has proven the point that the whole application is the user experience (not just the UI). The "ilities" count in UX (Scalability, Reliability, Flexibility, Maintainability) @Alan - That’s true, but some things (like Jabber support, multi-feeds) would help relieve the stress on the system while other features (tracking specifically) will add to it… most of these, I think, would be pretty neutral or at least minimal to the system.

Either way, I think that twitter (more than anything else) has proven the point that the whole application is the user experience (not just the UI). The “ilities” count in UX (Scalability, Reliability, Flexibility, Maintainability)

]]> By: Alan Stevens http://developingux.com/2008/06/24/top-10-twitter-feature-requests/#comment-349 Alan Stevens Tue, 24 Jun 2008 11:34:21 +0000 http://developingux.com/2008/06/24/top-10-twitter-feature-requests/#comment-349 I suspect some of these convenience features will come once the uptime is fixed. We could write our own convenience features using the api if they'd stop limiting requests. ++Alan I suspect some of these convenience features will come once the uptime is fixed. We could write our own convenience features using the api if they’d stop limiting requests.

++Alan

]]>