First of all, I appreciate Support's prompt response. Thank you for the clarification. How about it? Any other's interested in this feature?
As I understand it, AirNav has four applications each of which specialize in displaying one or more of four different data streams: Live ADS-B, Networked EU ADS-B (delayed), FAA ADSI (delayed), SELCAL/ACARS (live and/or delayed).
Splitting the data streams across 4 applications seems (to me) a disjointed marketing approach, though I speculate that the history of implementation of AirNav's network and technologies has much to do with the evolution of separate products.
If I were standing in an ATC center looking at an operations console, I would expect to see (more or less) every plane in the air within the viewing window of the radar envelope.
Consequently I would like to see a single RadarBox application that emulates this experience as closely as possible and I wouldn't mind paying a premium for this integrated capability. Charge me, if you wish, for enabling different modules/data-streams, but give me a common integrated interface from which to do so.
Having read much of the forums, I understand the issues relating to live versus delayed data. I think the trick would be how effectively AirNav's software development would integrate the various data streams with their various delays into a single integrated customer experience. I don't believe the effort would either be wasted or that complex.
Personally I would give the client the option of turning all or individual data streams on and off as well as provide a mechanism for synching all enabled streams to one common timing delay (or just let the streams display raw/unsynched and let the user sort it out his or her own preference.)
There are a lot of good reasons for doing this from the client side aside from an integrate and enriching virtual ATC experience. For one, an integrated interface would significantly reduce the video paging, cpu and memory allocation overheads associated with four concurrently operating applications.
From a business model point of view, application pricing could be tiered based on the number of modules or streams the user wishes to enable, plus the "upgrade" to an integrated application would contribute added revenues.
Taking the concept one step further, how interesting would it be to button in ShipTracks as an additional module? Just because I am a pilot enthusiast doesn't mean that I don't have an interest monitoring the movements of various cargo vessels bringing in or delivering vendor/client cargo. Then again it's probably 'cooler' to split and display air and water apps between separate PC's or monitors.
Like Prbflight, I think it would be interesting to see how many others feel the same way.
Thanks for listening.