Keep the journey connected
The product groups guide discovery, booking, and real-time chat around the same travel task, so a conversation can follow an expression of interest rather than start from scratch.
The problem
Guide Lanka brings the early steps of a trip into one platform: travelers can find local guides, arrange a booking, and continue the conversation there. Guides and travelers need different actions at different points in that journey.
The constraint
Discovery, booking, and conversation each carry context from the previous step. Splitting them into disconnected tools would make it harder to follow a trip from interest to an agreed plan.
Decisions behind the work
Design for both sides
Role-based access gives travelers and guides the actions relevant to them. This keeps the main journey clear while the underlying application handles different responsibilities.
Connect interface and services
The React interface works with Node.js and Express services, MongoDB data, and Cloudflare R2 storage. The case is about making those parts support the visible workflow.
What the work delivers
The built platform brings guide discovery, booking, and conversation into one product journey. No public usage or conversion figures are available, so this case describes delivered capabilities rather than measured impact.
What I took from it
When a product has several participants, the handoff between steps matters as much as any individual screen.
React · Node.js · Express · MongoDB · Cloudflare R2
Next projectInventory Management System