appfunctions

Android app workflows are made discoverable by transforming app code into executable AppFunctions. This approach exposes features like creating notes or playing media directly to on-device system agents, bypassing fragile UI automation.

Implementing Android AppFunctions requires a targetSdk of at least 36 and a compileSdk of 37 or higher. The implementation uses Kotlin with KSP, requires appfunctions compiler aggregation to be enabled, and enforces AppFunctionContext as the first parameter.

You test and execute registered AppFunctions locally via ADB using JSON-safe commands. These ADB commands list and invoke functions while strictly following the constraints defined in each function's metadata and agent-readable KDoc.

Kotlin KDoc is optimized for on-device agents and MCP by refining it to be agent-readable. This involves structuring the documentation to clearly define workflow constraints and action parameters for system agents discovering the AppFunctions.

The best way to identify high-value app features for AppFunction generation is through workflow discovery. This process analyzes an Android app to find user actions, such as sending messages or playing media, that can be expressed as actionable, agent-executable functions.

Your AppFunction implementation requires an AppFunctionContext parameter to enforce a standard execution environment. mandating it as the first parameter ensures the function correctly interfaces with the on-device system agent infrastructure.