Before building User-Agent Parser, we checked how a well-known existing UA parser presents its results, and looked into what Chromium's own documentation says about what a modern mobile User-Agent string actually contains.
Chrome stopped telling the truth about your phone (on purpose)
Since Chrome 110, mobile User-Agent strings no longer report your device's real OS version or model — Chromium's own documentation confirms the values are frozen to generic placeholders, typically showing as Android 10; K regardless of what device or Android version you're actually running. It's a deliberate privacy change, not a bug — but a parser that reports "Android 10" without explaining that is handing you a fake data point dressed up as a real one.
An existing tool we checked doesn't mention it
We looked at a well-known UA parser's site and found no warning about this anywhere in the free tier — parsed fields are presented straightforwardly, and Client Hints support (the modern replacement standard) is reserved for paid plans. This tool detects the exact frozen pattern and shows a warning explaining what it means, for free.
Even without the freeze, don't trust it too much
Independent device-detection research has found that UA-string-based mobile device/brand identification is wrong or returns nothing about 22% of the time, industry-wide — a limitation of the approach itself, not any one parser's implementation. This tool's FAQ says so directly, rather than presenting results with more confidence than they deserve.
