SuperApp strategy
Partner ecosystem UX framework. 2 pilot partners, MAU +30%.
Today I'd do it this way
Plugging in partner services via SSO + widgets is still the right architecture. But designing each new partner can collapse into a single skill: input is the partner's tech documentation, output is the flow, widget variants, entry points, and a commercial proposal.
partner-integration-blueprint
Coming soonFull design + business blueprint for a new partner integration.
- Takes partner API and current UX as input
- Generates widget variants, entry points, status models
- Commercial proposal with a revenue-share model
How it was done then
Summary
Full version available in Russian. Read in Russian →
Designed the strategy for letting third-party partners into our app. After workshops with architects and analysis of pilot partners, I chose an architecture: widgets in our UI, WebView for partner flows, SSO for auth, partner API powering the scenario inside our UI.
Built the supporting infrastructure: design system for partner widgets, a commercial proposal package, and a step-by-step guide for designers integrating any new partner.
Two pilot partners connected, MAU +30%, the integration mechanism became the standard.