Roadmap

Roadmap for future Avitab development

Updated in March 2026.

We are (with @fpw's support and approval) adopting Avitab to continue its maintenance and development. This is the outline of where we might go. Unless we decide to go somewhere else!

Get our first Avitab release published.

• Snapshot the Avitab 0.7.1 release baseline [done].
• Fix issues with clean build of 3rd party libraries (incompatibilities between old packages and newer tools).
• Bring 3rd party libraries up to date (as appropriate - not if Avitab source needs major overhaul).
• Scripts to automate creation of release package(s).
• Write a basic test plan for release verification.
• Restore Navigraph API capabilities.
• Import PRs that are pending in @fpw's repo.
• Update any relevant docs.
• Prepare a 1.0 release candidate and publish for test and feedback.
• Fix any newly introduced bugs.
• Publish (first TeamAvitab) release of Avitab 1.0.

Project structure and build system.

Updates to internal project structure and scripts. Limited visibility to Avitab users. Major impact on contributors!

• Separate repo for building and consolidating 3rd party libraries.
• Use github CI actions.
• Support for Visual Studio (MSVC) and Apple Xcode.

MSFS support

Complete ongoing work to support an Avitab in-game panel in Microsoft Flight Simulator.

UI updates

Migrate to newer version of LVGL. Likely to need considerable updates to Avitab source. Streamline/improve UI.

X-Plane SDK updates

Are there any new X-Plane SDK features that Avitab could make use of, or take advantage of? Updates to older deprecated APIs?