Sortie is being built as a planning-first travel app. Our goal isn't to become a toolbox containing every travel utility imaginable. We're focused on making the whole planning journey work beautifully.
This page shows what Sortie can already do, what we're working on now, and what we plan to build next.
Roadmap dates are target windows rather than guaranteed release dates. Priorities may move as we learn from users, uncover technical issues, or find better ways to solve a problem.
The major building blocks of Sortie are already in place.
Create and manage trips with the structure complex travel actually needs. Multi-city and multi-segment planning are core Sortie capabilities.
Organise the trip by day, then shape each day around the stops, timing, and travel between them.
Accommodation can act as part of the trip structure, giving each segment a useful geographic anchor—especially across multi-city journeys.
Keep trip reservations alongside the plan, with booking links, details, and attachments in context.
Browse places, attractions, stays, and experiences with destination-aware results. Viator experience integration adds bookable options to the mix.
Save and organise the places you want to remember, then bring them back into trip planning.
Collections are intended to become the bridge between inspiration and itinerary planning, rather than a folder full of forgotten bookmarks.
Sortie currently covers roughly 800 destinations, with destination search, pages, continent browsing, discovery, suggested-itinerary infrastructure, and Discover/planner integration.
Destination coverage and destination depth are not currently the same thing.
Sortie follows a DB-first model for place search: fetch once, store, improve, reuse. External paid APIs are intended as fallbacks rather than the default source for every search.
Place records bring together identity, destination, location, images, descriptions, facts, search information, and nearby data. Quality and depth currently vary as this foundation improves.
A multi-source image pipeline is being refined around exact-place matching, reuse of already-sourced imagery, quality checks, reliable fallbacks, and storage efficiency.
Public trip pages, public itinerary infrastructure, and generated/template itineraries are developing together.
Publishing more itineraries is not the goal. Publishing good itineraries is.
Sortie works across desktop, tablet, mobile, and small mobile screens, with the planning surface adapting to the way you are using it.
Protect the planning experience before adding more to it.
Before adding more surface area, we are hardening the parts travellers already depend on.
A dedicated phone app focused primarily on the on-trip experience—not simply responsive web work. The initial product will centre on viewing, navigating, bookings, documents, on-trip actions, and offline resilience.
Planning often happens on a larger screen. Travelling does not. The responsive web application will remain the richer planning surface initially, while the native app focuses on the journey itself.
Enriching destinations one city at a time does not scale with approximately 800 destinations. The next platform initiative is to make quality-controlled enrichment measurable and repeatable.
Sortie currently covers roughly 800 destinations, but manually enriching cities one at a time does not scale.
Initial scalability target
~50 destinations per batch
The next enrichment system must prove it can process approximately 50 destinations in a single batch while maintaining measurable quality. If it cannot do that reliably, we don't consider the scaling problem solved.
Better descriptions, traveller-relevant information, categories, official websites where available, location, imagery, visit duration, nearby recommendations, related experiences, Save to collection, and Add to trip.
Save a place, add it to a trip, or add it to a specific day where appropriate.
Multi-select saved places, choose a trip, segment, and day, then get a suggested placement.
Bookings should reference the relevant itinerary stop rather than creating duplicate place records.
Walking, driving, and public transport where practical, with better estimates, transition buffers, a persistent travel mode, and unrealistic schedule detection.
Potential warnings for too many stops, excessive travel, backtracking, sparse days, impossible timing, and poorly spaced commitments.
Fill gaps around existing stops and bookings using location, travel time, duration, and opening information.
Use hotel location, bookings, existing stops, opening hours, visit duration, geographic clustering, trip pace, interests, multi-city segments, and travel between stops.
Reduce backtracking and travel, improve stop order, and preserve bookings and locked/user-selected stops. Changes must be proposed before application.
Potential preferences include relaxed, balanced, packed, food, culture, outdoors, nightlife, family, budget, and luxury. They must influence recommendations, not exist as decorative tags.
Explain useful context such as “8-minute walk from your previous stop,” “Fits the 90-minute gap before dinner,” or “Close to three places you've already saved.”
Offline access to the full itinerary, bookings, addresses, notes, tickets, documents, and selected imagery. The initial mobile app will already aim for basic offline resilience.
Better organisation for tickets, PDFs, booking confirmations, reference numbers, and attachments.
Skip a stop, move it later or tomorrow, replace it, or find something nearby.
Potential reminders for upcoming bookings, time to leave, the next stop, and important travel moments—without overpromising notification functionality.
Shared trip roles such as owner, editor, and viewer.
Shared ideas for restaurants, activities, accommodation, and trip planning. Sortie is not trying to become a social network.
Existing Viator support may grow across experiences, accommodation, tickets, and reservations. Commercial options should appear where they are genuinely useful to the planning process.
Potential premium capabilities include advanced planning intelligence, itinerary optimisation, offline trip packs, collaboration, advanced destination information, additional document storage, and premium map functionality. Packaging and pricing will follow observed product use rather than being locked prematurely.
Quality scoring, publication thresholds, approval controls, destination relevance, and better itinerary structure.
Places, things to do, neighbourhoods, experiences, suggested itineraries, planning information, and collections—with expansion following demand and quality rather than forcing every destination to reach equal depth.
These are ideas we're interested in, but they are not currently committed roadmap items.
Some may become important. Some may never be built. We'd rather solve the core travel-planning experience exceptionally well than accumulate features simply because other travel apps have them.
The roadmap follows the product loop: protect the foundation, make the trip useful in motion, then connect the pieces with care.
Sortie already has most of its major nouns:
Destinations · Places · Collections · Trips · Segments · Days · Stops · Bookings
The next phase is about building better verbs between them:
Discover something
→ save it
→ add it to a trip
→ put it on the right day
→ attach the booking
→ use it while travelling
→ carry the whole thing in your pocket
Want to see the planning workflow in action? Start with a destination, save a few places, and build a trip around them.
Explore destinations
