HO

Hans Oheneba

Airban Homes Platform

I built Airban Homes as a full-stack real estate and product platform where users could browse properties and doors, submit enquiries, and where internal staff could manage content through a custom CMS.

View Live Site

Tech Stack

Core technology logos only

Next.js
TypeScript
Tailwind CSS
Python
MySQL
Resend

Project Overview

I built the platform to serve two distinct product journeys: property listings and door products. Although both existed under the same brand, they required different UX approaches.

Properties needed strong visual storytelling and enquiry capture, while doors needed fast catalog browsing and filtering.

The goal was a polished frontend plus a backend that empowered non-technical staff to manage content, listings, and enquiries without relying on a developer.

Built to optimize for

  • Conversion clarityEnquiry-first UX
  • Operational speedCMS workflow
  • Perceived performanceSkeleton states & Loaders

Key Product Decisions

Scroll-driven reveal using Framer Motion

I separated product journeys

Decision 1

Doors and Properties were designed as distinct experiences. Doors emphasized grid-based browsing with clear CTAs, while properties emphasized galleries, location context, and enquiry forms alongside content.

I implemented skeleton loading states

Decision 2

Structured skeletons reduced layout shifting and made the interface feel faster by keeping users oriented while data was fetching.

I built a custom CMS

Decision 3

Internal staff could add, edit, and remove doors and properties, plus update enquiry statuses. Submissions became trackable items rather than scattered email threads.

I designed enquiries as a workflow

Decision 4

Enquiries were stored with statuses like Pending and Resolved, so the team could track operational progress inside the dashboard.

Architecture & Data Flow

The frontend was built with Next.js and TypeScript, while the backend API was developed using Python Flask. The API handled validation and database communication with MySQL.

When users submitted enquiries, the data was stored and triggered transactional emails using Resend. This separation kept the frontend performant and the backend clean, secure, and database-driven.

Data path

  1. 1Browse Doors or Properties
  2. 2Submit enquiry form
  3. 3Flask validates and stores in MySQL
  4. 4Resend sends transactional emails
  5. 5Staff updates status in CMS

Outcome & Impact

The final result was a production-ready real estate and product platform with a structured backend, operational CMS, and a clear conversion-focused user journey. The system reduced dependency on technical staff for updates and introduced a more organized approach to handling customer enquiries.

Visit myairbanhomes.com