Mobile-optimized dashboard and trip pages
The main planning surfaces now feel intentional on phones and tablets instead of behaving like compressed desktop screens.
Building MapMyWander in public
What we're building next
MapMyWander is now stable enough to focus on product depth. This page tracks the work that matters most as real usage shapes the roadmap.
Recently shipped
Recently shipped
The core planning system is live. The product can now spend more energy on depth instead of platform churn.
Completed-trip memory mode
Finished trips can hold reflections, photos, and the emotional afterlife of a journey instead of becoming dead records.
Production itinerary generation
Trip generation is now running through the real backend worker path, which makes the planning flow stable enough to rely on.
Maii in production
The trip assistant is live end-to-end and can now participate in planning through the same production architecture as the rest of the app.
Dedicated backend and worker Lambda architecture
Frontend, API, itinerary generation, and Maii now run as separate responsibilities, which makes the system easier to reason about and harden.
Now
Now
The current focus is making planning more editable, trustworthy, and satisfying after the trip too.
Manual itinerary editing
Travelers should be able to add, edit, delete, and reorder activities inside a day without being forced back through AI generation for every change.
Completed-trip polish and memory depth
Completed trips need richer storytelling surfaces so the product feels emotionally complete after a journey, not just before it.
Maii reliability and clarity
The assistant needs clearer system states and stronger trust signals so suggestions feel dependable instead of magical but opaque.
Next
Next
Once editing is strong, the focus shifts to trip-type-aware planning, sharing, and making itinerary assets more durable.
Trip types for day trips, weekend getaways, and perfect vacations
The planning flow should support short same-day rides, nearby weekend escapes, and full destination vacations as distinct trip shapes instead of treating everything like a long tourist itinerary.
Itinerary sharing
A traveler should be able to share a trip through a clean read-only view instead of stitching together screenshots and copied notes.
Image persistence to S3
Generated itinerary imagery needs to be stored reliably so the experience does not depend on third-party image links that expire later.
Lifecycle notifications
Trips should feel alive between planning sessions through reminders and lifecycle nudges instead of slowly going stale.
Later
Later
These are meaningful expansions, but they should land after the core planning loop becomes stronger and easier to trust.
Multiple flight and hotel options
Instead of showing a single recommendation, the app should surface alternatives so travelers can choose what fits them best.
Booking flow
Long term, MapMyWander should move from planning recommendations into actual booking support with confirmations and follow-through.
Group trips
Collaboration, edit permissions, and split-aware planning belong in the product, but only after the single-user journey feels stronger.
The roadmap will keep moving as we learn from real travelers and real trips.