Friday, September 22nd, 2006

UI Cleanup: Telegraph Ryder Cup Scores

Category: Editorial

I am watching the Ryder Cup Live Scores over at the Telegraph (don’t know why there…. but that is another story).

Now we are used to nice Ajax, and even Comet interactions, it over seems really painful to see a “live” scorecard like this that is only live due too:

  1. <meta http-equiv="refresh" content="120" />

Wouldn’t it be nice if they added a splash of Ajax in here and:

  • Have the current score change in real-time (ish)
  • Update the cells as they happen (each hole is finished)
  • Have a highlighted bar at the top showing you the latest news “Europe went 1/UP in the X game with an eagle to the US’s par”

But then again, is it worth it for them to spend the time on this? The current solution works across more browsers.

I would like to think that it is worth spending this time (minimal), and in fact, now I will head over to another site that is more interactive (show me the puts as they happen, etc).

Ryder Cup Telegraph Interface

Posted by Dion Almaer at 11:08 am
3 Comments

++---
2.4 rating from 15 votes

3 Comments »

Comments feed TrackBack URI

Would it really add to your experience to see this in Ajax? Doing it because it’s cool to do doesn’t mean you should do it.

Comment by MojoMark — September 22, 2006

this is news???

Comment by ajaxianfading — September 22, 2006

First I will like to says this post was useless to the creative process you guy’s are trying to pass to us reader.
If you really want to make a point give us an example of the site where I quote “I will head over to another site that is more interactive” like that you can make a constructive study.
Question 1) Do you have any idea the amount of traffic a page like this get while the ryder cup is on.
Question 2) You says “worth spending this time (minimal)”. Do you have any idea the amount of time it it take to implement rich user interface on this kind of high traffic website?

Just re-think for a second the load on 1. the production server 2. the database request 3. the caching framework.

Please don’t take this the wrong way but there is a difference between developing a prototype or funky website that will get 1000 request when people discover it and a high traffic website that will 100 thousand of request per minutes over a reather long period.

Regards

Comment by Laurent — September 23, 2006

Leave a comment

You must be logged in to post a comment.