NewCity

Starting with Bandung

NewCity started as a capstone project with friends at university. We began by exploring the Sustainable Development Goals, looking for a direction we could develop into a project together.

We focused on problems people encountered around Bandung but often left unreported. Sometimes they didn’t know where to send a report. Sometimes they simply left the issue alone. We wanted to explore a clearer path between noticing a problem and getting it to someone who could handle it.

How a report would move

The proposed flow connected a resident’s mobile app, a web admin dashboard, and a separate mobile interface intended for government staff.

A resident would submit a report from the mobile app. It would arrive in the admin dashboard, where an admin would check whether it was valid. Valid reports would then be forwarded to the staff interface for monitoring and handling.

That review step sat between the public submission and the follow-up. Each interface had a different part in the same reporting flow.

My contribution

I worked on the web admin dashboard UI and contributed to the backend. The dashboard covered the review stage, where incoming reports would be checked before being passed on.

The admin dashboard used Vue 3 and Bootstrap, with a Laravel 11 backend providing the reporting APIs. The team’s mobile app was built in Flutter.

As a student team, we shared responsibilities and helped across different parts of the project.

Where it stands

NewCity remained a campus capstone project. It wasn’t used as a public reporting service, and the reporting flow described here was our proposed approach rather than a service operating in Bandung.