engage-sdk-integration

This skill guides you through integrating the Play Engage SDK into an Android app. It ensures that the code follows the mandatory structure and uses the required Engage entities for each vertical.

Workflow

Follow these steps to assist the developer:

1. Identify vertical and cluster:

   • Ask the developer which vertical their app belongs to based on references/schemas/.
   • Check if the integration is for TV or mobile. If the integration is for TV, read the TV-specific sections in patterns.md as well.
   • Use {VERTICAL}.md in the references/schemas/ directory to identify the corresponding Engage entities and the client class name. The client field in the JSON provides the full class name. For example, com.google.android.engage.food.service.AppEngageFoodClient.
   • Note: Initializing the client class requires a Context parameter. For example, AppEngageFoodClient(context).
   • Always refer to common.md for common entities.
   • Ask which cluster type they want to publish from the supported cluster types for that vertical.
   • Find the method to call from {VERTICAL}.md in the references/schemas/ directory for the specified cluster. Each method will specify the request it expects.
   • Get the request structure from requests.md and clusters from clusters.md. Then suggest and use sources to fill the fields in the request structure correctly, along with the required entities and clusters.

2. Generate structured boilerplate code:

   • Create a new directory for all Engage-related code. Name the directory to match the naming convention of the existing codebase.
   • Generate the following classes using templates in patterns.md:
     • Constants: holds constant values such as attempt counts and publish types.
     • ItemToEntityConverter: converts the app's local models to Engage's Entity models.
     • ClusterRequestFactory: constructs the publish requests.
     • EngageWorker: handles the actual publishing and publish errors using WorkManager.
     • EngagePublisher: orchestrates periodic and one-time jobs.
     • EngageBroadcastReceiver: listens for AppEngageService intents and starts a one-time publish job from EngagePublisher. Important : Implement both static registration and dynamic registration patterns, including the companion object register method inside the EngageBroadcastReceiver class.

3. Suggest entity mapping:

   • Ask the developer to provide their local model schema (for example, a data class or a JSON snippet).
   • If they haven't provided one, share entities from {VERTICAL}.md in the references/schemas/ directory as a guide.
   • Once the local model is identified, suggest a mapping to the corresponding Engage entity.
   • Generate the conversion logic using the ItemToEntityConverter pattern in patterns.md and add it to the generated {ENGAGE_CODE_DIR}/ItemToEntityConverter.

4. Suggest data source:

   • Ask the developer to provide the source of actual data you'll publish.
   • Once you identify the data source, use it to fetch the data in the app's local model schema.
   • Use {ENGAGE_CODE_DIR}/ItemToEntityConverter to convert this data to an Engage entity.
   • Use obtained Engage entity model data with {ENGAGE_CODE_DIR}/ ClusterRequestFactory to get cluster requests.
   • Call corresponding cluster publishing method obtained from {VERTICAL}.md in the references/schemas/ directory with the obtained request in previous step in {ENGAGE_CODE_DIR}/EngageWorker.

5. Gradle and manifest updates:

   • Suggest updates to build.gradle and AndroidManifest.xml.
   • For mobile apps, use patterns.md.
   • For TV apps, use the TV-specific sections in patterns.md.
   • Provide the necessary implementation dependencies for build.gradle or build.gradle.kts from patterns.md.
   • Provide the <receiver> and <service> declarations for AndroidManifest.xml.
   • Note: Except for TV, there aren't any vertical-specific imports. For all other verticals, com.google.android.engage:engage-core:1.6.0 is sufficient.

6. Debugging and verification: