Build Zoom Virtual Agent

# Android WebView Lifecycle

1. Build intent with URL and policy flags.
2. Configure WebView (`JavaScriptEnabled`, optional multi-window support).
3. Inject user context config before page interaction.
4. Inject bridge script on `zoomCampaignSdk:ready`.
5. Handle callbacks via `@JavascriptInterface`.
6. Route URL actions and handoff payloads.
7. Close view and clean references on exit.


# Android JS Bridge Patterns

## Inject Native Bridge

```kotlin
private fun injectJavaScriptFunction() {
    val js = """
        javascript: window.addEventListener('zoomCampaignSdk:ready', () => {
            if (window.zoomCampaignSdk) {
                window.zoomCampaignSdk.native = {
                    exitHandler: { handle: function() { AndroidExit.handleExit(); } },
                    commonHandler: { handle: function(e) { AndroidCommon.handleCommon(JSON.stringify(e)); } }
                };
            }
        });
    """.trimIndent()
    webView.loadUrl(js)
}
```

## Handoff Relay

```kotlin
private fun injectHandoffFunction() {
    val js = """
        javascript: window.addEventListener('support_handoff', (e) => {
            AndroidHandoff.handleHandoff(JSON.stringify(e.detail));
        });
    """.trimIndent()
    webView.loadUrl(js)
}
```

## URL Governance

- Use `shouldOverrideUrlLoading` for in-app vs system-browser policy.
- Use multi-window callbacks for `target="_blank"` handling.


# Android Reference Map

## Core Docs

- Get started: https://developers.zoom.us/docs/virtual-agent/android/get-started/
- Integration scenarios: https://developers.zoom.us/docs/virtual-agent/android/integration-scenarios/
- JavaScript events: https://developers.zoom.us/docs/virtual-agent/android/javascript-events/
- Resources: https://developers.zoom.us/docs/virtual-agent/android/resources/

## Observed Sample Patterns

- Java and Kotlin implementations follow the same bridge contract.
- Bridge command routing centers around `commonHandler` JSON payloads.
- `support_handoff` events are emitted from JS and consumed in native layer.


---
name: virtual-agent/android
description: "Zoom Virtual Agent Android integration via WebView. Use for Java/Kotlin bridge callbacks, native URL handling, support_handoff relay, and lifecycle-safe embedding."
user-invocable: false
triggers:
  - "virtual agent android"
  - "android webview zva"
  - "zoomCampaignSdk:ready android"
  - "support_handoff android"
  - "javascriptinterface"
---

# Zoom Virtual Agent - Android

Official docs:
- https://developers.zoom.us/docs/virtual-agent/android/

## Quick Links

1. [concepts/webview-lifecycle.md](concepts/webview-lifecycle.md)
2. [examples/js-bridge-patterns.md](examples/js-bridge-patterns.md)
3. [references/android-reference-map.md](references/android-reference-map.md)
4. [troubleshooting/common-issues.md](troubleshooting/common-issues.md)

## Integration Model

- Host campaign URL in Android WebView.
- Inject runtime context (`window.zoomCampaignSdkConfig`).
- Register JavaScript bridge for `exitHandler`, `commonHandler`, `support_handoff`.
- Apply URL policy via `shouldOverrideUrlLoading` and optional multi-window callbacks.

## Hard Guardrails

- Initialize handlers before expecting JS callbacks.
- Treat legacy `openURL` command handling as compatibility path only.
- Prefer DOM links or `window.open` handling plus explicit native routing.

## Chaining

- Product-level patterns: [../SKILL.md](../SKILL.md)
- Contact Center mobile scope: [../../contact-center/android/SKILL.md](../../contact-center/android/SKILL.md)


# Android Common Issues

## Bridge Callback Never Fires

- Ensure JS bridge injection runs after page load and SDK readiness.
- Ensure `addJavascriptInterface` names match injected handler names.

## Link Opens in Wrong Context

- Implement both `shouldOverrideUrlLoading` and multi-window behavior.
- Distinguish `_self` and `_blank` paths explicitly.

## Deprecated `openURL` Path

- Avoid relying on `{"cmd":"openURL"...}` as primary flow.
- Prefer