Why does swipe to type suck so much?

Generated on 7/31/2024

1 search

The issues with "swipe to type" could be related to several factors discussed in the WWDC sessions, particularly around text input and multilingual support. Here are some potential reasons:

  1. Marked Text Handling: In languages like Chinese or Japanese, the keyboard uses marked text, which is temporary text before a suggestion is chosen. If an app modifies the text on every keystroke to provide auto completions, it can interrupt typing. Ensuring that there isn't any marked text before modifying the text can help improve the experience (Build multilingual-ready apps).

  2. Font and Script Compatibility: In some languages, such as Hindi, the way text is highlighted can cause it to appear broken. This is due to the way vowels and other marks attach to letters. Using consistent fonts and ensuring compatibility can help mitigate this issue (Build multilingual-ready apps).

  3. Localized Standard Range: Different languages have different rules for what are considered different spellings. Using APIs like localized standard range can help match text more accurately across different scripts and spelling conventions (Build multilingual-ready apps).

  4. Text Entry Suggestions: Ensuring that text entry suggestions are relevant and keep up with the typing speed is crucial. Providing consistent and predictable suggestions can help build trust and improve the typing experience (What’s new in AppKit).

For more detailed insights, you can refer to the sessions: