https://developer.android.com/agents/skills/play/engage-sdk-integration/skill

What problem does it solve?

Integrating the Play Engage SDK can be error-prone because developers must correctly pick vertical-specific entities, build the required cluster requests, and wire WorkManager publishing plus BroadcastReceiver registration in both manifest and runtime.

Core Features & Use Cases

• Vertical + cluster selection: Guides you to identify the correct client, entities, and cluster type/method from the vertical schema files (including TV vs Mobile differences).
• Deterministic code scaffolding: Produces a complete set of required classes (Constants, ItemToEntityConverter, ClusterRequestFactory, EngageWorker, EngagePublisher, EngageBroadcastReceiver) following the expected structure and intent handling rules.
• Correct request + entity mapping: Converts your app’s local models into Engage Entities and builds the appropriate publish requests using the schema-defined request formats.
• WorkManager-based publishing with status handling: Ensures publishing is executed via an EngageWorker with retry behavior and status updates.
• Android manifest + dynamic receiver registration: Ensures both static receiver declarations and required dynamic registration using EngageBroadcastReceiver.register(context).
• Debugging and verification checklist: Provides a structured resolution workflow for Gradle/import/build issues and a final checklist to confirm integration completeness.

Quick Start

Tell me your app’s Engage vertical (for example FOOD or TV), the cluster type you want to publish, and a sample of your local data model so I can generate the required conversion and publishing code structure.