paldom/mobile-app-inspector
GitHubGet the app on a device
Hand it a Play Store link and it works out the package, checks whether the emulator can actually install anything, and gets the app running — or names exactly which wall you hit.
Drive it and take it apart
The agent-shaped loop: a screen becomes a dozen numbered rows instead of 24KB of XML, taps target text rather than pixels, and assertions fail loudly with what was really on screen.
Review the whole app
Point it at a Play link and get a bounded, evidence-backed report — every finding tied to a screenshot, every skipped area named, and the app's own on-screen text treated as data rather than instructions.
Show it, don't tell it
Record the app driving itself and burn explanation cards straight into the MP4 — because you cannot overlay a third-party Android app, the captions are stamped live and composited afterwards.
What the store and the wire say
Read an app's public Play listing — rating, reviews, installs, changelog — and capture which servers it actually contacts, all without owning the app or rooting the device.
Is the UI any good
A UX/UI heuristic audit: it measures touch targets and screen-reader-invisible controls from the accessibility tree, judges the twelve usability categories against fixed thresholds, and scores findings by severity — no laundered overall grade. Then it runs the same app at 320dp, on a tablet, in landscape and at 200% text, and takes the camera, network and permissions away to see what it does without them.