Developer Guides
Legacy integration: How to Build In-App AI Guidance for Android
Legacy Android registry-based SDK reference for existing applications. The new Aven Mobile Android Views integration is in development.
Published Aug 17, 2026 · Aven Team
The practical problem
This article describes a legacy SDK and does not apply to the new Aven Mobile integration. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
How to approach it
The Android SDK is published as com.avenappagent:aven-android and uses explicit page and element registration. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
Implementation considerations
Attach the assistant on the active screen and update the current page under application control. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
Tradeoffs to keep in view
This article describes a legacy SDK and does not apply to the new Aven Mobile integration. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
Where Aven fits
The Android SDK is published as com.avenappagent:aven-android and uses explicit page and element registration. Teams should begin with a narrow and observable task, describe the user goal and product state, then test the supported next step with real permissions, loading states, and interruptions. This keeps guidance useful without making unsupported assumptions about the interface.
Build this with Aven
Aven uses developer-registered pages, elements, and workflows. The host application owns navigation, target readiness, and completion.