Android architecture and platform decisions: where state lives, what survives process death, what work leaves the main thread, and what…
Use to find stuck coroutines, leaked jobs, and suspended awaits with no resumer — the concurrency bugs that don't crash but cause hangs…
Persistence and offline behaviour: where a value lives, what survives, transactions, migrations, and what happens when the network does…
The object graph: what lives how long, what may depend on what, and when a wiring mistake is discovered.
Images that arrive at runtime, fetched or picked or decoded: caching, sizing, cancellation, and what a picker actually hands back.
Java on Android without the language features Kotlin has: threading, equality, resource handling, and interoperating with Kotlin.
The shape of the layer graph: which layers exist, which way dependencies point, and what each one may touch.
Talking to a server: client configuration, what comes back, what happens when it does not, and how a request is authorised.
Runtime permissions: whether to ask at all, how to ask, and what the app does with every answer including the silent ones.
Material Design 3 and Android platform guidelines.
Use to flip framework-level diagnostics without code changes — verbose framework logging (`log.tag.<Tag> VERBOSE`), view-bounds overlay…
Keeping a secret on a device you do not control: key storage, backup, intents, and client-side checks that are signals rather than controls.
What makes a test able to fail for the right reason: the shape of the seam, the scheduler it runs on, and what an assertion is allowed to…
Use to answer questions logging can't — "did this run, on what thread, for how long, in what overlap with frame boundaries?" Wrap suspect…
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
The View system: layouts, adapters, RecyclerView, ViewBinding, and the seam where a ComposeView sits inside a View hierarchy.
Build, compose, or style any Spiderly Angular admin-panel UI — pages, cards, panels, dashboards, buttons, tables, dialogs, empty/loading…
Global Angular best practices: component lifecycle, clean code, lazy loading with permissions, and *ngFor trackBy performance.
Debug complex Claude API issues including context window overflow,
Build Claude tool use (function calling) workflows with the Messages