data_entry_ops · saas · workflow
Google Research launches on-device grammar correction in Gboard on Pixel 6
Composing longer text on smartphones is cumbersome; grammatical errors frequently creep in and are time-consuming to correct on a small display. Building an on-device grammar correction feature required addressing memory size limitations, latency requirements, and the challenge of handling partial sentences.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · User types in Gboard
Gboard sends a request to the on-device grammar model whenever the user has typed more than three words, whether the sentence is completed or not.
Tools used
GboardTransformer encoderLSTM decoder
Outcome
The on-device grammar correction model requires only 20MB of storage and performs inference under 22ms on 60 input characters on the Pixel 6 CPU, processing text entirely on-device to preserve privacy, with hard distillation producing significantly higher quality suggestions than training on the original cloud model data.
Results
Time savedunder 22ms
Volume20MB
Running sinceOctober 2021
Grounding & classification
Source type: technical build writeup
17 fields verified against source quotes.
content generationchat transcriptmetric backedproduction runtime claimedtools describedworkflow describedsoftwareaccuracy improvementtechnical build writeupdata entry opsmonitor detect alert