engage-sdk-integration

What problem does it solve?

Integrating the Play Engage SDK into an Android app is error-prone because it requires strict entity/cluster structure, correct Gradle/manifest wiring, and careful broadcast + WorkManager publishing flow.

Core Features & Use Cases

• Vertical & cluster-aligned integration: Guides you to select the correct vertical, entities, and client class, then map your local models to the required Engage entities and request payloads.
• Boilerplate code generation patterns: Produces the recommended integration building blocks (Constants, converters, request factory, WorkManager worker/publisher, and a BroadcastReceiver).
• Publishing flow correctness & debugging: Includes step-by-step Gradle/manifest updates and an explicit debugging/retry mindset, including recoverable vs non-recoverable publish errors.
• Critical registration guidance: Stresses that both static <receiver> registration and dynamic EngageBroadcastReceiver.register(context) are required for reliable intent handling.

Quick Start

Use the engage-sdk-integration skill to generate the required Play Engage integration skeleton for your app, including WorkManager publishing and an EngageBroadcastReceiver that is both statically declared and dynamically registered in your Application.