Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Reconsider adaptive touch correction? Slimmer proposal with details

Aberta
  • Algo errado?
#676 2 comentários 1 reação 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@4di-hello já está trabalhando nisso.

Desde 14/10/2026.

  • #680 de @4di-hello — aberto

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
12/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
android, kotlin
Domínio
mobile

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Kotlin
Estrelas
1k
Forks
59
Merge médio
13h 21min
PRs com merge (30d)
48

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de LeanBitLab/LeanType

Todas as issues de LeanBitLab/LeanType

Issues semelhantes

Mais issues de Kotlin

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.