NewCity

Why it exists

NewCity started with a practical civic question: what should happen between noticing a problem nearby and getting that problem into a system that can respond?

That question made the reporting flow more important than any single screen. People need to know what information matters, what will happen after they submit it, and whether the report is moving.

What I worked on

I contributed to both the UI/UX and the backend. On the interface side, I thought through how someone describes a problem, adds context, and understands its status. On the backend side, I worked with the data and logic that keep those reports connected to the experience.

Decisions that mattered

The useful unit was not a form submission. It was a report with context and a visible state. Treating it that way made the product easier to reason about from both sides.

I also learned that civic interfaces need unusually clear language. A clever interaction matters less than helping someone feel confident that their report was understood.

Where it stands

NewCity represents one of my earliest experiences building a system around a real-world problem. It gave me a foundation for thinking about products as connected flows rather than isolated pages.

What I learned

This project changed the way I look at backend work. The backend is not hidden technical machinery; it shapes what the interface can promise and whether that promise feels trustworthy.