Runtime

Every bug report asks the same first questions: which build, which device, which Android version, how much memory. Runtime is the screen you copy those answers from, so nobody has to go looking in Settings.

Why it is not on the bottom bar

Runtime is reference data you consult occasionally, not a workflow you switch between, so putting it on the bottom bar would spend a permanent slot on something you open once a session.

Instead it sits behind a circular icon button in the top bar, immediately left of the close button, badged with the number of sections it holds. Tapping it opens Runtime as its own full screen.

What it collects

App

Package name, version name and code, build type, target and minimum SDK, first install and last update time, and the process name — which matters more than it sounds in a multi-process app.

Environment

The configured environment name, plus any custom metadata your app supplied.

Device

Model, OS version, CPU ABIs, locale, timezone, 24-hour setting, font scale, dark mode, total and available memory, screen size and density.

Session

Session id, session start time, the number of loaded modules, and any custom session data.

Tap any row to copy its value, or share the whole runtime summary at once — which is usually what you want at the top of a ticket.

Adding your own fields

The sections above are collected automatically, but the details that identify a build inside your organisation are yours: which backend the app is pointed at, which feature-flag cohort the user is in, which internal release train this is.

Supply those through the environment and initial-metadata groups of AppInspectConfiguration and they appear here alongside everything else. See the configuration reference.