Google appears set to address one of the most persistent complaints about Gboard, the default keyboard app on Android devices, in the upcoming Android 17 release.
Gboard’s autocorrect function has drawn sustained criticism from users for overriding intentional word choices, particularly with names, slang, and technical terms.
What Is Changing
Android 17 is expected to introduce behavior changes that give users more control over how autocorrect applies corrections during typing, according to early reports citing code changes in Android’s developer preview builds.
The specific mechanism under review involves the keyboard’s tendency to silently substitute words after a user taps the spacebar, a behavior many users describe as disruptive to their writing flow.
Why It Matters
Gboard ranks among the most widely used mobile keyboard applications in the world. Google lists it as having over one billion installs on the Google Play Store.
On Android, Gboard ships as the default input method on most devices running the operating system. That scale means even incremental changes to its behavior affect a substantial share of global smartphone users.
The Broader Context
Google has updated Gboard’s autocorrect model multiple times in recent years, incorporating on-device machine learning to personalize suggestions based on individual typing habits.
Still, user frustration has remained a consistent thread across Android community forums, with complaints concentrated on the keyboard correcting words after a deliberate pause — a pattern distinct from catching genuine typos mid-word.
The Android developer preview cycle typically runs from early in the calendar year through a stable release in the third quarter. Google has confirmed Android 17 is in active development, with the first developer preview already available to registered developers.
Earlier Android releases have incrementally expanded Gboard’s customization options, including the ability to add words to a personal dictionary to prevent repeated corrections.
That option, while functional, requires manual upkeep by the user and does not address the underlying autocorrect behavior at the system level.
Google has not issued a formal statement confirming the specific fix or detailing its technical scope. Reports of the change draw primarily from analysis of Android 17 developer preview code, a method that has reliably surfaced upcoming features in past release cycles but does not constitute official confirmation.
The final feature set for Android 17 remains subject to change before the stable public release.
-
-
-
-
-
-
-
-
