---
title: "Android Graphics Truth Facts"
url: https://deallocatedobjects.com/posts/android-graphics-truth-facts
author: Jake Marsh
published: 2011-12-06
updated: 2013-11-16
link: https://plus.google.com/100838276097451809262/posts/VDkV9XaJRGS
topics: ["Design"]
description: "Andrew Munn points out a simple truth about Android vs. iOS graphics rendering: It’s because on iOS all UI rendering occurs in a dedicated UI thread with real-time priority."
---

# Android Graphics Truth Facts

By Jake Marsh, December 6, 2011. HTML: https://deallocatedobjects.com/posts/android-graphics-truth-facts

This is a link post about https://plus.google.com/100838276097451809262/posts/VDkV9XaJRGS

[Andrew Munn](https://twitter.com/#!/andrewmunn) points out a simple truth about Android vs. iOS graphics rendering:

> It’s because on iOS all UI rendering occurs in a dedicated UI thread with real-time priority.

He also clarifies:

> 1. Compositing and previously set-up animations—all the stuff that involves the Core Animation rendering layer tree—do indeed happen on a background thread. 

> 2. Drawing new content into Core Animation layers and setting up their animations happens on the main thread. This is the same thread that user interface actions occur on.

> 3. In naively written code, all developer-written code would occur on the main thread. However, Apple provides very easy APIs (Grand Central Dispatch and `NSOperation`) to move things into system-managed background threads. In iOS 5, you can even declare that a Core Data (object-relational database) context cannot be used directly on the main thread.

I love that we're finally starting to see some in-depth writing about the meat of these issues. 

Pretty much everyone I speak to on a regular basis tells me "Android just feels laggy" or something of that nature. I can't speak to the specific causes of Android's hiccups in this department, but Andrew's post sounds pretty accurate to me in regards to Core Animation and UIKit rendering behavior.
