WorkCase study
Milla Homes
A property site for a real-estate agency, built on one rule: make it actually professional.

- 1developer, me
- 4languages
- 6weeks from Figma to launch
Overview
Milla Homes is a property site I designed and built on my own for a real-estate agency on the Costa Blanca. Most property sites are functional and forgettable: dense, slow and built without much thought for the person looking for a home. I wanted to prove that one developer, working carefully, could ship something genuinely professional.
The problem
Most property sites are functional and forgettable.
Most portals feel like database dumps with a stylesheet: dense listing grids, uneven spacing, photos in random aspect ratios and no visible thought for how someone actually searches for a home.
The brief I set myself: a strict design system before any code, several languages from day one, and a CMS so the agency can update listings without ever calling a developer.
Approach
Figma first. Always.
I spent the first week only in Figma: a type scale with two typefaces and six sizes, spacing on an 8px grid, and every component variant from the property card to the filter pill and the gallery. No code until the system was done.
The rule held the whole way: if a decision isn't in the design system, it doesn't go in the product. It felt slow at first. By week three every new page took half the time, because the decisions had already been made.
What I built
Listings, search, four languages and an admin that gets used.
Four parts, each with different requirements and different users.
- ListingsFilter by sale or rent, price and location. Pages are pre-rendered with ISR and revalidate as soon as the admin saves a listing.
- Property pageLazy-loaded gallery, full specs, location and an enquiry form that goes straight to the agent. Structured data for search engines is built in.
- LanguagesEnglish, Spanish, Russian and German. Detected on the first visit and switchable at any point, with its own URL path and sitemap entry per language.
- AdminBehind Supabase Auth. Create, edit and archive listings, upload and reorder photos, answer enquiries. No developer needed for content.


Technical decisions
Why these tools.
A handful of choices shaped the whole project.
- Next.js and ISRProperty pages need fast reads for people and search engines, but listings change rarely. ISR with revalidatePath on save is exactly that pattern.
- SupabaseOne platform for PostgreSQL, photo storage and admin auth. Row-level security means the public API cannot write at all.
- next-intlTranslations in the App Router have real gotchas at the server and client boundary. next-intl handles them and builds static paths per language.
- VercelISR pages come from the edge cache. Preview deploys on every branch let me review the design on a real URL before merging, even working alone.
What I learned
The honest retrospective.
- Design systems pay for themselves. The week in Figma felt like a tax. By week four a new component took 20 minutes because spacing, colour and type were already decided.
- Map cache invalidation before you build it. When the admin saves a listing, the detail page, the listing index and the sitemap all need to refresh. Decide that up front, not after shipping stale data.
- Supabase row-level security is powerful and takes time to understand. Policies are SQL that runs on every query: elegant once it clicks, mysterious until then.
- Real clients use a fraction of what you design. The admin I shipped had fewer features than the prototype, and those are the ones used every week. Shipping less, sooner, is almost always right.