I dont know why you are so dismissive of this
Obviously there are very good future prospects for this project. Why should the US Air Force build separate software packages for each of its aircraft projects?
Why not have a common API where you can use it to build "apps" to control the aircraft's capabilities? That way every time you build a new drone project, there is no need to build a new software for it. You can just standardize its capabilities and then "load" the app to the drone.
The way i envision it is that you can load a "night vision", IR, weapons control (BVR, WVR etc), communications, EW, loyal wingman app, autonomy app, dogfight modules etc
There are a lot of things which can be standardised among the fleet and it would tremendously reduce time and complexity in developing brand new capabilities and upgrades.
I believe that the future is this app-based approach if they can realise standardization on the firmware level and APIs
Maybe I am wrong here, so if anyone knows more about it feel free to correct me
API means "Application Programming Interface".
It is a standardised way for a software to communicate with other software, including the elements of the operating system.
Example, if a software wants to draw a windows then it needs to request a resource from the operating system, by a predefined way , including the precise definition of the functions, methods, parameters, pointers and entry points of DLLs regards of it.
The multitasking capabilities of the operating system implemented as API as well, means example in the windows a thread exist and communicate with other threads through the relevant APIs.
Now, if the air force needs a tablet, with add on software to handle tasks originally designated to the onboard computer , then the API of the F-35 (and considering that it is the most advanced software package of the USA on all other aircrafts) incapable to handle certain functions, expansions , new software or capabilities, because of the bad system design from the begining.
It is like replacing the character CRT and the keyboard on an IBM System/360 with a modern PC, and fake to the bank mainframe a human operator for the online transactions - lot of banks doing this (or the equivalent with additional software).
If you ever wandered why the old, big banks has chunky and primitive online capabilities compared to the Transferwise or REvolut, then here is the answer.