Frontend lessons from the ERP trenches

I've spent a good chunk of my career inside ERP and billing systems — Angular + Spring Boot, PrimeFaces + Java, fiscal compliance, thousands of daily users. It's unglamorous, and it made me a better engineer. Here's what carries over to any frontend.

1. Data integrity is a UI concern

In enterprise software a wrong number isn't a bug, it's a liability. That mindset — validate at the boundary, make illegal states unrepresentable, never trust the client alone — makes consumer apps better too.

2. Performance is about the slowest query, not the prettiest animation

Optimizing Oracle queries and schemas improved one system's performance by 40%. The frontend felt "fast" only because the data path underneath got fast. Know the whole stack your UI sits on.

3. Accessibility and cross-browser support are requirements, not polish

Enterprise users are on whatever browser IT gave them, often all day. WCAG, keyboard flows and cross-browser testing aren't a nice-to-have — they're the job.

4. Boring, consistent components win

ERP UIs live or die on consistency: the same table, form and validation patterns everywhere. A small, well-documented component system beats a clever bespoke screen every time.

Takeaway

Enterprise constraints — correctness, scale, accessibility, consistency — are just good engineering with the volume turned up. Build like the data matters, because it always does.