Money screens have to be unambiguous
An investor looking at a dashboard needs to know what is committed, what is pending, and what has settled, without guessing. At Reitium I built dashboards for tracking investments, rental income, and account activity, where the hard part is state that reads clearly rather than charts that look impressive.
Investment forms fail in more ways than normal forms
A transaction can be rejected, partially filled, held for review, or fail after submission. Those states have to be visible and recoverable in the interface, because a person who is unsure whether their money moved will stop using the product.
Regulated flows constrain the UI
Minimums, eligibility, and disclosure requirements are product rules that show up as interface rules. Reitium was open to Canadian residents with a one hundred dollar minimum, and constraints like those decide what a form can accept before anything reaches the backend.
Consistency at consumer scale
On the TurboTax redesign, I delivered React frontend work with headless WordPress integration and resolved production issues across multiple releases.
Shared UI with versioning
I built versioned shared component libraries at Reitium so that cards, tables, status states, and account screens stayed consistent as the platform grew, and refactored the frontend architecture and CI/CD workflows to make releases more modular and more reliable.
Getting to a first public launch
The first public Reitium frontend shipped in three months, covering property discovery, account areas, investment forms, and transaction states. Speed at that stage comes from deciding early what has to be right and what can be revisited.