China turned government into a runtime. The e-social-security card has 1.07 billion holders (73% population coverage) and served 17.05 billion online requests in 2024; Zhejiang's 浙里办 has 120 million registered users and 3 million daily actives; the national government service platform sits inside WeChat and Alipay. Citizens do birth registration,社保, 医保 and 公积金 in a mini-program. But you cannot export a Chinese government app — and you should not try. The lesson is the architecture, never the payload.

Why government is the ultimate "pattern, not payload" case

Every other category in this series travels at least partially: games travel on a runtime, social commerce on a pattern plus a rail, mobility and food on a local operational stack. Government services are different — identity, statute and data residency make the app 100% sovereign. What crosses borders is not the content but the design: one front door for many agencies, data shared behind it, and certificates that are digital by default.

DimensionRatingWhat the evidence says
Model maturityS1.07B e-social-security cards, 浙里办 120M users / 3M DAU, national one-network governance is globally leading
Demand universalitySEvery citizen-facing government wants lower friction; the demand is universal
PortabilityWThe app is sovereign — national ID, law and data residency make it 100% non-transferable
Localization depthPMust rebuild on the local civic identity, local statute and local agency topology
Infrastructure dependencyPRequires a national ID system, inter-agency data sharing and a local government cloud
Regulatory fitWThe app is the regulation; only the architecture transfers, never the content

The three moves worth copying

  1. One-stop portal inside a runtime. 一网通办 puts every agency behind one mini-program UI. The runtime hosts the front door; the back-end data sharing stays local and sovereign. A government does not need to build a native app per agency — it ships services as mini-programs in one runtime.
  2. Data sharing & e-certificates. Once identity and certificates are digital (电子证照), ~90% of "running around" disappears. This is governance engineering any state can copy: standardize the forms, share the data, sign the certificate once. The runtime is just the surface; the reform is organizational.
  3. Multi-channel, same-source publishing. 浙里办 publishes the same service to app, web, self-service kiosk, Alipay and WeChat. The runtime makes a service portable across channels — not across borders. The pattern ("write once, appear everywhere locally") is exactly what a universal runtime is built for.

The CrossMiniApp angle

A universal runtime plus an open catalog lets a local government ship a citizen-services portal as mini-programs — without building native apps for every agency. The catalog carries the service pattern; the sovereign content stays home. This is the cleanest proof that "universal runtime + open catalog" is a governance primitive, not just a commerce trick. The runtime constrains what third-party code can do; the catalog distributes the proven service pattern; the state keeps its data.

The rule

The app is sovereign. The architecture is free to borrow.

Sources