OpenHaus.
A map-led property platform. Full-stack engineering, from Ireland's county boundaries to the systems behind each listing.
AI-generated architectural concept for OpenHaus. Project artwork, not an application screenshot or a property listing.
Start with a place. Find a home.
OpenHaus brings geographic exploration and property listings into the same experience. The journey moves from Ireland to a county, into a local area, and finally to a home. The map and catalogue follow the same selection, so moving around the map does not mean losing your place.
Keep the geometry. Update the state.
County boundaries contain detailed geographic geometry. Recreating those shapes on each navigation change adds unnecessary work. The map implementation retains county polygons and changes their presentation as the selection changes. Regression tests cover reuse through county navigation, local-area loading and availability changes.
A selection should not rebuild the map.
Property markers are preserved through zoom and selection changes. Highlight updates change the existing marker state rather than reconstructing the whole collection. Tests check marker counts and selected-state behavior. This is a structural performance improvement; no latency or speed multiplier is claimed here.
One experience. Clear responsibilities.
The React and TypeScript client owns interaction and map selection. A Go REST API connects it to PostgreSQL and PostGIS for persistent property and spatial data. OpenAPI documents the boundary. Background media processing runs as a separate asynchronous workflow rather than holding an upload request open.
What I'm taking forward.
The map is the part of this project I'm proudest of: connecting algorithms and data structures to something people can see and use. The next step is to keep testing realistic geographic journeys and measure the experience before making numerical performance claims.