The following is the first few sections of a chapter from The Busy Coder's Guide to Android Development, plus headings for the remaining major sections, to give you an idea about the content of the chapter.


Stetho

In 2015, Facebook announced Stetho, “a new debugging platform for Android”. That description is more apt than you might think, in that Stetho allows you to examine your view hierarchy, see network requests, and otherwise analyze your project… using Chrome.

Wait, Wut? Chrome?

Many modern Web browsers have Web client debugging tools, either built into the browser itself or available as an extension or other add-on. These tools can let you browse the content of the Web page, see network requests, and otherwise analyze the content of a browser tab.

Stetho leverages the Chrome Developer Tools, available in Chrome and Chromium, to have those tools examine an Android app, rather than a browser tab.

This works by way of Chrome Developer Tools’ support for remote debugging. Stetho basically embeds a small server in your app that speaks the same protocol that Chrome Developer Tools uses for remote debugging. From Chrome’s perspective, your Android app is just another Web browser. In reality, Stetho translates Chrome Developer Tools’ requests (e.g., “give me your DOM”) into things that would help an Android developer (e.g., “give me your view hierarchy”).

Basic Stetho Integration

The preview of this section is [REDACTED].

Connecting Chrome to Your App

The preview of this section will not appear here for a while, due to a time machine mishap.

What You Get In Chrome Dev Tools

The preview of this section was fed to a gremlin, after midnight.

Getting Help with Stetho

The preview of this section was fed to a gremlin, after midnight.

Hey, What About Sonar?

The preview of this section is sleeping in.