Products: in-app and studio tools
Appwin is a set of products that share a project, an App ID and a user identity.
You enable what you need, when you need it. Nothing forces you to take it all, and adding a product asks for neither a new key nor a resubmission of your app.
Two families
In-app products have a surface inside your mobile app, rendered by the SDK: Community, Support, Notifications. They need the SDK installed and the product enabled on the dashboard side. Analytics goes through the same SDK without drawing anything: it measures, and is read in the studio.
Studio products live only in the dashboard: Finance, ASO, Planner, Documents. They need an integration connected, or nothing at all.
| Product | Family | What it does | Prerequisites |
|---|---|---|---|
| Community | In-app | A community feed in your app, moderated from the studio | SDK + enabling |
| Support | In-app | A messenger and an FAQ, an inbox on the team side | SDK + enabling |
| Notifications | In-app | Push and in-app campaigns, audiences, automations | SDK + APNs / FCM |
| Analytics | In-app | Events, analyses, funnels, feature flags and A/B tests | SDK (iOS and Android) |
| Attribution | Studio | Ad spend, ROAS, SKAN postbacks, signal activation | Ad accounts; SDK for conversion values and activation |
| Finance | Studio | Revenue, subscriptions, acquisition spend | RevenueCat |
| ASO | Studio | Store listing, keywords, reviews, competitors, screenshots | App Store Connect / Play Console |
| Planner | Studio | Tasks, Kanban boards, views, tags | None |
| Documents | Studio | Collaborative knowledge base | None |
What they all share
Isolation by project. A community, an inbox, campaigns, figures always belong to one project and one only. Nothing is aggregated across projects: two apps from the same studio have different users and figures that mean nothing added together. See Concepts.
The only exceptions are team objects - Planner tasks, documents, Support macros and tags - which can sit at studio level and be shared between apps.
The end-user's identity. An end-user recognised through
AppwinCore.identify is the same one in Community and in Support. Your
team sees a single interlocutor, not two records.
The kill switches. Every in-app feature has a switch on the studio side. Turned off, it disappears from the SDK's interface rather than being greyed out, and the server stops serving the corresponding data.
Not documented yet
Formation and Discover exist in the product but do not have their page here yet. Custom dashboards are described in Finance, whose metric catalogue they share.