W3C home > Mailing lists > Public > public-bpwg@w3.org > November 2005

why auto-refresh makes sense in the mobile context

From: Barbara Ballard <barbara@littlespringsdesign.com>
Date: Wed, 23 Nov 2005 17:27:43 -0600
Message-Id: <A64D5E0B-2051-4D21-9702-6112B5CD93CD@littlespringsdesign.com>
To: public-bpwg@w3.org

Many have argued that auto-refresh is especially bad for mobile  
devices due to the cost of network connectivity, as well as due to  
some accessibility issues.

While I tend to agree with this argument for news applications, I  
disagree for certain other applications.  For example, if I am  
looking at a stock quote, I would prefer to trust that the data is as  
recent as possible - I may be making financial decisions as a result.

Similarly, if I am looking at an email inbox, I would like to have  
the message list be up-to-date.  In particular, on a mobile device,  
if I've bothered to leave the browser running (highly unlikely on a  
phone) and pointed to an inbox page, I would like my email list to be  
up to date - perhaps with a default of 5 minutes like most email  
applications on computers.  This, of course, would be user-settable.


Further, while I've never encountered a browser without a Back button  
(or at least a Clear button which performs the Back function), I have  
encountered several browsers which do not respect content expiration  
times.  This experience spans 6 years of working with a wide variety  
(perhaps 60 devices?) of mobile browsers in the US.


---
Barbara Ballard       1-785-838-3003
barbara@littlespringsdesign.com
Received on Wednesday, 23 November 2005 23:27:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:50 UTC