The API could allow external applications to communicate data to i_fly such as indicated airspeed, angle of attack, engine performance, CHT, EGT, Fuel Levels, Gear position, OAT, etc..
I-Fly could use this information to develop a black-box feature to capture flight information and integrate it with existing tracking information.
Additionally, it could invoke application controls such as opening a check list or switching to another view as directed by an external app. An example would be an external voice activated application that would allow the pilot to speak commands to i-Fly instead of using the touch interface.
I am interested in developing such an application that would monitor the intercom audio and send API commands to I-Fly via Wi-Fi and/or Bluetooth connection.
I-Fly could use this information to develop a black-box feature to capture flight information and integrate it with existing tracking information.
Additionally, it could invoke application controls such as opening a check list or switching to another view as directed by an external app. An example would be an external voice activated application that would allow the pilot to speak commands to i-Fly instead of using the touch interface.
I am interested in developing such an application that would monitor the intercom audio and send API commands to I-Fly via Wi-Fi and/or Bluetooth connection.