{"id":493662,"date":"2026-09-06T20:05:42","date_gmt":"2026-09-06T20:05:42","guid":{"rendered":"https:\/\/savepearlharbor.com\/?p=493662"},"modified":"-0001-11-30T00:00:00","modified_gmt":"2026-09-06T20:05:42","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=493662","title":{"rendered":"Your Desktop Anti-Detect Setup Doesn&#8217;t Survive Mobile"},"content":{"rendered":"<div xmlns=\"http:\/\/www.w3.org\/1999\/xhtml\">\n<p>When I added mobile personas to a browser that already had desktop ones working, I assumed the work was mostly string substitution: swap the user agent, set touch points to 5, shrink the viewport, done. That assumption survived about a day.<\/p>\n<p>Mobile fingerprints aren\u2019t a variant of desktop fingerprints. They\u2019re a different set of constraints, and most of the desktop toolkit either doesn\u2019t apply or actively gives you away. Here\u2019s what I ran into, in the order it hurt.<\/p>\n<h3>The user agent has almost no room left<\/h3>\n<p>Desktop anti-detect work still has a habit of treating the UA string as a place to be creative. On mobile, UA reduction has frozen the format into a small number of shapes. There is essentially one correct form for Chrome on an Android phone, one for an Android tablet, and one for desktop Windows. Everything else \u2014 every extra token, every version in the wrong segment \u2014 is a mismatch against a string the detector can generate itself.<\/p>\n<p>This turned out to be the single most effective filter when I was building a library of real device profiles. I collect fingerprints from consenting real visitors, and the first rule is: <strong>the UA must match one of the known-good forms character for character.<\/strong> A whitelist, not a blacklist. It rejects Edge, Samsung Internet, Opera and Yandex builds in one move \u2014 which matters because the engine reports Chrome branding, so a Samsung Internet UA sitting in the same profile row is a contradiction, not a variation.<\/p>\n<p>It also catches something the collection side gets wrong: in-app webviews. Facebook\u2019s, Instagram\u2019s and TikTok\u2019s embedded browsers announce themselves in the UA (<code>; wv)<\/code> plus an app token), and my collector\u2019s own webview flag missed a batch of them. The UA string didn\u2019t. Never trust the capture layer\u2019s classification when the raw string is right there.<\/p>\n<p>Webviews matter because their font sets and available APIs are the host app\u2019s, not a stock browser\u2019s. A profile captured from one is a profile of a thing your browser can\u2019t be.<\/p>\n<h3>Client hints are where mobile identity actually lives<\/h3>\n<p>On desktop you can often get away with ignoring high-entropy client hints. On Android you cannot, because <code>model<\/code> and <code>platformVersion<\/code> are the two fields that say <em>which phone this is<\/em>, and they have to agree with everything else.<\/p>\n<p>The failure mode is subtle. If your persona lacks these values, something has to fill them in \u2014 and a generated placeholder like a round <code>15.0.0<\/code> platform version with an empty model is a fingerprint of your generator, not of a phone. So my import rules drop any captured device missing them. Those records are still a real device; they\u2019re just no longer usable as one.<\/p>\n<p>Same reasoning applies to what you might call the \u201cidentity cross-check\u201d: <code>navigator.platform<\/code>, the client-hint platform, and the UA all have to tell the same story. Any disagreement is an automatic reject on the way in, because a contradiction shipped to a user is worse than a smaller library.<\/p>\n<h3>The GPU is the tell<\/h3>\n<p>Android GPUs are Adreno, Mali, PowerVR, Xclipse. They report through OpenGL ES with a characteristic renderer string, a specific set of supported extensions, and specific shader precision ranges.<\/p>\n<p>Two rejects I check for explicitly:<\/p>\n<ul>\n<li>\n<p><strong>Software renderers.<\/strong> SwiftShader or llvmpipe in a mobile profile means it came from an emulator or a headless run, not a phone. Those get dropped.<\/p>\n<\/li>\n<li>\n<p><strong>Direct3D on Android.<\/strong> A profile claiming to be an Android phone whose WebGL layer reports a D3D11 backend is a Windows machine wearing a mobile UA. This is exactly what a desktop-first spoofing setup produces when it only rewrites strings, and it\u2019s trivially detectable.<\/p>\n<\/li>\n<\/ul>\n<p>That second one is the general lesson: <strong>mobile spoofing fails on the surfaces that are computed rather than declared.<\/strong> You can declare a UA. You cannot declare the shader precision ranges the driver reports, unless the substitution happens deep enough in the browser to replace the real answer.<\/p>\n<h3>Worker threads and iframes have to agree<\/h3>\n<p>The check that catches the most half-finished spoofing setups is also the cheapest to run: ask the same question from a Web Worker, and from an iframe, that you asked on the main thread.<\/p>\n<p>A userland override installed on the main thread\u2019s <code>navigator<\/code> does not exist inside a freshly created worker. So a page reads \u201cAndroid, model X\u201d on the main thread and \u201cLinux x86_64, no model\u201d from the worker, and it doesn\u2019t need any other evidence. I reject captured devices where the two disagree, for the same reason \u2014 that device was itself running something that only patched the main thread, and I\u2019d be importing someone else\u2019s broken disguise as ground truth.<\/p>\n<p>Anything that only lives above the engine has this problem structurally. Every new realm \u2014 worker, iframe, <code>about:blank<\/code> document \u2014 is a fresh set of natives your injection has to race and re-apply.<\/p>\n<h3>Screen geometry is a joint constraint<\/h3>\n<p>Desktop personas can get away with a viewport that\u2019s approximately plausible. Mobile ones can\u2019t, because the values are coupled:<\/p>\n<ul>\n<li>\n<p>Screen dimensions, device pixel ratio, available screen area and viewport size are all related through one device\u2019s actual hardware.<\/p>\n<\/li>\n<li>\n<p><code>navigator.maxTouchPoints<\/code> must be non-zero, and a \u201cmobile\u201d persona with a mouse-shaped pointer media query is a contradiction.<\/p>\n<\/li>\n<li>\n<p>Tablets and phones have different UA forms <em>and<\/em> different aspect ratios, and mixing the two is a common generated-persona failure.<\/p>\n<\/li>\n<\/ul>\n<p>The efficient answer here is not to generate these values but to sample them together from a real device, as one unit. Which is why I run a real-device library at all rather than a generator: the joint distribution is the hard part, and real hardware gives it to you for free.<\/p>\n<p>That library has a number I like quoting because it\u2019s the honest cost of the rules above: after all the filters, <strong>roughly one in nine collected devices is usable.<\/strong> Everything else fails on a webview UA, a mismatched platform, a missing client hint, a software renderer, or a worker-thread disagreement. Collecting a fake is much worse than collecting nothing, because a fake gets served to users under the label \u201creal device.\u201d<\/p>\n<h3>What mobile still can\u2019t do<\/h3>\n<p>Being straight about the ceiling: the platforms people most want mobile personas for \u2014 the big social apps \u2014 largely don\u2019t care about your browser fingerprint, because their real defenses are in their native apps. Request signing, device attestation and behavioral models built on native telemetry are not things a web browser can present, no matter how good the persona is. Community reports about account survival on those platforms are consistent and unflattering to every product in this category, mine included.<\/p>\n<p>Where mobile personas do earn their keep is everything else: mobile-only or mobile-preferential web experiences, testing responsive behavior against real device profiles rather than devtools emulation, and any target whose mobile web path is less hostile than its desktop one.<\/p>\n<p>Just don\u2019t reach for it thinking it\u2019s a desktop profile with a different UA. The UA is the one part you almost can\u2019t get wrong, because there\u2019s only one right answer. It\u2019s everything computed downstream that decides.<\/p>\n<hr\/>\n<p>\u0412\u043f\u0435\u0440\u0432\u044b\u0435 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u043e \u0437\u0434\u0435\u0441\u044c: <a href=\"https:\/\/antibrow.com\/blog\/desktop-anti-detect-does-not-survive-mobile\" rel=\"noopener nofollow\">https:\/\/antibrow.com\/blog\/desktop-anti-detect-does-not-survive-mobile<\/a><\/p>\n<\/div>\n<p>\u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438 <a href=\"https:\/\/habr.com\/ru\/articles\/1079142\/\">https:\/\/habr.com\/ru\/articles\/1079142\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I added mobile personas to a browser that already had desktop ones working, I assumed the work was mostly string substitution: swap the user agent, set touch points to 5, shrink the viewport, done. That assumption survived about a day.Mobile fingerprints aren\u2019t a variant of desktop fingerprints. They\u2019re a different set of constraints, and most of the desktop toolkit either doesn\u2019t apply or actively gives you away. Here\u2019s what I ran into, in the order it hurt.The user agent has almost no room leftDesktop anti-detect work still has a habit of treating the UA string as a place to be creative. On mobile, UA reduction has frozen the format into a small number of shapes. There is essentially one correct form for Chrome on an Android phone, one for an Android tablet, and one for desktop Windows. Everything else \u2014 every extra token, every version in the wrong segment \u2014 is a mismatch against a string the detector can generate itself.This turned out to be the single most effective filter when I was building a library of real device profiles. I collect fingerprints from consenting real visitors, and the first rule is: the UA must match one of the known-good forms character for character. A whitelist, not a blacklist. It rejects Edge, Samsung Internet, Opera and Yandex builds in one move \u2014 which matters because the engine reports Chrome branding, so a Samsung Internet UA sitting in the same profile row is a contradiction, not a variation.It also catches something the collection side gets wrong: in-app webviews. Facebook\u2019s, Instagram\u2019s and TikTok\u2019s embedded browsers announce themselves in the UA (; wv) plus an app token), and my collector\u2019s own webview flag missed a batch of them. The UA string didn\u2019t. Never trust the capture layer\u2019s classification when the raw string is right there.Webviews matter because their font sets and available APIs are the host app\u2019s, not a stock browser\u2019s. A profile captured from one is a profile of a thing your browser can\u2019t be.Client hints are where mobile identity actually livesOn desktop you can often get away with ignoring high-entropy client hints. On Android you cannot, because model and platformVersion are the two fields that say which phone this is, and they have to agree with everything else.The failure mode is subtle. If your persona lacks these values, something has to fill them in \u2014 and a generated placeholder like a round 15.0.0 platform version with an empty model is a fingerprint of your generator, not of a phone. So my import rules drop any captured device missing them. Those records are still a real device; they\u2019re just no longer usable as one.Same reasoning applies to what you might call the \u201cidentity cross-check\u201d: navigator.platform, the client-hint platform, and the UA all have to tell the same story. Any disagreement is an automatic reject on the way in, because a contradiction shipped to a user is worse than a smaller library.The GPU is the tellAndroid GPUs are Adreno, Mali, PowerVR, Xclipse. They report through OpenGL ES with a characteristic renderer string, a specific set of supported extensions, and specific shader precision ranges.Two rejects I check for explicitly:Software renderers. SwiftShader or llvmpipe in a mobile profile means it came from an emulator or a headless run, not a phone. Those get dropped.Direct3D on Android. A profile claiming to be an Android phone whose WebGL layer reports a D3D11 backend is a Windows machine wearing a mobile UA. This is exactly what a desktop-first spoofing setup produces when it only rewrites strings, and it\u2019s trivially detectable.That second one is the general lesson: mobile spoofing fails on the surfaces that are computed rather than declared. You can declare a UA. You cannot declare the shader precision ranges the driver reports, unless the substitution happens deep enough in the browser to replace the real answer.Worker threads and iframes have to agreeThe check that catches the most half-finished spoofing setups is also the cheapest to run: ask the same question from a Web Worker, and from an iframe, that you asked on the main thread.A userland override installed on the main thread\u2019s navigator does not exist inside a freshly created worker. So a page reads \u201cAndroid, model X\u201d on the main thread and \u201cLinux x86_64, no model\u201d from the worker, and it doesn\u2019t need any other evidence. I reject captured devices where the two disagree, for the same reason \u2014 that device was itself running something that only patched the main thread, and I\u2019d be importing someone else\u2019s broken disguise as ground truth.Anything that only lives above the engine has this problem structurally. Every new realm \u2014 worker, iframe, about:blank document \u2014 is a fresh set of natives your injection has to race and re-apply.Screen geometry is a joint constraintDesktop personas can get away with a viewport that\u2019s approximately plausible. Mobile ones can\u2019t, because the values are coupled:Screen dimensions, device pixel ratio, available screen area and viewport size are all related through one device\u2019s actual hardware.navigator.maxTouchPoints must be non-zero, and a \u201cmobile\u201d persona with a mouse-shaped pointer media query is a contradiction.Tablets and phones have different UA forms and different aspect ratios, and mixing the two is a common generated-persona failure.The efficient answer here is not to generate these values but to sample them together from a real device, as one unit. Which is why I run a real-device library at all rather than a generator: the joint distribution is the hard part, and real hardware gives it to you for free.That library has a number I like quoting because it\u2019s the honest cost of the rules above: after all the filters, roughly one in nine collected devices is usable. Everything else fails on a webview UA, a mismatched platform, a missing client hint, a software renderer, or a worker-thread disagreement. Collecting a fake is much worse than collecting nothing, because a fake gets served to users under the label \u201creal device.\u201dWhat mobile still can\u2019t doBeing straight about the ceiling: the platforms people most want mobile personas for \u2014 the big social apps \u2014 largely don\u2019t care about your browser fingerprint, because their real defenses are in their native apps. Request signing, device attestation and behavioral models built on native telemetry are not things a web browser can present, no matter how good the persona is. Community reports about account survival on those platforms are consistent and unflattering to every product in this category, mine included.Where mobile personas do earn their keep is everything else: mobile-only or mobile-preferential web experiences, testing responsive behavior against real device profiles rather than devtools emulation, and any target whose mobile web path is less hostile than its desktop one.Just don\u2019t reach for it thinking it\u2019s a desktop profile with a different UA. The UA is the one part you almost can\u2019t get wrong, because there\u2019s only one right answer. It\u2019s everything computed downstream that decides.\u0412\u043f\u0435\u0440\u0432\u044b\u0435 \u043e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d\u043e \u0437\u0434\u0435\u0441\u044c: https:\/\/antibrow.com\/blog\/desktop-anti-detect-does-not-survive-mobile\u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438 https:\/\/habr.com\/ru\/articles\/1079142\/<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-493662","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/493662","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=493662"}],"version-history":[{"count":0,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/493662\/revisions"}],"wp:attachment":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=493662"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=493662"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=493662"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}