I built and now maintain multiple android apps, some C++ apps, some Asp.net apps etc.
So you can see that why I'm a bit...stretched to the limit.
I wonder why the pilots don't use the app?
Management complains that the pilots only use DJI Fly.
They said something along the lines of (paraphrased for OPSEC):
"I don't know why the pilots using our web service are not using the app? Our app is very complete, packed with features, and have automated features so we don't have to manually upload things every week! You need to tell them to begin using the apps?"
I find this absolutely hilarious because my apps are dogshit. I mean, one person coding two drone apps with different SDKs.
We had to travel to the dockyard to test fly every time, of which the roundtrip transportation takes up to 2 hours, with mosquito swarms (I saw a snake once), blisteringly hot sun, lack of infrastructure (toilet/snacks/drinks), and debugging DJI SDK itself is trial and error, with vague errors and you can't even plug in the USB while flying the drones.
My apps have:
- Shit security (anyone decompiling it can see the passwords because I don't bother with obscuration
- Questionable edge case handling
- Incomplete app logic
- God class variables ensure if the pilots don't use it perfectly, it WILL have memory leaks
- AI generated code with tons of inconsistent code
- Adding listeners on top of listeners
- Clear and create mission just to simulate a special return to home "ritual".
- Lots of different "onMove" handlers that are added within the listeners themselves
- Fake autopilot simulating actions and timing
- Support for multiple maps that straight up have different ecosystems from each other
- Shit tons of defensive coding of "if else"
- Sometimes the app crashes mid air (banzai!!!!)
- Shit tier UI handling and forced landscape/portrait locks. If anyone have a small phone they will see buttons disappear into the corner.
- The best part of it all — the custom flight logger was created to rely on the altitude sensor, so if the drone crashed, no one would be held accountable because no one knows what happened LOL (joke; DJI SDKs have an internal logger)
There are way more features that I am not mentioning for OPSEC reasons, that should have been handled seamlessly by DJI themselves, but the official implementations either do not work or exist at all.
They call this app on the Google Play "flight certificated, professional grade, high accuracy, advanced algorithms, AI, with many missions flown, commercial grade multiaspect protection" (again, paraphrased for OPSEC).
They have the audacity to charge money for the Apps!!!
The marketers want to market this slop to "millions of users" on Play store. Well, I recalled my app causing a drone to slam into a tree (no damage though), so this is a scenario I don't hope for LOL.
I would have fixed some of the errors, but deadlines took over and I have been told "we (that means me) will fix the edge cases later" many times.
Moreover, I repeatedly tell my colleagues that they are hacked together and complicated, that if DJI Sdk doesn't support a particular feature then we shouldn't have a particular feature.
I hope the pile of shit apps are scrapped; not that I care about user experience or something, but to reduce the legal trouble when it inevitably causes a crash.
I still tell my colleagues to tell the pilots to fly high and be ready to switch to DJI Fly when it crashes, but I'll never know if the message was actually sent to the pilots.
"No no it's ok."
So you can see that why I'm a bit...stretched to the limit.
I wonder why the pilots don't use the app?
Management complains that the pilots only use DJI Fly.
They said something along the lines of (paraphrased for OPSEC):
"I don't know why the pilots using our web service are not using the app? Our app is very complete, packed with features, and have automated features so we don't have to manually upload things every week! You need to tell them to begin using the apps?"
I find this absolutely hilarious because my apps are dogshit. I mean, one person coding two drone apps with different SDKs.
We had to travel to the dockyard to test fly every time, of which the roundtrip transportation takes up to 2 hours, with mosquito swarms (I saw a snake once), blisteringly hot sun, lack of infrastructure (toilet/snacks/drinks), and debugging DJI SDK itself is trial and error, with vague errors and you can't even plug in the USB while flying the drones.
My apps have:
- Shit security (anyone decompiling it can see the passwords because I don't bother with obscuration
- Questionable edge case handling
- Incomplete app logic
- God class variables ensure if the pilots don't use it perfectly, it WILL have memory leaks
- AI generated code with tons of inconsistent code
- Adding listeners on top of listeners
- Clear and create mission just to simulate a special return to home "ritual".
- Lots of different "onMove" handlers that are added within the listeners themselves
- Fake autopilot simulating actions and timing
- Support for multiple maps that straight up have different ecosystems from each other
- Shit tons of defensive coding of "if else"
- Sometimes the app crashes mid air (banzai!!!!)
- Shit tier UI handling and forced landscape/portrait locks. If anyone have a small phone they will see buttons disappear into the corner.
- The best part of it all — the custom flight logger was created to rely on the altitude sensor, so if the drone crashed, no one would be held accountable because no one knows what happened LOL (joke; DJI SDKs have an internal logger)
There are way more features that I am not mentioning for OPSEC reasons, that should have been handled seamlessly by DJI themselves, but the official implementations either do not work or exist at all.
They call this app on the Google Play "flight certificated, professional grade, high accuracy, advanced algorithms, AI, with many missions flown, commercial grade multiaspect protection" (again, paraphrased for OPSEC).
They have the audacity to charge money for the Apps!!!
The marketers want to market this slop to "millions of users" on Play store. Well, I recalled my app causing a drone to slam into a tree (no damage though), so this is a scenario I don't hope for LOL.
I would have fixed some of the errors, but deadlines took over and I have been told "we (that means me) will fix the edge cases later" many times.
Moreover, I repeatedly tell my colleagues that they are hacked together and complicated, that if DJI Sdk doesn't support a particular feature then we shouldn't have a particular feature.
I hope the pile of shit apps are scrapped; not that I care about user experience or something, but to reduce the legal trouble when it inevitably causes a crash.
I still tell my colleagues to tell the pilots to fly high and be ready to switch to DJI Fly when it crashes, but I'll never know if the message was actually sent to the pilots.
"No no it's ok."
Last edited:
