Well, we have some new information to further explain it for folks who may not understand that the gap still exists.
Earlier this week, app developer Infinum published a blog post detailing the differences between developing for an iOS device and an Android device. You can probably guess the outcome, but it’s the specific numbers that really sparked my interest.
Looking back over its last six projects, each of which was released on the App Store and the Google Play store, Infinum found that on average, the Android versions of the apps required 38% more coding than the iOS versions.
More in the article, worth your time (should you choose to read it). Some bonus bullet points below–
Just more code – applications for Android are written in Java, which is simply a more verbose language than Objective-C or Swift. You’re bound to write more code. More often than not, having to write more code means working longer and more potential bugs.
Emulators are slower – even with GenyMotion, Android emulators are just slower than iOS simulators. This is just a factor that slows down the overall development.
Fragmentation – more devices to test against, more potential vendor-specific bugs (“Damn, this only shows up on this random Chinese phone you can only buy in Lithuania!”)
XML layouting – on Android, layouts are primarily written manually in XML, so WYSIWYG techniques are used less than on iOS.
Swift, Apple's new language, is going to keep Apple ahead in this respect, as well. I feel it's worth noting that this information isn't something BGR produced, it's something BGR shared from a developer blog. Just in case someone were about to foolishly use the crutch-word, "Bias."
Log in to comment