dotMobimobiThinkingmobiForgemobiReadyDeviceAtlasgoMobi

Posted by zoftworx 3 years 39 weeks ago

pic
 zoftworx
mobiForge Newbie
Posts: 8
Joined: 3 years ago
[offline]

Please bear with me, I am still new to developing mobile web sites, and I am still trying to figure out what I should use, and why:

I have created a test page where I use .Net to determine the Mobile Device capabilities, items such as:
- Request.Browser.IsMobileDevice
- Request.Browser.MobileDeviceModel
- Request.Browser.Cookies
- Request.Browser.IsColor
- Request.Browser.ScreenBitDepth
- Request.Browser.SupportsDivAlign
- Request.Browser.ScreenPixelsWidth
- Etc.

Then at the same time, I get as much information on the same Mobile Device from the latest WURFL database.

I have now tested about 20 different phones already, and in all cases the .Net got the same information as the information listed in WURFL for screen width, cookies, and most of the rest.

If .Net is accurate, why is it still recommended to use WURFL or something similar to get the device capabilities? In my case, I want to make sure that the graphics display correctly, and how to align the content.

I'll appreciate all opinions regarding this. What is your experience with detecting the devices capabilities, and why should I for example use a database such as WURFL or DeviceAtlas? What am I missing here?

Posted by atrasatti 3 years ago

pic
 atrasatti
dotMobi logo
Mobile Genius
Posts: 325
Joined: 5 years ago
[offline]

Let me clarify here. I think what you are saying is that the default device detection (Mobile Controls) that are part of .NET are doing a good job detecting a mobile device. Is that correct?

If I understood correctly, I'd be curious to know what devices or browsers you tested. The .NET framework comes with an ini file that includes a limited number of devices and mostly Microsoft devices. If you tested with any of those devices you're probably good enough, but if you start searching for a Nokia or a Motorola device, you will most likely get wrong values.

The advantage of a device database like DeviceAtlas is that it will cover many more devices and offer more properties than the existing Mobile Controls.

Posted by zoftworx 2 years ago

pic
 zoftworx
mobiForge Newbie
Posts: 8
Joined: 3 years ago
[offline]

Hi Andrea,

Apologies, but I have not seen your reply to my original post earlier. But just for completeness sake (should anybody out there have similar questions to what I had at the time).

At that stage, I have mainly tested with SonyEricsson phones (P1i, W880i, S700i), Samsung SP-i600 and a Nokia 5140.

They all were detected without much problems.

Since then I have tried with numerous other phones, and you are correct, they are not always correctly identified.

So to conclude, the databases such as DeviceAtlas and WURFL caters for those cases that are not always correctly identified.

Best Regards
Jan

Posted by jangkrik 1 year ago

pic
 jangkrik
mobiForge Newbie
Posts: 6
Joined: 4 years ago
[offline]

sorry OOT, but anyone still using tera wurfl here?

Posted by jangkrik 1 year ago

pic
 jangkrik
mobiForge Newbie
Posts: 6
Joined: 4 years ago
[offline]

sorry OOT, but anyone still using tera wurfl here?

Posted by jangkrik 1 year ago

pic
 jangkrik
mobiForge Newbie
Posts: 6
Joined: 4 years ago
[offline]

sorry OOT, but anyone still using tera wurfl here?

Posted by xiaopy12 1 week ago

pic
 xiaopy12
Mobile Champion
Posts: 582
Joined: 1 week ago
[offline]

Gucci Outlet Online dfhrtj