Implementing feature requests like this are always a balancing act of how widely the feature will be used in our SkyView installed and potential user base versus our available engineering resources (which are always busy).
Dynon Avionics doesn't just "throw a new feature together" and "slap it into SkyView".
Our first consideration is if a requested new feature is a new capability to SkyView that would make SkyView more capable... or is the requested new feature a refinement of an existing feature, and how many customers could / would use this new feature. In this new feature request, receiving and displaying traffic is already a feature of SkyView, and at the moment very few customers could / would make use of such a feature. SkyView can receive TIS traffic through our SV-XPNDR-261/262 transponders, can receive ADS-B traffic through our SV-ADSB-470 ADS-B IN receiver, and can receive and display traffic from other devices such as Zaon's units.
Adding a new feature is a very deliberate process of specifying the exact way the feature should work / how it should look, doing the engineering work to implement that new feature, and testing the new feature that it actually works the way it should, under all conditions... and most importantly that in implementing the new feature, all the other (existing) features weren't adversely impacted. Then, of course, we add it to our documentation and train our personnel to support the new feature.
It's also somewhat problematic when the new feature requires interfacing with another company's product, such as this new feature request. Doubly so when interfacing requires "reverse engineering" of another company's proprietary interface protocol... it CAN be done (and HAS been done)... but it's a LOT of engineering work. There are always unknown variables in the other product... at times, there are bugs in the other product that have to be engineered around if we want the new feature to work in SkyView the way we think it should.
At the moment, this particular new feature request is not scheduled for implementation. That could change in the future, but we don't want to mislead you that this requested new feature will be implemented in the near future.
That's a pity but thank you for the response.
You use the word "currently", is there any likelihood that will change soon or is the demand simply not high enough?
