Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Reconsider adaptive touch correction? Slimmer proposal with details

Aperta
  • Qualcosa non va?
#676 2 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@4di-hello ci sta già lavorando.

Dal 14/10/2026.

  • #680 di @4di-hello — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, kotlin
Ambito
mobile

Direzione di ricerca

This is a design proposal, not a ready task. Read the maintainer's earlier concerns in #671 and the open pull request #680 before anything else. The payload names InputLogic as the core file the change touches, plus a separate statistics package with 17 tests. Done means the maintainers have agreed on a design, not that a patch exists. Wait for that decision before starting code.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Thanks again for reviewing #671. I'd like to explain the feature in more detail and offer a much slimmer version, because I think it addresses your concerns.

Why it matters
I'm an experienced, heavy phone typist. Still, over ~1,250 recorded touches about 13% landed on a neighboring key — roughly every 8th letter. And it's systematic, not random: "a" hit as "s" is consistently my most frequent miss. A fixed, per-user offset like this is exactly what adaptive touch correction fixes, and as far as I know it has been standard in mobile keyboards for many years.

What it does
The keyboard learns where this user actually touches each key, based on the words they finally commit (including reverted autocorrections and self-corrections). Once a key has enough data (30+ touches), a touch near the border between two keys is assigned to the key the user most likely meant. The shift is capped to a fraction of a key width, and the dictionary receives the corrected coordinates too.

Your concerns

  • Determinism: same data, same key. It only differs from today near key borders and only after enough data. With the feature off, the exact current code path runs.
  • Latency: per touch a few arithmetic operations on cached offsets, no I/O.
  • Muscle memory: it adapts to the user's muscle memory instead of changing it.
  • Code footprint: of the ~1.5k lines, ~1.45k are in a separate package (model, statistics screen, 17 tests). Core changes are ~115 lines.

Slimmer proposal

  • One single switch ("Adapt to my typing"), fixed strength, no other settings.
  • Move all recording logic out of InputLogic into the separate package, leaving ~60 lines of hooks in core.
  • Optional: drop the statistics screen if you prefer.

If you're still not convinced, no problem — I'll keep it in my fork.

Lingua principale
Kotlin
Stelle
1k
Fork
59
Merge medio
13h 21m
PR unite (30g)
48

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di LeanBitLab/LeanType

Tutte le issue di LeanBitLab/LeanType

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.