"..." everywhere

[louistimlululu]

I testet some cotypist alternatives and this is the best so far, but a lot of completions are still nonsensical.
While other apps sometimes give u non existing words keytype is good at actually giving u real compilations that form a real sentence.
however a lot of times the completions are possible completions, but not what I wanted to type.

One thing I particularly noticed in all the alternitves is "..." as a completion this happens sometimes for full sentences but especially if u stop in the middle of a word.
To be fair ... is an accurate ending to an sentice or word... ,but not a very useful one.

Also I noticed that the speed of the small model matches the speed of the 2b Modell at cotypist while the 2b Modell in keytype has me waiting for completions.

another minor problem is font size of the ghost text not matching the real one. And compilations just not generating

Overall keytype is great and realy impressive! Im just missing the magic feeling of it "reading ur mind"

[johnbean393]

@louistimlululu

Let me address your suggestions one by one.

1. "..."

Believe me when I say this used to be a more serious issue; I'd get absolutely nonsensical suggestions like "*cd.." or "11111111"!

That being said, completion quality and latency are my top priorities for KeyType. I'll keep pushing hard on this front.

Speaking of latency... (I tried to fit a "..." into my comment haha)

2. Latency

You are right that using a bigger model typically leads to better completions, but can have more latency and reduce overall utility. Cotypist did an excellent job balancing latency and quality, and it's the "industry" standard for good reason.

So far, I've managed to speed up constrained branch generation to 500% of my initial baseline. My understanding is that inference wise, the remaining levers might not have great ROI.

Starting with release V1.2, I'm shifting focus to work on other non-inference areas that can lower latency, like caching. More improvements will drop soon.

If you have sufficient memory (≥32GB), I recommend LFM2.5-8B-A1B-Base for the best balance between latency and quality. More information here.

3. Fonts

KeyType uses the macOS Accessibility API to capture font, text field and text caret information. This is undoubtedly one of the worst APIs on macOS, and there are a ton of edge cases across apps.

Getting the ghost text to show up and work perfectly across apps will take time, and I'm glad most people seem to understand this!