Google·DX

Layout Inspector 2.0

Giving Android developers a live, hierarchical view of their UI at runtime.

Lead UX Designer · May 2020

Layout Inspector 2.0

The original Layout Inspector in Android Studio was full of friction: it took over the full screen, showed post-rendered pixel data instead of developer-coded attributes, and didn't map 1:1 with the Layout Editor. Developers were bouncing in and out of the tool constantly just to complete simple debug tasks.

As Lead UX Designer I redesigned the inspector end to end. The new version introduced a docked tool window, a live attributes panel tied directly to XML, a streamlined flow connecting the inspector to the emulator, and a 3D modeler for surfacing layering issues invisible in 2D. Shipped to Canary early 2020, stable May 2020.

Before

Original Layout Inspector — full-screen takeover with pixel data

After

New Layout Inspector — docked tool window with attribute panel

Key Problems

Inspector didn't map 1:1 with the Layout Editor, causing constant context switching
Showed pixel-based data instead of DP and XML attributes developers actually work in
Full-screen takeover made it impossible to run alongside code or the emulator
Low discoverability meant the tool went unused despite existing in the IDE
Lagging behind Xcode and Chrome DevTools in core inspection capabilities

The Solution

Three major changes drove the redesign: docking the inspector as a tool window so it could run side by side with code, replacing pixel metadata with the actual XML layout attributes developers wrote, and connecting the inspector directly to the live emulator for real-time iteration without redeployment.

Tool window — inspector docked next to emulator
Tool window — inspector alongside code
3D modeler — layer separation view
3D modeler — full hierarchy

The 3D modeler was an entirely new capability, letting developers view their app in 3D space to find layering and alignment issues that are invisible in a flat 2D view. Users can drag into 3D, toggle views, inspect hierarchy, and click nested elements directly.

Outcomes

Shipped to Canary early 2020, stable release May 2020 in Android Studio 4.0
Received organic community coverage on Reddit and Medium from Canary users highlighting the improved debugging workflow
Positive reception validated the core thesis: making the tool speak the developer's language, not the device's, was the right call
© 2026 Carl ThomasBuilt with Claude Code & Next.js