While it’s pretty much a universally terrible idea to use a tablet as your primary camera, for something like video chat or in an emergency it’s better to have one than not. In the case of the iPad Pro, the camera is essentially identical to what we saw with the iPad Air 2, which is to say an 8MP 1.1 micron 1/4” sensor, with an F/2.4 aperture and 3.3mm focal length, which translates to a 35mm equivalent focal length of 31mm. There’s no PDAF or anything fancy going on here, so it’s pretty much a guarantee that the camera is the exact same module that we saw with the iPad Air 2. The front facing camera is still a 1.3MP F/2.2 2.65mm focal length module, which leads me to believe that it too is shared with the iPad Air 2. I honestly don’t see any difference between the iPad Air 2 and iPad Pro cameras, so rather than spending time dwelling on those this comparison will be focused upon how it compares to popular smartphones and the tablet competition. As I don’t have a tripod mount that can actually fit the iPad Pro, I’ve elected to forgo some of our standard latency tests to avoid presenting data with confounding variables.

Daytime Photography Scene 1

In our first daytime scene the iPad Pro is actually not that far off from the iPhone 6s. If you look closely it’s obvious that there is less detail to be seen, but it’s honestly quite difficult to see the difference. Relative to the iPhone 6, detail is almost identical. For a camera that should basically be never used for the kinds of photos I’m taking for this review, the camera will work well in a pinch. By comparison the Pixel C is rather disappointing. Even in this ideal condition, detail is visibly worse when compared to the iPad Pro. I’m not sure whether this poor showing is caused by camera shake or AF issues but in general the AF system for the Pixel C had some pretty noticeable issues in general. There are also some obvious problems with color noise despite base ISO, which is shocking.

Daytime Photography Scene 2

In the interest of trying to collect more than one data point for presentation in the review, I tried another scene. Once again, the iPhone 6s shows a minor resolution lead and the iPad Pro is pretty close to the iPhone 6 here. By comparison while there isn’t any obvious weirdness going on the Pixel C clearly has less detail and a noticeable amount of color noise, which is surprising even for a tablet camera. Color noise is one of the most distracting things in any photo, so I’m always concerned when any mobile device has a camera where the JPEG output shows color noise.

Low Light Photography Scene 1

Low Light Photography Scene 2

Moving on to the low light testing, we clearly see the disadvantage that comes with smaller pixel sizes. The iPad Pro is just clearly worse than the iPhone 6 and 6s here. The 6s Plus is the clear winner of this test. While the iPad Pro has dark output, it’s miles better than the Pixel C and Nexus 9, both of which show enormous amounts of color noise. The Tegra X1 and K1 ISP for whatever reason is struggles with doing things like hot pixel compensation in low light, as in the dark areas of the photo there are obvious bright speckles of pixel noise.

Low Light Photography Scene 3

In another low light scene we see the same sort of ordering that was in the previous scene. The iPad Pro is acceptable here, but the iPhone 6, 6s, and 6s Plus are all clearly superior. However, the iPad Pro is clearly superior to the Pixel C and Nexus 9 on the basis of better detail and noise reduction. Unlike most smartphones I don’t really see a huge difference in how well everything freezes motion here, but I suspect this might just be because the entire image for the Pixel C and Nexus 9 is so lacking in detail.


1080p30 Video

Looking at video performance, the iPad Pro noticeably lags behind the iPhone in feature set, which isn't entirely unsurprising given that the camera on any tablet should be strictly reserved as a fallback for when you can’t get to a smartphone or literally anything else. 1080p30 is encoded with H.264 high profile at 17 Mbps, with around 82 Kbps single channel AAC audio. For the most part, quality here is actually comparable to the iPhone 6 and 6s in daytime, with a noticeably tighter crop due to the longer 35mm equivalent focal length. The iPhone 6s Plus is again the obvious winner here though, due to its use of OIS in video. By comparison, the Pixel C shows clearly less detail, and the higher contrast leads to worse detail in areas like the road and in shadows.

Slow-Motion Video

In 720p120, the iPad Pro is clearly worse than the iPhone 6s and 6s Plus just by virtue of not supporting 1080p here. That's not exactly surprising, but as a result the quality looks to be roughly comparable to the iPhone 6. Given that both are using H.264 high profile at 30 Mbps it’s not exactly a surprise though. The Pixel C and Nexus 9 are both unable to participate in this test at all as they don’t support slow motion video, which might be an ISP limitation of some sort as we’ve seen Nexus devices on the smartphone side with support for slow motion video.

Overall, camera performance on the iPad Pro is probably as good as it gets for tablets, but it's obviously not competitive with the best smartphones. No one should really be surprised that this is the case though, as tablets are basically cameras of last resort, while smartphones are often primary cameras now.


On the WiFi side unfortunately I have reason to doubt the validity of our current testing methodology, especially on iOS. As a result for this review we won’t be running any particular benchmarks for the iPad Pro but I never saw any particular issues with WiFi performance on the iPad Pro, which uses Broadcom’s BCM4355 WiFi/BT combo chipsets.

I also don’t have any particular equipment to really test speaker quality to its full extent, but subjectively the speakers are some of the best I’ve ever experienced on a mobile device in terms of sheer volume and frequency response. The speaker amps are shared with the iPad Air 2, which is Maxim Integrated’s MAX98721 IC. The audio codec/DAC is Cirrus Logic’s CS42L81, which isn’t entirely unsurprising given how most every Apple mobile device seems to use a Cirrus Logic codec of some sort.

I also found a number of interesting design wins, which include TI’s BQ27540 for the battery fuel gauge, and an MCU related to the Orion dock that seems to handle accessories like the Smart Keyboard. This MCU is connected over i2c, with some suggestion that this connector can act as a USB port, but I haven’t been able to figure out much else about this system.

Software UX Final Words


View All Comments

  • ddriver - Friday, January 22, 2016 - link

    Should have named in iPad XL or something, this device will barely suit the need of any professional. Performance is good, but without supporting professional software, the hardware is useless. Reply
  • Coztomba - Friday, January 22, 2016 - link

    And why would anyone bother to make professional software if the hardware wasn't capable? They needed a starting off point to say "Hey we can produce the hardware to run pro apps on a iPad. It's only going to get better. Start developing!" Reply
  • ddriver - Friday, January 22, 2016 - link

    If anyone could stimulate software companies to do that, I guess that would be apple with its mountains of money and strong sales. They do have enough resources to do the software themselves.

    Mobile device hardware has been capable of professional workloads for at least 2-3 years. Nobody bothered to do it. Big software companies did not port their applications to ARM, instead they made cheap, crippled lesser versions. This is IMO a stupid move, they probably did this to promote their professional software to common folk, but it would have been more lucrative to bring professional software to mobile platforms.

    There are 2 main issues with mobile platforms - memory and CPU performance. Modern software is very bloated memory consumption wise, especially software relying on managed languages, the latter are also significantly slower in terms of performance than languages like C or C++.

    There is one big issue with legacy professional software - it originates back from the days developers were locked in platform specific application development APIs, so it represents a significant effort to port them to mobile platforms - essentially, most of the stuff needs to be rewritten.

    But a rewrite in faster and more efficient language, taking advantage of contemporary technology such as OpenCL can easily bring professional software to mobile platforms at an experience as good as that of desktop workstations. Naturally, more efficiently written software will also run that much better on powerful desktop machines as well.
  • mr_tawan - Friday, January 22, 2016 - link

    Not all pro are in the multimedia industry, you know :-).

    For most office workers, for instance, the only things they might need are notetaking (onenote), email (outlook), wordprocessor (word), and calendar (onenote). Most all tablet are capable to all of that, but it is a bit awkard to work with (due to the missing stylus, and not-so-comfy keyboard).

    With iPad Pro which, well, address this issue in the same way as the Surface Pro by adding keyboard and stylus to the tablet. It's much easier to use the table extensively (rather than just browsing web and watching video, which is hardly described as a profession job). So I personally think that adding these two options could takes the iPad into the 'professional' realm.

    I think that Apple would love to have iPad to complement MacBook (and Mac Pro), rather than to compete. If you need more power than just by Mac Pro :-).
  • ddriver - Friday, January 22, 2016 - link

    Yeah, why use one device when you can buy and lug around two devices instead. Reply
  • melgross - Friday, January 22, 2016 - link

    There's actually quite a lot of professional software available on iOS, and has been for some time. I suppose if you do t use iOS, and so do t know what's a bailable, you can say that little is available, but it's simply not true. Microsoft itself had about two dozen professional apps on iOS. You really need to look through the App Store. Reply
  • ddriver - Friday, January 22, 2016 - link

    What would those 24 ("two dozen") professional microsoft apps be? Reply
  • Dave Bothell - Saturday, January 23, 2016 - link

    Word, Excel, PowerPoint, Outlook, OWA for iPad, Sunrise Calendar, OneDrive, OneDrive for Business, OneNote, SmartGlass, Skype, Bing for iPad, Remote Desktop, Lync, Office 365 Admin, Intune, Azure Authenticator, Sway, SharePoint Newsfeed, Dynamics CRM, Dynamics Business Analyzer, Dynamics Time Management, PowerApps, Global Startup Directory. There's more, but you asked for 24. Reply
  • xerandin - Saturday, January 23, 2016 - link

    Smartglass isn't a professional app--it controls Xbox 360s or Xbox Ones, depending on which version of the app you install. Reply
  • dsraa - Sunday, January 24, 2016 - link

    you forgot isnt a professional app either. Reply

Log in

Don't have an account? Sign up now