There are people who always fight when it comes to comparing the Android devices vs iPhone. iPhones are way more expensive than Android devices even with the same specifications. However, the iPhone works a lot smoother and faster than an Android device with the same amount of RAM. That means an iPhone with 2GB RAM works much faster than an Android device with 2GB RAM with same features.
If you compare the performance of iPhone 7 (2GB RAM) with Google Pixel (4GB RAM) or Samsung s7 (4GB RAM), You’ll see no difference in performance. iPhone 6 was the best performing phone in its time with just 1 GB of RAM. Now, the question is why does the iPhone require less RAM than Android devices? Why does the Android device need more RAM?
Why does the iPhone require less RAM than Android devices?
It involves many factors. Basically the Garbage collection, App Management, User Interface, and Hardware.
1. Garbage collection
In the case of Android, since it involves garbage collection which requires more memory. The Android apps use Java and as a result, Android does garbage collection. The problem with garbage collection is that memory usage grows until it’s collected, so there might be more memory allocated than necessary. That’s bad for devices with restricted memory and no option to swap.
When the garbage collector runs, it scans the heap to find memory that’s no longer being used, and that’s an expensive process, that slows down the device until it has completed.
The iPhone does not use Garbage Collection. It uses Automatic Reference Counting, which is an innovative way of managing Objective-C objects on iOS. It does away with explicit retain, release and autorelease messages, and it behaves the same on both platforms. Unlike garbage collection, ARC does not handle reference cycles automatically. This means that as long as there are “strong” references to an object, it will not be deallocated. Strong cross-references can accordingly create deadlocks and memory leaks. It is up to the developer to break cycles by using weak references.
Here is the full Difference between ARC vs Garbage Collection.
2. User Interface
An Android user often complains about phone lag but the iOS UI runs so smooth. The main reason is that the iOS UI rendering happens in a separate thread with real-time priority but on Android, this happens in the main thread with normal priority. This means that other apps in Android can take over the processor resources and hurt basic UI interactions, translating into a noticeable lag.
3. App management
Android let developers run processes in the background more freely than iOS. iOS kills any process when it thinks it doesn’t need to be running. Apps that play music in the background or similar can stay alive.
Android gives a lot of freedom to app developers that cause memory leaks or resource hogging background processes which means you need to be careful what you install on your Android device. Android has made some attempts to control this, such as killing apps that use too much CPU, but still, these problems can be noticed by the user.
The iOS puts a lot of limitations on the developers and what they can do causes them not to do much harm.
Apple’s iOS is optimized to run on the hardware, which is also designed and tested by Apple, and manufactured by Apple’s manufacturing partners. Android doesn’t have that level of control because the OS developers are separate from the hardware makers.
5 thoughts on “Why does the iPhone require less RAM than Android devices?”
Given the customisability of Android are there some set of measures that can be taken to mimic the garbage collection algorithm of an iPhone?
very good 😀
This article seems like it was not written by a developer 🙁
Android does update the UI on a UI thread…https://developer.android.com/reference/android/app/Activity.html#runOnUiThread%28java.lang.Runnable%29
Threading strategy has negligible impact on RAM
The description of how background apps are treated is vague and largely incorrect. One of the best parts of iOS is how it doesn’t have to kill processes because it uses RAM efficiently.
Read this article if you’re actually interested https://www.androidauthority.com/android-ios-ram-memory-usage-744848/
you’re making us all look bad… can you please, please do your research extensively? and please be consistent because ui rendering and ui interaction are not the same