Trip planning
Keep trip creation, dates, itinerary days, and activities clear enough for a real vacation plan.
Public roadmap
A public roadmap for reliable trip planning.
We publish only the work that belongs on the public product path: stabilize the planning workspace, improve collaboration and finance views, then explore mobile and smarter planning without fixed-date promises.
Public snapshot
Current beta
The web app is open for trip planning while the core workflow is being polished.
No fixed dates
Items move when real usage shows that a different sequence would ship a better product.
Experiments are separate
AI, maps, offline mode, and integrations stay research items until they are scoped.
Now
Stabilizing the planning workspace people already use.
The current focus is not a long list of promises. It is making the web product dependable for real trips: itinerary management, travelers, transport, budgets, expenses, analytics, and invitations.
People and access
Make travelers, collaborators, roles, and email invitations understandable without mixing travel participation with edit access.
Budgets and logistics
Improve planned budget rows, real expenses, analytics, and transport legs as one practical planning flow.
Milestones
What is live, what is next, and what remains later.
This roadmap avoids exact dates and keeps speculative work out of the committed path. Public items stay broad enough to be honest and specific enough to be useful.
Now
In progress
Core planning workspace
Stabilize the product surfaces that make PYNTravel useful before adding larger product areas.
- Web trip planning
- Day-by-day itineraries
- Travelers and shared access
- Planned budgets and real expenses
Next
Next
Make real trips easier to run
The next milestones focus on reducing friction once users are planning with actual people and actual costs.
- Public web beta polish
- Better onboarding
- Clearer collaboration controls
- More polished finance views
Later
Later
Companion surfaces and portability
These items are useful directions, but they should follow a reliable core web experience.
- Native mobile companion
- Export options
- Account and privacy improvements
- Optional paid upgrades
Exploring
Research
Ideas under consideration
These areas are intentionally not promised until they have a clear product shape and implementation cost.
- Smarter planning assistance
- Maps and route improvements
- Offline access
- Booking and integration research
Principles
How items earn a place on this page.
Public means credible
We list work that is live, in progress, or close enough to be explained without pretending dates are fixed.
Reliability first
Trip planning, finance, access, and transport have to work well before bigger automation is announced.
One shared product model
Web and mobile clients should use the same trip data, roles, travelers, expenses, and invitation logic.
Research is labelled research
AI, maps, offline sync, and integrations stay clearly marked as exploration until they are scoped.
Research
Directions we are not promising yet.
These are useful product directions, but they should not read like commitments before we know the scope, cost, and user demand.
- Smart planning assistance
- Research how suggestions could help without replacing deliberate trip planning.
- Maps and routes
- Explore route context for days, activities, and transport legs.
- Offline companion usage
- Evaluate what travelers need when connectivity is unreliable during a trip.
- Booking integrations
- Consider imports or integrations only where they reduce manual planning work.
- Exports and documents
- Study portable trip summaries, confirmations, and finance reports.
Public plan
Create account
The roadmap is directional, not a release contract.
Roadmap items can change as we learn from real trip planning usage. We prefer to ship reliable planning tools before announcing larger integrations or automated features.