# Mobile devices/browser/version metrics and user-agents

**URL:** <https://club.ministryoftesting.com/t/mobile-devices-browser-version-metrics-and-user-agents/63827>\
**Category:** Archive\
**Tags:** metrics\
**Created:** [29 November 2022 19:26 UTC](https://club.ministryoftesting.com/t/mobile-devices-browser-version-metrics-and-user-agents/63827 "2022-11-29T19:26:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![petalmd](https://avatars.discourse-cdn.com/v4/letter/p/ed8c4c/32.png) [@petalmd](https://club.ministryoftesting.com/u/petalmd)\
**Post date:** [29 November 2022 19:26 UTC](https://club.ministryoftesting.com/t/mobile-devices-browser-version-metrics-and-user-agents/63827/1 "2022-11-29T19:26:47Z")

</div>

Hello Club !

This is my first question so I hope I do it right 😃

We are trying to get information on devices, OS, versions used on our web applications.  
Until now User-Agents were our go to solution, but recently we understood that it’s less and less easy to work with user-agents.

- [Windows 11 is reporting as a windows 10](https://developers.whatismybrowser.com/learn/browser-detection/user-agents/detect-windows-11-user-agent)
- [OSX is caped to 10\_15\_7](https://chromestatus.com/feature/5452592194781184)
- IOS devices reporting as iphone or ipad with no more details about models

We need this information to make sure we are investing our testing effort on the more used device/browser/version combinations.

I was wondering what are you doing exactly to get your web app devices/broswers/versions metrics ?

Thanks all ! 😃

---

<div class="post-metadata">

**Author:** ![denngrck](https://avatars.discourse-cdn.com/v4/letter/d/9fc29f/32.png) [@denngrck](https://club.ministryoftesting.com/u/denngrck)\
**Post date:** [30 November 2022 08:22 UTC](https://club.ministryoftesting.com/t/mobile-devices-browser-version-metrics-and-user-agents/63827/2 "2022-11-30T08:22:26Z")

</div>

You might want to take a look at Client Hints, which web servers can request from user agents. There seems to be good support in modern browsers (except Firefox it seems) for this new/upcoming method of getting infos about the user agent. This also includes the relevant `Sec-CH-UA*` and related headers, which provide the browser, versions, platform etc. See:

> **[HTTP Client hints - HTTP | MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Client_hints)**
>
> Client hints are a set of HTTP request header fields that a server can proactively request from a client to get information about the device, network, user, and user-agent-specific preferences.
> The server can determine which resources to send,...

And:

> **[Future of Device Detection in Modern Browsers: User-Agent Client Hints](https://blog.bitsrc.io/future-of-device-detection-in-modern-browsers-user-agent-client-hints-dd271f3397e4)**
>
> Understanding the device data transmission by modern browsers

---

<div class="post-metadata">

**Author:** ![conrad.connected](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/conrad.connected/32/10123_2.png) [@conrad.connected](https://club.ministryoftesting.com/u/conrad.connected)\
**Post date:** [30 November 2022 10:00 UTC](https://club.ministryoftesting.com/t/mobile-devices-browser-version-metrics-and-user-agents/63827/3 "2022-11-30T10:00:37Z")

</div>

User agent returned values are an unquantified risk. If your app has a single sign-on or other integration, then it becomes important, so keen to know what the use case or actual risks you have found to be are.

Technically, you are doing nothing wrong. If a browser says it is the XYZ browser, that’s the browser you test, not the platform you should test. Unless your web based app interacts with the platform clipboard, filesystem, firewalls or other, you really want to ignore the platform. I know this sounds like god speaking, and I can hear the ringing of the lightening strike build-up, but that was the entire idea of browsers. I would be far more interested in metrics like canvas size, and orientation dark modes and performance as a tester. Things like does our page run well on a 4G connection is far more interesting to me than if Chrome is on a iPhone or a Samsung. Although there are some things to watch out for still, but display/canvas size is still your clue.
