Android Apps

Android applications

Manage the application surface of a connected device: discovering what is installed, starting it, stopping it, and opening deep links or settings panes.

When to use

• "What apps are installed?" / "Open WhatsApp" / "Close that game".
• Opening a specific settings screen or a http(s):// deep link.
• Checking a package is present before automating its UI.

Tools used

• apps_list — enumerate installed packages (optionally filtered).
• app_launch — start an app (package or resolved name).
• app_stop — force-stop a running app.
• open_url — resolve and open a deep link (intent://, http(s)://).
• open_settings — open a named settings pane.
• ui_tree / ui_read — confirm what actually came to the foreground.
• shell — fallback inspection (pm list packages, dumpsys filters).

Procedure

1. apps_list (filter by name/package) to locate the target.
2. If launching: use app_launch; prefer the resolved app name over raw package.
3. After launch, ui_tree on a short delay to confirm the launcher has the expected foreground surface.
4. If UI did not settle, screen capture the top window and re-ui_find.
5. Always return the foreground window + launched package as evidence.

Security

• app_launch / app_stop change device state: require confirm=true.
• Only interact with applications the user asked about; do not enumerate or poke apps speculatively.

Related skills

android-ui · android-intents · android-screen · android-control