improve word selection
Currently, swipe typing gibbers me the wrong word almost always. Like there, I corrected 4 of the words in that first sentence bit O left gibbets because like wtf? why in the heck would it think I want to type gibbers? AMD these stupid troops (tips!!! typos! -- swipe won't recognize "typos" every) plague every sentence I type. theft is an issue in regular default keyboard top, buy out (but it) is even worse here with tie (your ) keyboard. I meet (never ) had so much trouble typing ok Android. I was hoping this keyboard would be ab improvement ("ab" 🙄 seriously? It always governess that instar of "at". I sweat (swear ) this is stupid world now!
can I not auto insert space after every word?
Also, please include a tiny opensource LLM, as an option for people with slightly older phones. I know there are tiny LLMs that I can run on iPhone 12 even without apple intelligence. include it ad an option with a disclaimer about potential performance issues and increased power drain, and have an option to be able ti easily turn it on/off directly from the keyboard. The godawful lack of sensible contextual auto-correction/auto-suggestion call for a tiny LLM to handle reasonably not utterly imbecilic contextual fictional (functionality ).
cloud Ai for keyboard is completely unacceptable. maybe I'll experiment with your api option before the demo expires. somehow I doubt u can connect to my own llama.cpp server running on my lab (lan)? if I can though then I might pay for the keyboard anyway, depending on how well it works.
also if you auto -insert spaces you really should remove the space when people type things like - and ) abs other things like }, you do it for periods and commas but not for hypens or brackets?
so far the demo experience had been just worse than default keyboard. which is too bad cause I would totally pay for a better keyboard.
Discussion
Sign in to comment or vote.
@ultranash the swipe mistakes you listed come from the current engine, and I'm replacing it. A new engine is already in testing and comes to the App Store in one of the next updates.
After a swipe the space doesn't go in right away, only when you start the next word. So a - or ) typed straight after a swiped word sticks to it (never-corrected, (this)). If you tap the space bar yourself, I leave that space alone, because "a - b" is a normal way to write a dash.
Whether the keyboard can reach your llama.cpp server is up to your setup: it has to be reachable from the internet, not just your LAN, and over HTTPS, since iOS blocks plain http. Then pick OpenAI-compatible under API key and enter the address. It's used for translation and AI edits, not for corrections while you type.
I did try a small model on the phone for corrections. It made every word noticeably slower, so it's off for now.