DevTools

Debug builds include an on-device performance overlay.

Toggle the overlay

Start the development application:

pam mobile dev .

From another terminal:

pam mobile devtools .

Run the DevTools command again to hide it.

The receiver and overlay are excluded from release builds.

Metrics

The overlay reports:

smoothed frame rate;
decode time;
mount and commit time;
rendered node count;
mutation batch count;
patch versus full commits; and
native heap use.

Use it to identify an expensive interactive path, not as the final benchmark artifact.

Raw Android command

Integrations can send the broadcast directly:

adb shell am broadcast \
  -a dev.pam.nativeapp.action.TOGGLE_DEVTOOLS \
  -p your.application.id.debug

Profiling workflow

pam mobile devtools .
pam mobile profile .
pam mobile benchmark .

DevTools shows live symptoms. The profile and benchmark commands produce repeatable evidence suitable for comparison and CI.

Watch the native buffer count after an update. It must return to zero after the frame finishes; a retained non-zero count indicates an ownership or release bug.

When the development app redraws but buttons stop responding, or the reload port is already occupied, follow the hot reload guide. It includes the single-listener contract and an interaction test after remount.