iOS and Android, A Comparison for New Mobile Developers

By | February 29, 2012

The interest in mobile application development is continually growing. Even developers who are least open to change are starting to come around to the idea of developing on a mobile platform. Choosing between the two most popular platforms, Android and iOS, isn’t as simple as it may seem on the surface. Developers need to know what to expect from each platform before even starting a napkin drawing of their next great app idea. Between laying out an application’s interface, memory management styles and the native coding language available, understanding the similarities and differences of iOS and Android platforms will help programmers new to mobile development choose which platform is right for them.

The reduced display real estate on mobile devices will affect how a developer approaches conveying information effectively. Developers coming from web or desktop development will find the screen size very restrictive, so they must think farther ahead about how they will layout an application before they even begin coding. The vast range of available display densities and ratios for the Android and the limited number available for iOS will define how a developer new to mobile must approach creating an application’s interface. There are only two layouts for iOS, the iPhone size and the iPad size, and this means less time coding, testing and thinking about layout. However, every other application for iOS has the same restrictions on size and ratios, and that means standing out from the crowd on iOS will require extra design time. Since there are very little hardware restrictions for Android device manufactures, developers working on Android have a wider range of devices they must consider when developing and testing. Creating Android layouts requires thinking flexibly, letting the user interface flow and scale to a wide range of ratios and resolutions. The two platforms are very similar when it comes to cutting a layout into usable graphics, because both support three major pixel densities. Basic Android applications should support high, medium and low pixel densities ranging from 240 dpi (dots per inch) down to 120 dpi, while iOS applications should support the standard display’s 320×480 resolution, Retina display’s 640×960, and the iPad’s 1024×768 resolution. Each platform’s layout methods will define how a developer conceptualizes and creates visually appealing applications.

To make well designed, responsive, and beautiful applications, developers will have to carefully manage their memory. Memory management is approached very differently on iOS than on Android, and developers new to the mobile concept of reduced memory availability on mobile devices need to be aware of how each platform will handle allocations. Android uses automatic garbage collection, which will periodically run to see what objects in memory no longer have references to them and then remove those objects at that time. Some new mobile developers might get the impression that this makes memory management an after-thought, but that would be a mistake, because automatic garbage collection alone won’t keep an application from running out memory. Garbage collection automatically frees up unused objects, but the developer is still responsible for removing all references to objects to allow them to be garbage collected. These devices have very little memory available, and something as rudimentary as displaying images without making sure they are properly removed after they have finished being used will quickly turn into a big problem. iOS applications, which do not offer any form of automatic garbage collection, require developers to keep track of every object they allocate and release it explicitly from memory when they are finished using the object. This means that iOS memory overhead has the ability to always be at its lowest possible point with correct allocation tracking. Keeping track of memory reference counts can add a lot of extra lines of code to an application, but there is a new compiler feature for iOS, called Automatic Reference Counting, which adds these lines automatically at compile time. These two varied memory management styles are a part of each platform’s native programming language.

The native languages, Java for Android and Objective-C for iOS, are both object-oriented languages but offer very different coding styles that will greatly influence a new mobile developer’s decision of which platform they choose to pursue. Objective-C stays very close to its C roots, with each class consisting of a header and an implementation file. The header file defines what code will be written in the implementation file. Java files, which are more modern than Objective-C files, are made of a single class file that doesn’t have any separate header files. Both languages share a set of standard C primitive types like int, bool, char, float and double, which most developers will find familiar. They are both statically typed languages, which means that variables, functions and assignments are checked for type compatibility when the application is compiled. Their object-oriented styles allow developers to utilize a wealth of existing coding patterns such as Model-View-Controller and Singletons. When defining what a particular class will do, Java uses interfaces and Objective-C uses protocols. The interfaces of Java don’t need to be used in simple applications, but in Objective-C, protocols are heavily used because the primary method of passing information around is by way of delegates. While the difference in these two native languages may be great, the similarities of static typing and object-oriented design make either of them worthy choices. A developer who is already familiar with either one of the language backgrounds, Java or C style, might consider learning the other for the different perspective and challenges each language presents on mobile development.

Whether a developer goes with iOS or Android, the mobile space is opening up with new opportunities every day. Every existing company has some application in the mobile world and new companies are being created using only mobile applications. Mobile application development is a valuable skill to have, and a developer looking to stay current and relevant for the future of his or her career will want to learn more. Understanding the differences in how the platforms layout their interfaces, knowing how the memory is managed for each operating system and finding out which native language interests or fits developers best will give an eager developer the push they need to get started now. Knowing the basics about either of these two great platforms will give developers interested in iOS or Android enough information to choose which one they will want to learn more about. Any developer can, with a little research, find the right platform.

2 thoughts on “iOS and Android, A Comparison for New Mobile Developers

  1. capirucho

    In your article you mention that iOS apps do not have ” automatic garbage collection” and subsequently you mention a new compiler feature called ARC for iOS. My question then, is this feature used to automatically collect “garbage”? I have limited programming I guess interpreting this new feature (ARC) as the garbage collector? Is memory management the same as garbage collection?

  2. sosuke Post author

    Automatic garbage collection is a process that happens while the application is actively running. There will be certain times when automatic garbage collection is run in the background of your active application and memory is freed up at that time. ARC, Automatic Reference Counting, is a feature that automatically adds retain and release lines of code at compile time. It doesn’t run any extra process while the application is running. ARC just removes the need to be explicit when writing your code about retaining and releasing memory for Objective-C. Garbage collection is just one style of memory management.

Leave a Reply

Your email address will not be published. Required fields are marked *

Comment moderation is enabled. Your comment may take some time to appear.

This site uses Akismet to reduce spam. Learn how your comment data is processed.