The Input Method That Turns Typing Into Flashcards

There is a category of software you interact with more than your editor, your browser, or your group chat: your input method. If you type Chinese, you funnel essentially every word you write — messages, code comments, search queries, passive-aggressive commit messages — through a pinyin-to-character converter that runs hundreds of times a day. The team behind Qingjian looked at that surface and asked a question that sounds almost too simple: what if the converter taught you something on the way through?

The answer is an input method, written in Rust, that does everything a normal pinyin IME does — whole-sentence input, candidate ranking, the usual dance — and then adds one small thing: a translation, rendered small and shallow, next to each candidate. Type the pinyin for a word meaning “development” and the candidate list shows the Chinese characters you expect, with the English word sitting quietly beside them. Not a popup. Not a quiz. Just a gloss, visible for the half-second your eyes pass over the candidate window before you hit the number key.

That’s the entire pitch, and it’s a better pitch than it first appears.

The idea: learning as a side effect of existing

The project’s stated philosophy is worth taking seriously because it’s a genuine design constraint, not marketing garnish. The README is explicit about what Qingjian will not do: it won’t stack five languages onto one candidate, won’t pop quizzes every few words, won’t force spaced repetition into your typing flow, won’t sacrifice input speed for pedagogy. “If the user has to think about whether they’re typing or memorizing vocabulary right now, Qingjian is probably designed wrong.” Input first; learning happens as a byproduct.

This is a rejection of how language-learning software normally works. Every flashcard app, every spaced-repetition system, is built on the premise that you will carve out dedicated time — ten minutes on the train, twenty before bed — and concentrate. The Qingjian position is that this premise is the failure mode. People already spend hours a day producing text. If a fraction of that attention can be siphoned into a single auxiliary gloss, the marginal cost of “studying” drops to approximately zero, and the frequency goes up by orders of magnitude compared to any deliberate practice schedule.

The constraint of one learning language at a time is the tell that this is a considered design rather than a feature checklist. A candidate window is a tiny, high-velocity UI element. Attaching English, Japanese, Korean, and German glosses to every candidate would turn it into a wall of noise that users would learn to ignore within a week — the visual equivalent of banner blindness. One language, one shallow annotation, keeps the signal below the threshold of annoyance and above the threshold of noticing.

The boring part is where the value lives

The genuinely interesting engineering here is not the translation display. It’s the candidate pipeline. The README’s demo shows whole-sentence pinyin typed in one breath, then a pause while “a local small model re-ranks the candidates.” That sentence carries a lot of weight. Modern Chinese input quality lives and dies on conversion ranking — taking an ambiguous pinyin string and guessing which character sequence the user meant. The big commercial IMEs lean on enormous server-side language models and cloud suggestion services to do this well; Microsoft’s own Simplified Chinese IME, for instance, pulls text suggestions from Bing directly into the candidate window. Qingjian is attempting to get comparable re-ranking quality from a small model that runs on the user’s machine, with no network round-trip in the critical path.

That’s the bet, and it’s the same bet being made across the local-AI wave: that small models, run where the latency budget is measured in keystrokes rather than seconds, can do work that used to require a datacenter. An input method is arguably the most latency-hostile deployment target imaginable — the candidate window must appear and update faster than the user can perceive delay, or the IME is unusable. If a local model can re-rank candidates within that budget, the privacy story and the performance story stop being in tension.

The architecture reflects a second, quieter decision: the core input engine is platform-agnostic, and each platform contributes only a thin shell — Input Method Kit on macOS, Text Services Framework on Windows, IBus or Fcitx on Linux. The README’s own slogan for this is blunt: “the platform is just a shell; the core is Qingjian.” Anyone who has watched IME projects die by platform lock-in will recognize this as the correct instinct. macOS is the reference implementation; Windows has reached internal testing with the TSF integration running as a separate engine process — a detail that suggests the team has hit the classic TSF pain points, where an input method that crashes takes your application’s text input down with it. Linux is on the map but not yet shipped.

A field built for natives, used by learners

To understand why this project exists at all, it helps to look at the landscape it’s entering. As the Hacking Chinese guide to input methods observes, input methods “are largely developed for native speakers with no thought given to second language learners.” The entire interaction model — type a phonetic string, pick from candidates — assumes you already know which character you want. A learner picking from a candidate list is often selecting a glyph they couldn’t produce from memory, which is precisely the situation where a little contextual information does the most good.

The demand is visible, if fragmentarily. A Reddit thread from the r/ChineseLanguage community, titled simply “Pinyin input method that returns English translations along with candidates”, asks for exactly this feature — though the thread itself is inaccessible behind Reddit’s login wall, so it’s unclear whether anyone had a good answer at the time. Similar threads asking for IME recommendations for learners, like this one on Windows 10 input methods, hit the same wall. The signal is the persistence of the question, not any documented answer.

Meanwhile, the incumbent options illustrate the problem from the other side. Reviews of Android Chinese keyboards, like this long-running comparison, consistently find that IMEs are excellent for one language and mediocre for the other — Sogou’s Chinese prediction is superb while its English input frustrates, and bilingual users end up keyboard-hopping. Qingjian’s approach sidesteps the bilingual-keyboard problem rather than solving it: it doesn’t try to make English input better, it makes Chinese input carry the English along as freight.

Privacy as architecture, not policy

The privacy stance is unusually concrete for a project at this stage. Pinyin conversion, the lexicon, the learning features, and the glosses all run locally; there are no accounts and no telemetry. The one network feature — cloud association, off by default — sends requests directly from the user’s machine to an AI provider the user themselves configures, bypassing the authors entirely. Input logs are written locally and can be disabled and cleared.

This matters more in the IME world than elsewhere, because input methods are the purest form of surveillance surface: they see every character you type before any application does. An IME that phones home is a keylogger with a business model. Qingjian’s local-first design makes the privacy claim structural — there is no server to subpoena — rather than a promise that could be quietly revised in a terms-of-service update. The contrast with cloud-suggestion features in mainstream IMEs is not subtle.

Rough edges and honest labels

The project is candid about its maturity: beta, self-hosted by the developers, being packaged for a small group of testers, with the explicit warning that the API, project structure, and feature design may all change substantially. That’s the right posture, and readers should calibrate expectations accordingly — this is a project to watch and possibly test, not one to bet a workday on yet.

The licensing is also worth noting, because it’s a slightly unusual split. The code is GPL-3.0-or-later, with the standard copyleft obligations. But the Qingjian name and logo are explicitly outside the license grant, and the bundled data — lexicons, language models, gloss tables, emoji sets, vocabulary grading — each carries its own upstream license, inventoried in the repo’s design docs. The README also contains a line that does a lot of community-trust work in very few words: the official channels distribute it free, and “if you paid someone to obtain it, you were scammed.”

One practical hazard deserves mention, because it is fully visible in the sources: the name. “Qingjian” is not an unclaimed word on the internet. Qingjian Group is a Chinese construction and engineering conglomerate founded in 1952, with billions in annual revenue and a Singapore arm, Qingjian International, plus a prominent local developer, Qingjian Realty, behind a string of residential projects. Searching for the input method means wading through construction awards and condominium launches first. The name itself is lovely — a reference to bamboo-slip manuscripts, the ancient medium of the written word — but its SEO collision with a real-estate empire is a small, permanent tax on the project’s discoverability.

The open question

Strip away the aesthetics and Qingjian is a hypothesis: that ambient exposure, at typing frequency, produces measurable vocabulary retention. The README doesn’t claim evidence for this — it claims plausibility, and the plausibility is real. Hundreds of micro-exposures a day to a gloss you chose to see, in a context where you already know what you meant to say, is a textbook case of incidental learning. Whether it actually moves the needle, and by how much, is an empirical question the project hasn’t answered and can’t answer alone.

What’s not in question is the design intelligence on display. The restraint — one language, no quizzes, no UI sprawl, input speed as a hard constraint — suggests a team that understands the difference between a feature and a habit. Most software that tries to teach you things interrupts you to do it. Qingjian’s wager is that the future of incidental learning isn’t an app you open. It’s the thing you were already doing, annotated.