UserAgent Mobile 200825

What is a User Agent?

A user agent is a crucial component in the interaction between web browsers and servers, serving as an identifying string that provides significant details about the user’s browsing environment. When a user accesses a website, their web browser sends this user agent string to the web server. This string typically includes information such as the browser type, its version, and the operating system used on the device. Understanding the user agent is vital not only for web developers but also for optimizing the user experience across different platforms and devices.

Each web browser has its unique user agent string that it generates based on its specifications. For example, a user agent string from Google Chrome will differ from that of Mozilla Firefox, containing identifiers that relay various pieces of information. This helps servers to yield content that is compatible with the specific browser in use, thus facilitating effective content negotiation. In addition, user agents enable websites to adapt their designs and functionalities depending on the capabilities of the device accessing them.

The importance of user agents extends beyond just identifying browsers. They play a pivotal role in web standards and practices, allowing for the proper rendering of web pages. By understanding the nuances of user agents, developers can create more responsive and mobile-friendly websites that ensure consistent performance across a myriad of devices and browsing environments. In essence, user agents bridge the communication gap between web applications and users, streamlining the delivery of tailored content that meets the expectations of diverse audiences.

The Role of User Agents in Mobile Browsers

User agents play a crucial role in mobile browsers by providing essential information about the device’s capabilities and identifying the browser in use. This information helps servers tailor responses that improve user experience, considering the unique aspects of mobile devices. Unlike desktop user agents, mobile user agents must account for factors such as screen size, touch interface, and various mobile networking environments, facilitating the delivery of optimized content.

The differences in screen size significantly impact how content is displayed. Mobile devices typically have smaller screens compared to desktops, requiring web developers to create responsive designs. The mobile user agent communicates the dimensions and resolution of the screen, allowing servers to serve appropriately-sized assets. This often includes adjusting images and modifying layout structures to enhance readability and usability on varying screen sizes.

Additionally, touch capabilities are inherent to most mobile devices. Unlike desktops that prioritize mouse input, mobile browsers utilize touch-based interactions, such as swiping and tapping. The user agent conveys this information, enabling web applications to respond with touch-friendly layouts and controls. This adaptability is essential since users expect seamless and intuitive navigation while using mobile devices.

Mobile networking considerations also play a significant role in the effectiveness of mobile user agents. Users may experience varying network speeds and types, such as 4G or Wi-Fi. By identifying the browser and its capabilities, user agents can help determine whether to deliver lighter, data-efficient pages for slower connections or richer, media-heavy content for faster networks.

In summary, mobile user agents are instrumental in ensuring that websites and applications provide an optimized experience tailored specifically for mobile users. By understanding their role, developers can enhance accessibility and usability, ultimately leading to higher engagement and satisfaction among mobile users.

Common Mobile User Agent Strings

User agent strings are critical components in identifying the specifics of a browser and device. Each mobile browser generates a unique user agent string that provides information regarding the browser type, version, operating system, and device model. Understanding these strings is vital for web developers aiming to optimize their sites for various devices.

For instance, consider a typical user agent string from an iPhone using Safari:

Mozilla/5.0 (iPhone; CPU iPhone OS 15_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Mobile/15E148 Safari/604.1

This string reveals several key components. “Mozilla/5.0” indicates the compatibility of the browser. “iPhone; CPU iPhone OS 15_0” specifies the device type and operating system version. “AppleWebKit/605.1.15” identifies the rendering engine, while “Version/15.0” denotes the browser version, ultimately concluding with “Mobile/15E148” and “Safari/604.1,” identifying the mobile platform and the specific browser.

Now, let’s look at an example from an Android device using Google Chrome:

Mozilla/5.0 (Linux; Android 12; Pixel 6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Mobile Safari/537.36

This string also carries significant insights. The “Linux; Android 12; Pixel 6” part provides details about the operating system and the specific device model—here, the Pixel 6. “AppleWebKit/537.36” states the rendering engine, while “Chrome/93.0.4577.82” discloses the version of the Chrome browser. The end of the string reinforces its mobile nature with “Mobile Safari/537.36.”

Diverse browsers and operating systems generate their own user agent strings. For instance, Firefox on a mobile device has a different structure, demonstrating uniqueness across platforms. By dissecting these user agent strings, developers can ensure optimal website performance tailored to each user’s device and browser compatibility, which is increasingly essential in today’s mobile-centric web landscape.

How to Retrieve the User Agent in Mobile Apps

Retrieving the user agent string in mobile applications is essential for various purposes, including analytics, user experience, and compatibility checks. In mobile app development, both iOS and Android platforms provide straightforward methods for accessing the user agent. Understanding how to effectively retrieve this information can be beneficial for developers aiming to optimize their applications.

For iOS applications written in Swift, the user agent can be accessed using the following code snippet:

let userAgent = UIWebView().stringByEvaluatingJavaScript(from: "navigator.userAgent")print("User Agent: \(userAgent ?? "Unavailable")")

In this example, a UIWebView instance is utilized to execute JavaScript, which fetches the user agent. This method may be useful when the application needs to adapt its behavior based on the user’s device. However, note that UIWebView is deprecated; thus, using WKWebView is advisable for newer projects. You can retrieve the user agent from WKWebView with the following approach:

let webView = WKWebView()webView.evaluateJavaScript("navigator.userAgent") { (result, error) in    if let userAgent = result as? String {        print("User Agent: \(userAgent)")    }}

On the Android platform, obtaining the user agent string can be done through the WebView class. Here is a straightforward implementation:

WebView webView = new WebView(context);webView.getSettings().setJavaScriptEnabled(true);webView.loadUrl("about:blank");webView.setWebViewClient(new WebViewClient() {    @Override    public void onPageFinished(WebView view, String url) {        view.evaluateJavascript("navigator.userAgent", new ValueCallback() {            @Override            public void onReceiveValue(String userAgent) {                Log.d("User Agent", userAgent);            }        });    }});

Retrieving the user agent string in mobile applications is particularly useful in cases where developers need to ensure compatibility with different browser environments or when tailoring content for specific devices. By effectively using these methods, developers can enhance the user experience and improve the overall functionality of their mobile applications.

User Agent Spoofing: Risks and Benefits

User agent spoofing refers to the practice where users or applications modify the user agent string transmitted by their browser to appear as if they are using a different browser or operating system. This manipulation can serve various purposes, such as accessing restricted content, enhancing privacy, or testing website functionality across different platforms. However, it is essential to explore both the benefits and risks associated with this technique.

One of the primary advantages of user agent spoofing is the ability to bypass geographical restrictions imposed by certain websites or services. For instance, users may change their user agent to mimic a device located in a different country, thereby gaining access to content that would otherwise be unavailable in their region. Additionally, this method can enhance the level of privacy for users by concealing their actual device and browser information, making it more challenging for websites to track their online activities.

Despite these benefits, user agent spoofing carries significant risks that should not be overlooked. One major concern is the potential for security vulnerabilities. By altering the user agent string, individuals may inadvertently expose themselves to malicious sites that exploit specific vulnerabilities, as some sites may deliver unsafe content based on presumed compatibility with the spoofed user agent. Furthermore, websites may not function correctly if they detect a spoofed user agent, leading to compatibility issues that hinder user experience.

Additionally, some services might flag or block users engaging in user agent spoofing, resulting in denied access or account suspension. In doing so, these services aim to protect their platform’s integrity and keep their content secure. Thus, while the temptation to utilize user agent spoofing for various benefits exists, users must carefully weigh these advantages against the accompanying risks to make a prudent decision.

Impact of User Agents on Web Development

User agents play a pivotal role in web development, significantly influencing how websites are rendered and function across various devices. When a user accesses a website, the browser sends a user agent string that provides crucial information about the browser type, version, and device specifications. This information is vital for developers to tailor their applications to offer optimal performance and functionality on diverse platforms.

One significant application of user agents is in responsive design. Developers can utilize user agent strings to identify the device’s characteristics, including screen size and resolution. This allows the website to adopt responsive layouts that adjust seamlessly to different screens, thereby enhancing usability. By delivering content that is visually appealing and easy to navigate, developers can improve the overall user experience. Moreover, user agents enable developers to focus on specific CSS media queries and HTML elements that enhance performance for mobile users, facilitating a smoother interaction with the website.

In addition to responsive design, user agents assist in feature detection. By analyzing the capabilities of the user’s device, developers can implement or omit certain features based on compatibility. For instance, if a user agent indicates an older browser that lacks support for modern JavaScript or CSS features, developers can provide fallbacks to ensure that essential content remains accessible. This careful tailoring based on user agents is essential in creating a consistent experience across various devices and technologies.

Moreover, the influence of user agents extends to optimizing website performance. By understanding the browsing environment through user agent strings, developers can make informed decisions about resource loading, improving page loads, and minimizing latency. Efficient resource management facilitated by interpreting user agents leads to enhanced website speeds, ultimately resulting in higher user satisfaction and retention. Consequently, knowledge of user agents is indispensable for modern web development.

Challenges with Mobile User Agents

In the domain of mobile web development, user agents serve as a critical component for determining the capabilities of a device and ensuring optimal content delivery. However, the handling of mobile user agents by various browsers often presents several challenges. One significant issue arises from the inconsistencies in how different mobile browsers report their user agents. For instance, identical hardware may yield varied user agent strings based on the browser or its version. This inconsistency can lead to difficulties in identifying device capabilities accurately, ultimately complicating the development process.

Furthermore, the rapid proliferation of new mobile devices exacerbates these challenges. Each new device often carries unique specifications that need to be accounted for in the development and testing stages. As manufacturers continuously release new smartphones and tablets with varying operating systems, it becomes increasingly difficult to maintain a comprehensive user agent database. This evolving landscape also necessitates frequent updates and adjustments in both server recognition scripts and testing tools, further stretching resources for web developers.

These challenges have far-reaching implications for web compatibility. When user agents fail to provide accurate data, developers may inadvertently deliver suboptimal experiences to users. For example, a website designed for one browser may not display correctly on another, leading to potential frustration for the end user. Inconsistent mobile user agents can also hinder effective testing, making it difficult to ensure that web applications perform as intended across multiple platforms.

As a result, developers must remain vigilant in monitoring changes in the mobile user agent landscape to adapt their strategies accordingly. Continuous education and staying updated with industry standards are vital for addressing these challenges, ensuring that websites cater effectively to the diverse array of mobile devices and browsers in use today.

Future Trends: Evolving User Agents in Mobile Technology

The landscape of mobile technology is continuously evolving, with user agents playing a pivotal role in shaping user experiences. As advancements in artificial intelligence (AI), machine learning, and progressive web apps (PWAs) come to the forefront, these technologies are poised to significantly influence the development of mobile user agents. The integration of AI and machine learning algorithms in mobile browsers may lead to enhanced performance and personalized experiences. For example, AI can allow user agents to analyze usage patterns and predict user behavior, enabling them to preemptively load resources or suggest content that aligns with individual preferences.

Moreover, the rise of PWAs presents an opportunity for user agents to facilitate seamless interoperability between different devices and platforms. By bridging the gap between web applications and native applications, PWAs leverage service workers and caching strategies to deliver enhanced performance. As more developers shift towards creating PWAs, mobile browsers may be equipped with more sophisticated user agents capable of better handling these applications. This could result in faster load times and a more fluid user experience across a variety of devices.

Looking ahead, the evolution of mobile user agents is also likely to include improvements in privacy and security features. With increasing concern over user data protection, mobile browsers may integrate more robust privacy measures into their user agent architectures. These enhancements could include advanced tracking prevention and more transparent data collection practices, ultimately bolstering user trust in mobile technology.

In conclusion, as mobile technology progresses, user agents will adapt to harness emerging technologies like AI, machine learning, and PWAs. This evolution promises to improve both user experience and device interoperability, setting the stage for a more efficient and secure mobile browsing future.

Conclusion and Best Practices

In summary, user agents in mobile browsers serve as critical components that facilitate the interaction between users and web applications. They not only identify the type of device and operating system but also provide information about the browser being utilized. This information can significantly influence how websites are delivered and how content is rendered on mobile devices.

To enhance web experiences through effective handling of user agents, developers should prioritize responsiveness in their design approaches. Ensuring that websites are optimized for a variety of screen sizes and device capabilities is essential. Responsive web design techniques, which adapt to differing user agents, can significantly improve usability and engagement. Moreover, employing feature detection over user agent sniffing is often recommended, as it allows developers to serve functionalities based on actual capabilities rather than assumptions made from user agent strings.

Users, on the other hand, should be mindful of the privacy implications associated with their mobile user agents. With many websites collecting data based on user agent information, it becomes crucial to understand how this data can track browsing behaviors. Using privacy-focused browsers or extensions that minimize the sharing of user agent information can empower users to regain control over their online experiences. Additionally, it is advisable for users to regularly review their mobile browser settings, ensuring that permitted data leaks are minimized.

Ultimately, a well-informed approach to mobile user agents can foster better web communication and protect personal information, positioning both developers and users to navigate the evolving landscape of mobile browsing with confidence.

Mozilla/5.0 (Linux; Android 10; SM-A105M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 13; SM-N975F) AppleWebKit/537.36 (KHTML like Gecko) Chrome/109.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 14; SM-A135F; GMSCore 24.49.62) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.88 HuaweiBrowser/14.0.5.303 Mobile Safari/537.36
Mozilla/5.0 (Linux; U; Android 11; fr-fr; SM-A127F Build/RP1A.200720.012) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.6778.260 Mobile Safari/537.36 PHX/16.3
Mozilla/5.0 (Linux; U; Android 15; hi-in; V2250 Build/AP3A.240905.015.A2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.6422.165 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; Android 10; MAR-LX1A; HMSCore 6.13.0.342; GMSCore 24.47.38) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.88 HuaweiBrowser/13.0.5.303 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 12; V2203 Build/SP1A.210812.003) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.6834.122 Mobile Safari/537.36 OPX/2.7
Mozilla/5.0 (Linux; Android 13; GCrpNZnHSo; U; en) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.5938.153 Mobile AT/1.0.2 Safari/537.36
Mozilla/5.0 (Linux; Android 14; motorola razr 2024 Build/U3UCS34.63-88-12-3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.6834.122 Mobile Safari/537.36 OPX/2.7
Mozilla/5.0 (Linux; U; Android 8.1.0; fr-fr; TECNO CF8 Build/O11019) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.6778.104 Mobile Safari/537.36 PHX/17.2
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.0.7885525621562044
Mozilla/5.0 (Linux; U; Android 10; fr-ca; TECNO BD2 Build/QP1A.190711.020) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.101 Mobile Safari/537.36 PHX/17.3
Mozilla/5.0 (Linux; Android 8.0.0; SM-A320FL Build/R16NW; ) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.262 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 15; I2403 Build/AP3A.240905.015.A2) AppleWebKit/537.36 (KHTML, like Gecko) Yfxmdq/4.0 Chrome/131.0.6778.260 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 5.0; SM-G900P Build/LRX21T) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.4406.1803 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 13; Redmi Note 5 Pro Build/TQ3A.230805.001) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.6834.122 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 13; ONEPLUS A6003) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6354.225 Mobile Safari/537.36
Mozilla/5.0 (Linux; U; Android 11; am-; TECNO LE6 Build/RP1A.200720.011) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.85 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; U; Android 12; es-mx; V2118 Build/SP1A.210812.003) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.6778.135 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; Android 5.0; SM-G900P Build/LRX21T) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.8981.1911 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 13; LM-G900 Build/TKQ1.220829.002; ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Mobile Safari/537.36 NewsSapphire/30.5.430123006
Mozilla/5.0 (Linux; U; Android 10; in-id; SM-G965U Build/QP1A.190711.020) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.6723.107 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; U; Android 9; en-us; itel L6501 Build/PPR1.180610.011) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.87 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; Android 11; SM-A750GN) AppleWebKit/537.36 (KHTML like Gecko) Chrome/132.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.6147.1500 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 8.1.0) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/124.0.6367.113 Mobile 18+/5 Safari/537.36
Mozilla/5.0 (Linux; Android 14; SM-P620 Build/UP1A.231005.007) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/132.0.6834.122 Safari/537.36 Blackboard/10.0.0 platform/Android
Mozilla/5.0 (Linux; U; Android 11; fr-fr; Infinix X689C Build/RP1A.200720.011) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.6778.135 Mobile Safari/537.36 PHX/5.9
Mozilla/5.0 (Linux; U; Android 13; fr-fr; SM-A325F Build/TP1A.220624.014) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.141 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; U; Android 11; en-us; M2101K6G Build/RKQ1.200826.002) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.210 Mobile Safari/537.36 PHX/17.4
Mozilla/5.0 (Linux; U; Android 12; en-gb; CPH2471 Build/SP1A.210812.016) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.6723.107 Mobile Safari/537.36 PHX/17.4
Mozilla/5.0 (Linux; Android 9; TECNO BB4k Build/PPR1.180610.011) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/132.0.6834.122 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 9; LH9920 Build/PPR1.180610.011) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/132.0.6834.122 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 13; AE9260 Build/TP1A.220624.014) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/132.0.6834.122 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 15; 24040RN64Y Build/AP3A.240905.015.A2) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.260 Mobile Safari/537.36 SznProhlizec/10.6.10a
Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.7170.1890 Mobile Safari/537.36
Mozilla/5.0 (Linux; U; Android 9; en-us; itel L6005 Build/PPR1.180610.011) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.5304.141 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; Android 13; M7_WIFI Build/V4_20240829) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.6834.122 Mobile Safari/537.36
Mozilla/5.0 (Linux; U; Android 11; pt-ao; itel A509W Build/RP1A.201005.001) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.6167.178 Mobile Safari/537.36 PHX/17.2
Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.8625.1607 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 11; Infinix X659B Build/RP1A.200720.011)) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/132.0.6834.79 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 13; SM-G9508) AppleWebKit/537.36 (KHTML like Gecko) Chrome/114.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 8.1.0; LeaPad_X Build/O11019) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.6834.122 Safari/537.36
Mozilla/5.0 (Linux; Android 13; A302ZT Build/TP1A.220624.014; ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Mobile Safari/537.36 NewsSapphire/30.5.430123006
Mozilla/5.0 (Linux; U; Android 11; fr-fr; SM-F926B Build/RP1A.200720.012) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.141 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; Android 7.1.2; Vii) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36
Mozilla/5.0 (Linux; Android 14; 22101320G) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.6778.262 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.6901.1686 Mobile Safari/537.36
Mozilla/5.0 (Linux; U; Android 13; fr-fr; SM-A226B Build/TP1A.220624.014) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.6778.260 Mobile Safari/537.36 PHX/17.4
Mozilla/5.0 (Linux; U; Android 10; zh-CN; 5G Build/QP1A.190711.020) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/123.0.6312.80 Quark/7.6.5.720 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 14; SM-J330F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6336.224 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 13; Nokia 7.2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.6333.199 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 9; JKM-LX1; HMSCore 3.0.3.300; GMSCore 24.50.64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.88 HuaweiBrowser/13.0.4.302 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 14; Samsung Galaxy S9) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.6314.196 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 14; SM-A205G) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.6823.68 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 15; QCiq2Eisqj; U; ja) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.5938.153 Mobile AT/1.0.2 Safari/537.36
Mozilla/5.0 (Linux; Android 9.0; SM-G955U) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 14; ASUS Chromebook C202SA Build/R103-14816.131.0; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.0.0 Safari/537.36
Mozilla/5.0 (Linux; U; Android 10; am-; TECNO CD6 Build/QP1A.190711.020) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.87 Mobile Safari/537.36 PHX/17.4
Mozilla/5.0 (Linux; Android 9; SM-G977B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 10; SM-A115F) AppleWebKit/537.36 (KHTML like Gecko) Chrome/127.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 13; SM-M325F Build/TP1A.220624.014) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.260 Mobile Safari/537.36 GinxDroid/17.0
Mozilla/5.0 (Linux; U; Android 15; zh-Hans-CN; OPD2404 Build/UKQ1.231108.001) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/100.0.4896.58 Quark/6.13.6.581 Mobile Safari/537.36
Mozilla/5.0 (Linux; U; Android 6.0.1; ha-; SM-N916L Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.74 Mobile Safari/537.36 PHX/16.0
Mozilla/5.0 (Linux; Android 14; CPH2013) AppleWebKit/537.36 (KHTML like Gecko) Chrome/123.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; U; Android 14; en-us; 2409BRN2CA Build/UP1A.231005.007) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.6778.260 Mobile Safari/537.36 PHX/16.3
Mozilla/5.0 (Linux; Android 14; MRX-W09) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.6785.62 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 13; 220333QNY Build/TKQ1.221114.001;) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/132.0.6834.122 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 12; CPH2121 Build/SP1A.210812.016) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.6834.122 Mobile Safari/537.36 OPX/2.7
Mozilla/5.0 (Linux; Android 9; ANE-LX1 Build/HUAWEIANE-L01) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.6834.80 Mobile Safari/537.36 OPX/2.6
Mozilla/5.0 (Linux; U; Android 12; fr-fr; Infinix X6516 Build/SP1A.210812.001) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6261.66 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; U; Android 14; am-; TECNO KL4 Build/UP1A.231005.007) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.6778.262 Mobile Safari/537.36 PHX/16.3
Mozilla/5.0 (Linux; Android 13; Lenovo TB-X606FA) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.6328.208 Mobile Safari/537.36
Mozilla/5.0 (Linux; U; Android 12; fr-fr; Infinix X669C Build/SP1A.210812.016) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.6723.108 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; Android 14; M2103K19PG) AppleWebKit/537.36 (KHTML like Gecko) Chrome/121.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; U; Android 14; en-us; SM-T220 Build/UP1A.231005.007) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.6723.107 Mobile Safari/537.36 PHX/17.4
Mozilla/5.0 (Linux; U; Android 14; en-us; V2338 Build/UP1A.231005.007) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.6533.103 Mobile Safari/537.36 PHX/17.5
Mozilla/5.0 (Linux; Android 9; SM-J530G Build/PPR1.180610.011; ) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.261 Mobile Safari/537.36 NewsSapphire/30.5.430123001
Mozilla/5.0 (Linux; Android 13; SM-G9860 Build/TP1A.220624.014)) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/111.0.5563.116 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 4.2.1) AppleWebKit/536.0 (KHTML, like Gecko) Chrome/56.0.879.0 Safari/536.0
Mozilla/5.0 (iPad; CPU iPad OS 17_1_2 like Mac OS X) AppleWebKit/535.0 (KHTML, like Gecko) CriOS/40.0.800.0 Mobile/98J795 Safari/535.0
Mozilla/5.0 (iPhone; CPU iPhone OS 1_1_5 like Mac OS X) AppleWebKit/533.2 (KHTML, like Gecko) CriOS/41.0.895.0 Mobile/11G084 Safari/533.2
Mozilla/5.0 (iPad; CPU iPad OS 17_1_2 like Mac OS X) AppleWebKit/536.0 (KHTML, like Gecko) CriOS/26.0.830.0 Mobile/48F750 Safari/536.0
Mozilla/5.0 (Linux; Android 4.2.2) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/20.0.848.0 Safari/532.0
Mozilla/5.0 (Linux; Android 2.0) AppleWebKit/533.0 (KHTML, like Gecko) Chrome/21.0.885.0 Safari/533.0
Mozilla/5.0 (iPad; CPU iPad OS 4_2_1 like Mac OS X) AppleWebKit/533.1 (KHTML, like Gecko) CriOS/28.0.883.0 Mobile/20Z194 Safari/533.1
Mozilla/5.0 (iPad; CPU iPad OS 12_4_8 like Mac OS X) AppleWebKit/535.2 (KHTML, like Gecko) CriOS/44.0.809.0 Mobile/58N422 Safari/535.2
Mozilla/5.0 (Linux; Android 4.0.2) AppleWebKit/535.0 (KHTML, like Gecko) Chrome/34.0.897.0 Safari/535.0
Mozilla/5.0 (Linux; Android 4.2) AppleWebKit/531.2 (KHTML, like Gecko) Chrome/61.0.896.0 Safari/531.2
Mozilla/5.0 (iPhone; CPU iPhone OS 17_1_1 like Mac OS X) AppleWebKit/535.0 (KHTML, like Gecko) CriOS/55.0.882.0 Mobile/60K145 Safari/535.0
Mozilla/5.0 (Linux; Android 2.3.1) AppleWebKit/532.1 (KHTML, like Gecko) Chrome/32.0.876.0 Safari/532.1
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_12_2) AppleWebKit/533.0 (KHTML, like Gecko) Chrome/16.0.887.0 Safari/533.0
Mozilla/5.0 (iPhone; CPU iPhone OS 17_2 like Mac OS X) AppleWebKit/534.1 (KHTML, like Gecko) CriOS/23.0.890.0 Mobile/02Z141 Safari/534.1
Mozilla/5.0 (iPhone; CPU iPhone OS 17_1 like Mac OS X) AppleWebKit/535.0 (KHTML, like Gecko) CriOS/62.0.840.0 Mobile/34R553 Safari/535.0
Mozilla/5.0 (iPad; CPU iPad OS 3_2_2 like Mac OS X) AppleWebKit/533.1 (KHTML, like Gecko) CriOS/52.0.805.0 Mobile/72F224 Safari/533.1
Mozilla/5.0 (iPhone; CPU iPhone OS 14_8_1 like Mac OS X) AppleWebKit/536.2 (KHTML, like Gecko) CriOS/21.0.863.0 Mobile/89C159 Safari/536.2
Mozilla/5.0 (Linux; Android 4.4.1) AppleWebKit/536.2 (KHTML, like Gecko) Chrome/22.0.852.0 Safari/536.2
Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_2 like Mac OS X) AppleWebKit/535.0 (KHTML, like Gecko) CriOS/42.0.898.0 Mobile/13P440 Safari/535.0
Mozilla/5.0 (iPad; CPU iPad OS 16_7_7 like Mac OS X) AppleWebKit/531.1 (KHTML, like Gecko) CriOS/62.0.882.0 Mobile/52Q781 Safari/531.1
Mozilla/5.0 (Linux; Android 4.1) AppleWebKit/536.1 (KHTML, like Gecko) Chrome/46.0.841.0 Safari/536.1