PT PP is a leading Indonesian state-owned enterprise operating across construction, building, infrastructure, engineering, procurement and construction, plants, and equipment. The company also invests in infrastructure, property, and energy.
As a public organization, PT PP has a responsibility to provide information services that are transparent, standardized, and accessible to stakeholders. Its PPID, or Information and Documentation Management Officer, plays an important role in helping the public request information, ask questions, and raise objections when necessary.
Previously, these services were primarily accessed through the PT PP website. While the website contained the required information, it did not fully support users who needed a faster way to submit, track, and manage requests.
In 2024, PT PP partnered with Suitmedia to develop PPID PT PP mobile applications for iOS and Android. The new apps extended the existing information service to mobile devices, giving users a more direct way to access public information and monitor their submissions.
A Transparent Information Service Needed to Work at the Speed of Its Users
1. Public information was available, but access was not yet convenient enough
PT PP already provided PPID information through its website. However, a website-based service can become less convenient when users need to access it repeatedly, submit a request, or monitor the progress of an interaction.
Users may need to return to the platform to check a submission, review a response, ask a follow-up question, or raise an objection. If every step requires navigating through a website that was not designed around these actions, the process can feel slower than necessary.
This is particularly important for public information services. Accessibility is not only about whether information exists online. It is also about whether people can find it, request it, and follow up without unnecessary effort.
PT PP needed to make the PPID service more practical for users who increasingly rely on mobile devices for everyday digital interactions.
2. The service involved more than reading published information
A PPID platform is not simply an online library.
Users may want to search for existing information, submit a formal request, ask a question, or raise an objection when they believe a request has not been handled appropriately. They may also need to monitor what happens after submission.
Each action creates a different user need. Reading information requires clear organization. Submitting a request requires a guided form. Monitoring requires status visibility. Questions and objections require clear channels for follow-up.
The previous website did not fully support these needs through a mobile-first experience. PT PP needed a platform that could make information access and interaction work together.
3. Public trust depends on clarity and responsiveness
For a state-owned enterprise, public information services influence how stakeholders experience transparency.
If users cannot easily understand the process, they may be unsure about what information is available, how to submit a request, or whether their submission has been received.
This uncertainty can weaken confidence even when the organization is committed to disclosure. A clear and responsive digital service helps demonstrate that transparency is supported by a functioning process, not only by a policy statement.
The application therefore needed to make the service easier to understand and use. It had to guide users through the process while helping PT PP manage information requests more consistently.
4. Content and technology had to improve together
A mobile application could not solve the problem if it only copied website content onto a smaller screen.
The platform needed to address both content organization and technical performance. Information had to be structured in a way that made sense on mobile devices, while the application needed to respond reliably to user actions.
This meant understanding what information users needed, how they moved through the service, and what the organization needed to manage behind the scenes.
The objective was to create a standardized and manageable information service that remained accessible to users across different devices and situations.
5. The application needed to serve public users and internal teams
The public would use the application to access information and submit requests. PT PP’s internal teams would need to receive, manage, monitor, and respond to those interactions.
A successful system therefore needed to support both sides of the service.
If the public experience was simple but internal handling remained fragmented, the overall process would still be slow. If the internal system was efficient but difficult for the public to use, adoption would remain limited.
The application had to create a more connected process from submission to response.
Designing a Mobile-First Information Service Around Real User Actions
1. We started by understanding the complete PPID journey
Suitmedia began with requirements gathering and analysis.
The purpose was to understand what users needed to do, what information they needed at each stage, and how PT PP’s teams managed those interactions.
The analysis considered the full journey:
- Finding available information.
- Understanding the PPID service.
- Submitting an information request.
- Asking a question.
- Raising an objection.
- Monitoring the status of a submission.
- Receiving or reviewing a response.
Mapping this journey helped prevent the application from becoming a collection of disconnected features. Each part needed to support the next step.
The work also helped identify where content needed to be clearer and where technical improvements could reduce user effort.
2. We created the sitemap before building the interface
The sitemap established how information and actions would be organized within the applications.
This was important because users should not have to understand PT PP’s internal structure before they can find the right service. The navigation needed to reflect user intent: access information, submit a request, monitor progress, ask a question, or raise an objection.
A clear sitemap also supported consistency across the iOS and Android versions. Users should encounter the same logic regardless of which operating system they use.
The structure became the foundation for the design prototypes and helped PT PP review the proposed experience before development began.
3. We used prototypes to test clarity before implementation
Design prototypes allowed the team to explore how the application would look and behave before committing to development.
This created an opportunity to refine navigation, forms, content presentation, and interaction flows early in the process. Changes made at this stage are generally easier to manage than changes made after the application is fully built.
The prototypes also helped translate abstract requirements into something stakeholders could review directly. Instead of discussing features in isolation, PT PP’s teams could see how a user might move through the service.
This supported shared understanding and reduced the risk of developing a technically functional application that did not match the organization’s operational needs.
4. We designed the interface around mobile behavior
The applications were designed for iOS and Android with a focus on accessible, user-friendly interaction.
Mobile users typically navigate with limited screen space and shorter periods of attention. Important actions must be visible, forms must be manageable, and information must be presented in a way that can be reviewed without unnecessary scrolling or confusion.
The interface therefore needed to prioritize the actions users were most likely to take. Accessing information, submitting a request, and monitoring a submission should not require users to move through a complicated sequence.
The design also needed to create confidence. Users should understand what they are submitting, what happens next, and where they can check progress.
5. We made information requests possible from a smartphone
One of the application’s key benefits was allowing users to submit information requests directly from their smartphones.
This reduced the effort required to interact with PT PP’s PPID service. Users did not need to wait until they were at a desktop computer or navigate through a less convenient mobile website.
A mobile request process can also support more timely interaction. Users can submit questions when they arise instead of postponing the action until they have access to a different device.
The value was not only speed. A simpler submission path can make the public more likely to use the official channel rather than rely on informal communication or incomplete sources.
6. We added question and objection functions to support accountability
The application allowed users to ask questions and raise objections directly through their smartphones.
These capabilities recognized that public information services require more than a one-way publishing model. Stakeholders may need clarification, additional information, or a formal way to respond when they believe a request has not been adequately addressed.
Providing these functions in the same application created a clearer service path. Users could move from reading information to asking about it or formally challenging the outcome without switching to another channel.
This supported a more complete model of public engagement and gave PT PP a more structured way to receive those interactions.
7. We made monitoring part of the service experience
Users could monitor their submitted reports or requests through the applications.
Status visibility is important because a submission does not end when a form is sent. Users need to know whether the request has been received, is being processed, or has reached a response stage.
Without monitoring, users may need to contact the organization repeatedly to confirm progress. This creates work for both the public and internal teams.
A tracking function reduced that uncertainty by giving users a clearer view of what was happening after submission.
8. We standardized content to make the service easier to understand
The project focused not only on application functionality but also on improving and standardizing the content delivered through the service.
Standardization helps ensure that users receive consistent information regardless of how they access the platform. It also makes the service easier for internal teams to maintain and update.
Clear content supports better decisions. Users can understand what types of information are available, what a request involves, and what steps they should take next.
For PT PP, this created a stronger relationship between content governance and user experience. Information became easier to manage internally and easier to understand externally.
9. We used a cross-platform development approach
Suitmedia used Flutter to develop the applications for both iOS and Android.
A cross-platform approach allowed the project to maintain a more consistent experience across operating systems while supporting efficient development and maintenance.
The backend used PHP and Laravel, while MySQL was used to store and manage application data. These technologies supported the application’s need for reliability, scalability, performance, and practical administration.
The technology choices were made to support the service, not to distract from it. The priority was to create a stable application that could manage information and user interactions across both major mobile platforms.
10. We designed for ongoing improvement
The application was created as a foundation for continued digital improvement rather than a one-time technical delivery.
A public information service will evolve as users ask new questions, regulations change, and PT PP improves its internal processes. The platform therefore needed to support future updates to content, functionality, and operating procedures.
This required a structure that internal teams could manage and a technical foundation that could be maintained over time.
The long-term value of the project depended on PT PP being able to keep the service accurate, responsive, and aligned with stakeholder expectations.
From Website-Limited Access to a More Responsive Public Service
1. Users gained mobile access to official information
The iOS and Android applications made PT PP’s PPID information services available through mobile devices.
Users could access the same core information previously available through the website in a more direct and convenient format.
This expanded access for people who prefer mobile interaction or need to use the service away from a desktop environment.
The application gave PT PP a more flexible public-facing channel without replacing the website. It extended the service to match how users increasingly interact with digital information.
2. Requests and reports became easier to submit
Users could submit information requests and reports directly through the applications.
This reduced the number of steps required to initiate contact with PT PP’s PPID service and made the official process more accessible.
The simpler path also supported better standardization. When users submit through a structured application, the organization can receive information in a more consistent format and process it more efficiently.
3. Monitoring improved visibility after submission
The ability to monitor submissions gave users greater clarity about the status of their interactions.
This helped reduce uncertainty and the need for repeated follow-up. Users had a clearer way to understand what was happening after they submitted a request, question, or report.
For PT PP, status monitoring also supported more accountable service management. The organization could manage requests within a defined digital process rather than relying only on disconnected communication.
4. Questions and objections became part of one accessible workflow
The application gave users a direct channel to ask questions and raise objections from their smartphones.
This strengthened the completeness of the PPID service. Users could access information, request additional disclosure, seek clarification, or challenge an outcome within the same digital environment.
The experience supported a more constructive relationship between PT PP and its stakeholders. Transparency became a process that allowed response and follow-up, not only publication.
5. The project improved accessibility and efficiency across both platforms
The applications enhanced accessibility for public users while helping PT PP manage information interactions more systematically.
The result was not only a more modern interface. It was a clearer connection between public requests and internal handling.
This can improve efficiency over time because structured submissions and visible statuses reduce repeated questions, manual clarification, and uncertainty about ownership.
6. The application reinforced PT PP’s public image
The mobile application demonstrated PT PP’s commitment to improving access to public information.
A state-owned enterprise is judged not only by the projects it delivers, but also by how it communicates with stakeholders and responds to public needs.
By offering a dedicated, responsive, and transparent mobile service, PT PP strengthened the digital expression of its institutional responsibilities.
The application became part of the company’s public-facing brand—showing that accessibility and transparency were being supported through practical digital tools.
7. PT PP’s team recognized the value of the collaboration
PT PP expressed satisfaction with Suitmedia’s support in improving the PPID website and developing the mobile applications.
The company recognized that the work improved access to information disclosure and contributed positively to its brand.
This feedback is important because public-service applications succeed only when both users and internal teams can adopt them. The project created confidence that the platform could support future improvements and deliver continued value.
What the PPID PT PP Project Reveals About Public Information Services
1. Accessibility means more than publishing information online
Information is not truly accessible if users cannot find it, request it, or follow up on it easily.
A strong public information service supports the entire interaction: discovery, submission, monitoring, response, and objection.
Mobile applications can help make these actions more available, but only when the experience is structured around what users actually need to do.
2. Transparency requires a response mechanism
Publishing information is only one part of transparency.
Users may need clarification or may disagree with how a request was handled. Providing question and objection functions creates a more complete accountability process.
The broader lesson is that transparency should include a way for stakeholders to respond, not only a way for organizations to publish.
3. Mobile access can reduce the distance between people and institutions
A mobile service allows users to interact with an organization at the moment a need arises.
This can reduce delays and make official channels easier to use. It can also increase the likelihood that users will choose a structured institutional process rather than informal alternatives.
4. Standardized content improves both user experience and internal control
Clear and consistent content helps users understand the service. It also helps internal teams manage requests and maintain information more reliably.
Content governance should therefore be treated as part of application design, not as an editorial task added after development.
5. Tracking is a trust feature
Users are more likely to trust a service when they can see what happens after submission.
Status monitoring does not guarantee that every request will be resolved quickly, but it makes the process more visible and accountable.
For public information services, that visibility is an important part of the user experience.
6. Cross-platform consistency matters for public access
Citizens and stakeholders use different devices. A service that works well only on one operating system creates an unnecessary barrier.
Developing for both iOS and Android helped PT PP provide a more inclusive digital service and maintain a consistent experience across mobile users.
Strategic Insights for the C-Suite
- Treat public accessibility as an end-to-end service responsibility.
Providing information is only the beginning. Users also need clear ways to request, question, monitor, and challenge information through one connected process. - Make transparency visible through status and response.
A transparent organization does not only publish information; it shows users what happens after they submit a request. Tracking and clear follow-up mechanisms help build public confidence. - Design digital services around actual user actions.
Start with what people need to accomplish, then design the content, interface, and technology around those tasks. This produces more useful platforms than starting with a list of technical features. - Treat content governance as part of digital transformation.
Consistent and current information improves user understanding and internal control. Technology cannot create trust if the content it delivers is unclear or poorly managed. - Use mobile to reduce institutional distance.
When official services are available through a convenient mobile experience, people can interact with the organization more easily and at the moment they need support.
