821114 - Please create a client-side script that can detect device features and capabilities

Status: RESOLVED FIXED

(Marketplace Graveyard :: Developer Pages, defect)

Description

[Daniel Buchner [:dbuc]]

We need a client-side script that can detect the following data points:

- General device/platform info
  > device model
  > WebRT version
  > OS version

- WebRT API availability

- Screen capabilities
  > resolution
  > physical size

Comment 1

[Christopher Van Wiemeersch [:cvan]]

Who would run this script against the device? And when?

Comment 2

[Wil Clouser [:clouserw]]

This is part of the planning meeting we had with dbuc.  I filed a tracker at bug 821402

Comment 3

[Matt Basta [:basta]]

> - General device/platform info
>   > device model

This doesn't appear to be a thing. Do we need this information? I thought we were doing feature sniffing.

>   > WebRT version

Is there an API for this? Is it part of the user agent?

>   > OS version

Same as the above questions.

> - Screen capabilities
>   > resolution

window.screen?

>   > physical size

window.devicePixelRatio?

I don't know if there's an API (or will be an API) to return the physical size of a pixel.

Comment 4

[Matt Basta [:basta]]

bump? We can't make the client-side device profiler work until we have a list of specific things that need to be tested.

Comment 5

[Wil Clouser [:clouserw]]

this was filed prematurely.  project is currently in product/ux stage

Comment 6

[Daniel Buchner [:dbuc]]

(In reply to Wil Clouser [:clouserw] from comment #5)
> this was filed prematurely.  project is currently in product/ux stage

I disagree - we know, empirically, most of what we need to capture for the system to operate as desired. UX/UI is downstream from the data-capture requirements. Whatever pretty pictures and user flows UX/UI creates to elicit/display the data is fine, but it does do not dictate what we need to capture - know what I mean?

Let's figure out the ones we know for sure now:

- Privileged API availability (must be checked per API)
- Screen size (for association with general device types)
- Device pixel ratio
- Flash support
- Payments support (carrier)
- What else???

Comment 7

[Wil Clouser [:clouserw]]

(In reply to Daniel Buchner [:dbuc] from comment #6)
> (In reply to Wil Clouser [:clouserw] from comment #5)
> > this was filed prematurely.  project is currently in product/ux stage
> 
> I disagree - we know, empirically, most of what we need to capture for the
> system to operate as desired. UX/UI is downstream from the data-capture
> requirements. Whatever pretty pictures and user flows UX/UI creates to
> elicit/display the data is fine, but it does do not dictate what we need to
> capture - know what I mean?
> 
> Let's figure out the ones we know for sure now:
> 
> - Privileged API availability (must be checked per API)
> - Screen size (for association with general device types)
> - Device pixel ratio
> - Flash support
> - Payments support (carrier)
> - What else???

Discussions like this don't go well in bugzilla.  This is what the product/PRD stage of a project is for.

Comment 8

[Matt Basta [:basta]]

We're now passing the following information to the API:

- Device platform (desktop, android, fxos)
- Wide/narrow screen
- Device profile (API compatibility for non-certified and critical APIs)

https://github.com/mozilla/fireplace/commit/f1cd47d7081ff5e1c64585f1aa5a573c22aff5b6

Chrome has a profile of 3088.22.1.
Firefox Nightly has a profile of 2277237.22.1.

See code for details

Comment 9

[Christopher Van Wiemeersch [:cvan]]

https://github.com/mozilla/fireplace/commit/f1cd47d7081ff5e1c64585f1aa5a573c22aff5b6#commitcomment-2940668

Comment 10

[Matt Basta [:basta]]

you're literally the worst.

https://github.com/mozilla/fireplace/commit/3aa63cea5551e5394ae92964e5d0934167388e38