Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Reconsider adaptive touch correction? Slimmer proposal with details

Abierto
  • ¿Algo no está bien?
#676 2 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@4di-hello ya está trabajando en esto.

Desde el 14/10/2026.

  • #680 de @4di-hello — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, kotlin
Área
mobile

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Kotlin
Estrellas
1k
Forks
59
Merge medio
13 h 21 min
PR fusionados (30 d)
48

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de LeanBitLab/LeanType

Todos los issues de LeanBitLab/LeanType

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.