GoogleChromeLabs / GoogleChromeLabs/adaptive-loading

Alternative ways of obtaining device information (other than UA string)?

Open
#118 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
264
Forks
30
PR merge metrics
No merged PRs in 30d

Description

HI folks,

This is a great project. I'm starting to get into the details of this solution, as companies are starting to ask for it.

Reading the docs, it seems like you are using the UA string to obtain some device info. Now that there's an ongoing proposal to [deprecate and freeze the UA](https://groups.google.com/a/chromium.org/forum/?oldui=1#!topic/blink-dev/-2JIRNMWJ7s), are you thinking on alternative ways of obtaining this info?

Seems like the most obvious one would be using client-hints (which you have already discussed [here](https://github.com/GoogleChromeLabs/adaptive-loading/issues/39)). The current limitation being that you can't get these signals in the first page load (although [that might change](https://github.com/WICG/client-hints-infrastructure/issues/16)).

I'm wondering if you guys are contemplating this scenario, and have any thoughts or recommendations around it.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.