Software

Building Super Apps: Mini-Program Architecture

Strategies for building platforms with integrated mini-programs, learning from Alipay, WeChat, and emerging Indian platforms.

All articles
SoftwareNexaEx TeamDecember 15, 2025 9 min read
Building Super Apps: Mini-Program Architecture

Super Apps and Mini-Programs

A super app is a platform hosting mini-programs (lightweight, disposable applications). WeChat, Alipay, and increasingly Jio and PhonePe are super apps. Building one requires rethinking mobile architecture.

Core Characteristics

A true super app:

  • Integrated discovery: Users browse mini-programs within the main app.
  • Frictionless launch: Mini-programs load in <2 seconds, no installation.
  • Shared identity: Single login, payment, and wallet across mini-programs.
  • Low resource overhead: Mini-programs run in sandboxed environments, rarely exceeding 10MB.

Mini-Program Lifecycle

User in super app → discovers mini-program → taps → loads → uses → closes
↓
Super app retains mini-program cache locally
↓
Next time, launch is instant from cache

Sandboxing and Security

Mini-programs run in a sandbox. They can't:

  • Access device file system directly
  • Read device contacts or calendar
  • Launch arbitrary code
  • Drain battery with background processes

Only access granted explicitly by super app and user.

Implementation:

  • JavaScript engine sandboxing: Run mini-program JS in a V8 isolate or JavaScriptCore context with limited globals.
  • API whitelisting: Mini-programs call superApp.getUserLocation(), not navigator.geolocation. Super app controls what's exposed.
  • Resource limits: CPU time, memory, network quota. Misbehaving mini-programs get killed.

UI Framework

Mini-programs need a lightweight UI framework. Options:

  1. Proprietary: WeChat's WXML (XML-like), Alibaba's Axml. Fastest, most control, proprietary learning curve.

  2. Web-based: Web components running in WebView. Developers use HTML/CSS/JS; easier for web developers.

  3. Native: Platform-specific frameworks (Jetpack Compose for Android). Best performance, highest friction for developers.

Most successful: Proprietary framework with web-developer-friendly syntax.

Payment and Monetization

Mini-programs use super app's payment system. Developers never touch payment credentials:

// Mini-program calls
superApp.pay({
  amount: 100,
  currency: 'INR',
  orderId: 'mini-app-123'
})

// Super app handles payment, returns result to mini-program
// Developer never sees user's payment credentials

Revenue sharing: Super app takes 15-30% commission. Developers get remainder. Clear upfront.

Storage and Sync

Mini-programs have limited local storage (5-50MB). For persistent data:

  • User-scoped storage: Each user's mini-program data isolated. Synced via super app server.
  • Mini-program shared storage: Shared across users (similar to session storage).

Database: Mini-programs call superApp.query(), super app queries server backend.

Discovery and Ranking

How do users find mini-programs? Mechanisms:

  1. Trending feed: Algorithm-ranked by engagement.
  2. Search: Users search by name or category.
  3. Recommendations: Personalized suggestions based on user history.
  4. Direct links: QR codes, links from SMS/email launch mini-programs.
  5. Navigation tabs: Categories like "Shopping," "Finance," "Food."

Ranking is crucial for success. Developers optimize for engagement similarly to apps on app stores.

Real-World Example: Indian Super App

A fintech super app in India includes:

  • Payments mini-program: Bill pay, send money.
  • Investment mini-program: Stocks, mutual funds.
  • Lending mini-program: Personal loans, quick credit.
  • Shopping mini-program: Marketplace integration.
  • Third-party mini-programs: Partner vendors like insurance, food delivery.

All share identity (single login), payments (wallet), and user data (with permission). Super app controls discovery; users rarely leave the main app. Total main app size: 80MB. Each mini-program: 2-8MB.

Challenges

Fragmentation: Each platform (WeChat, Alipay, Jio, PhonePe) has slightly different frameworks. Cross-platform mini-program development is complex.

Developer economics: 70% revenue split (30% to super app) is tight for developers. Only high-volume mini-programs break even.

Network effects: A super app succeeds only if developers and users both adopt. First mini-programs are free or heavily subsidized to bootstrap.

When to Build

Build a super app if you have:

  • Existing user base: 10+ million active users.
  • Multiple complementary services: Payments, shopping, lending.
  • Defensible platform: Regulatory, data, or capital moat.

Don't build a super app just because it's trendy. The Bar is high.

Frequently asked questions

What's the difference between a super app and an app with integrations?

A super app hosts mini-programs with sandboxed execution, frictionless launch (<2s), and shared identity/payment. An app with integrations uses deep links and passes data to external apps.

How do mini-programs stay under 10MB?

Code splitting, lazy loading, shared runtime libraries, and compression. Mini-programs reuse UI frameworks and SDKs provided by the super app platform.

What's a reasonable revenue split for mini-program developers?

70% to developer, 30% to super app platform is standard. Some platforms offer 85/15 for top performers. High volume is required to break even.

Let's build your next idea

One conversation to scope the work, meet the team, and get a proposal — usually within two business days.