Martin Tithonium (tithonium) wrote,
Martin Tithonium
tithonium

If you have a mobile device with web access and wouldn't mind helping me out, go to http://martian.at/mobile and fill out the little form?

(I've rewritten how it saves the data, and put in some javascript to determine if a) javascript is on and b) if javascript can figure out your screen size. generally the answer is no.)

edit: to be clear: the page is just a simple form, plus some javascript that will add a few hidden form fields if it can. On the back end, I'm recording the user agent and any environment variables the CGI gets that it doesn't get from normal browsers (frex, some browsers send the screen rez as a header, and I get that as an environment variable). If you submit the form, it records that too, so I can then identify the device, if it isn't clear from the user agent (it frequently isn't). So I get stuff like this:

UA: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; PalmSource/Palm-D052; Blazer/4.5) 16;320x320 QS: platform=treo+700P&window_innerWidth=320&window_innerHeight=258&document_body_parentNode_clientWidth=undefined&document_body_parentNode_clientHeight=undefined ENV: HTTP_X_WAP_PROFILE="http://downloads.palm.com/profiles/Blazer450.rdf"
UA: Mozilla/4.0 (compatible; MSIE 6.0; Windows CE; PPC; 240x320) Opera 8.65 [en] QS: platform=opera+mobile+%28fit+to+screen%29%2C+wm6%2C+htc+8925&window_innerWidth=320&window_innerHeight=162&document_body_parentNode_clientWidth=600&document_body_parentNode_clientHeight=102 ENV: HTTP_IF_MODIFIED_SINCE=Tue, 29 Apr 2008 17:41:50 GMT, HTTP_TE=deflate, gzip, chunked, identity, trailers, HTTP_X_EBO_UA=BID=1.3.0, BCReq=5253CF3E44DDAF65967EAB847567941F


which I can then take and start figuring out a) how to identify something as a mobile browser vs a regular one, without having to make a big list of every UA known to be mobile, and b) how, if possible, to determine how big your screen is, so that pages can be adapted to fit.

One annoying thing I've learned is that most mobile browsers I've tried don't /actually/ support the 'handheld' css media type, so you can't just write stylesheets to fit your content to mobile devices. And worse, even if you could, they're all different shapes and sizes, so it's nearly impossible to determine how much space you have to work with and thus how much to display or how big. I'm planning to add a mobile mode to Sightseer, and LunchOClock will /REALLY/ need to work mobile, so these are important issues for me.
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 6 comments