A resident needs a certificate by Friday. The counter closes at four. The online portal renders beautifully on a desktop, but the only device in the house is a phone with an unreliable connection and no patience for another account. Two weeks later the certificate is still a paper form, and the resident has made a second trip for nothing. Nothing about that story is a technology gap. It is a distribution gap, and public agencies keep solving the wrong half of it.
The World Bank's 2025 GovTech Maturity Index makes the split visible. More than 75% of economies now run online tax portals, e-filing, e-payment services and job portals, and 59% report using digital ID for identification and online services. Yet roughly four in ten economies still lack an operational one-stop service portal. The group of high-maturity economies grew from about 35% in 2022 to 41% in 2025, while Africa stayed near 13%. Building systems has outrun getting them into the hands that need them.
The install is the barrier
| Citizen task | Why it stalls | What the in-app service does |
|---|---|---|
| Apply | A separate app nobody keeps | A form opened from the host app |
| Pay | A portal that rejects the local wallet | A fee settled where identity already lives |
| Prove | Documents requested again at each desk | A verified credential shown in context |
| Alert | Deadlines sent to an unread inbox | A notice beside the service it concerns |
| Renew | A paper reminder that arrives late | A renewal opened from the same record |
A bespoke government app has to win a place on a crowded home screen against messaging, maps and banking, and it usually loses. A mini-program rides inside a host that already has attention and a verified identity, so the agency can launch a service without asking anyone to download anything. This is not a cosmetic difference. The hardest part of public digitalization has never been the form; it has been the distance between the form and a person who needs it on a Tuesday afternoon.
The instinct in many ministries is still to build one flagship app per department. That produces a portfolio of thin apps, each with its own login, its own release cycle and its own abandoned update. A shared runtime reverses the logic. Services behave like entries in a catalog rather than like separate products, and the agency can change a fee schedule on the day a regulation changes instead of waiting for a store review and a forced-update campaign. The host, meanwhile, gains something no promotional campaign buys: the app that resolves a real errand becomes harder to delete.
There is a genuine tradeoff buried in that arrangement. Riding inside someone else's surface means accepting someone else's release cadence, design rules and outage risk. Procurement, data residency and accessibility obligations do not disappear because the interface moved. The agency still owns the record and the legal responsibility for it; the host owns the relationship with the phone. Treat the runtime as a distribution channel with rules, not as a way to outsource governance, and the arrangement holds up.
Brazil shows how far this can go when identity and distribution are treated as one layer. The GOV.BR platform reached 175 million registered users and 80 million monthly unique accesses in March 2026, with a Gold account tier that unlocks access to thousands of public services. Digital identity is the foundation that makes the rest cheap to add. Without it, every new service rebuilds the same proof of person from scratch, and the citizen pays for that repetition in time and frustration.
Accessibility is the part most often cut when schedules tighten. A service that works only on the newest phone, on a fast connection, with a keyboard, reproduces the exclusion the paper counter created. The shared runtime helps because one published service can inherit the host's text sizing, language settings and offline handling instead of reimplementing each in every ministry. That is a mundane benefit, but it decides whether the service reaches people at the end of the queue.
The measure of a digital public service is completed errands, not downloads. On a shared runtime, a new rule becomes a form update in a surface people already open for other reasons. The town square moved into the pocket years ago; the service only has to follow it there.