Usability & iOS 7

The iPad Air remains one of the best consumer tablet experiences around. The OS and Apple’s first party applications are both extremely well suited to the tablet, and there’s a very healthy ecosystem of third party applications to fill in the gaps left by Apple.

Lately Apple has been doing wonders to limit those gaps. Both iLife and iWork suites are now free with the purchase of any new iOS 7 device, including the iPad Air. Previously each of the three iLife apps set you back $5 a piece ($15 total), while the iWork apps were priced at $10 a piece ($30 total). Apple has truly embraced its role as a devices and software company and is using the latter to help sell the former. On the one hand this is an admission that the market is growing more competitive, as tossing in free software is a great differentiator. On the other hand, freeing up iLife/iWork is a vote of confidence in Apple’s ability to continue to demand a premium for its hardware. Neither suite comes preinstalled on the iPad Air, but upon a visit to the App Store users are reminded that they can get all six of the apps for free if they should desire to. I suspect part of the reason that they’re not bundled by default is to avoid eating up space on the devices with less NAND by default.

The core iOS apps are quite approachable and easy to use. Applications like Safari and Mail make great use of the high resolution screen. Obviously the same can be said for things like Photos and iPhoto. The virtual keyboard experience is great on the large display (especially in landscape mode). Honestly, if there was a good Google Hangouts app (the Android version is much better in my experience) for iOS 7 I think I could be very comfortable and productive on the iPad Air.

I find that task switching is far better on the iPad than it is on the iPhone since multitasking gestures are supported. A four finger swipe left/right between applications or up/down to bring up the task switcher is so much quicker for me than a double tap of the physical home button. Similarly a five finger pinch to get back to the home screen from any application is significantly faster. The new iOS 7 multitasking UI feels so much more at home on the iPad’s large display as well.

My only complaint about task switching on the iPad Air is that UI frame rate will regularly drop below 30 fps during some of these transitions. The added GPU performance on the A7 doesn't seem to really impact things compared to the A6X, so I’m fairly convinced at this point that the solution to the problem will have to come in software. It’s quite reminiscent of the Retina MacBook Pro UI frame rate issues under Mountain Lion, although not nearly as bad (and I’m hoping it won’t take a year to get these ones resolved).

The release of iOS 7.0.3 addressed (at least partially) some of my concerns around the OS. As I already mentioned, stability on 64-bit platforms seems somewhat improved - at least compared to the initial release of iOS 7. The other big improvement in my mind is the ability to turn off/reduce the transition animations. The impact to usability on the iPhone 5s is huge, but it’s also pretty significant on the iPad Air. The animations themselves are pretty but I find that they get repetitive after continued use.

Memory Size & The Impact of 64-bit Applications

The iPad Air, like the iPhone 5s, ships with 1GB of LPDDR3 memory. Apple frowns upon dissection of review samples but I think it’s a safe bet that we’re not talking about a PoP (Package-on-Package) configuration but rather discrete, external DRAM here. It’s also probably a safe bet that even the iPad mini with Retina Display will ship with 1GB of memory as well.

Something I didn’t have time to address in my iPhone 5s review was the impact of 64-bit applications on memory usage. I actually ran some tests after the 5s review hit but never got the chance to share the data, so I figured now is as good a time as any to do just that.

Unlike traditional desktop OSes, iOS doesn’t support paging to disk (or in this case, NAND). Application data can either reside in memory or the associated process is terminated and has to be reloaded the next time you request it. It’s a decision likely made to both maintain user experience and limit the number of program/erase cycles on the internal NAND.

The good news is that iOS was architected to run on as little hardware as possible and as a result tends to be quite memory efficient. There are also power implications of going to larger memories. The combination of these two things has kept Apple on the conservative side of increasing memory capacity on many iDevices.

The move to a 64-bit platform however does complicate things a bit. Moving to a larger memory address space increases the size of pointers, which in turn can increase the footprint of 64-bit applications compared to their 32-bit counterparts. So although there’s clearly a performance uplift from app developers recompiling in 64-bit mode (more registers, access to new instructions), there’s also an associated memory footprint penalty. Since the iPad Air and iPhone 5s don’t feature a corresponding increase in memory capacity, I wondered if this might be a problem going forward.

To find out I monitored total platform memory usage in a couple of scenarios. Before measuring I always manually quit all open apps and performed a hard reset on the device. Note that the data below is reporting both clean and dirty memory, so it’s possible that some of the memory space could be recovered in the event that another process needed it. I hoped to minimize the impact by always working on a cleanly reset platform and only testing one app at a time.

I looked at memory usage under the following scenarios:

1) A clean boot with no additional apps open
2) Running Mobile Safari with 4 tabs open (two AnandTech.com tabs, two Apple.com tabs, all showing the same content)
3) Infinity Blade 3 (64-bit enabled) sitting at the very first scene once you start the game
4) iOS Maps in hybrid view with 3D mode enabled, with a WiFi assisted GPS lock on my physical location
5) Google Maps in the same view, under the same conditions. I threw in this one to have a 32-bit app reference point.

In general you’re looking at a 20 - 30% increase in memory footprint when dealing with an all 64-bit environment. At worst, the device’s total memory usage never exceeded 60% of what ships with the platform but these are admittedly fairly light use cases. With more apps open, including some doing work in the background, I do see relatively aggressive eviction of apps from memory. The most visible case is when Safari tabs have to be reloaded upon switching to them. Applications being evicted from memory don’t tend to be a huge problem since the A7 can reload them quickly.

The tricky part is you don’t really need all that much more memory. Unfortunately as with any dual-channel memory architecture, you’re fairly limited in how you can increase memory capacity and still get peak performance. Apple’s only move here would be to go to 2GB, which understandably comes with both power and financial costs. The former is a bigger concern for the iPhone 5s, but on the iPad Air I would’ve expected a transition sooner rather than later.

Although things seem to have improved with iOS 7.0.3, the 64-bit builds of the OS still seem to run into stability issues more frequently than their 32-bit counterparts. I still see low memory errors associated with any crashes. It could just be that the move to 64-bit applications (and associated memory pressure) is putting more stress on iOS’ memory management routines, which in turn exposes some weaknesses. The iPad Air crashed a couple of times on me (3 times total during the past week), but no where near as much as earlier devices running iOS 7.0.1.

Battery Life Final Words
POST A COMMENT

444 Comments

View All Comments

  • Ins0mnihack - Friday, November 1, 2013 - link

    As an owner of a 2nd gen Nexus 7 and iPad 3 (soon to be replaced by an iPad Air) I have to largely agree with this. While I wouldn't call the Nexus 7 a "POS", its an inherently cheap device with an incredibly limited selection of tablet optimised apps.

    While I vastly prefer the flexibility and freedom of Android (particurarly when it comes to app intents, and choosing default apps) it still doesn't make up for the severely lacking ecosystem for Android tablets. And while the Nexus 7 does have a nice 1200p display, the Tegra 4 chipset doesn't seem capable of driving Jellybean at a nice frame rate (or maybe it's just the inherent micro-stutters of Android - either way it stutters when scrolling and during quite a few system animations). iOS's touchscreen responsiveness and frame rate are still much better than Android.
    Reply
  • ESC2000 - Sunday, November 3, 2013 - link

    Um I'm really doubting you own a nexus7 based on your comments. It has a Qualcomm snap dragon processor, not tegra 4, and it has 4.3. The processor runs it like a charm. The nexus even has a nicer screen than all the 10 inch iPads including the iPad air not to mention it ismuch more reasonably priced. something all non windows tablets lack is good multitasking. A 10" iPad like the air should be more than a gigantic iPod touch. Reply
  • Lizbeth - Sunday, November 3, 2013 - link

    I dunno. The Amazon HDX is pretty tight and isn't listed in the comparison. They are easy to hack and add full google play functionality even if it does void the warranty. Why is Amazon Fire HDX not listed in the comparison? Reply
  • Walkop - Tuesday, November 5, 2013 - link

    I like your comment.

    It makes me laugh. :D
    Reply
  • akdj - Wednesday, October 30, 2013 - link

    An absolute and collective "AMEN" John2k13! Thanks for the excellent response...a breath of fresh air---and excellent response from the drivel Mr. dsumanik tries to lay down as 'issues'. Unreal.
    Anand....and the rest of the crew, thanks once again---a magnificent review as always! The depth you...and your crew go to is as extensive as it gets and IMO, easily the most 'objective' on the 'web.
    Thanks again....would be nice for the comment section to be a 'paid' or 'donation only' area---where those that have the ability or should I say---the 'privilege' to post would have to donate to your cause;)
    J
    Reply
  • pdjblum - Wednesday, October 30, 2013 - link

    lol. Your kidding right? Maybe they could make it so only people who agree to kiss anand's ass should be able to comment. Reply
  • robco - Thursday, October 31, 2013 - link

    *you're Reply
  • akdj - Monday, November 4, 2013 - link

    Not kidding...you're the joker here bud Reply
  • teng029 - Wednesday, October 30, 2013 - link

    Well said. No one is forced to come to Anand's site to read his reviews. Don't like the way he reviews products? Go somewhere else. Most of us actually appreciate the fact that he does a very thorough job of reviewing products that come his way.

    As for those asking for Thunderbolt on an iPad, you seem to forget that Apple does not own Thunderbolt; Intel does. You also seem to forget that iDevices are based on processor technology owned by ARM; Intel's competition. Why would Intel allow their proprietary technology to run on a competitor's platform?
    Reply
  • Djasonw - Thursday, October 31, 2013 - link

    Your thoughts and comments mirror mine. Well said. Some people are VERY dumb. Reply

Log in

Don't have an account? Sign up now