Picture a woman applying for a small business permit in her city. In the morning she creates an account on the permit app. By midday she is asked to register again on a different app to join a small business training program. The following week, it is the turn of the capital assistance app.
Name, ID number, address. Typed out three times.
She may never have heard the term data integration. Yet she clearly feels the consequences when it is missing.
27,000 apps, and still counting
In early 2026, Indonesia’s Deputy Minister of Communication and Digital Affairs, Nezar Patria, said there were around 27,000 government applications across central and regional institutions. Many of them overlap, doing similar things with similar data.
That number is not a sign that regions are reluctant to innovate. Quite the opposite. Almost every new program arrives with its own app, built by a different agency, a different vendor, in a different budget year. Over time, what forms is not one system but a cluster of islands that never speak to each other.
The costs are not always visible
On paper, apps that do not connect rarely look like a problem. Everything runs and reports still get done. Take a closer look, though.
Residents fill in the same data again and again, and some end up putting off dealing with services altogether.
Staff copy data between systems, then match it by hand as reporting deadlines approach.
Two agencies can hold different numbers for the same thing, and meetings get spent arguing over which figure is right.
Apps whose contracts have ended often keep running without updates. The data is still there. The people looking after it are not.
That last point is the one least talked about, even though it carries the biggest risk.
The center is already moving the same way
The good news is that national policy is now heading in the same direction. The Ministry of Communication and Digital Affairs is pushing for regional systems to align with central infrastructure, including the National Data Center and national APIs as the channel for exchanging public service data.
During those discussions, the ministry outlined several strategies, including separating the data layer and applications, building a single integrated service portal, and providing the SPLP, or Government Service Linking System, a shared layer for exchanging data between government systems.
Regional representatives in the same forum raised an equally important point. Local governments still need room to adapt policies, along with budget support and staff capacity building.
The question is no longer which app to build this year, but how the apps already in place can connect with each other.
So where do you start?
There is no need to wait for a big project. The following steps can begin even before next year’s budget is approved.
First, map what already exists. Which apps the institution owns, who owns each one, whether it is still used, and what data it holds. Many institutions only realize how many apps they have once they actually count them.
Second, agree on master data sources. Who holds population data, who holds business data. That way residents only need to provide their data once, and other systems can draw on the same source.
Third, write integration into procurement specifications. Every new app should have a data exchange path (API) on day one. Adding it later is almost always more expensive.
Beyond that, two things are often overlooked. Budget for maintenance, not just development. And be willing to shut down apps that are no longer used, once their data has been migrated properly.
In the end
Residents do not count how many apps their local government owns. What they remember is whether their business got done without starting over.
Integration is not as exciting as launching a new app. There is no ceremony and no ribbon cutting. Yet that is exactly where public services start to feel truly easy.
