SuperApp strategy
Partner ecosystem UX framework — one process for onboarding and standardisation.
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 docs and current UX, output is the flow, widget variants with status models, and a mapping of the partner's design onto our design system via token sync.
partner-integration-ux
Coming soonFull design + business pipeline for a new partner integration.
- Takes partner API and their current UX (in their own design) as input
- Maps the partner's design onto our design system via token sync
- Generates widget variants and their status models
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. Result: a scalable integration mechanism that became the standard for onboarding new partners.