By Joe Levi | November 14, 2013 2:35 PM
I talk with a lot of people about mobile technology (a LOT of people), and I read a lot of comments. A common thread that comes up when people learn that I’m Joe the Android Guy™ is the sentiment that “Android is laggy”. So let’s set the story straight: Android isn’t laggy — but your cheap phone or tablet may be.
The problem isn’t with the operating system. Android itself is plenty snappy, but Android does things a bit differently than other mobile operating systems. Android runs tasks all the time, no much unlike most modern desktop computers. The more tasks you’re running, the slower your entire system gets. User interaction tasks, like key presses and mouse clicks, have to get in line just like every other task. Most of the time this approach works great, but sometimes things can get bogged down. When you run a lot of apps with a lot of tasks, lines can get long.
The perception of speed
Think of your favorite reseller during a huge shopping day. Lines are long — ridiculously long. It doesn’t matter how smooth the checkout process is, or how friendly the people in line with you are, you’re going to be there a while — just like everyone else.
If someone has a HUGE basket, or they have problems with their payment, or the system can’t find one of the products they’re trying to purchase, that line backs up. People have to either wait, or change to other lines so they can keep moving. That’s the way your desktop and laptop computer work, and it’s pretty much the same for Android. The solution? Open more lanes and optimize the process, right?
Apple’s iOS is different, it puts its emphasis on the user interface above everything else. Essentially, any interaction by the user causes every other task to stop and wait for the user interaction to complete. In our shopping analogy, it would be like walking into the store and every employee stops what they’re doing to focus completely on you. That sounds wonderful, as long as you’re the one who gets all the attention. Everyone else hates you. This gives the impression of a smooth and fluid experience, but tasks actually take longer to complete under this model than under the model that Android uses.
As long as your Android-powered device has sufficient hardware under its proverbial hood, you should be fine. A 1.2GHz dual-core processor (or above), a GIG of RAM (or more), and ample storage space should be plenty to keep your experience satisfactory. There are, however, two problems with this statement.
First, apps are continually changing. They’re getting new features which take more time to process. The hardware that ran all your apps quickly and efficiently with the previous version of all your apps may struggle to run the versions that were just released, not to mention updates that will arrive sometime in the future. This obviously will make my previous statement obsolete and out-of-date sooner than we’d all like to admit.
Second, not all versions of Android are created equal. There are two categories of Android: those that are AOSP-based, and those that are heavily customized by the OEM. HTC, Samsung, LG, Motorola, and others take “Android” and modify it — some more than others.
These custom layers can add additional features and functionality, but they come at a cost. Often times that cost is lag. The perfect case-in-point are the HTC One and Galaxy S 4 Google Play Edition devices compared to their OEM equivalents. Because these phones are so high-end, the difference in speed (and lag) may be hard to notice, but it’s there if you look closely enough. Those who own the devices powered by the Google Play Edition version of Android say they’re faster and less laggy than those directly from HTC or Samsung. I’m my experience, I concur.
It may seem obvious, but the opposite of “sufficient hardware” is “insufficient hardware”. Devices that fall into this category give every other Android-powered device a black-eye. People will see that a smartphone or tablet runs Android, look at an impossibly low price, then impulse buy it — without checking specs or user reviews. Sure, it might perform okay out of the box, but as apps are added or updated, it gets slower and slower until it’s almost unbearable to use.
These devices are cheap — and they’re usually inexpensive, too. Yes, there is a difference. I’m of the opinion that cheap hardware is usually far too expensive when you factor in all the variables.
This is probably Android’s biggest strength, too. Anyone can build a device powered by Android, even if it’s grotesquely under-powered. That’s why Android is currently selling on three out of every four handsets.
Android 4.4 KitKat to the rescue?
Android 4.4 KitKat is lowering the memory footprint of the OS and core apps. Doing so should help low-end devices run apps more fluidly and will help to combat the perception of “lag” that so many complain about.
Unfortunately, current and previously released “cheap” Androids probably won’t see an update to Android 4.4, and will continue to lag in their laggy lagginess. New devices, once they come with KitKat pre-installed, may not suffer as badly, but I’m not going to hold my breath.
Why is iOS immune?
In addition to the “perception” of speed that we talked about earlier, iOS has one major advantage over Android: Apple controls the hardware.
Think about it, Apple makes every single iPhone and iPad on the market. It controls the version of iOS that runs on each unit, and tweaks the apps and the user experience to take advantage of the hardware powering each device. This means some devices don’t get the features that an OS updates touts, and others get a watered down implementation of the new features.
Google doesn’t have that luxury with Android; OEMs can do as they please.
Android isn’t laggy
Despite what the naysayers say, Android itself isn’t laggy. OEMs who make cheap and under-powered devices are laggy, but those devices would be laggy regardless of which OS they ran.
OEMs (with otherwise sufficiently spec’d devices) that load bloated skins and launchers inadvertently make their devices feel slow and laggy.
Next time someone tells you that “Android is laggy”, point them to this article, and politely tell them that some OEMs deliberately or accidentally “lag up” Android, and you’d gladly help them select a smartphone or tablet that will blow their socks off.
Interested in another way Google is hoping to make Android even faster? Want to learn more about Android 4.4 KitKat? Perhaps you want to learn more about the Snapdragon 800 SoC and why it’s so awesome. No problem, Pocketnow has got you covered!
Image credits: Bill and Ted’s Excellent Adventure