Moovna

Property portals tend to fail in one of two ways: they optimize entirely for search and browsing, or they optimize for listing management. Moovna needed to serve three audiences at once - buyers/renters searching, owners listing a property, and agencies managing portfolios at scale - without becoming three disconnected products. Mapped the full IA first: public site, auth, listing creation across 5 property types and 2 transaction types, discovery, two dashboards, org admin, email - before touching any screen, to find where flows converge and where they have to diverge.

Discovery runs map and list views on one shared, property-type-aware filter model, so switching property type never means relearning the UI. Listing creation uses a single stepper pattern across all property and transaction types, diverging only where the data does. B2C and B2B dashboards share one layout grammar at two densities, with an org/admin layer added on top of B2B only where needed. Contact and booking stay visible on listing detail, next to the gallery, not buried below the fold.

The system shipped to production. Handoff leaned on the shared patterns from design - the stepper, the filter shell, the dashboard layout grammar - so engineering built one flexible component set rather than one-off screens per property type or per audience. Design stayed close through build to catch the places where a "shared" pattern quietly needed an exception.