ShiftBOiContact

Selected ProjectsSKNAT

SKNAT

Full-stack product build

The Overview

Finding a home should feel clear not fragmented.

SKNAT unifies public discovery with seller and admin operations — search, map, compare, and back-office in one Next.js + MySQL system.

1 APP FOR BUYERS + OPS · 2025

Browse, compare, and manage listings end to end

A single product surface for discovery and operations — so agents aren’t stuck in one tool while buyers live in another.

Details

Browse, compare, and manage listings end to end. A single product surface for discovery and operations — so agents aren’t stuck in one tool while buyers live in another.

Search, map, favorites, compare

Filters that match how people actually hunt homes — transit, district, bedrooms — plus side-by-side compare.

  • Map · DISCOVERY

Back-office in the same product

Listings, media, location picking, and role-aware portals without bolting on a second codebase.

  • Roles · ADMIN · SELLER

Modern web ops foundation

Next.js front-to-API with Dockerized MySQL — designed to be demable, deployable, and extendable.

  • Stack · NEXT + MYSQL

Real estate without the tool sprawl

SKNAT is a Thai real-estate platform built so buyers can explore properties with confidence while sellers and admins run the business from the same system.

The public side feels like a polished marketplace: search, map browsing, favorites, and compare. The private side covers inventory, inquiries, and sales workflows — without forcing a separate legacy admin forever.

Discovery and operations usually divorce each other

Too many property products look great on the landing page and fall apart the moment an agent needs to update a listing or an admin needs to see what happened to a lead.

SKNAT’s bet was simple: one coherent product loop. If the buyer experience and the ops experience share models and UI language, the whole company moves faster.

End-to-end product surfaces

I worked across the stack — from the public browsing experience to role-based portals and API routes that keep listings, members, and transactions honest.

The interesting part wasn’t any single widget. It was making filters, maps, and compare feel premium while still wiring CRUD, media, and permissions that hold up past a demo.

  • Public property discovery with map and comparison flows
  • Seller / admin tooling for listings and operations
  • Auth and role separation for different operators
  • Dockerized MySQL foundation for local and staged runs

Full-stack ownership on a real domain

This project shows how I approach product engineering: start from user jobs (find a home, list a home, close a lead), then shape the data model and UI so those jobs don’t fight each other.

Sensitive business data and private credentials stay out of this write-up. What belongs here is the craft — architecture choices, UX decisions, and the ability to ship a multi-role marketplace shape.

Client-ready product thinking

SKNAT is the kind of build clients and employers recognize: a domain people understand, a surface that looks intentional, and a backend story that isn’t hand-wavy.

It demonstrates I can take a messy real-world workflow and turn it into something people can click through without apologizing for the admin side.

Stack
  • Next.js
  • React
  • TypeScript
  • MySQL
  • Docker
  • Tailwind