Six updates in, iPadOS still needs work

It hasn’t even been two months since Apple shipped iPadOS, but in that time the tablet offshoot of iOS 13 has seen six maintenance updates–from iPadOS 13.1.1 to 13.2.3.

That plethora of patches has squashed some obvious bugs, like the ones that made Dock shortcuts to recently-opened non-Apple apps inert. They have not, however, cured other trying aspects of iPadOS:

• The new QuickPath gesture-typing option is, for some reason, confined to the floating keyboard you can invoke, not the standard-sized one. Has nobody at Apple tried using Google’s Gboard?

• The new multiple-windows option for an app is buried beneath a long-press of a Dock icon–sufficiently hidden that I did not realize that feature existed until reading Ars Technica’s iPadOS review.

• I appreciate Apple’s attempts to make me aware when apps request my location in the background, but after being nagged 10 times about my choice to let the Dark Sky weather app check my coordinates in the background, I’d appreciate having an option to the effect of “I know what I’m doing and you can stop asking about this.”

• Seeing which apps have updates or have been recently updated takes more steps than in iOS 12–presumably, so that Apple could use that spot at the bottom of the App Store app to promote its Apple Arcade subscription gaming service.

• The process of moving app icons around feels even more maddening than before, especially if I happen to drop an app inside a folder by mistake. Meanwhile, the OS still affords no relief from its inflexible app grid; I can’t leave a row or a column blank as negative space to set off particular icons.

• AirDrop remains as enabling of anonymous harassment as ever.

• I still see display glitches like the charming overlap of portrait and landscape screen modes shown in the screengrab above.

It’s not that I regret installing iPadOS–some of the new features, like the privacy-preserving Sign in with Apple option, are only starting to reveal their promise. Others, such as the Sidecar Mac screen-mirroring option, require newer hardware than the aging iMac on which I’m typing this. But seeing these obscure, illogical or insensitive bits of user experience, I can’t help thinking of all the times I’ve taken a whack at Windows for the same sort of design stumbles.

News sites, can you at least stop nagging distant readers to get your local-update newsletters?

With my industry becalmed in its current horrid economic state, you’d expect news sites to strive to make new readers welcome. Instead, they keep resorting to clingy, creepy behavior that must send a large fraction of those new readers lunging for the back button.

I’m speaking, of course, of the giant sign-up-for-our-newsletter dialog that pops up as you’ve read a third or half of a story, encouraging you to get that site’s latest updates in your inbox.

This is dumb on strict user-experience grounds–at a minimum, you shouldn’t see this until you’ve read to the end of the story. Would you like NPR affiliates to run their pledge drives by sounding an air horn in the middle of Morning Edition and then asking for your money? No, you would not.

But the newsletter nag looks especially dumb when a local newspaper greets a distant reader with this interruption. The odds that I’m going to want daily updates about developments in Richmond, Buffalo (as seen above), or some other place where I do not live are just about zero. And the fact that I’m reading hundreds or thousands of miles away should be obvious to every one of these sites via basic Internet Protocol address geolocation.

I’m willing to click or tap those dialogs closed and keep reading, because I don’t want to sandbag the journalism business any further. But it’s hard to blame readers who instead respond by switching to the stripped-down reader-view option of Safari or Firefox. Or by running an ad blocker.

AirDrop apologists have some opinions

Who knew suggesting that an Apple interface enabled undesirable outcomes and ought to be changed would be so controversial? Me–I’ve been critiquing Apple’s products since before the company was doooomed in 1996.

But even so, the level of enraged techsplaining that greeted last weekend’s Yahoo post about AirDrop file-sharing has been something else. To recap that briefly: While AirDrop’s default contacts-only setting is safe, accepting a file transfer from somebody not in your contacts requires setting it to “Everyone”–a setting that does not time out but does automatically display a preview of the incoming image. The predictable result: creeps spamming strangers who had set AirDrop to Everyone and then forgot to change it back, and by “spamming” I mean “sending dick pics from iPhones with anonymous names.”

AirDrop settings screen on an iPhone.(For more details, see my Aug. 2017 USA Today column or this Dec. 4 post from the security firm Sophos.)

Suggesting that Apple have the Everyone setting time out or not auto-preview images did not go over well the people–most apparently men–who filled the replies to my tweet Sunday sharing the post. Let me sum up the major points these individuals vainly attempted to make, as seen in quotes from their tweets:

“It’s contacts only by default.” Yes, and if nobody ever interacted with people who weren’t in their contacts and offered to use this handy feature to share in a file, you would have a point. As is, this request comes up all the time–my wife saw it from Apple Store employees–as I explained in the post that these techbros apparently did not finish reading.

“Still trying to make a big deal of something I’ve never experienced.” Thank you, sir, for proving my exact point about the problems of having development teams dominated by white men. As writing about “Gamergate” made obvious, things are often different for the rest of humanity, and “I don’t have this problem” is not a valid defense of a social feature without confirmation from people outside your demographic background. Sorry if asking you to acknowledge your privilege is so triggering, by which I mean I’m not sorry.

“At some point, you have to take some goddamn responsibility.” Ah yes, the old blame-the-customer instinct. I hope the multiple people who expressed some version of “why are you coddling people too dumb to turn Everything off” don’t and never will work in any customer-facing role.

“you don’t have to accept every airdrop item that comes in.” What part of “automatically display a preview” don’t you understand?

“What I don’t understand is why these creeps aren’t reported by the receivers to authorities.” What part of “iPhones with anonymous names” don’t you understand? And before you next resort to victim blaming like this, you should really read up on the relevant history.

“There are far worse UX issues in iOS if that is what you are concerned about.” News flash, whataboutists: I write about problems in the tech industry all the time. Stick around and you’ll see me take a whack at a company besides your sainted Apple.

And that brings me to the annoying subtext beneath all these aggrieved responses: The notion that questioning Apple’s design choice is an unreasonable stretch, so we should look anywhere else for solutions to what even most of my correspondents agreed was a problem. Well, if that’s your attitude, turn in your capitalist card: You’re not a customer, you’re a supplicant. And I don’t have to take your opinion here seriously.

Ugh, Washington Gas is the worst at customer experience

We got a message on our home phone yesterday from Washington Gas, and even by voicemail standards of annoyingness it was unhelpful: “We value you as a customer. Please contact us for an important message.”

Right, I’m going to listen to a voicemail and call a company back in 2019 to get a message that it could just put in my account online. Unfortunately, that is not at all out of character for how the D.C. area’s gas utility operates. Even when its customer site hasn’t been in the grip of a relaunch meltdown that left me unable to login for weeks, it’s mainly functioned as an exhibit of how not to run a payment portal.

The single biggest failing here comes if you choose to pay your bill via credit card–as you absolutely should, since there’s no surcharge compared to a bank deposit and you can make 2 percent cash back on each payment via a Citi Double Cash card. (I will set aside for now the fact that we’ve just had to get this card replaced for the third time in four years after some joker tried to make yet another fraudulent purchase on our number.) But clicking the button to pay via credit yields a dialog from the previous century: “A popup blocker is currently enabled. Please switch this to disable for Credit Card payment to function.”

Fortunately, you can disable pop-up blocking for a specific site in Chrome and Safari. Doing so will allow the Washington Gas page to launch a full-screen page from a service called Kubra EZ-Pay. EZ, this experience is not so much: It breaks the entry of your credit-card across two screens, which seems to stop Google Pay from auto-filling the second one, then asks for a phone number and e-mail when neither should be necessary in this transaction.

It’s all a pain, yet I keep taking this payment option because I don’t want to give Washington Gas the satisfaction of knowing that I gave up a 2 percent return because of its janky user interface. The only problem is that because I can’t automate a credit-card payment, I sometimes forget about this bill… which is what I suspect that call was about, not that the Washington Gas payment portal had any message of its own following up on the call.

This is the worst interface I’ve ever seen

Our water heater broke sometime Monday, and we found out the analog way: Only cold water came out of the tap.

A visit to the basement revealed that the heater had already been reporting a problem in the least intuitive way possible. A single green LED on an assembly near its base was blinking out a pattern–eight flashes in a row, followed by a pause of a few seconds and then two more flashes.

That sequence, a small sticker explained, was the heater’s way of saying “Temperature sensor fault detected.” This same sticker listed 17 other sequences of flashes and pauses that could report anything from “No faults” to “Flammable vapor sensor fault detected.”

(The temperature sensor had indeed gone bad, although it took multiple visits by techs to confirm that and then return with a working replacement. This has left me with a renewed appreciation for household modern conveniences.)

That’s an awful user interface. It’s also what happens when you supply a single, single-color LED to display the status of a fairly complex home appliance. Bradford White, the manufacturer, could have put in a light that changed color–seeing a once-green indicator turn to red is usually your tip that something’s changed for the worse–or put in two or more LEDs.

Or that firm could have splurged on a digital readout capable of showing numeric error codes, bringing the discoverability of this interface up to that of the “DSKY” control of the Apollo Guidance Computer that NASA astronauts sometimes struggled to decipher on their way to the Moon.

Instead, sticking with that sole green LED and offloading the work of discovering its Morse-code-esque interface to customers may have saved Bradford White a dime per heater. On the upside, I’m now pretty sure I’ve seen the worst possible UI. I mean, not even Lotus Notes got this bad.

Samsung’s Android versus stock Android: how six common tasks compare

I didn’t get around to reviewing Samsung’s Galaxy S7 and Galaxy S7 Edge after their introductions at Mobile World Congress this February, but a couple of months ago Verizon Wireless PR offered to loan me one anyway. The device had a useful cameo role in a story about mobile payments, I did my customary battery-life tests, and then I had one last chore: taking notes on the differences between Samsung’s “TouchWiz” version of Android and the stock-condition software I have on my Nexus 5X.

Galaxy S7 and Nexus 5XThese interface gaps aren’t as jarring as they used to be, thanks mainly to Samsung having an attack of sanity and no longer putting a menu button where Android’s standard recent-apps button should be. Instead, a back button occupies that space, with recent-apps’ overlapping rectangles moved to the bottom-left corner.

But some differences remain, and I should keep them in mind the next time I’m writing up a cheat sheet about how to tackle certain Android chores. Consider this post a little FYI to myself…

Enable airplane mode:
• Samsung: Swipe down from the top of the screen to show the Quick Settings bar, swipe left to reveal the “Airplane mode” button, tap that. You may see a confirmation dialog if you haven’t told the phone not to nag you about this again.
• Stock: Swipe down twice (or swipe once with two fingers) and tap “Airplane mode.”

Check data usage:
• Samsung: Swipe down to show Quick Settings, tap the gear icon, choose “Data usage” in the Settings app you just opened. Or, less obviously, swipe down twice or swipe once with two fingers, then tap and and hold the “Mobile data” icon.
• Stock: Swipe down twice or swipe once with two fingers, then tap the signal-strength icon.

View app permissions:
• Samsung: Swipe down to show Quick Settings, tap the gear icon, choose “Privacy and emergency” in the Settings app you just opened, tap “App permissions.”
• Stock: Swipe down twice or swipe once with two fingers, tap the gear icon, select “Apps” in the Settings app, tap the top-right gear icon, tap “App permissions.”

Pair with a Bluetooth device:
• Samsung: Swipe down, tap and hold the Bluetooth icon.
• Stock: Swipe down twice or swipe once with two fingers, tap the menu below the Bluetooth icon.

Check per-app battery consumption:
• Samsung: Swipe down, tap the gear icon, choose “Battery” in the Settings app.
• Stock: Swipe down twice or swipe once with two fingers, tap the battery icon.

See how much storage space is left:
• Samsung: Swipe down, tap the gear icon, choose “Storage” in the Settings app.
• Stock: Swipe down twice or swipe once with two fingers, tap the gear icon, choose “Storage & USB” in the Settings app.

Overall, I don’t see Samsung’s interface saving any time compared to Google’s. Which makes me wonder yet again why it bothers to craft such a different front end for this operating system.

What posting a Facebook Offer taught me about Facebook’s privacy rules

Some months ago, a PR person for Gogo handed me a few freebies I probably couldn’t use: three free passes for that company’s inflight WiFi service. (Ethics aside, almost all of my transcon flights are on planes that don’t employ its connectivity, while on shorter flights Gogo’s unintentional free access to Google apps suffices.) Many weeks later, I finally remembered that I could try giving the passes to readers with the Offers function on my Facebook page.

Gogo WiFi passesIt seemed simple enough: You create a special post on your page with the image and brief description of your choice, you set an expiration date and limit how many people can claim the deal, and you watch the audience love roll in.

But I didn’t realize, by virtue of not reading the documentation before, that readers would have to take an extra step to collect this freebie. The lucky winners got an e-mail with this instruction: “To use the offer, visit Rob Pegoraro and show this email.”

As the page owner, meanwhile, I only got a notification that the offer had been claimed–without a hint of who had won it. As Facebook’s help explains: “To protect the privacy of the individuals who claimed your offer, you will not be able to see any of their personal information.” They’d have to get back to me somehow.

I wasn’t planning on any face-to-face interaction, but I didn’t get much of the digital sort either. One longtime reader left a comment saying he’d redeemed the offer–I took him at his word and e-mailed one of the three Gogo alphanumeric codes–and nobody else responded, even after I posted comments imploring them to e-mail me.

That’s bad in the sense that I have some readers wondering why they never received the free inflight WiFi they sought. But it’s good in the sense that Facebook seems to have defaulted to privacy at the expense of marketing convenience.

That, in turn, matches up with such Page limits as my not being able to send messages to fans unless they’ve sent me one first. So if you were holding off on Liking my page because you didn’t want your name in lights–go ahead, since even I probably won’t know unless I spend a lot of time scrolling through Graph Search results for “people who like Rob Pegoraro.”

(Whoever can see your profile will, however, see your new Like. If they already mock you for your taste in tech news, you might want to hold off on the appreciation.)

In the meantime, I have two Gogo passes left. Let’s do this instead: E-mail me about how you’ll make great use of them, and the first two people to send a persuasive story will have the codes in their inboxes soon after.