When the Scoops Run Dry

Wednesday, 31 May 2017

800-word report for Bloomberg by Mark Gurman and Alex Webb on Apple’s long-rumored Siri speaker product, with one sentence of actual news:

The iPhone-maker has started manufacturing a long-in-the-works Siri-controlled smart speaker, according to people familiar with the matter.

Seriously, that’s about it for news about the product.

Next sentence:

Apple could debut the speaker as soon as its annual developer conference in June, but the device will not be ready to ship until later in the year, the people said.

The keynote is five days away and Gurman and Webb don’t know if it’s going to be announced.

The device will differ from Amazon.com Inc.’s Echo and Alphabet Inc.’s Google Home speakers by offering virtual surround sound technology and deep integration with Apple’s product lineup, said the people, who requested anonymity to discuss products that aren’t yet public.

The “virtual surround sound” feature is arguably news, but there’s not one word about what “virtual surround sound” means. They could have at least linked to Wikipedia. And Ming-Chi Kuo had a report with details of the device’s “excellent acoustics performance (one woofer + seven tweeters)” a month ago.

Gurman and Webb:

Inventec Corp., the Taipei manufacturer that already makes the AirPod wireless headphones, will add the speaker to its Apple repertoire, the people said. Apple employees have been secretly testing the device in their homes for several months, they said. The Siri speaker reached an advanced prototype stage late last year, Bloomberg News reported at the time.

What does it look like? How big is it? Does it have a display? Crickets.

[Update: I missed this sentence at the end of Gurman and Webb’s report: “Apple’s speaker won’t include such a screen, according to people who have seen the product.” That sets up a delicious claim chowder standoff with Ming-Chi Kuo, who wrote two weeks ago, “We also believe this new product will come with a touch panel.”]

Apple has also considered including sensors that measure a room’s acoustics and automatically adjust audio levels during use, one of the people said.

What did Apple decide about those sensors? If the device is in manufacturing, and the device might be announced in five days, one presumes Apple has made that decision, no? Crickets.

“Apple’s long-rumored Siri-driven HomeKit speaker hub has entered manufacturing in Taipei” — there’s a 13-word summary with all the actual news in this story. I like Mark Gurman, but it’s painful to see these meager stale morsels stretched into feature articles.

AirPods — now that was a scoop. Nine months before Apple unveiled them, Gurman had an accurate description of how they worked, the charging case, and even had the “AirPods” name (albeit with a “which may be what these are called” caveat, and with the wrong assumption that AirPods would be Beats-branded rather than Apple-branded). With this Siri speaker dingus, he’s a month behind and has far fewer details than either Ming-Chi Kuo or Sonny Dickson.

The closer we get to the WWDC keynote, the more likely things are to get spoiled. But here we are 5 days out and no one has leaked just about anything about iOS 11 or MacOS 10.13, or what’s going on with this 10.5-inch iPad Pro, or if there’s anything new coming for WatchOS or tvOS. Again, there’s a lot of time between now and Monday morning, but it might be time to give Tim Cook credit for “doubling down on secrecy”. ★

What If the iPad Smart Keyboard Had a Trackpad?

Wednesday, 31 May 2017

Here’s an idea I tossed out on the latest episode of The Talk Show, while talking with Jim Dalrymple about what Apple might do with the iPad Pro: what if they added a trackpad to the Smart Keyboard? David Chapman took the idea and made a quick mockup of what it might look like. (I think the trackpad should be smaller than in his mockup — more like an older MacBook than a new MacBook, but his image conveys the general idea.)

I’m not talking about adding an on-screen mouse cursor to iOS for clicking and dragging. That’s a terrible idea. My loose idea for an iPad trackpad is based on a few things:

1. iOS’s trackpad-like mode for using the on-screen keyboard to move the insertion point around like a mouse cursor while editing text. A lot of people don’t know about this feature, and some who do misunderstand it, but it’s one of my favorite additions to iOS in recent years. If your iPhone has 3D Touch, while editing text you can hard press on the keyboard to turn it into a trackpad for moving the insertion point around in the text editing area. While in that mode, you can hard press again to change from moving the insertion point to selecting words (like double-click-then-drag on MacOS). iPads don’t (yet?) have 3D Touch, but you can access the same mode by putting two fingers on the on-screen keyboard and dragging. Two-finger touch on the keyboard and drag right away: move the insertion point. Two-finger touch on the keyboard, wait a moment for the insertion point to change to a barbell, and then drag: select words.

2. tvOS’s UIFocusEngine. That’s the interface framework that allows Apple TV to be controlled by a trackpad or game controller without an on-screen mouse cursor. On Apple TV, you don’t move a cursor around, you move the selection around. Two years ago Steven Troughton-Smith discovered that an incomplete version of UIFocusEngine was built into iOS 9.

3. As things stand today while using an iPad with any hardware keyboard, selecting text and moving the insertion point around stinks. Yes, you can use the arrow keys on the keyboard (along with shortcuts like Option to move word-by-word instead of character-by-character, and Shift to select as you go), but it seems like a regression to 1983 to encourage an entirely keyboard-based routine for text editing. The original Mac didn’t even have arrow keys on the keyboard, to force users to use the mouse for moving the insertion point.

In short, when you’re using the iPad’s on-screen keyboard, you have a crummy (or at the very least sub-par) keyboard for typing but a nice interface for moving the insertion point around. When you’re using the Smart Keyboard (or any other hardware keyboard) you have a decent keyboard for typing but no good way to move the insertion point or select text. Using your finger to touch the screen is imprecise, and, when an iPad is propped up laptop-style, ergonomically undesirable.

A hardware keyboard with a trackpad could have just as good an interface for moving the insertion point and selecting text as the software keyboard. Even better, really, since you wouldn’t have to use two fingers or start it with a 3D Touch force press. And, a trackpad would make this feature discoverable. An awful lot of iPad owners — most of them, probably — don’t know about the two-finger drag feature on the on-screen keyboard.

When you’re not editing text, the trackpad might not do much on an iPad. But the entire point of the smart keyboard is that you’re writing and editing text while it’s connected, or you’re just using it to prop up the iPad for watching video or something. But I think the trackpad could be used for selecting things or changing input focus. On the home screen you could use the trackpad to select an app to launch, just like on Apple TV. In split-screen multitasking mode, you could use a multitouch gesture on the trackpad to switch which pane has focus. Two-finger drags on the trackpad could scroll the current view, much like on the Mac.

I fully admit this is not a perfect idea. But I do think it would greatly improve the efficiency of text editing on an iPad, and if text editing isn’t an essential task for iPad users, I don’t understand why Apple bothered making the Smart Keyboard in the first place. And, unlike adding touchscreen support to MacOS, adding trackpad support to iOS would not harm anything that is good about the way things already are.

The biggest problem with this entire notion is that the way the Smart Keyboard folds from a cover to a keyboard would have to be redesigned, because the current design leaves no room at all for a trackpad. What I’m proposing might only be possible with a hard (non-folding) keyboard cover.

Stephen Coyle came up with a different idea:

The keys on the Smart Keyboard are very low profile, so it’s easy for one’s fingers to glide over them. With this in mind, why not make the entire top surface of the keyboard touch sensitive, then use it in the same way as the software keyboard? All that’s needed is a way to toggle trackpad mode, and I think this is a perfect opportunity to ditch the “caps lock” key, and replace it with a “trackpad mode” key, which can be held down while using one’s other finger to move the cursor.

There are a few reasons why I think this approach would be better than a discrete trackpad. First, it requires no extra space, nor any major changes to the current design. Second, as mentioned above, it maintains gesture parity with the current trackpad mode on iOS. Third, it removes the expectation of a system-wide, mouse-style pointer, which I think a laptop-style trackpad would create. I think this is a significant consideration; a more precise pointing device would be really useful on iOS for more than just text entry, but I don’t expect this to come in the form of a mouse pointer. Thus, I think avoiding the suggestion of one altogether would lead to less confusion. With my proposed method, pro users who need this functionality won’t take long to become aware of it, and users who don’t need it won’t have what they may perceive as a half-broken laptop trackpad present at all times.

Coyle very nicely summarizes the most common objection I’ve heard to the idea of adding a trackpad to iPad keyboards: that adding a mouse pointer to iOS is a bad idea because when users see the trackpad they’ll expect a mouse cursor system-wide, not just while editing text.

Maybe!

But my gut tells me this concern is overblown. Even if users expect a mouse cursor when they first see the trackpad, they’ll adjust quickly when they realize it isn’t there. If they wanted a MacBook they’d be using a MacBook. By definition anyone using an iPad is not expecting it to act like a Mac. I do think something should happen when you move your finger(s) around the trackpad even when you’re not editing text, but tvOS shows that that something doesn’t need to be a mouse cursor moving around the screen.

I have three objections to Coyle’s alternative solution. First, I think it would prove to be a technical challenge to create a touch-sensitive surface with Apple-quality latency and responsiveness that also doubles as a good surface for typing. The existing Smart Keyboard is rubbery for several reasons, but I don’t think rubbery can be used for a touchpad, and I think the gaps between keys would result in stuttery cursor movement. Second, making it a two-handed operation is clunky (and it would be two-handed for people who want to move the insertion point using their right hand). Third, making it a mode — even an easily toggle-able mode — feels like a bad idea. Modes aren’t always bad in UI design — the iOS software keyboard’s “move the cursor” feature is a mode — but it’s almost always better to avoid modality if you can. With a discrete trackpad, the keyboard is always the keyboard and the trackpad is always the trackpad. That’s better than a keyboard that is usually a keyboard but sometimes a trackpad.

I say don’t overthink it. Just put a small trackpad under the keyboard for moving the insertion point around and Apple TV-style navigation. Simple. ★

Halide

Tuesday, 30 May 2017

It takes some real grit to create a new iPhone camera app in 2017. To say that “camera apps” constitute a crowded category in the App Store is an understatement, and every camera app is competing against the system’s built-in Camera app, which (a) is very good, and (b) has built-in advantages — like being accessible from the lock screen by swiping right — that third-party apps can’t match.

Halide — a brand-new iPhone camera app designed by Sebastiaan de With and developed by Ben Sandofsky — rises to the challenge.

The first question Halide needs to answer is why should anyone even consider it instead of the system’s Camera app. The answer is that the Camera app has a wide range of responsibilities: separate modes for time-lapse, slow-motion video, regular video, regular photos, square photos, and panoramic photos. Camera also has to be usable by all iPhone users. Camera has a few semi-advanced features for still photography, like auto-exposure and auto-focus lock, but for the most part it only functions as a point-and-shoot camera, because it needs to be understood by the most casual of casual users.

Halide only does still photography. No video, no panoramic photos, no time-lapse. That frees precious on-screen real estate for advanced still photography features — the sort of things photographers expect from “real” cameras:

• A fast live-updating histogram.
• An easily-toggled, easily-used manual focus mode.
• Manual ISO and white balance controls.
• RAW support.
• Perhaps best of all, at least in my opinion, Halide has a focus peak feature: this highlights, in real time, which parts of the image have the sharpest contrast.

So if you’re a camera enthusiast, Halide easily passes the bar for features that justify the price (a mere $2.99 for now, but going up to $4.99 in a week). But as I mentioned before, there are dozens, maybe hundreds, of camera apps in the App Store, and none of Halide’s features are unique to it.

What sets Halide apart is design.

How the features are arranged. How they are accessed. How they are indicated visually. With traditional camera hardware, good reviews spend a lot of words talking about not just what the camera does, but what it is like to use. Camera reviewers often obsess over the placement and feel of all the buttons and dials. Halide brings that sort of obsessive attention to the placement and feel of its controls. This sort of maniacal attention to the smallest of details deserves to be celebrated.

Here’s how de With and Sandofksy put it in their announcement:

Smartphone cameras have improved massively over the years, but the shooting experience hasn’t. The built-in camera app is a little too simple, while advanced apps feel like an airplane cockpit. We needed an elegant app for deliberate and thoughtful photography, so we built Halide. […]

Lots of little details are scattered around the app, like a full fledged retro styled user manual and a custom typeface for the UI called Halide Router, developed by Jelmar Geertsma.

This was a labor of love. It’s an effort by two friends who love photography and found there wasn’t a tool out there that met our needs. We wanted a premium camera for our phone.

I love the page-turning in the user manual, and I love the textured shutter button. There’s a way to do modern UI design while keeping some whimsy, texture, and depth — and Halide is a wonderful example of how to do it right.

The custom Halide Router typeface is what puts the whole thing over the top in my book. For chrissake just look at it:

Clearly inspired by the lens inscriptions on kit from Leica and Zeiss, it just exudes camera-ness. The fact that Sandofsky and de With went so far as to commission a custom typeface is probably all you need to hear about Halide. Some of you will hear that and think “That’s insane, why would anyone waste so much time and effort on a custom typeface just for a few UI controls?”

The rest of you are like me, and will think, “That’s insane, I need to check this out immediately.” ★