Skip to main content

Debug Your Mobile Website Using Chrome

[PLACEHOLDER]
Image


Introduction
Recently I worked on a redesign of one of my client’s mobile website.  One of the key challenges I encountered was to test the new features of the mobile-only website on the emulators.  This is because there are some new features which is hard to test without an actual device.
Therefore I decided to  debug the mobile site by using an actual device connected to a laptop and using Chrome as the tool for it. But I encountered new challenges. One of them being the device not getting recognized for debugging and not even showing in the Windows Device Manager.
In this article we are focusing on the Android side of things. I used the following tools:
  • A PC laptop (with window 7 and above)
  • An Android phone. (I used a Samsung Galaxy S5 Neo)
  • Browser: Chrome

Clarification note:
This is not a step by step article for debugging the apps as you can find that in the reference provided here. This article is my personal experience when going through the debugging exercise, items that you might not find in the reference links, so please consider this as an extended documentation that might help your website and it’s new features.

Before starting:
  1. You might find some trouble when you are connecting your smartphone as it may not get recognized by your PC. For that reason I placed this link in the  reference section at the end of this article.
  2. If you are looking for documentation on debugging using your device I strongly advise you to follow the guidelines in here under the reference section.

Here are the lessons learned based on what happened during the debugging:
1. Make sure you have the right cable as not all cables can be used for debugging. As I tried to debug the mobile website with the Android device, the computer was unable to recognize the smart phone. This was after installing the USB drivers that I downloaded. The smart phone was charging as it was connected, and the laptop was flagging that device as connected, but I was unable to use the device for instance I wasn’t able to access the media files in it or see it in the Device Manager from Windows. Therefore I decided to change my cable and BOOM! - It worked.
2. Sometimes you may need to get the the latest Chrome browser. Or others may recommend getting the Chrome Canary version which is a different from what you would normally install. Canary is a one of the different releases Chrome may have in their roadmap with features that are still not in the current production release however it is not well tested.

3. I don’t want to repeat the wheel or take credit for a well documented process. So I would advice you to follow the android instructions: https://developer.chrome.com/devtools/docs/remote-debugging
3b. If you are debugging then in order to make your life easier, chances are you will need it eventually, so download the Android Studio and the SDK at:
https://developer.android.com/studio/index.html  Follow instructions and install.
4. Go to your Device Manager and make sure the device is appearing in:
1. Modems. ex Samsung Mobile USB Modem as shown below
2. as it's own device: Samsung Android Phone
3. inside Universal Serial Bus Controllers. Ex. Samsung mobile USB Composite Device. See image above.

Note: if you cannot see your device as a media to transfer files, something is definitely wrong. So go back to item list 1 and 4, until you get it working. Perhaps getting the correct driver, if Microsoft updates do not work for you when you connect the device. Be patient, Microsoft screen will take a while to get the drivers (from 1 mins to 5 mins., but eventually believe that something is happening. If it takes longer than that cancel and repeat. If repeating does not work, then download the drivers and install. And then retry the steps again).

5. Once your device is recognized by your laptop then you are on the right track.
Make sure you follow the android steps for debugging. Specially turning your device developer mode and USB debugging:
At this point then open the explorer. Look for the Android folder, normally in the program files folder. Then go to sdk > platform-tools folder. You will find the adb.exe. Do the following:
5.1) copy the location path
5.2) load powershell or cmd
5.3) CD [location path copied]
5.4) run command “adb start-server” .
If your phone is connected it should prompt the screen of "Allow USB debugging" with the computer RSA key fingerprint (the same that you would see at the "Discovering devices in chrome" section in this link).

6. Now if you go to chrome://inspect/#devices on your chrome PC you should see the device if "Discover USB devices" is selected as shown below.
Screen when no devices found
In this example I’m loading google.ca on the phones browsers. At this point I’m able to inspect it using Chrome Developer Tools:
Screen when devices found

Final notes:
When you are done debugging and you would like things the way they are then:
  1. Go to the command prompt (or to powershell) and run the command “adb kill-server”. When you do this, if you go to the chrome inspect devices you will no longer see the mobile device.
  2. Finally go to your device and turn off:
    1. USB debugging
    2. Developer option off as well
References:
Install USB Drivers:

Remote debugging:
Device mode and mobile emulation:

Dev tools:

Trending posts

Steer for a talent transformation strategy (and avoiding AI fatigue)

 There was a debate on whether to feature the term “AI” in the title of this article. Honestly, a key motivation for pursuing the research that led to this post was sparked by the widespread excitement about AI appearing constantly in our LinkedIn feed, to the point of feeling the fatigue, and even a bit disappointed in the algorithm of this, and the others, social media and content curated apps.  We soon discovered that there is an entire concept called "AI fatigue", not exactly how we were feeling it, but more about the mixed emotions people in the workforce have regarding the use of AI tools. Photo by Mart Production via Pexels (background updated with AI and Adobe  tech) From micro blog posts to video podcasts, lately, most of the tech content we encounter revolves around AI. They often sound or read very similar, usually mentioning the same few top providers. The articles (and social posts... at least the popular ones with paid-campaigns behind it) tend to focus less...
Read more

Reimagining Digital Experience Management: How Agentic AI is Transforming Adobe Experience Manager

 Adobe Experience Manager (AEM) has introduced powerful new Agentic AI capabilities designed to continuously improve and adapt digital experiences at the speed of AI. By integrating advanced AI orchestrators through Agent-to-Agent (A2A) and Model Control Protocol (MCP) tools, AEM enables brands to automate complex workflows and enforce compliance seamlessly across enterprise ecosystems. Through a suite of specialized agents, teams can transition from manual, weeks-long processes into fast, AI-assisted workflows powered by simple natural language prompts. Photo by Tunahan KALAYCI via Pexels   Here is a breakdown of the key agents driving AEM’s new Agentic capabilities, their value propositions, their guardrails, and their current availability status. 1. Brand Experience Agent. Overview. The Brand Experience Agent accelerates digital modernization through specialized sub-agents—the Experience Modernization Agent, Experience Production Agent, and Experience Development Agent. Tog...
Read more

Designing Habit Forming Mobile Application

Anonymous
Mobile Applications have become an integral part of our daily lives - we use mobile apps as alarm clocks to wake us up in the morning, to create to do lists when we start our day, to communicate with our colleagues at work via apps like Skype. We even check reviews of restaurants to visit on apps like Yelp and we seek entertainment on apps like Netflix and spotify. So what drives us to use these apps so seamlessly in our daily lives? Why we prefer some apps over others? Is there a science behind designing successful mobile apps like Facebook?  Photo by Peter C from Pexels A study in US revealed that a user between the age of 18 and 44 visits the Facebook app on average 14 times a day [1]. This shows that using the Facebook app is a daily routine for many of its users. This makes Facebook a great example of a habit forming mobile app which is designed with human psychology in mind that encourages habit forming behavior in its users .   I recently attended a seminar ...
Read more

Building MCP with TypeScript

MCP servers are popular these days. We’ve been researching and exploring a few code repos, some where missing modularity, others just not having pieces that we were looking for… therefore we decided to build our own, simple and foundational that could be a starting point for those trying to solve for the similar things we were… and we decided to share it with the community, via our public github. MCP host, server,data sources     Before we start.  Using Typescript and NodeJS was one of our requirements. This proved somewhat challenging because I don't code as frequently these days due to my leadership responsibilities, and I typically prefer working with C# or Python. Colleagues in my tech community have been working with their teams on some of their MCPs going the Python route. Therefore, I said, “I guess we are trying the other route” 😊. One of our reasons to go with TypeScript was due to the need of the integration with APIs, and based on the research, it seems t...
Read more

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed