Travel & booking · Nov 2024 – Oct 2025
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.
Built the React.js frontend and Node.js backend APIs; built the admin dashboard and payment validation logic.
Technology used.
| Frontend | React.jsResponsive design |
|---|---|
| Backend | Node.jsREST APIs |
| Payments | Payment gateway integration |
How it fits together.
Components
- Customer web app
- Admin dashboard
- Node.js API
- Payment gateway
How they connect
- $ 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.
Admin approval step before payment confirmation
Package availability for sacred pilgrimage slots needed a human check that a plain self-serve checkout would have skipped.
Code-splitting and lazy loading across the booking flow
Mobile users browsing packages needed fast page loads on the primary conversion path.
Metrics that matter.
5,000+
Monthly users
Mobile, tablet, desktop
Devices
Code-splitting + lazy loading
Performance work
What actually went wrong, and how it got fixed.
Validating booking transactions cleanly through a third-party payment gateway.
Implemented validation logic around the payment workflow so failed or partial transactions couldn't leave a booking in an inconsistent state.
Keeping the booking flow fast across mobile, tablet, and desktop for a broad, non-technical user base.
Used code splitting and lazy loading to keep the critical booking path light on mobile networks.