Development Battle - Android vs. iOS - Part 4: Deployments, Analytics, and Metrics
Let’s take a look at the last mile of the mobile application process, deploying to users and post deployment.
Let’s take a look at the last mile of the mobile application process, deploying to users and post deployment.
Here’s the recap of the battle of the mobile platforms:
Android
Draw
Draw
Android
I’ll be comparing my experiences with basic debugging across both platforms. What won’t be included are automated testing frameworks or 3rd party tools.
To communicate effectively, you have to know the language. Let’s take a look at the native languages of both platforms at a very high level; For iOS: Objective-C/Swift and for Android: Java.
Developers are vital to each platform’s success, so let’s compare the development tools available for each platform. I’ll cover the pros and cons of each platform, based on my personal experience.
For the better part of 6 years, I have soley been an Android advocate, ignoring iOS at whatever cost. In the last few years, I have been working on a side project (formerly brausr.com) that I thought would benefit from being on both platforms. Over the next series of posts, I’m going to compare and contrast my experience building the same application on both platforms.
Caching in a mobile application serves two important purposes and a good caching strategy should cover both:
The Google Plus app for Android has a nice ListView
animation when scrolling down in a list, ListView
items slide up into place. This transition only happens on list items you haven’t viewed yet and only in the scroll down direction, not in the scroll up direction.
When building a ListView in Android, 9 times out of 10 it’s likely that you’re using a custom Adapter to bind data to your list. By introducing the ViewHolder pattern into your Adapter, you can increase the performance of your ListView substantially.
Overdraw is painting a pixel more than once and it’s very easy to overlook when building an Android application.