ASODA

ASODA brings property listings, search, and real-estate workflows into a single platform, replacing the fragmented listings and manual processes typical of property discovery.

It was originally built by a team of around seven developers and is now maintained by around ten. I was one of the original developers, contributing across frontend, backend, database, and production delivery.

Frontend (Next.js, TypeScript, Tailwind CSS), backend (NestJS), and the PostgreSQL schema and Prisma data layer — plus SEO and performance work based on keyword research from a specialist on the team. I still contribute across the stack as the platform has grown from seven developers to ten.

A Next.js frontend talks to NestJS backend services over structured APIs, with PostgreSQL and Prisma handling persistence — server-rendered where it matters for public property content and SEO.

The main challenge was consistency across layers — a change to a property workflow could touch the UI, API contracts, validation, and the database models all at once, and requirements kept evolving during development.

We handled it by keeping frontend, backend, and data-access responsibilities separate, with typed code and structured APIs throughout, so individual features could change without dragging the rest of the system with them.

Next.js · TypeScript · Tailwind CSS · NestJS · PostgreSQL · Prisma