Android Emulator Automation

When To Use

• Use this skill when the request is about: android emulator automation, adb semantic ui automation, uiautomator dump and tap.
• Primary outcome: Use semantic ADB and UIAutomator workflows to inspect, launch, and interact with Android apps from agents.
• Reach for this skill when an agent needs to launch an APK, inspect the current screen, or perform a deterministic interaction without writing Espresso or Compose UI tests.
• Handoff skills when the scope expands:
• android-testing-ui
• android-permissions-activity-results

Workflow

1. Verify the Android SDK, adb, the target device or emulator, and boot completion before attempting interaction.
2. Install or launch the target app with explicit package awareness so the request stays tied to the right artifact.
3. Dump the current UI hierarchy and prefer semantic selectors such as text, content description, or resource ID over raw coordinates.
4. Perform the smallest interaction that proves the workflow and re-dump the screen when state changes matter.
5. Hand off long-lived regression coverage to UI tests once the automation path is understood.

Guardrails

• Prefer semantic selectors to pixel coordinates; only fall back to coordinates when the UI tree is missing the required metadata.
• Treat automation as an inspection and smoke tool, not a replacement for deterministic UI tests.