I've always liked Gboard, Google's alternative keyboard for iOS. Gboard combines Google's intelligence (with accurate and personalized autocorrect, emoji and GIF suggestions) with handy features such as glide typing. However, as I mentioned before, I couldn't use Gboard as my primary keyboard on the iPhone for a variety of reasons: it lacked iOS' native dictation mode, couldn't automatically switch light and dark themes depending on the context of the current app, and, worst of all, it didn't support multi-language typing without manually picking a different keyboard layout.
Siri dictation and simultaneous multi-language support are still missing (the former will likely never be added), but today's update is an important step towards making Gboard feel more integrated with iOS. Gboard can now switch its default theme between light and dark based on the app you're using. I'm not sure how Google pulled this off, but I tested Gboard with the dark modes in Apollo, Tweetbot, Copied, and Bear, and the keyboard always used the dark theme instead of the light version. Conversely, in Safari, App Store, and other light-themed apps, Gboard used the light mode instead.
This was one of my complaints about the old Gboard: its default light theme looked garish in dark apps; on the other hand, if you persistently enabled Gboard's dark theme, then it would look out of place in apps like Messages or Mail. With automatic theme switch, changing Gboard's default appearance is no longer a concern because it adapts to the app you're using.
I've found a couple of apps where Gboard doesn't correctly apply the dark theme (Overcast is one of them), but I'm impressed overall; Gboard even switches to the dark theme when you swipe down on the Home screen to open Spotlight. I'd be curious to know which iOS API Google is using to implement this option, and if third-party developers can optimize for Gboard in any way.
There’s been quite a stir over the last week regarding an area of the Apple cloud ecosystem where syncing has remained unreliable for years. Brian Stucki wrote a detailed post on the matter, which John Gruber linked to with echoing sentiments. Today, however, Gruber followed up on his post with an exciting update:
Good news related to yesterday’s item regarding the fact that text replacement shortcuts have never synced reliably between Macs or iOS devices: an Apple spokesperson emailed me to say they checked with the team, and an update that moves text replacement syncing to CloudKit should be rolling out to iOS 11 and MacOS 10.13 High Sierra users in the “next month or so”.
I use text replacement every day across my iOS devices, and haven’t dealt with syncing issues myself, but it’s great to hear that this long-standing problem should soon be put to rest for everyone else. Recent history shows that once a cloud product moves to CloudKit, syncing issues disappear almost entirely – hopefully that will be the case here as well.
One of the best third-party keyboard options on iOS just got better. The latest update for Gboard adds special integrations with two Google services: YouTube and Google Maps.
When using Gboard, tapping the G button will now present YouTube and Maps tabs alongside the standard Search option. Both new options present an assortment of suggestions when you first open them, along with the expected search function. YouTube’s suggestions appear to be a selection of top trending videos; in my testing Gboard wouldn’t show any videos personalized to me or my watch history, but that may change over time with more use. Maps shows an assortment of nearby locations, as well as your current location if you grant that permission. Making a selection copies a link to the content inside the text box, alongside a brief description of what you’re linking to.
The market for third-party keyboards on iOS has largely grown stagnant, but Google continues to show its commitment to Gboard. While adding new features to a keyboard could clutter its interface before long, YouTube and Maps are natural fits for Gboard, integrating well both from a functionality standpoint and in their placement in the interface.
I've been carrying Studio Neat's new Canopy, a combination keyboard case and iPad stand, for about a week. It's the first time Apple's Smart Keyboard has been off my iPad Pro since I got it, but I haven't missed it at all. There are still certain situations where I prefer the Smart Keyboard, but I love having the option to work on my iPad with Apple's Magic Keyboard when it suits my needs. So, while I won't be switching to a Magic Keyboard/Canopy combination full-time, it's a choice I'm glad to have and one I will use frequently.
Since getting a 12.9-inch iPad Pro last year, I've had a fairly troubled relationship with external iPad keyboards. I didn't like the original Logitech CREATE keyboard case, so, surprised by the lack of notable Smart Connector-based accessories, I ended up using an Apple Magic Keyboard for the majority of 2016.
Good overview of the Touch Bar and its developer API by Benjamin Mayo:
Developers can display pretty much whatever they want whilst their app is in the foreground; this includes swapping out views and buttons depending on the current window of their app (a compose window necessitates different Touch Bar accessory views than the inbox window). However, the Touch Bar does not allow persistent widgets, status items or similar features like always-visible news tickers. These constraints are unlikely to be lifted either; Apple is imposing the restriction so that the UI under the user’s finger isn’t constantly changing due to spurious notifications or text messages.
Apple wants the bar to display peaceful relatively-static UI based on the current task. Major changes to the Bar should only happen when the application state drastically changes, such as opening a new tab or beginning a new modal activity. To repeat: once an app’s window is not active, it loses its control to influence what is shown on the Bar. The system Control Strip sits to the right in a collapsed state by default, but can be disabled entirely in System Preferences if desired.
This makes sense to me: the Touch Bar is intended to be an extension of the keyboard that deals with input – it's not a smaller Dashboard or a widget container. This means that apps like PCalc won't be able to persistently display their controls in the Touch Bar unless they're the frontmost (active) app.
The more I think about it, the more the Touch Bar feels like the natural evolution of QuickType and the Shortcut Bar from iOS – to the point where I wonder if we'll ever get this kind of evolution on the iPad Pro as well (where the current app is always the frontmost one and system controls could use a faster way to be engaged than Control Center). Perhaps with a new external keyboard with its own embedded Touch Bar and T1 chip?
Google released a nice update to their iOS keyboard, Gboard, earlier today.
Cursor control can now be activated with 3D Touch, which is consistent with the behavior of Apple's keyboard. Gboard can't move the cursor freely on the screen like the system keyboard, though, which makes it more limited when it comes to swiping across multiple lines of text. Also, Google didn't implement haptic feedback when switching between contextual keyboard menus (such as holding down on the dash key), which is another detail that I appreciate in Apple's keyboard on the iPhone 7.
Similarly, Gboard now features Contacts integration to look up a person's contact card directly from the keyboard – but it's not as tightly integrated as QuickType suggestions in iOS 10. However, I prefer the presentation of contact cards in Gboard and I think Google's is a sweet solution as well.
Gboard is shaping up nicely, but I continue to wish Google paid more attention to the iPad layout and built true multilingual support for international users.
Nice update to Google's custom keyboard for iOS released today on the App Store:
Gboard is already available in English across the U.S., Europe, Canada and Australia. Starting today, Gboard is ready to start sending GIFs, searches, emojis and more for our friends who speak French, German, Italian, Portuguese (Brazil and Portugal) and Spanish (Spain).
Gboard's emoji search is the best way to search for any emoji I've tried on iOS. iOS 10's predictive emoji suggestions aren't even close to the Gboard's emoji features. I was hoping iOS 10 would have proper emoji search – maybe next year.
But I'm surprised that Google hasn't shipped an actual multilingual keyboard to type in two languages simultaneously. You have to switch between international layouts inside Gboard – just like in Apple's current keyboard for iOS 9. By contrast, iOS 10's upcoming multilingual keyboard is downright amazing, and I can't go back to keyboards without multilingual support now.
Apple has introduced new Smart Keyboards for the iPad Pro with localized layouts for several languages. According to 9to5Mac, the localized Smart Keyboards include British English, French, Spanish, Italian, Arabic, and others. The keyboards are available to fit both the 9.7 and 12.9 inch models of the iPad Pro and are available from Apple’s websites in the countries where the applicable languages are spoken, along with the existing US English version of the keyboards.