ForUI and the Civic App That Couldn't Wait

Building a civic engagement app for a Romanian municipality isn't about winning design awards. It's about shipping something that actually gets residents to report potholes instead of complaining on Facebook.
When I started e-Rădăuți, I had no designer. I had a tight deadline. And I had a long list of features: issue reporting with GPS, real-time bus schedules, air quality data, event calendars, direct contact with the city. The last thing I needed was to spend two weeks bikeshedding button styles.
That's when I picked ForUI.
The Problem I Was Trying to Solve
I needed a design system that felt whole - not a collection of random components. Users reporting infrastructure damage need to feel like they're using something legitimate, something the city actually built. No janky forms. No inconsistent animations. And I needed all of this without hiring a designer or spending weeks on the design phase.
Most design systems at this scale feel like they're fighting you. Material Design is safe and massive, but it requires decisions at every step: color tokens, typography scale, spacing rules. ForUI just... had opinions. Good ones. And I could get started in an afternoon instead of spending a week arguing with myself.
What Actually Saved Time
I built the core reporting flow - upload photo, pin location, fill form - in three days. Not because I'm fast, but because I wasn't making design decisions. ForUI's form components, inputs, buttons, and modals already worked together. The animations weren't gratuitous; they felt like they belonged. I could focus on the real problem: making it easy for someone to report a broken streetlight.
The same coherence helped when we built e-Sânpetru, a white-label version for another municipality. We literally changed the color palette in the ForUI theme config and shipped it. That's not hype. That actually happened. What would have taken days of finding every hardcoded color and inconsistent button style took an hour.
Where It Fell Apart
Then we needed a day-hour calendar view for local events and bus schedules. ForUI doesn't have it. And you can't fake a calendar - it's a complex beast with edge cases everywhere.
I built it from scratch. And here's the honest part: because ForUI's design language is so consistent, building a custom widget didn't feel like duct-taping something onto a car. It fit. The spacing, the animations, the way text sized itself - I could extend the system instead of fighting against it.
The Actual Payoff
A design system doesn't need every possible component to be valuable. Its value is skipping decisions for the 80% of the interface that's routine. A civic app earns residents' trust by working reliably, not by having good-looking buttons.
ForUI gave me that foundation fast. I spent my energy on the hard problem - routing reports to the right department, aggregating real-time schedules, making GPS location work - instead of grinding through design decisions.
When to Use It (and When Not To)
Use ForUI if:
- You're building fast and need a cohesive look without a designer
- You want to ship multiple white-label versions (the theme system is legit)
- You're okay with a modern, minimalist aesthetic
- You have flexibility to work around missing components
Skip ForUI if:
- You need total visual differentiation from day one (you're fighting the system)
- Your brand identity is really specific (custom design system from scratch might be better)
- You want Material Design familiarity (ForUI is a different language)
The Honest Takeaway
Would I use it again? Yes. On the next municipality rebuild, probably immediately. The productivity gain came from skipping a week of deciding if my button padding was right, not from writing code faster.
ForUI works because it's opinionated but flexible. It doesn't try to be everything. And for civic engagement software, where the goal is functionality and trust, not brand differentiation, that's exactly what you need.
If you're in a similar boat - tight timeline, no designer, need something that feels polished - it's worth spending an afternoon with ForUI's docs. Might save you a week you didn't know you had.