Camera

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.

Video

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.

Misc.

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
Comments Locked

408 Comments

View All Comments

  • dsraa - Sunday, January 24, 2016 - link

    You guys are a bit late reviewing this, no? Especially for a ipad that is the exact same thing, only a little bigger.....what a stupid idea,.....But of course idiots are gonna buy it cause its apple.
  • valentin-835 - Sunday, January 24, 2016 - link

    I'm buying it not because it's an Apple. It's the only one out there. Samsung had a 12 inch and they have discontinued it. As for Surface, I don't have a need for desktop apps on my tablet ( not yet ). If that makes me an idiot, so be it.
  • blackcrayon - Sunday, January 24, 2016 - link

    People that buy it are "idiots", yet you think the iPad Pro is the "*exact* same thing"? Not sure if you need a dictionary or what.
  • osxandwindows - Sunday, January 24, 2016 - link

    What a stupid comment.
  • NitT - Sunday, January 24, 2016 - link

    I am interested in iPad Pro because of the pen. Most of my tablets have active digitizer. I have never used iPad as there was no active digitizer available. I have a few Galaxy tablets before with active stylus. However below is my workflow. Please suggest if iPad Pro could handle my workflow.
    1. I have 200+ email per day and my company's cloud is very limited. It is only 2 GB so I have to archive my email every 15 days. Now I am using Outlook client. I have to access my email from 2013 or 2014 from time to time.
    2. My office works are mainly on Office suite either Word, Excel, PowerPoint. I need to copy content from one work (eg. Word) to another one (eg. Excel).
    3. I use OneNote heavily and require to copy content from Word/Excel/PowerPoint
    to OneNote for note taking.
    4. I use Outlook extensively for email, calendar and task. I prefer everything in one place and do not want to go to multiple apps to access those information.
  • digiguy - Sunday, January 24, 2016 - link

    Your workflow seems more typical of a laptop than of a tablet. It wouldn't be impossible to use the ipad pro, but it's definitely not the best device for that. A surface pro 3/4 (or even book) would be a much better option, especially if you copy and past a lot and (seem to) need the full office suite. Also if you want a fanless device, you have more options with similar devices such as the Lenovo Miix 700 and the HP Spectre X2.
  • osxandwindows - Sunday, January 24, 2016 - link

    Strange.
    There are no ms fanboys claiming, surface is better.
    Surface is better as a laptop, not as a tablet.
    Same go's for the iPad pro, the best professional tablet, not very good as a laptop.
  • KPOM - Sunday, January 24, 2016 - link

    Different tools for different tasks.
  • amrs - Monday, January 25, 2016 - link

    From the final words: "Android has some pretty severe issues with making a tablet UI that is more than just a scaled-up phone UI". What exactly are these severe issues? As I understand it the main issue with Android tablets has been apps: few apps lead to few sales so few apps. Video works and is apparently huge in some places but for other apps Microsoft's Office is one of the few good tablet apps on Android... Not talking about the 7-8" tablets where phone UI is usually OK.
  • ABR - Monday, January 25, 2016 - link

    Not sure if this is why the article says that, but the iOS APIs make it very clearcut and simple to build a UI that adapts to tablets and phones in standard ways. Android provides some of the building blocks, but leaves you much more on your own for putting it all together. So, while it's actually easier on Android to build the UI that simply expands and shrinks for the screensize, providing two separate modes for tablet-size and phone-size is mostly up to you.

Log in

Don't have an account? Sign up now