The roadmap update is here! It’s been a busy few weeks following the major Passenger2x update and the performance improvements rolled out to Passenger2 LITE and PRO. We want to thank you once again for the incredible support, feedback, and positivity you’ve shared across our channels. The Passenger2x update has been extremely well received, and we’re grateful not only for the community response but also for the kind words from several press outlets.
In our last post, we mentioned that a roadmap update was coming based on your upratings, and that’s exactly what we’ve now delivered.
One of the biggest changes in this roadmap update is the shift from a monthly roadmap to a quarterly one. This new structure gives us more flexibility to plan larger features without the pressure of monthly deadlines, while still allowing us to release updates whenever they’re ready.
To be absolutely clear:
This structure simply gives us the breathing room needed to plan properly, especially for features that touch multiple systems or require deeper backend work.
Your upvotes have directly reshaped the roadmap. The most popular items are now scheduled within the next three months, reflecting what the community wants most. This roadmap update is built around your feedback, not guesswork.
However, you may notice that a few highly requested features, such as the visual route map, appear later in the year. This isn’t due to lack of interest. Features like these require third‑party services, licensing, and negotiation, which naturally take more time.
The same applies to sound packs for Passenger2x, currently the most upvoted request. High‑quality audio production takes months to produce, edit, and master. It’s still a 2026 feature, but not necessarily an end‑of‑year one. We simply need the space to do it properly.
Please continue upvoting. We review the roadmap regularly and will keep adjusting priorities based on your feedback.
And yes… we saw the recent copycat on Reddit.
We’re flattered. Apparently, other “developers” like our ideas too
This roadmap update also reflects how interconnected many systems in Passenger2x have become. Features that look simple on the surface often rely on deeper structural changes, UI adjustments, or new backend logic. By planning quarterly, we can group related work together, reduce technical debt, and avoid rushing complex features into unrealistic timelines.
It also gives us room to respond to unexpected opportunities, like community‑driven ideas that suddenly gain traction, without derailing the entire schedule.
Transparency is a big part of this roadmap update. Some features, especially those involving licensing, external APIs, or audio production, simply require more time. Rather than hiding those realities, we want to be upfront about why certain items appear later in the year even if they’re highly requested.
As clocks change around the world, different countries switch at different times, and that can make local time displays look a little off inside Passenger2x. This is purely visual.
Passenger2x runs entirely on UTC, just like real‑world aviation.
Local time is cosmetic only and does not affect scheduling, logic, or any internal calculations. We do update our internal timezone database, but because it isn’t API‑driven, those updates only appear when we push a new build. So if your local time looks wrong for a week or two during global DST transitions, don’t worry — your schedules, blocks, and operations remain 100% correct in UTC.
We’ll continue updating the UTC database with each release. Thanks for your patience as the world slowly syncs its clocks again.
