skills.rest
fornewid
fornewidCOMMUNITY
Explore all skills by this author →
𝕏@fornewidGitHub

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

Generate Android components for Play Engage SDK integration with WorkManager and BroadcastReceiver registration.

5|Updated Feb 22, 2026
Search Tags:#android#entity mapping#workmanager#play engage#broadcastreceiver#gradle integration#tv vs mobile
One-click install
npx skills add https://github.com/fornewid/android-developers-changelog --skill https-developer-android-com-agents-skills-play-engage-sdk-integration-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: https://developer.android.com/agents/skills/play/engage-sdk-integration/skill
Source: https://github.com/fornewid/android-developers-changelog/tree/main/docs/agents/skills/play/engage-sdk-integration
Command: npx skills add https://github.com/fornewid/android-developers-changelog --skill https-developer-android-com-agents-skills-play-engage-sdk-integration-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about https://developer.android.com/agents/skills/play/engage-sdk-integration/skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate the Play Engage SDK to publish app content clusters on Android?▼

To integrate the Play Engage SDK, you map local data models to Engage entities, build cluster publish requests, and wire WorkManager execution with BroadcastReceiver registration. This ensures reliable content publishing for Mobile or TV apps.

What's the best way to handle Play Engage one-time and periodic publishing?▼

The best way to handle Play Engage publishing is using a WorkManager worker. It orchestrates both one-time and periodic publish requests, manages retry behavior, and sends publish status updates to ensure reliable data delivery.

Why does Play Engage require both static and dynamic BroadcastReceiver registration?▼

Play Engage requires dual BroadcastReceiver registration to ensure reliable publishing triggers. You must declare the receiver statically in AndroidManifest.xml and dynamically register it at runtime via EngageBroadcastReceiver.register(context) to handle publish intents correctly.

Does Play Engage SDK integration differ between Android TV and Mobile apps?▼

Play Engage SDK integration differs for Android TV vs Mobile apps based on the selected vertical. You must select the correct vertical schema, which determines the specific client, entities, and cluster types required for your target platform.

How do I convert my app's local data models into Play Engage entities?▼

You convert local data models into Play Engage entities using an ItemToEntityConverter. This component maps your app's local models to the correct Engage Entities defined by the vertical schema, ensuring compliance with the required integration structure.

What components do I need to scaffold for a complete Play Engage integration?▼

A complete Play Engage integration requires scaffolding Constants, ItemToEntityConverter, ClusterRequestFactory, EngageWorker, EngagePublisher, and EngageBroadcastReceiver classes. These components handle entity mapping, request construction, and WorkManager-based publishing orchestration.

Related Skills

Explore More Software Engineering Skills→
jhparktimejhparktime
1

android-testing

Configure Gradle for Android unit, integration, and screenshot tests.

Community
Advanced
yash-gargyash-garg

engage-sdk-integration

Integrate Play Engage SDK into Android apps with Gradle and manifest guidance.

Community
Advanced
PL-Coding-GmbHPL-Coding-GmbH
6

android-background

Implement WorkManager background tasks and foreground services in Android apps.

Official
Advanced
TMHSDigitalTMHSDigital
2

mobile-background-tasks

Schedule and manage background tasks for React Native, Expo, and Flutter apps.

Community
Advanced