This morning, I was reading about Henrique Prange's friend's stolen iPhone, and the financial damage the thieves inflicted in only a few hours time—yikes! I've got six-digit codes on all my iOS devices, which suddenly felt like not nearly enough.
Executive summary: I love this keyboard. I was on a road trip recently, gone for 12 days straight with nothing but a MacBook Air (of the 'broken butterfly' generation). As soon as I got home and switched back to my iMac, I was reminded of just how much better this keyboard is than the one built into my Air…and the one that came with my iMac.
(Note: The "Mac" in the name simply means that you're getting a keyboard with Mac-specific symbols on the Command and Option keys; I'm pretty sure the Windows version would work just as well, but without the Mac-specific look.)
This review won't be quite as thorough as that of my mouse, mainly because there aren't as many nifty features—it is "just" a keyboard, after all.
On Twitter, I've shared my distaste for Catalyst apps, as many of them just don't "feel" right to a long-term Mac user. I know that's vague, but today, the vagueness ends, thanks to a deep dive into Apple's recently-released Developer app for macOS. No, the deep dive isn't this blog post you're reading now, but rather one by Martin Pilkington.
He has written a great analysis of the numerous issues with the Developer app. (And importantly, he filed bugs on everything he listed.)
Many of the issues aren't specific to Catalyst, but reflect poor attention to the details that make a Mac app look and act as a Mac app should. Here are but a few of the examples from Martin's analysis:
The focus ring on the search field has square corners • The search field focus ring does not go away if you click elsewhere in the app • Doesn't show window title when toolbar is hidden • Content size is too small • Can't collapse groups in the sidebar • Find toolbar does not share search string across OS
I strongly encourage you to read Martin's article, as it puts into words just why I find many Catalyst apps so annoying to use. In addition, I'm going to provide a couple more examples—using the same Developer app—showing just how non-Mac-like a Catalyst app can be…
At the end of March 2016, I purchased one of the newly-introduced 9.7" iPad Pros—a Gray 128GB Wi-Fi only version, to be exact. And until Friday, that was the last full-size iPad I bought for my personal use. (I did buy an iPad mini at the end of 2017, mainly as a test device for new iOS releases.)
However, early last week I decided it was time to upgrade, and after comparing a few models, I chose the iPad Air—Space Gray, 256GB, WiFi only for $649. I didn't really need 256GB of storage, but Apple, of course, only offers the Air in 64GB or 256GB capacities—and as I had about 110GB of stuff on my old iPad, I had to get the 256GB model.
Physically, they two iPads are nearly identical—despite the iPad Air's much larger display area, it's only 0.4" taller and 0.2" wider than the old Pro (they're both .24" thick), and it weighs but 0.6 ounces more.
As I had a Pro before, why didn't I buy a Pro this time, too?
I mainly use my iPad for games, watching movies or listening to music, using the internet, reading books, and sending the occasional email. As an iPad will never be my primary work machine, I didn't feel it necessary to pay the extra $2502An iPad Pro 11" with 256GB and WiFi is $899 for an iPad Pro. (And by choosing the Air, I still don't own an Apple device with Face ID.)
I know, clickbait headline, but really, it's how I've felt since the release of the iPhone X, and still feel today. And no, this isn't about switching to Android. It's about not buying a newly-designed iPhone. Why not? Two reasons…
The notch adds nothing to the iOS experience, but takes away much. Those stupid ears grab my eyes every time I see them, and there's no way to avoid them, save never using anything but an all-black screen. When not in an app, they show status items on a black background, which is fine…as long as your iPhone's wallpaper is also black.
This morning, I launched the DirecTV app on my iPhone (connected to my home network via wifi).
On launch, I saw a login screen that looked slightly different than usual; the app had been updated recently, so I assumed it was the new login screen. But when I entered my user name and password (on the first attempt), I saw the screen to the right…
At this point, alarm bells went off. Not just because it was my first attempted login, but also due to the grammar of that last sentence:
"Please, contact AT&T operator."
That's wrong in many ways—and there's no provided method for contacting an AT&T operator. I now believed I had been scammed: Somehow, a fake login page was injected where the app would normally display its login screen. As soon as I pressed Enter after entering my password, I'm sure my username and password were sent off to some server somewhere.
I immediately opened the DirecTV web site on my Mac, logged in (using my supposedly-locked account and current password), and changed my password. That all worked, and I received the email stating I'd changed my password, so I'm pretty sure my account is fine. (And I use unique passwords for each service, so the one that was probably compromised is useless to the hackers.)
But the bigger question here is what happened and how did it happen?
It's not as bad as it was before, but it's definitely still there. You don't even have to tap super fast; I can make it happen whether I'm using two fingers or one. As long as a couple of button taps are within a reasonably-quick amount of time, you'll get the wrong answer.
Dec 14 Update: I've now visited an Apple Store, and can replicate the bug in iOS 11.2.1 on the X, 8/Plus, and 7/Plus. See below for a video of the iPhone X running iOS 11.2.1.
Dec 3 Update: Some users with the same phone models as those I've tested say they can't replicate the bug. I've added a video of my phone in use, showing exactly how quickly I was tapping, and that the bug is definitely there. Click the "more…" bit to see the video.
Dec 2 Update: Users have reported the bug is fixed on the iPhone 7 Plus and the X. But it's definitely present on the following phones: iPhone 6, iPhone 6S, and iPhone 8 Plus—I personally tested all three of those. If you have a different model and can test, please do so and let me know—I'll update the list when I receive responses.
Below are three examples; one with 3+2+1 and two with 6-5-4. The slow-motion version shows exactly how Calculator comes up with the wrong answer, as you can see incorrect values being inserted. This was recorded on my just-upgraded iPhone 8 Plus running iOS 11.2:
I can even make this happen with a simple "3+2" test. You may argue that I'm tapping the keys too quickly, but I'm not really hitting them at super-human speed, just quickly. And more importantly, the taps should be recognized and cached in order, regardless of what onscreen animations are occurring.
Trying the same experiment with PCalc, for example, I cannot make it fail, even tapping buttons much more quickly than I do in Calculator.
Kill the fancy animations, Apple, and just make Calculator remember our key taps, please?
No, I didn't buy one. (Though I could have; the nearby Apple store has had them in stock each day.) But I did spend about 20 minutes playing with one, just to compare it to my 8 Plus. Here then are my thoughts after that extensive hands-on period…
The Good Stuff
The screen is lovely (most of the time; see below). Very high pixel density makes for incredibly crisp text, and the OLED tech means blacks are black, and colors in images look stunning.
The 120Hz sample rate on the touchscreen makes for very snappy interactions.
Compared to my 8 Plus, the narrower iPhone X feels nicely sized in my hand.
I don't think it would take too long to get used to the gesture-based interface; I already find myself wishing that the "short drag up" to activate the app switcher worked on my iPhone 8 Plus.
Face ID is very easy to set up, much more so than Touch ID. (The store phones have a demo setup so you can see how it works and test it, but not really apply it as you would on your own iPhone.)
There's more, of course, but they're things that apply to the iPhone 8/8 Plus, too: The glass design feels good in the hand, much improved cameras, speedy CPU, etc. The X has all of that, though with an even better camera, thanks to stabilization on the zoom lens, too.
With the recent unveiling of Movies Anywhere, Apple has—willingly or not, I do not know—opened up the world of iTunes to movies from other places. Stated another way, you can now have movies in the Tunes ecosystem that weren't purchased there, or that weren't digital versions acquired by using an iTunes redemption code with a physical disc purchase.
To put it bluntly, this is huge; I've long wanted a way to get all of my movies into iTunes (and iOS) so that they could sync to devices, easily stream (without the computer on) to the TV, etc. The service goes well beyond iTunes/iOS, of course—the full list of supported players is quite extensive.
Important: As of now, Movies Anywhere is a US-only service. If you're not in the US, hopefully something similar will be coming to your country at some point in the future.
What's really amazing, though, is that you can not only combine purchases from multiple sources into iTunes, but convert and/or upgrade them in the process. Thanks to Movies Anywhere, I've been able to do two seemingly amazing things…
Put an UltraViolet-only (i.e. no iTunes version) digital redemption movie into the iTunes ecosystem.
Paid a modest fee—not to Apple—and converted an old physical DVD into a high-def —digital version.
Note: The original version of this post stated that you could convert a DVD into a 4K iTunes video. That is not the case, based on this article and my own testing. Thanks to @netnothing for the pointer.
How does this magic work? Honestly, I don't really know.
With the arrival of my iPhone 8 Plus and its A11 Bionic CPU, I thought it'd be interesting to compare its benchmark performance (for the CPU and GPU) with some of the other gear in our home—iOS devices, Macs, and even a PC and a Linux box. In total, I tested 15 devices.
How did I test? I turned to Geekbench, which you can run on MacOS, Windows, and Linux (anywhere from free to $99), as well as on iOS ($.99). It has tests for both the CPU (using single and multiple cores) as well as the GPU (OpenCL and Metal on iOS/macOS; OpenCL and CUDA on Windows; CUDA on Linux).
What follows is far from a scientific study; I was just curious how the CPU and GPU in the iPhone compared to other tech gear in our home. As such, I didn't run the tests under "ideal lab conditions," I just ran them—one time per machine, with no special setup other than some basic stuff…