How to Debug Website on Mobile Chrome

As mobile surf becomes the master mode of access for many users, ensuring that websites perform optimally on nomadic devices is essential. Debugging websites on Chrome for mobile involves overcoming unequaled challenges colligate to responsiveness, performance, and device compatibility.

This article outlines two method for debug websites on Mobile Chrome: Method 1: Android USB Debugging Mode, which provides direct debugging via USB, and Method 2: Interactive Chrome Debugging on Real Devices using BrowserStack, offer cloud-based testing on a multifariousness of real roving devices.

Method 1: Using Android USB Debugging Mode

Developers can leverage the Android USB debugging mode to debug websites on nomadic Chrome. Assuming that the developer has an Android device for screen purposes, they need to follow the steps below to get started with website debug on nomadic Chrome.

Step 1:From the device Settings, enable theDeveloper options. To enable the Developer option, tap theBuild Number pickseven times.

Note:As per the official Android documentation, one can find this option in one of the undermentioned locations, depending on the Android version:

• Android 9 (API level 28) and higher:Settings & gt; About Phone & gt; Build Number
• Android 8.0.0 (API level 26) and Android 8.1.0 (API level 26):Settings & gt; System & gt; About Phone & gt; Build Number
• Android 7.1 (API level 25) and lower:Settings & gt; About Phone & gt; Build Number

Step 2: Further, enable the USB debugging option in the Developer Options menu. One can find this option in one of the following locations, depending on the Android variation:

• Android 9 (API level 28) and high:Settings & gt; System & gt; Advanced & gt; Developer Options & gt; USB debugging
• Android 8.0.0 (API level 26) and Android 8.1.0 (API level 26):Settings & gt; System & gt; Developer Options & gt; USB debugging
• Android 7.1 (API level 25) and lower:Settings & gt; Developer Options & gt; USB debugging

Step 3:Launch Chrome

Step 4:Navigate to & # 8211; chrome: //inspect # devices.

Step 5:Ensure that the Discover USB devices checkbox is enabled as seen below.

Step 6:Now, the developer needs to Connect the Android gimmick directly to the development machine using a USB line.

Note:If the framework gens of your Android device is display, so DevTools has successfully established the connectedness to your device. On the contrary, If the device is showing up asOffline, accept theAllow USB Debuggingpermission prompt on your Android device. Refer to the official documentation for learning about trouble-shoot issues.

Step 7:Now, launch Chrome on the Android device.

Step 8: On the chrome: //inspect/ # devicepage, you see your Android device & # 8217; s model name, follow by its sequent routine. The version of Chrome that & # 8217; s lead on the device is also displayed in the parentheses.

Step 9:A unique subdivision is displayed for every unfastened page in the mobile Chrome, and one can interact with the desired tab from this subdivision.

Step 10:Enter a URL in theOpen tab with the URLtext box, and detentOpen. The page opens in a new account on your Android device.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Step 11:Now, clickInspectnext to the URL that you just opened. A new DevTools instance opens.

Now you can get alive Debugging for the craved web page on your roving Chrome.

Method 2: Synergistic Chrome Debugging on Real Mobile Devices use BrowserStack

In some cases, developers need to prove or debug a website on mobile Chrome for a specific handset. Purchasing a new device every time for testing isn ’ t a scalable resolution for most teams.

This is where come in. It provides access to a with over 3500+ real devices and browsers, enable live, interactive testing and debugging on actual device-browser combination. This eliminates the need for teams to invest in multiple device, saving both clip and cost.

With BrowserStack, developer can screen and debug website on handsets from result manufacturers like Samsung, OnePlus, Motorola, Google, and others. The program allows instant access to Chrome DevTools in alive session, afford developers the ability to scrutinise and debug mobile Chrome directly on the selected Android device.

Step 1:  on BrowserStack Live.

Step 2:Navigate to the Live dashboard.

Step 3:From the dashboard, choose Android OS and hover on the desired handset. (For model, Samsung S22 ultra).

Step 4:Click on the Chrome logo once it seem after vibrate.

Step 5: A new Live Chrome session will get instantly on a realSamsung S22 Ultra-Chromeformerly you click on the Chrome logotype.

Step 6:Now one can start testing and debugging the desired web page using the Devtools useable in the natation toolbar.

That ’ s how easy one can debug a website on Chrome for the desired real handset without any complex setup.

Additionally, teams besides get access to multiple features useable in the toolbar formerly a session begins:

• allows users to examine a website ’ s performance on mobile when accessed from a unique geographical location.
• Instant bug coverage (through Jira, Trello, Slack, Github) enables the users to report bugs to their squad directly from the Live dashboard.
• allows user to examine website in distinct screen declaration (like 1024 & # 215; 768, 1280×800, 1820×1024, and so on).
• enables users to test and debug work-in-progress web applications at scale in local environments without hosting them in public scaffolding environments.
• Network throttler let the QAs tryout the website ’ s performance in poor net weather.

Why Choose BrowserStack?

When it comes to mobile web testing, accuracy, speed, and flexibility are essential. BrowserStack provides an all-in-one resolution for debugging websites on Mobile Chrome, offering admittance to a wide range of real devices and browsers.

By testing on actual devices, developers can ensure that their website perform as expected under, eradicate the uncertainty that come with utilise.

Beyond just debugging, BrowserStack enhances the testing experience with a suite of powerful features available during Live sessions:

• : This feature enables users to assume accessing a website from different geographical positioning, helping developers test how location-based services and content behave in depart regions.
• : Teams can seamlessly describe bugs directly from the Live session splasher, with consolidation available for Jira, Trello, Slack, and Github. This streamlines collaboration and ensures issue are quickly log and dog.
• Antiphonal Testing:Developers can test website on diverse screen resolutions (such as 1024×768, 1280×800, 1820×1024) to verify that the layout and design adapt correctly across different device sizes.
• :This feature countenance developer to test and debug website in local or development environments without hosting them in a public staging area. This is especially useful for testing in-progress web applications before they are deployed publically.
• : It let developers to simulate different mesh conditions, allowing them to essay how websites execute under slow or unreliable internet connections. This ensures the site remains functional even in less-than-ideal conditions.

Talk to an Expert

Conclusion

Debugging on Chrome can be tricky in some cause, particularly when a bug needs to be traced on a specific handset. The methods explained above will help developers and QAs effectively test and debug site on mobile Chrome without any complex setup. No matter which method you choose, testing on real devices aid read the bottlenecks face under for precise exam results.

Related Guides