The friction no one plans for
Before using SpellCheck, text quality was one of those issues that never fully disappeared.
Copy lived across dozens of frames and flows, often updated until the last moment. Figma’s native spellcheck helped only while editing individual text layers, which made it easy to miss errors at scale. There was no simple way to review everything at once.
As a result, the process relied on manual checks. Screens were reviewed one by one, important flows were double-checked before handoff, and still, small mistakes occasionally slipped through.
Everything can look perfect visually, and then one small typo ruins the impression completely.
Alexander Gladilin
Senior Digital Designer at Sliday
This created constant friction — slower reviews, extra communication with developers, and a lingering uncertainty before delivery.
A small shift in the workflow
SpellCheck fit directly into Alexander’s existing workflow without adding complexity.
Instead of manually scanning files, he could run a check across a full page or the entire project and immediately see all text issues in one place. Corrections could be made instantly, without leaving Figma or breaking focus. What used to be a repetitive, attention-heavy task became a quick, reliable step.
It feels like a final QA step, but for text — and it takes seconds.
Alexander Gladilin
Senior Digital Designer at Sliday
Over time, this shifted how he approached design. Text validation stopped being something to remember later. It became automatic.