- Joined
- Mar 4, 2017
- Messages
- 13
- Reactions
- 4
- Age
- 79
It's really a no brainer. Software developers always know about the hardware they're coding for when coding for Apple products, and android developers actually have no chance to know of all the hardware that will be using their software. That has to play a huge part in making apple software alot more stable. Android can very quite a bit between devices.
Android developers don't need to know all the hardware or software they're coding for, they can simply aim for the main hardware platforms (which there's not many of) and restrict to certain OS versions as well then try and handle any of the more unusual or budget platforms. There are plenty of Android software developers that are able to produce stable Android packages that run on a variety of devices including Litchi which has none of the stability problems DJi Go4 has.
The problem isn't Android, it's just sloppy development - DJI Go3, the Mavic and Android worked without issue, the problems started with DJI Go4. To limit hardware issues, DJI only officially support a small number of Android handsets but I have one of them and it crashes the entire handset despite it being stable and no issues otherwise. What's worse is that they have their own Android powered device where they chose all the hardware and DJI Go4 apparently isn't stable on that either, many other Android developers are able to make their software stable on a variety of devices including Litchi. IOS no longer runs on a single platform either as there's an increasingly wide array of different iphones and ipads.
The answer is still IOS, as an Android person who dislikes Apple I'd buy an Ipad Mini 4 as it seems to work well with the Mavic although I'm hanging on to see if DJI improve their software as that's where the problem is, not Android.
Thanks.. svavar. I was agreeing with you. I suspect that DJI coded their devices originally with IOS. ...and why wouldn't they? Porting that code across to a different OS would bring it's own set of issues to resolve. Considering the wide range of Android iterations it's not surprising that not all are approved. [emoji106]I wasn't saying by any meens that there weren't any qualified android developers, I was simply saying that I tought life would be easier as a ios dev because of the devices running ios are fewer and therefor less hardware to think about. This is a fact you'd hardly be able to deny, and as you state,of course there are workarounds / known was that android devs use to make their product and work better and more manageable.
You did good in explaining this matter and where I was wrong, I like details.... Alot[emoji16]
Thanks.. svavar. I was agreeing with you. I suspect that DJI coded their devices originally with IOS. ...and why wouldn't they? Porting that code across to a different OS would bring it's own set of issues to resolve. Considering the wide range of Android iterations it's not surprising that not all are approved. [emoji106]
Most serious Mavic pilots fly using a ipad or tablet. For the most part it's the newbies that use a phone. Currently the ios OS is solid. I'm a android guy and I have used a nVidia K1 Shield until about 4 weeks due to the GO4 app not working with android 7. I also have a mini 2 I bought a year ago and never used it until now. The ios setup feels much more secure while flying.
I'm purchasing an iPad mini 4 just for the Mavic. Too many problems associated with Android, unfortunately.
Ok,
Im with you guys on my experience with iOS versus android but... I had 7 disconnects on 2 batteries Friday with iOS. Switched to the shield and didn't have a problem. May be an anomaly but happened none the less.