Geek Answers Handbook

Discover mobile devices to render rich web content

  • What are the most affordable mobile phones at the moment (models and / or user agents) and

  • What rules should be evaluated when trying to determine whether they will handle a site with an expanded mobile site?

I am developing a mobile website and am currently performing a user discovery to determine if the mobile device should see fully enhanced js, jquery mobile, css view or simple backup.

Here is what I currently have for my two questions, and I would like to receive some suggestions / suggestions on how this can be improved - this filtering is evaluated top-down:

Advanced view if the user agent contains the following: "iPhone", "iPad", "Android 3", "Android 2", "MSIE 9", "MSIE 8", "MSIE 7", "Windows Phone OS 7", " IEMobile / 7 "," BlackBerry99 "," BlackBerry 9800 "," BlackBerry Tablet "

then the Backup view , if the user agent contains the following: "Android 1", "MSIE 6", "MSIE 5", "MSIE 4", "MSIE" 3 ", that is, a whole bunch of old Blackberry UAs, i.e." BlackBerry8 "and older Opera Mini versions ie" Opera Mini / 3 "...

and then Advanced View if it turns out to be a web browser (also useful for testing). This is again determined by the user agent rules.

then the Backup view when the user agent is loaded (and found) in the WURFL API and the release date is considered too old. At the moment, I see this as until 2007.

then Backup view when the WURFL function device_os shows "Windows Mobile OS" with the option device_os_version "5" or "6".

then Advanced view , because it can’t determine what they are using, so give a better experience (this will serve the new graduation phones)

How to configure this, it is better to find reasons to exclude the device than turn it on, since the last condition will return an expanded view.

+2
user-agent mobile-website detection wurfl
source share
2 answers

What are the most mobile phone mobile devices to date (models and / or user agents)

I think you have already identified the most important of them: iOS devices, Android 2.0+ and the latest BlackBerry devices. But really, if you want to know how well your site is supported, you should check out the emulators / simulators available for specific devices.

An excellent list of sample User-Agent strings can be found here .

What rules should be evaluated when trying to determine if they will handle a rich mobile custom site?

BlackBerry devices running OS 6.0 or later will have a WebKit-based browser that supports the latest benefits, so you can improve the filtering of BlackBerry devices to predict new / unreleased devices that will work well. The following User-Agent example shows that the device is running OS 6.0.0.141:

Mozilla/5.0 (BlackBerry; U; BlackBerry 9800; en) AppleWebKit/534.1+ (KHTML, Like Gecko) Version/6.0.0.141 Mobile Safari/534.1+

Prior to OS 6.0, the BlackBerry user agent looked a bit different (and the web browser experience was much worse). The following User-Agent example shows that OS 4.7.1.40 is running on the device:

 BlackBerry9630/4.7.1.40 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/105
+2
source share

If the device supports preferred_markup = html_web_4_0

From WUFL

0
source share

More articles:


All Articles