Super App & SDK
Written by Jacinthe Busson, Co-founder & CPO at Fastory, based on her research and observations on mobile ecosystems, UX and Super Apps.
A Super App cannot scale by building everything itself.
That sounds obvious.
Yet it is one of the most important ideas behind the Super App model.
If an application wants to offer payments, transport, shopping, entertainment, healthcare, loyalty, public services and thousands of other use cases, it eventually faces a structural problem:
How can one product keep expanding without becoming an impossible monolith?
China's answer has been one of the most influential ideas in modern mobile architecture:
Mini Programs.
Weixin launched Mini Programs in 2017. Alipay subsequently developed its own Mini Program ecosystem.
The principle is simple.
Instead of asking users to install a new standalone application for every service, lightweight experiences can run inside an application they already use.
This transforms the Super App.
It is no longer simply an application containing many features.
It becomes a platform capable of hosting other applications and services.
And that architectural shift may be more important than any individual feature inside WeChat or Alipay.
From app accumulation to platform architecture
The traditional smartphone model is built around standalone applications.
A company wants to provide a mobile service.
It builds an iOS application.
It builds an Android application.
It publishes both in app stores.
Then the user has to:
discover the app;
download it;
install it;
open it;
create an account;
authenticate;
grant permissions;
understand a new interface;
and keep it installed.
This model works extremely well for products people use frequently.
Banking.
Messaging.
Transport.
Music.
Social networks.
But it becomes less efficient when a user needs a service only occasionally.
Does every restaurant need to occupy permanent space on someone's smartphone?
Every venue?
Every event?
Every retailer?
Every local service?
Every transport operator?
Every temporary interaction?
Mini Programs challenge this assumption.
Instead of:
Service → Standalone app → Installation → User
the model can become:
Service → Mini Program → Existing Super App → User
The service still exists.
But the distribution layer changes.
What exactly is a Mini Program?
Tencent describes Weixin Mini Programs as services that run on the Weixin platform and can be accessed through mechanisms such as QR codes or search.
Alipay's developer documentation describes Mini Programs as sub-applications that run inside a mobile application, allowing users to access services without installing additional applications.
That definition is important.
A Mini Program is not simply a mobile web page opened inside an app.
It operates within a platform framework.
The host application can provide:
navigation;
runtime infrastructure;
UI components;
authentication capabilities;
payments;
device access;
storage;
network capabilities;
security controls;
and other reusable services.
The Mini Program provides the specialised experience.
The host platform provides much of the environment around it.
This creates a different division of responsibility between platform and service provider.
The Super App becomes a runtime
This is where the architecture becomes particularly interesting.
A traditional mobile application directly contains most of the functionality that its development team builds.
A Mini Program platform introduces another layer.
The Super App contains a runtime environment capable of loading and executing experiences developed by third parties.
Alipay's current Mini Program platform, for example, provides an SDK that can be integrated into a host mobile application.
Its documentation describes the IAPMiniProgram SDK as a secure runtime environment that can:
manage and run Mini Programs;
provide reusable UI components;
expose APIs for device, storage and network capabilities;
and allow host applications to customise native components and platform behaviours.
The architecture therefore becomes something like:
Operating System
↓
Super App
↓
Mini Program Runtime / SDK
↓
Mini Programs
↓
Individual services
This is fundamentally different from adding another page to an application.
The host application is becoming an execution environment for other experiences.
Why this matters for Super Apps
In Inside Alipay: How a Super App Became an Everyday Operating System, we explored the idea that a Super App behaves more like a platform than a conventional application.
Mini Programs are one of the clearest technical expressions of that idea.
Without them, expanding a Super App means continually adding functionality to the core application.
Every new service increases:
code complexity;
release complexity;
maintenance requirements;
design complexity;
technical dependencies;
and organisational coordination.
Eventually, the application becomes difficult to evolve.
Mini Programs change the scaling model.
The platform operator maintains the ecosystem and shared capabilities.
External teams can maintain their own services.
Users still experience those services inside the same broader environment.
This allows the ecosystem to grow without requiring every service to become part of the Super App's core codebase.
Modularity is the real breakthrough
The most important word here may not be "Mini".
It may be modular.
A modular architecture allows different capabilities to evolve independently while still operating inside a shared system.
Consider a transport Mini Program.
It might need:
user authentication;
location;
payment;
QR scanning;
network access.
A retail Mini Program might require:
authentication;
payment;
product browsing;
storage;
notifications.
A loyalty experience might need:
identity;
rewards;
QR scanning;
user data;
messaging.
The services are different.
But many underlying capabilities are shared.
Instead of rebuilding these capabilities repeatedly, the platform can expose them as reusable building blocks.
Alipay's current Mini Program architecture does this through combinations of JSAPIs, Open APIs and native interfaces.
The Mini Program requests a capability.
The platform decides how that capability is provided.
This is what makes modular ecosystems powerful.
APIs are the language between services
An API allows one software system to interact with another.
Within a Mini Program environment, APIs can provide controlled access to capabilities offered by the host platform.
For example:
requesting location;
opening a scanner;
accessing storage;
triggering payment;
requesting user authorisation;
retrieving approved user information.
This creates an abstraction layer.
The Mini Program does not necessarily need to know how the Super App implements every capability internally.
It asks for a service through a defined interface.
This reduces duplication and creates consistency across the ecosystem.
It also gives the platform operator control over which capabilities are available and under what conditions.
SDKs provide the execution layer
APIs explain how systems communicate.
SDKs help developers implement capabilities inside applications.
This distinction becomes important when discussing Super App architecture.
Alipay's current platform provides an IAPMiniProgram SDK for embedding Mini Program capabilities into a host mobile application.
The SDK creates the runtime responsible for loading and running Mini Programs.
It can also bridge Mini Programs to capabilities provided by the host application.
This architecture is particularly interesting because it means the Mini Program model is no longer limited to Alipay itself.
The underlying approach can be integrated into other host applications.
Alipay's own developer platform explicitly presents this as a way for wallet applications to evolve towards a Super App model by opening their applications to third-party Mini Programs.
That is an important evolution.
The Super App model is becoming an architectural pattern, not simply a characteristic of a handful of Chinese platforms.
Native capabilities remain important
One of the limitations of purely web-based experiences is access to native mobile functionality.
Mobile applications can interact with cameras, location services, biometrics, local storage, notifications and many other device capabilities.
Mini Program platforms bridge these two worlds.
Alipay's documentation describes native interfaces that allow a host Super App to provide Mini Programs with capabilities including:
user authorisation;
user information;
payments;
QR and barcode scanning.
The Mini Program can therefore remain lightweight while still interacting with important capabilities of the surrounding native application.
This hybrid model is one reason Mini Programs are more interesting architecturally than simply embedding websites inside an application.
The experience can remain modular without becoming disconnected from the host platform.
Shared identity reduces friction
Authentication is one of the biggest sources of friction in mobile services.
A conventional standalone application may require:
registration;
email verification;
password creation;
login;
password recovery;
two-factor authentication;
and account management.
Each new service repeats part of this journey.
Inside a Mini Program ecosystem, the host platform can provide an identity layer.
The user still needs appropriate consent and authorisation.
But the service may be able to interact with an existing identity rather than asking the user to establish an entirely new relationship from scratch.
Alipay's platform exposes user-authorisation capabilities specifically for this purpose.
This directly connects Mini Programs with the principle discussed in The Power of Instantaneity:
reduce the distance between intention and action.
The less infrastructure the user needs to see, the more continuous the experience can feel.
Payments can become shared infrastructure
The same principle applies to payments.
If every service implements its own payment flow, the ecosystem remains fragmented.
Different credentials.
Different checkout experiences.
Different security behaviours.
Different interfaces.
A Super App can provide payment as a shared capability.
Individual Mini Programs can then integrate with that infrastructure instead of recreating the entire transactional layer.
This is what transforms payment from a feature into platform infrastructure.
And it explains part of Alipay's strategic advantage.
The platform did not need to convince users to trust a completely new payment system every time they entered a new service.
The payment relationship already existed.
Mini Programs could build on top of it.
QR codes become service entry points
In How QR Codes Changed Mobile Payments in China, we explored the QR code as a bridge between physical context and digital action.
Mini Programs extend that principle.
Tencent explicitly describes QR scanning as one way users can access Weixin Mini Programs.
Alipay's platform also provides capabilities for creating QR codes that redirect users to specific Mini Program pages.
This creates an extremely powerful interaction model:
Physical context → QR code → Mini Program → Service
No app-store search.
No installation.
Potentially no new account.
The physical environment can connect directly to a contextual service inside an ecosystem the user already knows.
This is a particularly mobile-native form of distribution.
Discovery moves inside the ecosystem
Standalone applications depend heavily on external distribution.
App stores.
Search engines.
Advertising.
Social media.
Direct links.
Mini Programs introduce another possibility.
Discovery can happen inside the host platform itself.
Search.
Recommendations.
Recent services.
QR codes.
Messages.
Merchant pages.
Contextual entry points.
The Super App therefore controls not only the runtime but also part of the distribution layer.
That has enormous implications.
For users, discovery can become easier.
For developers and merchants, access to an existing user base can reduce acquisition friction.
For the platform, controlling discovery increases its influence over which services gain visibility.
This is where architecture becomes economics.
The architecture creates dependency
Mini Programs solve many problems.
But they create new ones.
When a service operates inside another company's ecosystem, it becomes dependent on that ecosystem.
The platform can define:
technical requirements;
allowed APIs;
design standards;
review processes;
distribution rules;
data permissions;
payment policies;
security requirements;
release procedures.
If those rules change, the service has to adapt.
This is not inherently negative.
Platform rules can improve security, compatibility and user experience.
But they change the balance of power.
A standalone application controls much more of its own environment.
A Mini Program gains distribution and shared infrastructure in exchange for platform dependency.
That trade-off is one of the central tensions of the Super App model.
Governance becomes part of product architecture
Once third parties can run software inside a platform used by millions of people, the platform operator needs governance.
Who can publish?
Which APIs can be accessed?
Which information can be collected?
How are updates reviewed?
How are permissions managed?
What happens when a service violates platform rules?
Alipay's current platform documentation shows how deeply these governance mechanisms are integrated into the technical architecture.
Certain capabilities require activation and approval before a Mini Program can use them.
Releases can move through development, testing and controlled deployment environments.
Super Apps can define review processes and control access to platform features.
This illustrates an important point:
A Super App is not only a technical platform. It is a governed ecosystem.
Architecture and policy become inseparable.
Mini Programs need design consistency too
There is another challenge.
If thousands of third-party services operate inside one Super App, the user experience can quickly become incoherent.
Different navigation.
Different loading behaviours.
Different buttons.
Different terminology.
Different error states.
Different visual systems.
At that point, the ecosystem may technically be integrated while still feeling fragmented.
Platforms therefore need shared UX principles.
Alipay's Mini Program platform includes reusable UI components and design guidance, while its SDK allows host applications to customise native components such as title bars, loading views and error states.
This is a subtle but important part of Super App architecture.
Consistency is infrastructure too.
The platform is not only sharing code.
It is sharing interaction conventions.
The user should perceive continuity, not architecture
From a technical perspective, a Super App ecosystem can be extremely complex.
Different organisations.
Different services.
Different servers.
Different Mini Programs.
APIs.
SDKs.
Authentication layers.
Payment infrastructure.
Review systems.
Analytics.
Security.
But the user ideally sees none of this.
They see:
open;
tap;
scan;
use service;
pay;
continue.
This connects back to a principle that has appeared throughout this series:
The more complexity the system can manage, the less complexity the user should have to manage.
Mini Programs are a particularly clear example.
The architecture becomes more distributed.
The visible experience can become more continuous.
Mini Programs changed the economics of mobile distribution
There is another consequence worth considering.
Building a standalone application requires more than development.
It requires acquisition.
A company can invest heavily in creating an app and still struggle to convince users to download it.
Mini Programs can reduce that distribution barrier by giving services access to an existing host ecosystem.
This is part of why the model became economically significant.
Tencent reported that by 2020, three years after launch, WeChat Mini Programs had more than 300 million daily active users, while transaction value generated through Mini Programs had exceeded RMB 800 billion during 2019.
Those historical figures help illustrate that Mini Programs did not remain a technical experiment.
They became a meaningful layer of the WeChat ecosystem.
Mini Programs are not necessarily replacements for apps
It would be a mistake to conclude that Mini Programs make standalone applications obsolete.
The two formats solve different problems.
A standalone application may remain preferable when:
the product is used very frequently;
the experience requires deep native functionality;
the company wants full control over distribution;
offline capabilities are important;
performance requirements are particularly demanding;
or the application itself is the primary customer relationship.
Mini Programs become especially compelling when:
usage is contextual or occasional;
distribution friction is high;
users already spend time inside a host ecosystem;
shared platform capabilities provide meaningful value;
or the service benefits from being embedded inside a broader journey.
The question should therefore not be:
Mini Program or app?
It should be:
Which form creates the least friction for this particular service?
The model is spreading beyond WeChat and Alipay
This is where the story becomes especially relevant outside China.
The architectural logic behind Mini Programs can now be implemented in other mobile applications.
Alipay's current Mini Program Development Platform is explicitly designed to help wallet applications create open platforms in which third-party developers can build Mini Programs.
Its documentation currently supports SDK implementations for native mobile platforms and frameworks, while its platform allows Mini Programs to be distributed across multiple partner applications.
This means the model can increasingly be understood independently from Alipay itself.
A host application can provide:
a runtime;
shared capabilities;
identity;
payments;
distribution;
governance;
and development tools.
Third parties can provide services.
Users can access those services without repeatedly leaving the host environment.
That is effectively the architecture of a Super App.
From Mini Programs to embedded experiences
The terminology may evolve outside China.
Not every company will call these experiences Mini Programs.
We may instead hear:
embedded apps;
embedded experiences;
micro-apps;
modules;
in-app services;
mobile extensions;
or SDK-powered experiences.
The terminology matters less than the architectural principle.
A mobile application no longer needs to contain every experience itself.
Instead, it can become a host environment capable of integrating modular services.
This can change how companies think about mobile product strategy.
Instead of asking:
Which features should we build into our app?
they can ask:
Which capabilities should our app provide as a platform, and which experiences should be integrated as modules?
That is a very different question.
SDKs become strategically important
This is also where SDKs become increasingly relevant to the Super App conversation.
An SDK can allow a company to add capabilities to an existing mobile application without rebuilding those capabilities entirely from scratch.
Depending on the architecture, SDKs can provide:
runtime environments;
UI components;
authentication;
payments;
analytics;
native integrations;
content rendering;
interactive modules;
or connections to external services.
The concept is broader than Mini Programs.
But the underlying objective can be similar:
make an existing mobile application capable of hosting more experiences without turning every new capability into a standalone product.
This is why SDKs and Super Apps increasingly belong to the same architectural conversation.
Not because an SDK automatically creates a Super App.
It does not.
But because modular integration is one of the ways a mobile application can progressively evolve from a single-purpose product into a broader ecosystem.
Architecture shapes engagement
Mini Programs also have consequences for engagement.
In the previous article, Gamification: The Hidden Engagement Engine Behind Alipay, we explored how persistent engagement works particularly well when it connects to behaviours already taking place inside an ecosystem.
Mini Programs increase the number of contexts in which those interactions can occur.
A loyalty programme can exist inside one module.
A game inside another.
Commerce somewhere else.
A service elsewhere.
But identity and ecosystem context can connect them.
This creates the possibility of engagement operating across experiences rather than inside one isolated feature.
That is one reason modular architecture matters beyond engineering.
Architecture shapes what kind of user relationships are possible.
The Super App is increasingly an orchestration layer
At this point, the Super App can be understood through three layers.
The interface layer
What the user sees.
Navigation.
Search.
Recommendations.
Entry points.
The service layer
What the user can do.
Pay.
Shop.
Travel.
Play.
Access services.
The infrastructure layer
What makes those services interoperable.
Identity.
APIs.
SDKs.
Payments.
Permissions.
Runtime.
Security.
Data exchange.
Governance.
The strongest Super Apps coordinate all three.
That is why the model is so difficult to reproduce simply by adding more tabs to an existing application.
A Super App is not a navigation pattern.
It is an architecture.
The lesson is not to copy Mini Programs
As with many aspects of China's mobile ecosystem, the useful question is not:
How do we reproduce WeChat?
The market conditions that created WeChat and Alipay are specific.
Consumer expectations differ.
Regulation differs.
Payment systems differ.
App-store economics differ.
Digital habits differ.
The more valuable question is:
What architectural principle can be transferred?
Mini Programs demonstrate several.
Do not force users to install a new app for every interaction.
Reuse infrastructure where possible.
Separate core platform capabilities from specialised services.
Allow independent experiences to evolve without bloating the host application.
Create continuity between services.
Move complexity away from the user.
And design distribution as part of the product architecture.
These ideas are relevant far beyond China.
From apps to ecosystems
For most of the smartphone era, the fundamental unit of mobile product strategy has been the application.
Build an app.
Acquire downloads.
Drive usage.
Retain users.
Mini Programs challenge that model.
They suggest that the future unit may increasingly be the ecosystem.
An ecosystem in which the application becomes the host.
The SDK becomes part of the infrastructure.
APIs become the connectors.
Modules provide specialised experiences.
And users move between services without continually restarting their digital journey.
This does not mean every mobile application should become a Super App.
Most should not.
But for organisations that already own a meaningful mobile audience, the architectural question is increasingly worth asking:
Should the next capability be another standalone app, another feature inside the core product, or an embedded experience connected to the existing ecosystem?
The answer will vary.
But the question itself signals an important change in how mobile products can be designed.
Super Apps are not simply becoming bigger apps.
They are becoming platforms for modular experiences.
Frequently Asked Questions
What is a Mini Program?
A Mini Program is a lightweight application or digital service that operates inside a larger host application.
Platforms such as Weixin/WeChat and Alipay allow users to access Mini Programs without installing a separate standalone application for every service.
When did WeChat launch Mini Programs?
Tencent launched Weixin Mini Programs in January 2017.
They allow users to access services from merchants and institutions through the Weixin ecosystem, including through search and QR codes.
How are Mini Programs different from normal mobile apps?
A traditional mobile app is installed independently on the user's device and maintains its own application environment.
A Mini Program operates inside a host application and can reuse capabilities provided by that platform.
This can reduce installation friction and allow services to integrate more closely with an existing ecosystem.
Are Mini Programs just mobile websites?
Not exactly.
Although Mini Programs can use web technologies in parts of their architecture, they operate within a dedicated platform runtime and can access platform and native capabilities through controlled APIs.
They are therefore more integrated with the host application than a conventional webpage opened in a browser.
What role do Mini Programs play in Super Apps?
Mini Programs allow a Super App to expand without building every service directly into its core application.
Third-party organisations can create specialised services while using shared infrastructure provided by the host platform.
This makes the Super App more modular and scalable.
What is a Mini Program runtime?
A Mini Program runtime is the environment inside the host application responsible for loading and executing Mini Programs.
It can provide reusable UI components, network and storage capabilities, APIs, security controls and connections to native services.
What is the difference between an API and an SDK?
An API defines how different software systems or components communicate.
An SDK, or Software Development Kit, provides tools, libraries and code that developers can use to implement capabilities inside an application.
In a Super App architecture, APIs may expose specific platform services while an SDK can provide the runtime and integration layer required to support embedded experiences.
Can an SDK turn a mobile app into a Super App?
Not by itself.
A Super App also requires product strategy, shared services, governance, distribution, identity and an ecosystem of useful experiences.
However, SDKs can provide important technical building blocks for integrating modular capabilities and embedded experiences into an existing mobile application.
How do Mini Programs access native mobile features?
The host platform can expose selected native capabilities through APIs and software interfaces.
For example, Alipay's Mini Program platform can provide access to functions such as user authorisation, payments, QR scanning and other device or platform services.
Access is controlled by the platform.
Do Mini Programs reduce mobile friction?
They can.
Because users do not necessarily need to find, download, install and register for another standalone application, Mini Programs can shorten the path between discovering a service and using it.
The benefit is especially strong for occasional or contextual services.
Are Mini Programs only used in China?
No.
The model became particularly prominent through Weixin/WeChat and Alipay, but Mini Program infrastructure is now available to other applications and digital wallets.
Alipay's Mini Program platform, for example, provides technology designed to let other host applications integrate Mini Program capabilities.
What are embedded mobile experiences?
Embedded mobile experiences are services or interactive capabilities that operate within an existing mobile application instead of requiring users to move to a separate standalone product.
Mini Programs are one implementation of this broader architectural idea.
Why are Mini Programs important for mobile engagement?
They reduce distribution friction and allow services, loyalty, games, commerce and other experiences to exist inside an environment the user already knows.
When combined with shared identity and platform services, this can make engagement more continuous across different use cases.
What are the disadvantages of Mini Programs?
The main trade-off is platform dependency.
Developers need to follow the host platform's technical standards, permissions, review processes, design rules and distribution policies.
The host platform therefore has significant control over how third-party services operate within its ecosystem.
Sources & Further Reading
Tencent
Our Story — Weixin launches Mini Programs.
Official Tencent chronology documenting the launch of Weixin Mini Programs in January 2017.
https://www.tencent.com/who-we-are/our-story/
Tencent
Weixin Mini Programs.
Official overview explaining how users access Mini Programs through Weixin and how merchants and institutions provide shopping, dining, travel, healthcare, utility and other services.
https://www.tencent.com/products/weixin-mini-programs/
Tencent
WeChat Mini Programs Showcases New Capabilities to Celebrate its Third Anniversary.
Historical data on the development of the Mini Program ecosystem, including more than 300 million daily active users and over RMB 800 billion in transaction value in 2019.
https://www.tencent.com/wechat-mini-programs-showcases-new-capabilities-to-celebrate-its-third-anniversary/
Alipay Mini Program Development Platform
Documentation.
Official definition of Mini Programs as sub-applications that run inside mobile apps without requiring additional application installation.
https://miniprogram.alipay.com/docs-alipayconnect/
Alipay Mini Program Development Platform
Make Your App a Super App.
Official overview of the Mini Program platform and IAPMiniProgram SDK, including the runtime, UI components and infrastructure APIs available to host applications.
https://miniprogram.alipay.com/product
Alipay Mini Program Development Platform
IAPMiniProgram SDK — Quickstart.
Technical documentation for integrating the Mini Program runtime into Android applications.
https://miniprogram.alipay.com/docs/miniprogram/mpdev/sdk_android_quickstart
Alipay Mini Program Development Platform
Integrate Native SPIs.
Documentation explaining how Mini Programs can interact with host-app capabilities including authorisation, user information, payments and QR/barcode scanning.
https://miniprogram.alipay.com/docs/miniprogram/mpdev/sdk_android_integrate_native_spi
Alipay Mini Program Development Platform
Mini Program Lifecycle — Features Overview.
Documentation explaining how platform capabilities and JSAPIs are granted and controlled within Mini Programs.
https://miniprogram.alipay.com/docs/miniprogram/mp_lifecycle/features_overview
Alipay Mini Program Development Platform
Release Workflow.
Documentation describing development, testing and release-target environments for Mini Programs.
https://miniprogram.alipay.com/docs/miniprogram/mp_lifecycle/release
Alipay Mini Program Development Platform
Platform Overview.
Current documentation explaining how Mini Programs can be created once and distributed across participating host applications and wallets.
https://miniprogram.alipay.com/docs-alipayconnect/miniprogram_alipayconnect/platform/getting-started-overview
