← Back to all work
Product · CommunityBuilt with the community2026

Yuwoglow

A booking platform for a Karen community's eco-tourism in Mae On, built from the ground up alongside the villagers themselves, replacing a phone-and-Word reservation process with one simple flow.

Yuwoglow cover, site / Mae On landscape
Timeline2026 · Freelance
RoleFull-Stack Developer
StackNext.js · NestJS · Prisma · PostgreSQL · Beam
CommunityKaren villagers, Mae On
Long story short

To build the right thing, I went to the village and stayed a while.

The community ran bookings by phone and Word documents. Easy to double-book, hard to scale. Before writing code I travelled through Mae On, met the villagers repeatedly, interviewed them about their daily life and hospitality, and presented the website back to them to make sure it fit how they actually work.

01Discover

Repeated visits and on-site interviews with villagers in Mae On to understand their life, their guests, and their booking pain.

02Build

One 4-step wizard serving both activities and homestays, with webhook-confirmed payments and inventory held before pay to stop double-booking.

03Present

Walked the community through the finished site so it matched their words, their pace, and how they welcome guests.

On the ground in Mae On

Requirements gathered in person, not over email.

I met the community multiple times, travelled to different spots around Mae On to see the activities and homestays first-hand, interviewed villagers about how they host, and presented the website to them for feedback. These visits shaped every decision in the product.

The build

One flow for activities and homestays. No double-bookings.

One 4-step wizard

Unified two very different products, experiences and stays, behind a single, guided booking flow.

Inventory held before pay

Slots are reserved the moment a booking starts, so two guests can't claim the same night.

Webhook-confirmed payments

Payments confirm via webhook (Beam) before a booking is finalised. No manual reconciliation.

Booking wizard screens
The outcome
Phone → Webmanual process replaced
2-in-1activities + homestays, one flow
0double-bookings by design