IntelliJ Plugin for Subscription Tools Inside Your IDE
Subscription work rarely stays inside one window. A purchase-flow change can send you to a dashboard for metrics, a terminal for webhook output, and a browser for SDK notes. A published announcement describes an IntelliJ plugin that reduces that switching by placing a set of subscription-platform views and actions in a JetBrains tool window. This guide, based on that announcement, explains what the plugin covers, how the described setup works, and where it still hands you off to the dashboard or browser.
What the plugin puts inside the IDE
According to the announcement, the plugin is a JetBrains Marketplace add-on that connects your subscription-platform project to a side-panel tool window. Its scope is practical rather than exhaustive: it surfaces subscription metrics, purchase and webhook activity, offering details, project setup help, growth milestones, SDK release notes, and recent blog articles.
The announcement says it runs across IntelliJ-based environments, including IntelliJ IDEA, Android Studio, WebStorm, PyCharm, and Fleet, along with more than ten other JetBrains IDEs. That breadth matters for teams that move between an Android project in Android Studio, a cross-platform project in IntelliJ IDEA, and a React Native project in WebStorm.
A useful way to read the feature set is to separate actions that happen in the editor from actions that hand off to a web page:
- Stays in the IDE: viewing dashboard metrics, receiving purchase and lifecycle notifications, scanning offerings and packages, generating dependency and initialization code, setting growth targets, reading SDK release notes, and browsing blog headlines.
- Opens elsewhere: the paywall builder, an offering's full configuration page, and the full text of a blog article.
That split is the main expectation to set before installing. As described, the plugin is a convenience layer over the subscription platform, not a replacement for the dashboard.
Install the plugin and connect your project
The announcement describes a standard JetBrains Marketplace install:
- Open Settings → Plugins → Marketplace.
- Search for the plugin by name.
- Choose Install.
After installation, look for the plugin's tool window on the right sidebar. If it is not visible, enable it through View → Tool Windows. The first meaningful step is entering your API credentials in the settings panel; per the announcement, the metrics view populates once those credentials are accepted. The keys come from your subscription-platform dashboard.
A short pre-flight check helps avoid a blank panel:
- Confirm the plugin is enabled for the IDE you are actually using, not only installed in a different JetBrains product.
- Have the dashboard credentials ready before opening the settings panel.
- Expect the metrics to load after configuration rather than before it.
Metrics: what refreshes and when
The metrics panel mirrors key dashboard figures such as MRR, active subscriptions, active trials, and revenue. It is most useful while you are changing a purchase flow or adding a subscription tier, because you can check the result without leaving the editor.
One behavior is easy to misread: the announcement says the data updates when you press the refresh button or change a configuration. It is not described as a continuously streaming metrics feed. If a number looks stale after a test purchase, refresh before drawing conclusions.
This is also where the plugin's value is clearest. A morning check of subscription health can happen in the same window as the code you are about to edit, and a paywall or tier change can be reviewed against the metrics shortly afterward.
Purchase and webhook notifications
The plugin can listen for subscription-platform webhook events and show notifications for new purchases, renewals, cancellations, billing issues, and other lifecycle events. Notifications include the event type, the product involved, and related details.
Setup has more moving parts than the metrics panel:
- Configure webhook integration in the subscription-platform dashboard.
- Install ngrok following the plugin's guide.
- Let the plugin's lightweight local server receive events.
- Send a test event from the dashboard via Integrations → Webhooks → Send test event.
Once configured, the announcement says the listener starts automatically when the IDE restarts.
Worked example. Suppose you are testing a monthly plan in a sandbox account. You complete a purchase in the running app. Within seconds, the IDE notification should show a purchase event naming that product. If nothing appears, the failure is usually upstream of your purchase code: the webhook may not be configured, ngrok may not be running, or the local listener may not have started. Checking those three points first is faster than adding logging to the app.
This feedback loop is most valuable during development and testing, when confirming that a sandbox transaction completed would otherwise mean opening the dashboard or reading logs.
Offerings, packages, and paywall handoff
The offerings view lists each offering with its packages, display names, identifiers, status, and paywall configuration. An offering marked as current carries a badge showing which one the app serves by default.
The action buttons behave differently, and the difference is worth knowing before you click:
- Paywall appears when an offering already has a paywall and opens that offering's paywall tab in your browser.
- Add Paywall appears when no paywall exists; it creates one and opens the paywall builder so customization can begin.
- Manage jumps to the offering's configuration page in the subscription-platform dashboard for package changes, metadata edits, or advanced settings.
In other words, the plugin gives you a fast catalog scan and a direct route to editing, but the editing itself happens in the platform's web tools. The plugin covers part of the paywall workflow rather than the whole builder.
The integration wizard for new projects
Setting up the subscription platform in a fresh project normally means adding dependencies, configuring the SDK, defining entitlements, and wiring paywalls, with different requirements per platform. The wizard condenses that into a guided flow.
It supports Android, Kotlin Multiplatform, and Flutter projects. It detects the project type and generates dependency configuration for the relevant build system, whether Gradle or pub.yaml, using the latest SDK version. It also proposes initialization code suited to the platform.
You choose between two paths:
- SDK-only: core subscription-platform functionality for fetching offerings and processing purchases.
- Full paywall integration: adds the platform's UI components and generates code to render paywalls that you customize in the dashboard.
The wizard is a starting point, not a finished integration. Review the generated code against your app's architecture before committing it, particularly the initialization step and any entitlement assumptions.
Milestones as visible targets
You can define targets for MRR, active subscriptions, active trials, new customers, or total revenue. The plugin tracks progress against each target and shows where you currently stand, with a celebration when a milestone is reached.
The practical benefit is proximity: a subscriber goal sits beside the code that is meant to move it. A target that is 80% complete is a more concrete prompt than an abstract growth plan stored in a separate document. Treat milestones as motivational markers rather than as a substitute for deeper revenue analysis.
SDK release notes and blog updates
The plugin pulls release notes from the platform's GitHub repositories into a dialog. Releases are shown for the Android, iOS, Kotlin Multiplatform, Flutter, and React Native SDKs, each with a version number, publication date, and full notes. That makes it possible to judge whether an update affects your project without opening GitHub.
Notifications for new SDK versions are opt-in per platform. An Android-only team can follow just the Android SDK; a cross-platform team can enable several. When a release arrives, the notification includes the version and a link to the full notes.
The blog view works similarly: recent articles appear with title, date, and a short description, and clicking one opens the full article in a browser. Article notifications can also be enabled, so new posts arrive as IDE alerts with a title and a read-more link.
Is it a good fit for your workflow?
The plugin suits developers who already use a JetBrains IDE and want subscription context close to their code. It is less useful if your team works mainly in editors outside the JetBrains family, or if your process already centralizes subscription operations in the dashboard.
A quick fit check:
- You will benefit if you check metrics often during feature work, test purchase flows in sandbox, or want SDK release awareness without watching GitHub.
- You may not need it if you rarely touch subscription configuration, or if webhook testing already runs through a dedicated backend environment.
- Plan for the handoffs: paywall editing, offering configuration, and full article reading still happen in the browser.
- Budget setup time for webhooks: the local listener depends on ngrok and dashboard configuration, so it is not a zero-configuration feature.
Frequently asked questions
Which IDEs does the plugin target?
The announcement says it is built for the JetBrains family, including IntelliJ IDEA, Android Studio, WebStorm, PyCharm, and Fleet, plus more than ten other IntelliJ-based IDEs.
What is required before webhook notifications work?
Per the announcement, you need webhook integration configured in the subscription-platform dashboard, ngrok installed following the plugin guide, and the plugin's local listener running. The listener starts automatically when the IDE restarts after setup.
Do the metrics update automatically?
The announcement describes them refreshing when you click the refresh button or change a configuration. Treat the panel as an on-demand view rather than a live stream.
Can I edit a paywall inside the IDE?
No. The plugin opens the paywall tab or the paywall builder in your browser, and the Manage button takes you to the offering's configuration page in the dashboard. Editing happens in the platform's web tools.
Which platforms does the integration wizard cover?
Android, Kotlin Multiplatform, and Flutter. It detects the project type and generates dependency and initialization code for the matching build system.