Mumbo — Pilgrimage Travel Booking
Pilgrimage package bookings had no self-serve online path and no structured way for administrators to review and approve requests before payment.
- Company
- Xangars Infratech Solutions
- Role
- Full-stack developer
- Period
- Nov 2024 – Oct 2025
What I actually owned.
Technology used.
| Frontend | React.jsResponsive design |
|---|---|
| Backend | Node.jsREST APIs |
| Payments | Payment gateway integration |
How it fits together.
- Customer web app
- Admin dashboard
- Node.js API
- Payment gateway
- $ Customer web app → Node.js API
- $ Node.js API → Payment gateway
- $ Admin dashboard → Node.js API (approve / reject requests)
Bookings enter as pending requests; the admin dashboard drives approve/reject before a booking is confirmed and paid.
Decisions & tradeoffs.
Package availability for sacred pilgrimage slots needed a human check that a plain self-serve checkout would have skipped.
Mobile users browsing packages needed fast page loads on the primary conversion path.
Metrics that matter.
What actually went wrong, and how it got fixed.
Implemented validation logic around the payment workflow so failed or partial transactions couldn't leave a booking in an inconsistent state.
Used code splitting and lazy loading to keep the critical booking path light on mobile networks.
Other case studies.
Amber Car Rental
A car rental agency needed to move off manual, phone-and-spreadsheet bookings to a real-time online platform — built and run solo.
Quote Management System
An insurance quotation platform needed to scale past a monolithic frontend as more product lines and teams shipped features in parallel.