March 29, 2016
I love my iPads and I use them all the time for work, and while I’m lounging around, but still want to stay connected. There is no doubt that the 9.7-inch iPad Pro is very powerful, but there are some things, for me, that made this a standout release.
Before I talk about the new model, let’s take a look at the older iPad Pro for just a minute. The larger 12.9‑inch iPad Pro is a magnificent device. However, I found after using it for a while, that device required me to make a decision to use it. That’s not necessarily a bad thing, but it was still a decision I made to pick that up and start using it.
For the most part, I would use the larger iPad Pro on a table top or other flat surface. Due to its size, it really wasn’t a device I would use on my lap or walking around with.
Having said that, every artist I know loves the 12.9‑inch iPad Pro and they happily make that decision every single day. It’s all in the way you use it.
The 9.7-inch iPad Pro is a bit different for me. It’s the same size as the previous iPad, so it has a familiarity that is very comfortable. This is a device I instinctively reach for at the end of the day when I put my computer down. It’s the perfect size, and with the updated innards, it’s a powerhouse of a machine.
I’m not one of those people that wants an iPad to replace my Mac, and I don’t force myself to use an iPad to see if it can replace any of my other devices. For me, the iPad plays a very important role in my workflow as it is.
Sometimes, the iPad does replace my Mac for certain tasks, but that’s because it’s powerful enough to do it, not because it’s forced. The 9.7-inch iPad Pro has taken that a step further in the week that I’ve been using it, mostly because of its standout feature: True Tone.
Here’s how Apple describes True Tone:
The 9.7-inch iPad Pro features advanced display technologies, including a True Tone display, which uses new four-channel sensors to dynamically adjust the white balance of the display to match the light around you for a more natural and accurate, paper-white viewing experience.
Add to that, the 9.7-inch iPad Pro’s new anti-reflective display, which Apple describes:
The advanced Retina display is 25 percent brighter and 40 percent less reflective than iPad Air 2, making content even easier to see indoors and out.
Sounds great, right?
One of the biggest knocks on the iPad as a product is how difficult it is to read outdoors. I’m always moving around to create a shadow on the screen so I can see the words. It’s just how it is.
I’ll admit, I listened to Apple talk about True Tone with some skepticism. Having the power and clarity of a Retina Display and be able to see it outdoors seemed a bit much to expect.
After I unpacked my iPad and set it up, I took it outside, put in direct sunlight and sat down. To my utter amazement, I could see the screen perfectly. True Tone is like magic.
At one point the screen went to sleep—when I turned it back on, there was a couple of seconds when you could see True Tone adjusting the display for the ambient light around me, which in this case was direct sunlight. I had to look really quick to see it, but it was there.
It doesn’t matter where you are, the True Tone sensors are always monitoring your surroundings to give you optimal viewing. If you take it inside, it monitors the lighting in your house and adjusts the display for those conditions too.
As a test, I held my iPhone 6s Plus next to the iPad Pro and I had difficulty reading the iPhone screen. That’s not new, it’s just the way things are with devices in direct sunlight—I expect to shimmy around until I have a shadow on the screen so I can see it.
True Tone is an important feature for me because of the way I use my iPad. It’s the device I take to the coffee shop to do some writing. I use it outside to browse the Web and get caught up on email. I take it on trips and use it in airports, hotel rooms, and on the plane.
I use my iPad everywhere and that is exactly why True Tone is going to make such a big difference for me. That’s also why I find myself using this iPad a bit more than its predecessors.
It’s not that True Tone just adjusts the display, it actually makes it more comfortable on your eyes. That is incredibly important for someone like me that reads all day long. I don’t want to be fatigued just trying to read.
The 9.7-inch iPad Pro also uses the same P3 wide color gamut as the iMac with Retina 5K display. Think about that. The images on the iPad are stunning.
If there is one thing I could change, it would be the keyboard on the smart cover. I’m sure there is a technical reason why the keys are on the smaller side, but I’m used to 12-inch MacBook keyboard, which has the wider keys. It’s a small complaint, but I’d love the keys to be more like the MacBook.
Take True Tone, the anti-reflective display and add in the performance with the 64-bit A9X chip, Night Shift, a four-speaker audio system, 4K video, 5-megapixel FaceTime HD camera, faster wireless technologies, and support for the Apple Pencil, among other features, and you have a clear winner of a device.
I’ve been using the 9.7 iPad Pro more than any iPad before it. Apple not only made the iPad more powerful, it made it more useable, and that’s what’s important to me.
Written by Dave Mark
I can’t test this, since I don’t have a device that suffers from the “dead links” issue. But if you do have such a device, and can’t wait for Apple to roll out a fix, give this a try.
It’s a pretty interesting read. Clearly, the author implies that the problem is with the Bookings.com app, but it could be some other app as well.
From this post by Benjamin Mayo on 9to5Mac:
Previously, we pinpointed Bookings.com as a cause of the bug, although noting it affects other apps as well. On Twitter, it was found that their website association file, used by the system for the universal links feature introduced with iOS 9, was many megabytes, grossly oversized. This would essentially overload the daemon that had to parse these files, causing the crashing. The Booking.com app has since corrected its payload file to be a far more reasonable 4 kilobytes. Users of Booking.com should delete and reinstall the app, to refresh the system caches for the URL association file.
However, Booking.com is not the only case of a developer misusing the API, so people who continue to experience bugs will also find that they have other apps installed on the system which are also registering thousands of URLs. Unfortunately, it is practically impossible to find out which apps are the misdemeanours. In terms of high-profile cases, we have heard that Wikipedia and Eat 24 are among the apps registering too many domains in their universal link directory.
Sounds like no one ever tested iOS 9 with a massive list of universal links.
From the Universal Links page in Apple’s iOS Developer Library:
When you support universal links, iOS 9 users can tap a link to your website and get seamlessly redirected to your installed app without going through Safari. If your app isn’t installed, tapping a link to your website opens your website in Safari.
From this article in the New York Times:
“Courts should be skeptical going forward when the government claims it has no other option besides compelling a device maker’s assistance,” said Riana Pfefferkorn, a cryptography fellow at the Stanford Center for Internet and Society.
“Now that the F.B.I. has accessed this iPhone, it should disclose the method for doing so to Apple,” she added. “Apple ought to have the chance to fix that security issue, which likely affects many other iPhones.”
The FBI is faced with a choice between making iPhones safer from hackers or keeping a cracking technique to themselves that they know is in the wild.
Which side will they choose? We’ll know soon enough.
March 28, 2016
Here is the statement Apple provided to me tonight. I think it says all that needs to be said:
From the beginning, we objected to the FBI’s demand that Apple build a backdoor into the iPhone because we believed it was wrong and would set a dangerous precedent. As a result of the government’s dismissal, neither of these occurred. This case should never have been brought.
We will continue to help law enforcement with their investigations, as we have done all along, and we will continue to increase the security of our products as the threats and attacks on our data become more frequent and more sophisticated.
Apple believes deeply that people in the United States and around the world deserve data protection, security and privacy. Sacrificing one for the other only puts people and countries at greater risk.
This case raised issues which deserve a national conversation about our civil liberties, and our collective security and privacy. Apple remains committed to participating in that discussion.
Written by Dave Mark
Quentin Hardy, writing for The New York Times:
Timothy D. Cook has found himself in a strange position. It looks like someone knows about an important flaw in Apple’s flagship product, and won’t tell its chief executive what it is.
That could be because Apple doesn’t pay outside hackers who find exploitable flaws in Apple software. Paying so-called “bug hunters” has become the norm at many tech companies, and the United States government does it too.
Interesting premise. Google, others, have a bug bounty program, where they pay 3rd parties who identify major bugs in their products. Apple does have a number of funnels to bring bug reports into their bug-tracking system. But they do not pay for those reports.
Does a third party company (rumored to be Cellebrite, FBI denies it is them) have a technique to crack an iPhone? Would a bug bounty have prevented this possibility?
My two cents: I certainly don’t think paying for bug reports would, by itself, make a difference to the stability of Apple’s software. There’s no shortage of officially reported bugs that are in Apple’s official bug queue.
The question is, would a hacker aware of a critical vulnerability be more likely to report it to Apple if there was a cash payout for them?
Written by Dave Mark
Benjamin Mayo, writing for 9to5Mac:
Readers are reporting a strange bug with iOS 9.3 (and older versions apparently, exact characteristics of affected devices is unclear), primarily affecting the latest Apple devices, iPhone 6s and iPhone 6s Plus. The issue has also been reported on older phones and some iPad models as well. The cause is unknown, but many users are finding themselves unable to open links in Safari, Messages, Mail, Notes and other apps. Instead of visiting the target website, the app crashes, freezes or hangs.
To see this more directly, take a read through some of these bug reports on Apple’s support forum.
This is one of those maddening, difficult to reproduce bugs that makes it hard to predict whether your device is susceptible to this problem. I just upgraded my iPhone 6s Plus, no problem. But could be I don’t have the right model, or the right combination of apps that trigger the bug.
Other users are reporting that tapping on links simply does nothing, whereas a tap-and-hold causes a crash. A permanent fix for the issue is not known and Apple has yet to comment on what may be going on. Some people have reported that disabling JavaScript partially solves the issue for opening links in Safari, but remains for other apps.
I wonder if the Chrome browser suffers from the same problem on an affected machine. [From Ben via Twitter: Chrome worked for me. Doesn’t seem consistent.]
No doubt Apple has a team working on this around the clock. Hopefully, a patch will come out quickly.