What problem does it solve?
Play Engage SDK integrations often fail or partially work because developers miss mandatory setup steps, use the wrong vertical-specific entities, or publish malformed requests. This causes publish errors, missing content on surfaces, and debugging time sink across Gradle, manifests, and data mapping.
Core Features & Use Cases
- Vertical & cluster discovery: Identifies the correct Engage client, entities, and publish method by using the vertical schema and common entity definitions.
- Structured boilerplate generation: Creates the full Android publishing workflow including constants, entity converters, request factory, WorkManager worker, publisher orchestrator, and a BroadcastReceiver with both static and dynamic registration.
- Entity mapping & request construction: Maps developer-local models to Engage entity models, then builds cluster requests and publishes them through the correct Engage client APIs.
- Gradle and manifest hardening: Recommends required dependencies and AndroidManifest declarations needed for publishing and receiving publish triggers.
- Deterministic debugging workflow: Guides error resolution order (imports first, then compilation, then successful Gradle build) and provides a developer checklist to verify integration completeness.
Quick Start
Use the engage-sdk-integration skill to integrate the Play Engage SDK for your Android vertical by providing your vertical type, cluster type you want to publish from, and the local data model you want to convert into Engage entities.
