Flight Deck ONE – Bravo 3

Flight Deck ONE Bravo 3 is here!

This is the first feature complete beta for Flight Deck ONE.

Feature complete does not mean finished. It means every feature planned for version 1 (the Charlie series) is now in the app, even if some of those features are still rough, partially implemented, or not fully reliable yet. Some parts will work perfectly, some will feel unfinished, and some will be plainly INOP. That is expected at this stage and it is the whole reason this beta exists.

All decks included in this release are there. Not all of them are complete, and some decks or modules may have missing functions, placeholders, or behaviors that are not final. If something looks odd, assume it is still under construction, and please report it.

Store testing is enabled for beta testers. You will not be charged, but we want to test the full purchase flow and entitlement logic. Please start by using the free version first. If you decide to test purchases, “buy” only a few deck packs initially, then move to Premium and test the Premium features. This helps us spot issues step by step, instead of having everything unlocked at once and no way to tell what broke.

A quick reminder of what a beta is, and what it is not. A beta is not a preview of a polished product. A beta is a collaboration. You are helping us find bugs, unclear UX, broken edge cases, and performance issues before the public release. If something crashes, behaves inconsistently, or feels confusing, that is not you doing it wrong. That is you discovering something we need to fix.

Thank you for testing Bravo 3 and for being patient with the chaos. This is a big milestone, and your feedback is what turns a feature complete beta into a version 1 that we can be proud to ship.

All beta testers who actively contribute feedback, reports, or suggestions during the Bravo phase will be credited as beta testers in the Flight Deck ONE release credits and community. This is our way of acknowledging that this app is being shaped together, not just tested in isolation.

Versions and Builds

Bravo 3 is not a one shot release.

Under the Bravo 3 name you will receive frequent updates, often daily, each one increasing the build number. These builds will focus on quick fixes, refinements, and adjustments based on issues discovered by you and by us during testing.

Think of Bravo 3 as a moving target rather than a frozen snapshot. If something is broken today and reported clearly, there is a good chance it will already be addressed in the next build.

When the goals of this beta phase are met, we will move to Bravo 4. It will represent an almost complete product, approaching release candidate quality, where the focus shifts from adding or stabilizing features to final polish, reliability, and usability.

Release Notes

Decks

From the Decks panel, tap More Decks to see all available decks.

At the top you will find the Featured section. Its purpose is to highlight aircraft that are currently the most relevant.

For this beta, “Featured” also means the most complete decks available right now. They are not perfect, but they represent the best starting point for testing. Please begin your testing from these decks before moving to others, which may be more incomplete or partially INOP.

Bear in mind that, as the app itself, all the Decks are in Beta, but some of them are just Alpha, like the Challenger 650. They’re marked as Beta, which internally means “Beta of the Beta”…Play with them as you wish but please, don’t report yet.

Widgets

The main Widgets are feature complete and ready for testing, in particular Camera, Replay, and Volume.

Other Widgets, such as GroundOPS and Simulator, are still work in progress and need further refinement.

Please use the Widgets actively during your testing and let us know which quick actions you feel are missing or would be most useful. Widgets are meant to be fast, glanceable, and immediately actionable, so your input on what should be accessible with one tap is especially valuable here.

Performance

During development it became very clear that Flight Deck ONE is demanding. Real time computation, UI rendering, networking, and continuous data processing all happen together, and not all devices handle this equally well.

The minimum requirement of iPadOS 18 is intentional. It provides a first filter on device age and capability. Unfortunately, some iPads that technically support iPadOS 18, such as older iPad mini models, struggle when Flight Deck ONE is fully loaded.

On these devices we will progressively disable or limit certain features, for example the telemetry track (Black Box), to keep the app usable.

Please help us by reporting:

which device you are using
where performance drops are most noticeable
which features seem to stress the device the most

This feedback is essential to tune performance profiles and device specific limits.

Power & Battery

Needless to say, it is strongly recommended to keep the iPad connected to a power source while using Flight Deck ONE. The app performs continuous real time processing, networking, and rendering, which can drain the battery quickly and may lead to thermal throttling on some devices when running on battery alone.

Keeping the iPad under charge ensures more stable performance and a smoother experience, especially during longer flights or extended testing sessions.

Device Models and Deck Layouts

We are actively testing Flight Deck ONE across all supported iPad sizes.

For deck usability, the recommended devices are the 13″ iPad Pro models, simply because they provide the most comfortable space for complex panels and dense avionics layouts. That said, Flight Deck ONE is designed to work on all supported iPad models.

At the moment, some very large modules, for example the 737 MCP, and certain system panels in the footer area may not fit perfectly on smaller iPads. This is known and actively being worked on.

Please let us know:

your iPad model and screen size
which deck or module you were using
what layout issues you encountered

This feedback is essential to make layouts adaptive and usable across the entire iPad lineup.

Design

The overall design language of Flight Deck ONE is in place, but there is still work ahead. Many areas need refinement, including avionics visuals, panel backgrounds, icons, color usage, and general visual stability.

At this stage, expect inconsistencies and unfinished details. Feedback on readability, contrast, visual hierarchy, and overall clarity is very welcome, as this is the phase where design decisions are still flexible.

Premium Features

My Hangar
Fully functional and in good shape. This is one of the most solid Premium areas in this beta.
Logbook
Logbook tracking is active and usable. Expect refinements, but the core behavior is there.
Black Box (Telemetry)
The Black Box is working. Not all telemetry parameters are exposed yet. Please tell us which parameters you consider essential so they can be prioritized and added.
World Map
Still a work in progress, but looking cool. Perfect for Airport and Navaid search, but also to discover new places where to fly. This requires a free OpenAIP access key. Instructions in the app.
Deck Editor
This will become the most powerful and nerdy feature in Flight Deck ONE. Premium users will eventually be able to create and customize their own decks.At the moment it is rough, unfinished, and not representative of the final experience. Do not spend time on it yet unless you are explicitly curious about its direction.

Other Features

Dashboards

Dashboards are functional and usable, but there is still a significant amount of work ahead. The foundation is there, the structure is sound, but expect changes, refinements, and improvements in both behavior and presentation.

Providers

Providers are probably feature complete. Let us know if we missed some important flight-service out there.

Scratchpad

Scratchpad is complete.

Please take a close look at the phase based templates, which are loosely inspired by ForeFlight. Feedback here is very welcome, especially regarding:

clarity during different flight phases
missing fields or notes
overall usability in real flight scenarios

Control Center

The Control Center (accessed from the top right time badge) is in good shape functionally. Most of the remaining work is cosmetic: layout polishing, visual hierarchy, and small UX improvements. Functionality wise, it is already close to where it needs to be.

These release notes describe the current reality, not the marketing version. Some parts shine, some wobble, some are clearly under construction. That is exactly what Bravo 3 is meant to expose.