A new value to identify tablet devices.

[GaretJax]

I think it might be a good idea to all an identification of tablet like devices (if this kind of info can be taken from UAs at all).

There are mobile devices with relatively small screens and usually slow Internet. For this segment you want to create mobile, light websites.

There are laptops / personal computers that have huge screens and fast Internet. For this segment you want your full website to be displayed.

However if you deal with 'tablets' and devices alike it's not obvious what you want to do. It's neither a 'mobile device' in the sense explained above, nor a full sized computer. That means that some browscap users may decide to display mobile website for those devices, some may decide to display a full website, and perhaps some will have a 'full but light' version specifically for such devices.

I think it stands to reason to give people a mean to separate such devices using browscap.

[Joshua Estes]

I'm with you on this one. I want to have an is_tablet property added. There's a lot that can be done with this and adding new properties.

- Joshua Estes

@JoshuaEstes

"If you live periods of your life in misery, when you remember back to those times, all you'll remember is the misery. The misery robs you of great memories you could otherwise be making."

--
You received this message because you are subscribed to the Google Groups "browscap-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to browscap-dev...@googlegroups.com.
To post to this group, send email to browsc...@googlegroups.com.
Visit this group at http://groups.google.com/group/browscap-dev?hl=en.
 
 

[RAD Moose]

First, let me preface this with I would like more device oriented info into the "database" however, I do have some questions that I will raise not to block the adoption but to think through how do we resolve potential issues and future expand ability. The goal is to get even more useful data into the this project, while still maintaining the legacy requirements.

What do you do with devices that have similar user agents that might not allow you to determine if it is a tablet versus a smartphone?

Is a tablet a mobile device without cellular call capabilities?  (Assuming that an iPAD 3G doesn't have call capabilities for example)

Is tablet based upon screen size? (for example iPad Mini versus iPod Touch)

What is a Microsoft Surface RT? a Surface PRO? Lenovo Yoga?   Are these notebooks or tablets?

Do we just want a "is_tablet" properly over a "device_type" property to handle new devices such as consoles (xbox,) entertainment devices (Google Q,) alternate mobile devices (Google Glasses) etc?

[di...@duechiacchiere.it]

Hi all, I agree with Moose, here. Something more generic would definitely be more "future-proof" and flexible enough to cover the new device types as they are released. We all know that the next few years will see more blurred boundaries between device types ;)

A few words about me: I'm the developer of WP SlimStat, a popular analytics plugin for WordPress which includes browscap.ini to detect user agents. Users are contacting me about the inaccuracies, so I'm really hoping to see this project thrive, and I'm offering to lend a hand if needed.

Dino 

[Gary K]

>> Something more generic would definitely be more "future-proof" and flexible enough to cover the new device types as they are released. We all know that the next few years will see more blurred boundaries between device types ;)

That was why I added DeviceName and DeviceMaker to the files. :)

[di...@duechiacchiere.it]

On Wednesday, February 20, 2013 12:27:55 PM UTC-5, Gary K wrote:

That was why I added DeviceName and DeviceMaker to the files. :)

Yes, and I am actually thinking about using it in my software ;)