lunar-tourist

byMausham Gajmer

Build a Nepal travel app with 3 secure roles: 1. Tourist 2. Partner 3. Admin Login and sign-up rules: - Tourist has sign-up and login. - Partner has separate sign-up and login. - Admin login is private and only for the owner. - Add forgot password. - Add email verification. - Add optional phone verification later. - Store role and account status in the user profile. - Use role-based redirects after login: - Tourist -> tourist dashboard - Partner -> partner dashboard - Admin -> admin dashboard Account status values: - Pending - Active - Suspended - Rejected Access rules: - Tourist can only see own trips and requests. - Partner can only see own hotel or transport requests. - Admin can see everything. - Never expose admin data to tourists or partners. Security rules: - Protect all private data. - Add privacy rules for every private data type. - Add audit logs for sensitive changes. - Add notification records for all important events. General app rule: - Never auto-confirm bookings. - Never invent prices. - Never promise availability. Now design the full login system, role system, account-status system, and page routing.Build the tourist-facing Nepal travel assistant. First questions: 1. How many days are you staying in Nepal? 2. What is your total budget? 3. How many people are traveling? 4. What type of trip do you want? - Culture - Nature - Mountains - Wildlife - Pilgrimage - Mixed Main destinations: - Kathmandu Valley - Pokhara - Chitwan - Lumbini - Everest Region - Janakpur Trip logic: - Culture -> Kathmandu Valley, Lumbini, Janakpur - Nature -> Pokhara, Chitwan - Mountains -> Pokhara, Everest Region - Wildlife -> Chitwan - Pilgrimage -> Lumbini, Janakpur, Kathmandu Valley - Mixed -> combine destinations based on days and budget For each recommended destination, show: - short history - main attractions - best transport - approximate travel time - hotel category suggestions - ideal trip length - why it fits this traveler Itinerary logic: - Make realistic day-by-day plans. - Do not overload the schedule. - Include morning, afternoon, and evening. - Include transport if needed. - Include hotel category suggestion. - Include a short reason for each day. Hotel logic: - Show only categories unless verified prices exist. - Categories: Budget, Mid-range, Premium, Luxury - Never invent room prices. Transport logic: - Suggest road, tourist bus, private car, domestic flight, taxi, airport pickup, shared vehicle, or trekking on foot. - Explain transport simply. - Use approximate travel times only if known. Booking request flow: Collect: - Name - WhatsApp Number - Travel Dates - Number of People - Budget - Places to Visit - Hotel Preference - Transport Preference Then generate a booking request summary for manual review. Never confirm automatically. Never promise availability. Tone: - Friendly - Professional - Simple English - Honest - Helpful Output order: 1. Quick understanding of the trip 2. Best destination recommendations 3. Why each destination fits 4. Day-by-day itinerary 5. Hotel suggestions 6. Transport suggestions 7. Important notes 8. Booking request optionBuild the hotel/transport partner portal and the admin dashboard. Partner login rules: - Partner signs up separately. - Partner account stays pending until admin approves it. - Only approved partners can log in. Partner dashboard: - New requests - Request details - Reply or ask for more info - Availability notes - Hotel profile - Commission notes - Booking history - Notifications Partner rules: - Partner can accept, reject, or ask for more info. - Partner can update own profile and hotel details. - Partner cannot access admin pages. - Partner cannot see other partners’ data. - Partner cannot auto-confirm bookings in the tourist app. Admin login rules: - Admin access is private and only for the owner. Admin dashboard: - New trip requests - Pending booking requests - Approved requests - Rejected requests - Partner hotels - Partner transport providers - Itinerary templates - Destination content manager - FAQ manager - User messages - Revenue / lead tracking - Reviews / feedback - App settings - Version updates - Manual override / human support - Analytics Admin actions: - View all requests - Review bookings manually - Assign requests to partners - Track replies - Manage destinations - Edit itinerary templates - Update transport options - Update hotel categories - Add/remove partners - Export summaries - Manage app versions - Control AI wording - Suspend/activate accounts Status system: - Draft - Submitted - Pending admin review - Sent to partner - Partner replied - Awaiting tourist response - Approved by staff - Rejected - Closed Now build the complete partner workflow and admin workflow with strong privacy and access control.Add advanced features to the Nepal travel app. Advanced features: - Email verification - Phone number verification - Multi-language support - Saved itineraries - Push notifications - Offline itinerary access - Emergency support screen - Helpdesk / support inbox - Admin edit feature - Partner review and rating system - Message notifications - Premium paid support - Trip saved alerts - Draft booking requests - Audit logs - Version history - Content editing by admin only - Partner document verification - Loyalty or repeat traveler support Logic rules: - Verification should happen before account activation. - Multi-language support should switch UI text and destination content. - Saved itineraries should belong only to the logged-in tourist. - Notifications should trigger on request status changes. - Offline access should show saved itinerary data. - Emergency support should show local help, contacts, and travel safety info. - Admin edit tools must be visible only to admin. - Partner reviews should be visible only to approved users and admin. - Premium support should be a paid or manual upgrade later. - Audit logs must record important changes. - Version history should allow rollback. - The app must remain honest and never invent prices or availability. Now design these advanced modules as secure and role-based features.