My Coding Agent Could Render One Android Layout. A Real Screen Needed Activity, Fragment, RecyclerView and Overlays.
My coding agent could already render a single Android XML layout through Robolectric and get back a PNG plus a View Tree with pixel bounds. Then I pointed it at a real screen from a work app, and one layout stopped being enough. A real screen is an Activity shell, a Fragment container, a RecyclerView with data, and states like a loading overlay. Launching the production Fragment would drag in DI,…
The author's coding agent was initially capable of rendering a single Android XML layout using Robolectric and producing a PNG along with a View Tree that included pixel bounds. However, when the agent was pointed at a real screen from a work application, it became clear that a single layout was insufficient. A real screen comprises an Activity shell, a Fragment container, a RecyclerView with data, and states such as a loading overlay.
To launch the production Fragment, additional elements like DI, navigation, and networking are required, along with the rest of the app's runtime. The author sought to create a more narrow focus: a screen real enough for visual checks without running the entire app.
This led to the development of android-ui-renderer-mcp's composed-screen rendering feature, which aimed to achieve visual checks without launching the entire app. The work screen, represented in a demo repository, includes an Activity with a toolbar, Fragment, RecyclerView, master-detail, and loading overlay. All elements are rendered using the app's real UI resources, while runtime state is taken from a deterministic request rather than being run through DI, navigation, or networking.
The renderer utilizes the app's real UI resources but sets explicit runtime state from the deterministic request to avoid becoming an additional way to run the app.
The target structure for the renderer is defined using the activity_fragment tool, which inflates the Activity XML, finds the container, inflates the Fragment XML separately, and inserts it into the container. Parameters such as activityLayout, containerId, fragmentLayout, widthPx, heightPx, densityDpi, and orientation are specified to achieve the desired screen dimensions.
The toolbar title and menu icons are obtained from XML (app:title and app:menu) without any Activity code running. The details on the right are included through the use of an include, populating the layout based on the request parameters.
The author recognizes that the renderer doesn't emulate the Fragment lifecycle; instead, it focuses on capturing the visual result from real resources. Deterministic RecyclerView rows are achieved by incorporating real item layout, orientation, rows, and a fixture per row into the request. Each row is inflated using a temporary adapter, ensuring that the renderer creates a static representation of the UI structure, while the data used is test data under full control.
A loading overlay is treated as another XML layout with its fixture, and a frozen indeterminate ProgressBar is employed to avoid needless nondeterminism during automated visual checks.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
