Who they are
Polri is Indonesia’s national police force, serving a country of more than 270 million people through hundreds of units, each with its own systems and software vendors.
All case studies
01 / Case study · Polri
National Police Super App
One app for a hundred, without taking anyone’s keys.
What they set out to do
Bring more than 100 separate applications behind one experience officers and citizens could actually use, without the programme stalling over who owns what.
The problem they were living with
More than 100 applications, each with its own vendor, budget and owning unit. Officers moved between apps to finish one job and citizens had no single door. The brief treated it as an integration problem when the real obstacle was the distribution of control.
What it was costing them. A previous attempt had stalled. Vendors read a single integrated system as handing over the keys to their kingdom, so a technically central platform would still have failed to win cooperation.
What changed
- Vendors joined instead of being replaced
Each unit could contribute its own application through the shared builder, so participation no longer meant surrendering ownership.
- 15 million downloads
Reported for the product across app stores. These are product downloads, not downloads personally acquired.
- 4.8 out of 5 on the App Store
The Indonesian App Store rating was separately corroborated.
- Endorsed by the Chief of Police
Reported by Kevin; the endorsement moved a stalled approach forward.
- One door for citizens
Public services that had been scattered across separate apps arrived in a single place.
Figures are as reported by Kevin and the QuantumByte materials, with the App Store rating separately corroborated. The original brief covered more than 100 applications; that does not establish how many were finally integrated.
Designed solutions
What we designed for PRESISI’s people.
A shared super app shell
An initially empty application that units could publish into, rather than a finished system they had to adopt.
Low-code application builder
Each unit and its vendor could build their own application inside the shared platform, without handing over their source or their budget.
Vendor participation model
The commercial and ownership terms were designed alongside the software, so joining was an option rather than a surrender.
One door for the public
Citizen-facing services arrived in a single app instead of a directory of separate downloads.
Officer workflows in one place
The daily jobs officers moved between apps to finish were brought behind one login.
Release and review path
New unit applications could ship into the super app without rebuilding the whole platform.
The workflow
How the work flows now.
Bring the unit’s need
A unit and its vendor describe the application they already run or want.
Build inside the shared platform
The low-code builder produces it within the super app’s rules and design.
Publish behind one door
The application appears for the officers or citizens who need it.
Use it in the field
People finish the job in one place instead of moving between apps.
Improve without a new procurement
Changes ship through the same builder rather than a fresh vendor cycle.
Where else this applies
The same approach, in other industries.
| Industry | Fit | Why |
|---|---|---|
| Law enforcement | High | The same participation model fits any force whose units already run their own systems. |
| Emergency response | High | Multiple agencies must act in one place while keeping their own command and budgets. |
| Government services | High | Citizen-facing services scattered across ministries need one door without central seizure of ownership. |
| Large enterprise IT | Medium | Divisions with their own vendors face the same integration standoff at a smaller scale. |
| Utilities and infrastructure | Emerging | Regional operators could publish into a shared operational app, though procurement cycles are slow. |
Kevin’s part
Kevin reframed the integration strategy around vendor participation and led the product with the Quantum team.
Working on something like PRESISI’s?
Tell me where the workflow breaks today and who carries it. I’ll tell you what the smallest useful slice would be, and whether I’m the right person to build it.