My role
Product Designer & Full-Stack Developer
Project year
2026
Original scope
5 months
Context
Personal product
VillaHub — public website screenshot
Original screenshot of the public website, captured 15 November 2026. The live product may change over time. Visit the live site

Overview

VillaHub connects guests, villa owners, affiliates, and internal teams in one booking system. Web and mobile applications let guests discover and book villas while owners and staff manage day-to-day operations.

I designed and built the ecosystem: Laravel back end and administration, booking engine, multi-role permissions, and React Native applications. The scope also included the App Store and Google Play release process.

The ecosystem includes two distinct mobile clients. VillaHub App serves guests and affiliates through React Native CLI. VillaHub Partner uses Expo/React Native for owners, field staff, and coupon partners, with role-specific operational workflows.

The challenge

Bookings were spread across chats, spreadsheets, and manual payment checks. Owners lacked visibility, affiliate attribution was difficult, and finance teams reconciled records manually. The system needed to connect these workflows while showing each role only the actions and information it needed.

My contribution & approach

A Laravel back end provides role-based permissions and dedicated dashboards for guests, owners, affiliates, marketing, and finance. The booking engine manages availability and reservations; referral attribution supports commission reporting.

React Native applications share one codebase and the same REST API across iOS and Android. I managed the release process for both app stores as part of the end-to-end delivery.

Architecture & technical decisions

Booking consistency at checkout

The checkout path acquires a per-villa cache lock, rechecks availability, and creates the reservation in a database transaction. Pending bookings can have an expiry job, while a stored stay-price snapshot preserves the booking’s price context.

Separate clients for separate jobs

The guest/affiliate app covers discovery, reservations, e-tickets, rescheduling, and commission views. The partner app gives owners and field staff availability calendars; owner finance views are read-only. Coupon partners have a separate dashboard, camera scanning, verification, redemption, and scan history.

Authorization and coupon state on the server

Laravel API routes distinguish guest, owner, field-staff, affiliate, and coupon-partner access. Coupon redemption repeats validation within a transaction using a row lock, checks partner ownership and coupon status, and records scan outcomes. The mobile interface is not the sole boundary for those rules.

Outcome

Launched a booking platform with web, iOS, and Android access. Reservations, owner operations, affiliate tracking, and finance workflows live within one ecosystem instead of separate manual channels.

What the platform includes

  • Villa listings, availability, and reservation management
  • Separate dashboards and access controls for five user roles
  • Affiliate referral tracking and commission reports
  • Finance views for bookings and payouts
  • Shared REST API for web, iOS, and Android
  • React Native apps and app store deployment
  • Dedicated partner app for owners, field staff, and coupon partners
  • Availability editing and read-only owner finance views
  • QR/barcode coupon verification, redemption, and scan history
  • Push-notification routing to bookings, villas, and the notification feed

Technology

Laravel · PHP · MySQL · REST API · Sanctum · React Native CLI · Expo · TypeScript · Firebase Cloud Messaging

Visit the live site

Related reading

Back to selected work

Have a role or project in mind?

For opportunities, collaborations, and conversations about software.

Get in touch