[Note - this is (re)posted on behalf of Juergen (js@nooper.com), whose
mailer is insisting of responding to this thread in BASE64. Nick]
On Sunday, September 14, 2003, at 01:43 PM, keitai-l@appelsiini.net
wrote:
> Now I can write my system to automatically split large pages over
> multiple pages depending on phone type.
I don't want to discourage you to write your application like you
describe above, but please note that just because a phone can show
bigger pages, it doesn't mean that the user want long pages.
From a usability point of view, shorter pages are better, because
they load faster and they get read (mobile users have such a short
attention span).
Also if you always fill the cache until the limit, you get rid
of the advantage of having a "back" button...if the cached page
is already overwritten by the new page, the 'old' page has to be
requested again and this costs money and worse: time. It will
make your site feel like a tarpit.
The 505 also introduced a totally new problem...the logos from
mobile sites look now tiny on the QVGA screens, but to make them
bigger makes it even more expensive for the user (packet fees)
and also slower to load.
So many decisions to make in the design process...to really
find out if people like/accept it or not, you should test with
real users.
Just my .2 yen,
Juergen
Received on Sun Sep 14 14:13:44 2003