MIMRAHU V14 maps the customer journey from search to confirmation. It is designed so real provider APIs, affiliate links, payments and booking records can be connected without rebuilding the customer experience.
Every step is designed to keep the customer informed before handing off to a provider or completing an integrated booking.
These cards show the shape of real inventory. Prices and availability below are illustrative until a live provider is connected.
MIMRAHU will keep provider-specific complexity behind one normalized interface.
The customer should compare value, not decode different provider formats.
Depending on the partnership model, MIMRAHU can either complete the booking through an integrated flow or send the customer to the provider's approved booking experience.
A clear path from a travel search to a confirmed booking, with room for both API bookings and affiliate/provider handoffs.
This is the page a customer should see immediately before committing to a booking.
MIMRAHU can support different commercial models as the business grows.
Customer stays inside MIMRAHU while an approved API handles availability, reservation, payment and confirmation.
MIMRAHU sends the customer to an approved partner with tracking so the booking can be attributed correctly.
Next development work is to research eligibility, API access, coverage, commercial terms and technical requirements.
Property, room, rate and availability inventory.
FIRST PRIORITYSchedules, fares, routes and booking/referral options.
RESEARCHTours, attractions and destination experiences.
RESEARCHRental and transfer inventory with location filters.
RESEARCHSave options now; connect confirmed bookings and itinerary data as real providers are integrated.
V16 adds the customer-facing payment and revenue layer. The interface is ready for a real payment provider once MIMRAHU connects its backend.
The checkout can support different revenue models depending on the provider agreement.
A simple model for the future backend.
The internal layer for managing bookings, revenue, providers and marketplace performance.
Illustrative dashboard metrics for the future MIMRAHU business.
Providers can eventually manage inventory, performance, bookings and settlement information through their own portal.
Rates, rooms, availability, booking status and property information.
INVENTORYSearch coverage, fare data, ticketing/referral performance and reporting.
FLIGHTSActivities, capacity, schedules, prices and booking performance.
ACTIVITIESV15 gives customers a personal space for saved places, upcoming bookings and complete itineraries.
Delhi → Goa · 12–15 November
Customers can save hotels, destinations and experiences without booking immediately.
Saved destination · 3 properties
Saved destination · 6 experiences
Saved destination · 4 stays
V18 turns the responsive website into an app-like mobile experience, with fast search, bottom navigation and a future installable PWA path.
Stays · experiences · restaurants
Hotels from ₹3,900 · 4.7 ★
V18 is structured so MIMRAHU can later become an installable Progressive Web App, with a web manifest, service worker, offline shell, push notifications and app-style navigation.
Optimized mobile pages.
PWA-ready direction.
Trip and booking notifications.
Quick access to itineraries.
The next technical layer can turn this design into a true app-like experience.
Compact search UI designed for one-handed use and quick destination changes.
With permission, surface nearby stays, attractions and transport without exposing precise location unnecessarily.
Future notifications for booking confirmations, itinerary changes and reminders.
Future manifest, service worker, caching and install experience for supported devices.
Before MIMRAHU goes public, the prototype needs a real backend, secure infrastructure, verified providers, legal pages and production assets.
Verify API/affiliate contracts, credentials, rate limits, inventory coverage and booking rules for each category.
Store accounts, searches, bookings, saved trips, provider references, commissions and support records securely.
Connect a compliant payment processor, webhooks, refunds, reconciliation and fraud/risk controls.
Use HTTPS, secure authentication, secrets management, least-privilege access, logging and regular security reviews.
Prepare terms, privacy policy, cancellation/refund rules, provider disclosures, cookie controls and required business disclosures.
Replace prototype imagery with owned or properly licensed photos, finalize the MIMRAHU logo and confirm domain/trademark strategy.
Keep development separate from the live customer website.
MIMRAHU should be built so sensitive information is handled by the right systems instead of being stored unnecessarily in the website.
After production checks, V20 can bring the complete customer journey together for a real launch.
The complete MIMRAHU product vision is now brought together: travel discovery, comparison, booking flow, customer accounts, My Trip, payments, partner operations and a mobile-first experience.
V20 is the final planned product milestone in this prototype roadmap. It combines the work from V1 through V19 into one launch-oriented experience.
Search stays, flights, activities, cars and packages with a consistent MIMRAHU interface.
Save destinations, manage bookings and keep the complete itinerary in one customer account.
Designed for integrated API booking or approved affiliate/provider handoff with secure payment infrastructure.
Provider connections, inventory, performance, booking and settlement workflows.
Bookings, customers, revenue, providers, support and operational reporting.
Responsive web experience with a future PWA/app path for customers on the go.
These are the real-world tasks that must be completed before calling MIMRAHU a live booking business.
The prototype is complete. The next stage is no longer another visual version—it is building and connecting the real systems behind it.