View Single Post
Old 08-04-2005, 05:14 PM   #3
rlauzon
Wizard
rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.rlauzon put the bomp in the bomp-a-bomp-a-bomp.
 
rlauzon's Avatar
 
Posts: 1,018
Karma: 67827
Join Date: Jan 2005
Device: PocketBook Era
User Agent Issues

We are tackling the user agent issues at work when dealing with mobile devices.

One big problem is that the user agent doesn't necessairly tell you what you need to know.

Case in point: The 320x240, 320x480 and 800x600 WinCE devices (the first 2 handhelds, the 800x600 a tablet) all report the exact same user agent string.

Obviously, we can treat the 800x600 device like a PC, but have to provide specialized content for the other two.

What we decided to do was create a pre-page that uses java script to get the client screen resolution, and, based on that information, redirect the user to the appropriate version of the web application.
rlauzon is offline   Reply With Quote