The fact that I own an Android phone has rarely been more obvious than when I use my iPad–and I try to “gesture type” as if I were using my smaller mobile device’s onscreen keyboard.
The arrival of iOS 8 and its support of third-party keyboards made tracing a path from letter to letter to enter text not just a pointless exercise but a possibility. And with iOS 9’s less buggy support, it’s become a less annoying possibility, but still not a sure thing.
That’s become clear to me since Google shipped its Gboard keyboard app in May and, after a satisfactory tryout, I made that free app the default keyboard on my iPad mini 4.
Most of the time, Gboard appears whenever I touch a text field. I can gesture-type with ease (except when I’m holding the tablet sideways), and I could season my prose with emojis and GIFs were I, you know, 20 years younger.
But Apple’s built-in keyboard keeps on surprising me by resurfacing on its own. To get a better sense of how often that happens, I tried taking notes on this behavior this week and reached three conclusions:
• The system works more often than I gave it credit for. The departures from the norm stick out, but keeping track of them made me realize how rare they are.
• In certain cases, the stock keyboard shows up because it’s supposed to. As an Apple tech-support note explains, iOS’s keyboard automatically takes over in secure data-entry fields like the password dialogs of the App Store and Amazon apps.
• In rare occasions, iOS does get confused about keyboards for no apparent reason. A tap of the address bar in Safari would sometimes invoke the stock keyboard instead of Gboard, while the Duolingo language-tutorial app proved itself capable of alternating between the iOS and Google keyboards in a single session.
It’s tempting to blame Apple, given the iffy quality of much of its software. But I can’t rule out this being Google’s fault. I mean, as good as Gboard is, I still had to do a copy-and-paste job from a Web site to enter the symbol that best captures my latest diagnosis of the situation:
Pingback: Goodbye, Nexus; hello, Pixel | Rob Pegoraro