Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Reconsider adaptive touch correction? Slimmer proposal with details

Open
  • Is something wrong?
#676 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

@4di-hello is already working on this.

Since Oct 14, 2026.

  • #680 by @4di-hello — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Kotlin
Stars
1k
Forks
59
Avg merge
13h 21m
Merged PRs (30d)
48

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LeanBitLab/LeanType

All issues in LeanBitLab/LeanType

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.