YOUR FIRST COMPONENT
Choose. Inspect.
Make it part of your app.
Start with a Google API integration, generate a separate Kotlin or Java component, then connect its initialization and callbacks to your existing Android app.
Check your setup.
Use Android Studio or IntelliJ IDEA based on IntelliJ Platform build 261 or newer, and open your Android Gradle project. The current package has passed compatibility verification against IDEA and Android Studio 261; an open-ended build range does not mean every future IDE has already been tested.
Browsing the local templates does not require a Google account, OAuth token or service-account key. Configuring Google Play or Firebase for the Android app is a separate step.
The 0.1.9 package is for publisher-authorized development testing and is marked as not for commercial distribution. Commercial builds require a registered product configuration and Marketplace licensing. The planned product is paid and closed source, with no trial; this public guide is available to read before purchase. See licensing and availability.
Find the puzzle button.
If you have a developer-provided package, choose Settings → Plugins → gear menu → Install Plugin from Disk…, select the ZIP and restart if prompted. This local installation is a development workflow, not the final purchase or activation process.
Open Tools → GooglePlay API, or select the puzzle button in the tool-window bar. On a fresh New UI layout it appears in the lower-left group and opens a bottom-docked panel. Existing saved positions are respected; use the IDE’s Move to → Bottom action to reposition it.
Read the code before generating.
Choose an integration from Components. The preview includes Code, Initialize and Setup. Switch between Kotlin and Java; for In-app updates, choose Flexible or Immediate in the Update mode control.
- Code shows the reusable component.
- Initialize shows calls and lifecycle hooks to merge into your app.
- Setup describes dependencies, prerequisites and official sources.
The Official docs link opens the SDK documentation in your browser. Preview can be used outside Android projects; writing files requires a detected Android module.
Give the component a home.
Choose Generate…, select the target module and language, then choose your component package and class name. A blank package uses the module namespace plus .googleplay, with the application ID as a fallback.
Optionally generate a separate Activity or Application example. The existing entry-class field customizes instructions; it does not insert code into that class or replace your launcher.
app/
├─ src/main/kotlin/com/example/app/googleplay/
│ ├─ RatingComponent.kt
│ └─ examples/RatingComponentExampleActivity.kt (optional)
├─ docs/googleplay-api/play.in-app-review/README.md
└─ build.gradle.kts (when direct dependency merging is supported)Java output uses the Java source directory. Groovy builds, aliases and version catalogs receive dependency merge guidance rather than a complete automated migration.
Review each planned file.
Save relevant editor files and commit or back up your project. Under Changes, inspect the proposed source, existing content and Gradle changes before choosing Apply Changes. Different existing files trigger a conflict; selecting another update mode does not migrate a customized component.
Apply stops if an affected editor document has unsaved changes: save it and regenerate the preview. Apply and restoration register IDE Undo/Redo actions. Rollback checks all affected files first and refuses to overwrite later changes; linked output paths are rejected. Keep version control or backups for long-term recovery.
After Apply, the generated component opens in the editor. Read its integration guide alongside the resulting project diff.
Finish the integration in your app.
- Merge initialization, callbacks and cleanup into your existing Activity or Application.
- Keep current Manifest registrations and custom superclasses. Register a new example component only if you choose to use it.
- Merge dependency/plugin declarations using your project’s existing version owner, then sync Gradle.
- Complete service configuration and backend work, then test the runtime flow.
The generated components can be called from Views or Compose event handlers. They do not generate a complete app screen or automatically connect to your ViewModel or dependency-injection setup.
The Checks tab performs basic local project checks. It does not validate Play Console setup, backend security, Firebase report delivery or full release compliance.
A few things worth checking.
No Android module is available.
Open the Android project root and verify that its Android Gradle configuration can be detected. You can still inspect the templates without selecting a module.
Generated imports are unresolved.
Merge the generated dependency guidance and sync Gradle. Check repository declarations and keep a single version owner instead of adding literal versions alongside a catalog or root declaration.
The component already exists.
Compare the existing class with the proposed file. Preserve your customization or generate with another package/class name. Switching a mode is not an overwrite or migration command.
The review or update flow does not appear.
Google Play controls availability, eligibility and quotas. Follow each integration’s official test setup rather than treating a local debug APK as proof of the Play runtime experience.
Need the details for a particular API?
Explore the integration guides →