Although that looks very promising, the current Windows Bridge for iOS is only for applications written in Objective C and unfortunately our iOS app is actually almost entirely in Swift, which is still not supported at all:https://github.com/Microsoft/WinObjC/issues/25
Also the current roadmap shows that a lot of core functionality in it is still very incomplete:https://github.com/Microsoft/WinObjC/wiki/Roadmap
In particular, we use the AFNetworking SDK which is also listed without a checkmark next to it yet. I suspect there will also be a few other unlisted areas that we'll encounter problems with, such as our tight integration with Apple Maps SDK.
Additionally, I expect that Apple specific services may never be automatically supportable through their bridge. For example, Apple Push Notifications are used by the app to deliver flight alerts and are specific to their backend server interface. In-app purchasing to allow ad-removal is also going to be very Apple-specific. Both of those would probably need some Windows-specific reimplementation by us for them to work.