Subscription Platform Launch Party Recap: What Shipped and What's Next
A subscription platform's first Launch Party brought together a broad set of product updates for subscription app teams. This recap organizes the announcements by area, separates what was demonstrated at the event from what was announced but not shown, and explains what each change means in practice. The event took place in December 2023, so treat availability details as a dated reference and check current documentation before relying on any specific feature.
Mobile dashboard and PWA improvements
The dashboard had supported progressive web app behavior for some time. On iPhone, you could add the dashboard to your home screen from Safari using the share menu, which made the mobile web experience behave more like a native app. The Launch Party introduced several refinements:
- A refresh button appeared in the top menu on iOS, and the menu itself was improved across the regular mobile site as well.
- All Charts became usable on mobile, matching the desktop experience.
- Push notifications entered a limited preview. Users could subscribe on their phone to subscription events and choose which event types triggered an alert. Tapping a notification opened the relevant dashboard area. This feature was not yet publicly available; interested users could sign up for a preview and share feedback.
In response to an audience question, the team confirmed that push notifications would cover in-app purchases as well, displaying the same subscription events already sent through Slack or Discord integrations.
Weekly Performance Summaries
Weekly Performance Summaries was a new feature designed to deliver key subscription metrics by email every Monday morning, reducing the need to open the dashboard just to check on app health. Each summary answered three questions:
- How did a given metric perform over the last seven days?
- How did it change compared with the prior seven days?
- Where can I click through to see the overview and Charts for deeper analysis?
The feature was available to everyone through the Labs area of Account Settings, where users could select which Projects to include. When asked whether summaries could be pushed to destinations like Slack, the team said not yet, but that it was under consideration for the future, particularly after feedback on the initial email version.
Server-side developer experience
Several updates targeted teams integrating the platform from their own backend:
- REST API v2 for app management. Apps could be created and modified through the API, enabling remote control and automation without touching the dashboard.
- Overview metrics via API. All metrics shown on the Overview page became available through REST API v2, including the time each metric was last updated. This gave teams more flexibility to build custom dashboards.
- External purchases API (private beta). Because the platform could not natively support every payment platform, an external purchases API allowed subscription data from third-party sources to be sent in. For example, PayPal subscriptions could grant entitlements and appear in dashboards and Charts alongside other revenue. The feature was in private beta, with interested teams invited to get in touch.
- Webhook flexibility. Projects could have up to five webhook URLs, up from one. Webhooks could be filtered by app or environment (production or sandbox) and by event type, so teams only received events they cared about, such as new purchases or renewals. A new event type, SUBSCRIPTION_EXTENDED, could be sent whenever a subscription was extended, for example through the Google or Apple backends.
Apple Offers and pricing analytics
iOS supports three offer types: introductory offers, promotional offers, and offer codes. The platform used StoreKit 2 API endpoints on the backend to improve pricing accuracy for offers and expand offer analytics:
- The customer event page began showing an offer's pricing information alongside the offer code reference name. This data could also flow to other integrations, such as webhooks.
- A new Scheduled Data Exports template included offer and offer_type fields by default.
- Charts could be filtered or segmented by offer and offer_type.
To receive this information, teams needed to provide an in-app purchase key if they had not already done so. Beyond better offer tracking, the key unlocked other StoreKit 2 benefits. A separate tutorial covered running holiday sales on iOS.
StoreKit 2 SDK beta
StoreKit is Apple's in-app purchase framework, and the platform SDK relies on it under the hood on iOS. A new SDK version ran entirely on StoreKit 2. The motivation was straightforward: Apple had been gradually deprecating StoreKit 1, so migration was a question of when rather than if. Adopting the new SDK positioned apps to take advantage of new Apple features and protected against deprecations. The beta was available on GitHub.
Paywalls improvements
Paywalls lets teams build native paywalls from a template gallery, customize them in the dashboard and remotely, and test changes with Experiments. The Launch Party highlighted several iterative additions:
- Two new templates with fresh layouts and features such as a package discount tag to illustrate savings.
- Landscape mode support, particularly useful for games.
- watchOS support.
- An option to display a close button automatically.
Looking ahead, Paywalls for Flutter and React Native, then in beta, were slated for full launch early the following year. A Kotlin Multiplatform SDK was also planned for early the next year, with Paywalls support. On the experimental side, an AI-powered tool to generate paywalls automatically and AI-generated paywall translations were in development, though no ETA was given.
Targeting with scheduling
Targeting, released earlier that month, allowed teams to show specific Offerings and Paywalls to specific audience segments. A common example: showing a particular paywall and product package to customers in India while using default paywalls and offerings for the rest of the world. This let teams fine-tune monetization based on who the customer is.
The new addition was scheduling. Targeting rules could be given a start and end date, making it possible to run a promotional paywall during a defined period automatically.
Other updates not demoed
Several items were announced but did not make the live demo:
- Fresh test results for a full year after an Experiment ends.
- Automatic alerts when an Experiment performs poorly, so teams are notified if results are not going as hoped.
- A subscription status user attribute added to many integrations, making it easier to build CRM campaigns from platform data.
- Automatic refund detection for Google Play.
- A Discord integration for push notifications.
The team also indicated that more updates would be shared through future launch parties, social media, and the blog.
| Feature | Status | Notes |
|---|---|---|
| Mobile PWA refresh button and menu | Shipped | Applies to iOS and regular mobile site |
| Charts on mobile | Shipped | Matches desktop functionality |
| Push notifications | Limited preview | Sign-up required; covers subscription events |
| Weekly Performance Summaries | Available in Labs | Email every Monday; select Projects |
| REST API v2 app management | Shipped | Create and modify apps remotely |
| Overview metrics via API | Shipped | Includes last-updated timestamps |
| External purchases API | Private beta | Third-party subscriptions into the platform |
| Webhooks: five URLs, filters, SUBSCRIPTION_EXTENDED | Shipped | Filter by app, environment, event type |
| Apple Offers pricing and analytics | Shipped | Requires in-app purchase key |
| StoreKit 2 SDK | Beta | Available on GitHub |
| Paywalls: new templates, landscape, watchOS, close button | Shipped | Iterative improvements |
| Paywalls for Flutter and React Native | Beta, full launch planned early next year | Announced at event |
| Kotlin Multiplatform SDK | Planned early next year | Paywalls support planned |
| AI paywall generation and translations | Experimental, no ETA | In development |
| Targeting with scheduling | Newly available | Start and end dates for rules |
| Experiment results retention (one year) | Announced, not demoed | Fresh test results after experiment ends |
| Poor experiment alerts | Announced, not demoed | Automatic notifications |
| Subscription status user attribute | Announced, not demoed | Added to many integrations; useful for CRM campaigns |
| Google Play refund detection | Announced, not demoed | Automatic |
| Discord push notifications integration | Announced, not demoed | Integration available |
Status reflects announcements made in December 2023. Availability may have changed; consult current platform documentation.
Frequently asked questions
Can Weekly Performance Summaries be sent to Slack or other destinations?
At the time of the Launch Party, summaries were delivered only by email. The team said other destinations such as Slack were not yet supported but were being considered, especially after feedback on the initial email version.
Do push notifications cover in-app purchases?
Yes. Push notifications were designed to display for all subscription events, including in-app purchases, matching the events already available through Slack or Discord integrations.
What do I need to enable improved Apple Offers analytics?
You need to provide an in-app purchase key if you have not already done so. This allows the platform to use StoreKit 2 API endpoints for more accurate offer pricing and unlocks other StoreKit 2 benefits.
Why should I consider the StoreKit 2 SDK beta?
Apple has been gradually deprecating StoreKit 1. Moving to an SDK built entirely on StoreKit 2 helps future-proof your app, giving access to new Apple features and protection against deprecations.