Splitting Android devices

[Guypo]

Hi,

I was wondering if anyone considered splitting up the Android record
into separate devices.
Android devices vary in many ways, including max number of connections
(in general and per host), use of HTTP pipelining, CPU power and many
more.
Keeping the metrics about Android as a whole is a bit pointless, since
the results will vary and will not represent most Android phones. It
also misses out on a great opportunity to try and capture info per-
device.

Was that option contemplated? Is it in the works?

Cheers,
Guypo

[elsigh]

Hey Guypo,
We have definitely thought of this - it can be hard getting the device
entries, and so right now we're on hold until ua-parser is updated to
support this level of product detection from the UA string. I totally
agree, and if you look in the issue tracker you'll see notes to this
effect.
Wanna help with this work on http://code.google.com/p/ua-parser by
chance? ;)

[Guypo]

Good to know that it's in the queue. I'd love to help on the coding
front, but I'm afraid I don't have the cycles right now - probably the
most common answer, but true nevertheless... That said, I think that
given the public-service nature of Browserscope, it's possible that
Sencha (recently acquired tinySrc) or DeviceAtlas will donate that
piece of functionality to Browserscope. Since they'll be maintaining
it too, that might be a good move, maybe giving them some credit in
the site.

Until that point, I think it'll be worth adding a little footnote to
Android results indicating these tests will vary by device.
I know it's not as good as having the actual support, but at least it
makes people aware that they can't just take those numbers as a sure
thing.

Cheers,
Guypo