It seems all the various control apps--Go4, Litchi, Dronelink, FT Aviator, you name it--advise the user to force-kill all other apps that use the DJI SDK before starting theirs.
But then I also read of pilots who don't do that and never, in dozens-to-hundreds of flights, have encountered a problem. And my understanding of things suggests that's to be expected: an app in "background" is in suspended state. It should not (can not?) have access to the USB port, or in any other way interfere with the functioning of the foreground app.
My career was in software (I'm retired), but never on iOS or Android, so those ecosystems are a bit of a black box to me. Still, it seems inconceivable that either would permit destructive cross-talk between a foreground app and any background app.
I'd be most interested if an experienced app developer, for iOS and/or Android, could shed light on the question!
But then I also read of pilots who don't do that and never, in dozens-to-hundreds of flights, have encountered a problem. And my understanding of things suggests that's to be expected: an app in "background" is in suspended state. It should not (can not?) have access to the USB port, or in any other way interfere with the functioning of the foreground app.
My career was in software (I'm retired), but never on iOS or Android, so those ecosystems are a bit of a black box to me. Still, it seems inconceivable that either would permit destructive cross-talk between a foreground app and any background app.
I'd be most interested if an experienced app developer, for iOS and/or Android, could shed light on the question!