I am fed up of the stone-age autocomplete Gboard/MS SwiftKey virtual keyboards are providing for my Android phone. Especially for non-English languages with many word variations (1 word can have 10 prefixes/suffixes depending on context).
Do you consider reusing your Tab language model for making a superior autocomplete for phone keyboards? That may open another whole market and help Cursor users type prompts faster on their phones. Sometimes it’s not appropriate to voicetype.
Hey, thanks for the feature request. It’s an interesting idea, especially for languages with rich morphology where stock keyboards can feel pretty limited.
To be honest, Cursor Tab is a code autocomplete model that works off the editor context like files, diffs, and cursor position. It’s not a general text model for regular typing. A full phone keyboard for Android IME or an iOS custom keyboard would be a totally separate product, not an extension of Tab.
Right now our focus on mobile is the app for working with agents, and we don’t have any plans for a keyboard or IME, so there isn’t anything to share.
I’ll keep the thread open. If it gets more votes and community interest, that’s the best signal for the team. Thanks for sharing.