I guess that's true. Maybe I would argue more strongly for it if I
knew what the app was doing but I don't...I do know that when I was
doing both j2me / mobile content about 6 years ago the virtual device
programs you could use to develop your app against were always pretty
damn close to being the
Hi Jesse --
Oh we probably will create a different set of web pages for the phone
experience for all the reasons you mentioned, and also because the flow
through the app should probably be very different so as to reduce the
scrolling on the phone. But a simple proof of concept is what we are gunn
I've never had good luck trying to make the same html of a web app
work on a mobile phone or normal browser.
Everything is so constrained / different that I've always ended up
creating a separate set of templates that are specifically targeted
for mobile devices. You could probably detect the us
Thanks ... I will try that out .. unfortunately even if it works for me I
cannot compell my customers to download and us it. I don't want to try and
tell the customers how to do so either, as I am trying to sell my prodct not
opera's.
-Pat
On 2/10/07, Thiago H de Paula Figueiredo <[EMAIL PROTECT
Patrick Moore wrote:
Hi there --
I am trying to access my tapestry 4.1.2 application via a fairly high-end
phone browser. (Samsung a900m). I have some preliminary results and a few
gotcha's posted on my blog at :
http://www.sworddance.com/blog/2007/02/09/phone-usability-design-notes-part-1/
On Sat, 10 Feb 2007 04:10:35 -0200, Patrick Moore <[EMAIL PROTECTED]>
wrote:
Hi there --
I am trying to access my tapestry 4.1.2 application via a fairly high-end
phone browser. (Samsung a900m).
As far as I know, the best browser for cell phones is Opera Mini
(http://www.operamini.com/).
