
One Bangladeshi student, 4,381 commits, 870 stars: WM Keyboard went viral in the de-Google crowd on the claim that it has the most features of any open-source keyboard
What it is An MIT-licensed Android keyboard written from scratch, with swipe typing, offline voice input, on-device AI rewriting, 89 built-in tools and plugins. Everything runs on the phone and no data is sent out.
Why it took off Big-tech keyboards are pushing AI and accounts, and the existing open-source keyboards each have one obvious weak spot (swipe relies on a closed-source library, no word suggestions, licenses that don't count as open source, no GIFs). WM was the first to combine open-source offline operation with Gboard-level features. Users switching from FUTO on r/degoogle called it "the best open-source Gboard replacement," and F-Droid, AlternativeTo and a German blog comparison then named it one after another.
BHow you could copy it In categories where a big-tech product makes people uneasy and the open-source alternatives are old code forks, use AI coding to build features close to the big-tech version, then open-source it. List it on F-Droid, IzzyOnDroid and Play, and document clearly every network call and AI usage so privacy-community users spread the word for you.
- Data (updated daily) · Repo created 2026-08-10 · 1,045 stars · 7 days +116
GitHub · stars Data 2026-10-09 → 2026-11-20 (43 days, 42 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
WM Keyboard is an open-source Android input method by a student in Bangladesh, who says he used Claude Code to help write it. It grew to about 870 stars in 93 days, never made GitHub's trending list, and no big account on X has shared it. Almost all the stars came from word of mouth in de-Google communities like r/degoogle, F-Droid and AlternativeTo. Below: what it is, why people recommend it, who it's competing with, why the same selling point also turns people away, and finally which parts of this are worth copying for your own open-source project and which aren't.
Someone who thought FUTO had no GIFs
In 2026 Sep 27, Reddit user u/PingMyHeart posted on r/degoogle with the title "WM Keyboard might be the best open source Gboard alternative for Android." The first line: "I've been using FUTO Keyboard for a while and it still has no GIF support, and I've had enough. While looking for alternatives today I came across WM Keyboard and tried it."
The post got about 180 upvotes and 155 comments (Reddit search summary, 11-10). Comments included: "Way better than FUTO. Once installed it looks like the native keyboard / Gboard"; "Just downloaded it, I love it, this might finally beat Gboard"; "Ridiculously feature-packed. It has swipe typing and it works well, which I've been missing in other keyboards." Some urged caution: "Install it as a second keyboard for now and wait until the author fixes the rough edges."
The timing lines up: forks picked up noticeably from 09-21, external issues in the second half of September were the most in a month and a half, and after the Sep 25 release, per-version downloads on GitHub jumped from under 1,500 to 2,500–5,500 (GitHub Releases). A few weeks later someone on r/degoogle asked for "Gboard alternatives" and got this answer: "I'm playing with the recently released WM Keyboard, it's better than FUTO. FUTO has some old bugs and I'm starting to think they'll never get fixed."
The person who posted was not the author, but a user who switched from FUTO. This comes up again later.
What it is
A from-scratch Android input method built with Kotlin + Jetpack Compose, MIT license. The README's front page has three words: Private. Offline. Yours.
Author Wasi Master explains the reason in the README's "Why I built this" section: keyboards that don't send data out are mostly forks of the same decade-old Android code. "The skeleton is good and the intent is sound, but swipe requires installing closed-source libraries, there's no real toolbox, and the language I actually use is nobody's concern. Bangla is always an afterthought." So he wanted a keyboard that types Bangla with Avro phonetic input, ships with the everyday tools, and runs everything on the phone.
What he built is absurdly feature-heavy: a self-written swipe engine (no Google closed-source libraries), offline voice input (several engines including Whisper), on-device AI rewriting and translation, 89 tools (clipboard history, calculator, QR scanner, dictionary...), a theme editor, Lua plugins, and a plugin repository where users contribute themes and layouts. The project's own feature list has 2,288 items, 500 of which are marked "RARE." It can also directly import themes, layouts and dictionaries from FlorisBoard, HeliBoard, FUTO, Samsung Keyboard and even Gboard, so people switching don't have to reconfigure from scratch.
The author doesn't hide the AI part. The last README section, "How this was made," says most features were written by him; complex ones were planned with Claude Code's help and boilerplate was generated; for especially repetitive, time-consuming work, "it may be handed off to Claude Code entirely." The repo has 4,381 commits in 93 days, about 47 a day on average, nearly all submitted by him alone (GitHub, 11-10).
The author is not a newcomer. 2022 years ago he built 13ft, a self-hostable 12ft.io alternative that has 4,361 stars. So he knows how to write a README that persuades people.
Where the stars came from
| Timeline | What happened | How it looks on GitHub |
|---|---|---|
| 08-10 | Repo created, and 0.3.0 shipped the same day, meaning a version had already been written privately | — |
| First half of August | Two keyboard enthusiasts, cinnabar777 and Mokhyy, opened 40 issues in the first week; 08-29 Mokhyy also went to competitor LeanType's repo and recommended it there | 50 external issues, almost all from these two people |
| 09-11 ~ 09-23 | Listed on Appteka, fossdroid, IzzyOnDroid. The F-Droid main repo has it at about 09-23 listings. Privacy Guides received its first listing request (09-15) | Forks began rising from 09-21 |
| 09-27 | The r/degoogle post at about 180 upvotes | External issues in the second half of September: 228, and downloads stepped up a level |
| October | Reposted by Russian and Chinese tech aggregator sites; recommended in r/opensource and r/termux; 10-06 someone on r/LocalLLaMA said under a voice-model post that WM was already integrated | 10-09 484 stars, then growing by 3 to 21 stars a day |
| 11-10 | German blog linuxundich published an open-source keyboard comparison stating WM was "the most popular" in an r/flossdroid discussion thread | 11-11 single-day +66, the highest day since the repo was created (presumably driven by that article) |
By the evening of 11-10 it had 876 stars and 53 forks. Installer downloads on GitHub total about 42k, including auto-updates, so that is not a user count. On Google Play it has 5K+ downloads, 4.6 stars and 112 ratings (Play Store listing, 11-10). The Telegram group has 369 members.
Other channels barely contributed. On Hacker News, 10-01 someone submitted it, reaching 2 points and 1 comments. No big account on X wrote about it, and no tech media covered it. 11-08 The HowToGeek keyboard article was about another project, PixelBoard. It made the GitHub trending categories on only 11-05 and 11-06, and never reached the overall trending chart.
The overall curve is steady, with no spike-then-drop. Every new "open-source Gboard alternative" post, list or comparison names it once more, and the stars climb a bit more.
Why it gets recommended: it fills a gap in every rival
The "private open-source Android keyboard" category is actually crowded, but each option has an obvious pitfall:
| Keyboard | Scale | Weakness | What WM adds |
|---|---|---|---|
| Gboard | About 14B installs on Play cumulatively | Closed source; search, analytics and cloud voice send data to Google, and it's now moving toward Gemini | Typing is fully offline with no account |
| Microsoft SwiftKey | About 1.98B installs on Play | Since 2026-05-31, backup and sync require a Microsoft account, and it's pushing Copilot | No account, no cloud |
| HeliBoard | 6,553 star | A fork of old Android code; swipe needs a separate Google closed-source library; few tools | Its own swipe engine and 89 tools |
| FlorisBoard | 8,771 star | Long-running beta, no word suggestions | More complete prediction, themes and tools |
| FUTO Keyboard | 3,464 star | License not recognized as OSI open source; no GIFs, slow fixes to old bugs | MIT license, much faster iteration |
| LeanType | 1,175 star | A HeliBoard fork taking a "lean and stable" approach | An order of magnitude more features |
| Ridmik Keyboard (Bangla) | About 197M installs on Play | Has ads and requires a network connection | Bangla phonetic input with swipe, prediction and correction, and open source |
In one line: before, you could have "open source, offline" or "as full-featured as Gboard," but not both. WM was the first to offer both. The Reddit post, the reviews on AlternativeTo ("most features, most actively developed") and linuxundich's comparison all make this same point.
What makes this work is iteration speed. Users file an issue, and within days it's fixed in a release; dozens of versions shipped in 93 days. A single student reaching that pace is down to AI coding, which he states himself in the README.
The same selling point also turns people away
The closing recommendation in linuxundich's comparison wasn't WM but HeliBoard. The reason was direct: the regular GitHub build requests 44 permissions, including network access, location, contacts, camera, microphone, full file read/write, drawing over other apps, and installing apps. "A project maintained by one person with dozens of commits a week is hard to audit. For a keyboard, that asks for more trust than I'm willing to give upfront." The author does also offer a no-network build, but the comparison didn't check it closely.
On Mastodon, someone saw the AI disclosure in the README and replied "Eww. Uninstalled." 10-20 A user went to LeanType's repo proposing it copy WM's features, and LeanType's author replied: "The two keyboards have different visions. LeanType only adds features that don't affect stability; WM adds new features in nearly every release."
So be clear about who WM is winning: people in the privacy crowd who like tinkering and want Gboard-style features. The group that cares most about minimal permissions and auditability is one it isn't winning, and doesn't plan to.
If it were you
One-liner: the playbook is what's worth copying. Find a category where a big-tech product makes people uneasy, the open-source alternatives are all old code forks, and each has one obvious weak spot. Use AI coding to build something close to the big-tech feature set, open-source it, and get it in front of the r/degoogle and F-Droid crowd. What's not worth it is building yet another open-source keyboard: the most complete spot is taken by WM, and the most trusted spot by HeliBoard. Also think through the payoff: WM got under 900 stars after 4,381 commits. This path builds word of mouth and real users, not a burst of stars.
Who it's for: a solo Android (or desktop) developer who can iterate steadily over the long run, is comfortable writing code with AI, and is willing to answer issues every day and ship a release every few days. Ideally they're a user themselves of some need nobody maintains, the way the author needed Bangla typing.
Who it's not for: anyone who wants a few thousand stars in three months. Projects like this don't take off on HN or X. They wait for privacy-circle posts and comparison reviews to name them one by one. It's also a bad fit for anyone who won't disclose their AI usage, or who can't handle the comment "I won't install AI-written code." Your audience happens to be the group most sensitive to that.
How to do it, from most to least reliable:
- Switch categories, same playbook. Search r/degoogle and r/fossdroid for "alternative to" posts, and pick categories where the top-voted answer is an old project that's barely maintained or has very few features. Examples: a recorder with offline transcription, SMS apps, scanning, or camera apps, the everyday system-level apps. We haven't checked these one by one, so these are just examples; search for yourself before starting (inference). The test: can you name the biggest flaw of the existing open-source alternatives in one sentence? If you can, someone will post something like u/PingMyHeart did: "it finally got the feature."
- Start from your own language or community. WM's starting point was Bangla: Avro phonetic input, swipe, and prediction, none of which other open-source keyboards had. Your angle can be input, recognition, or typesetting that nobody has done well in your own mother tongue, but spread it to the global privacy community. WM's stars mainly came from the Western privacy crowd; Bangla users are mostly on the Play Store.
- Do the opposite: a version with fewer permissions that can be audited. Comparison reviews and objections on Mastodon are ready-made demand, but HeliBoard and LeanType already occupy this spot, so this is the least certain bet.
How to get users:
- On day one, list it on F-Droid (with reproducible builds), IzzyOnDroid, Obtainium, and the Play Store at the same time, then add yourself on alternativeto as an alternative to the big-tech product. This crowd only installs apps from these places.
- Document every network connection and every permission in the README, and write how AI was used into it. WM was written by its author, and disclosing it yourself is very different from having people dig it up.
- Build "import from competitor": themes, layouts, and dictionaries that can be carried over directly, so switching costs less.
- Look for early seed users in the competitors' issue trackers. There are plenty of people there complaining "when will you support X?" Fix the first few enthusiasts' issues the same day, and they'll recommend you elsewhere on their own. WM's Mokhyy posted in the LeanType repo.
- Don't post ads on Reddit yourself. The r/degoogle post was written by a user, and its persuasiveness comes from that. Your goal is to get your name into every "what are the open-source alternatives to X" thread and comparison review.
The window is before: the next year or two, while big tech is still stuffing AI and accounts into default products. Forced SwiftKey logins and Gboard wiring up Gemini both happened within 2026 years, and r/degoogle is full of posts looking for replacements. How long the window actually lasts can't be calculated.
Signs you've misjudged it: (1) WM's daily stars drop back to single digits, and later comparisons and lists stop bringing traffic. That would mean this category's star ceiling is around a thousand, and the same playbook in another category won't go much higher. (2) Privacy Guides refuses to list it, or the F-Droid community starts broadly boycotting AI-written projects. That would mean the "AI-built features" route doesn't work in the privacy circle. (3) Conversely, if someone runs the same playbook in another "open-source alternative" category and gets a thousand stars in three months, the route works, so move fast.
---
Data and sources: the README of GitHub repo wasi-master/wmkeyboard, release download counts, fork and issue dates, commit count (11-10); daily GitHub star counts (starting 10-09); the Google Play store page (11-10); the r/degoogle post 1wrv52j (09-27; upvote and comment counts come from search-engine summaries, since Reddit doesn't allow direct scraping), and the r/degoogle "Alternative to Gboard" thread; the linuxundich.de open-source keyboard comparison (11-10); LeanType repo Discussion #458 and Issue #706; listing pages on F-Droid, IzzyOnDroid, and alternativeto; the listing requests on privacyguides/verified-apps (09-15, 10-04, 10-16); the Hacker News submission (10-01); the Telegram group t.me/wmkeyboard; competitor scale comes from their GitHub pages and Google Play. The +66 for 11-11 comes from the linuxundich comparison and is an inference; we have no day-by-day star counts before 10-09, and the late-September inflection point is inferred from issues, forks, and download numbers.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one Gboard Big-company features 2013 Play roughly 14B cumulative installs (googleplay library) Closed source; search, statistics, and cloud voice send data to Google. WM's typing runs fully offline and requires no account. Microsoft SwiftKey Android 2010 About 1.98B installs on Play Backup and sync require a Microsoft account starting 2026-05, and it keeps pushing Copilot. WM has no account and no cloud. Ridmik Keyboard Android About 2015 About 197M installs on Play A long-established Bangladeshi input method with ads and network access. WM's Bangla phonetic input includes swipe, prediction, and correction, and it's open source. HeliBoard Open source 2022 6,553 star A fork of old AOSP code. Swipe requires Google's closed-source library and it has few tools, but it was rated the most trustworthy. WM was rewritten from scratch, has its own swipe engine, and has far more features. FlorisBoard Open source 2020 8,771 stars, 7 days +25 Long-term beta with no word suggestions. WM's prediction, tools, and themes are more complete. FUTO Keyboard Open source 2024 3,464 star Source-available license, not OSI-approved open source. No GIFs, and bug fixes are slow. WM is MIT-licensed and iterates fast. LeanType Open source 2026-01 1,175 star A HeliBoard fork with cloud AI. It positions itself on being lean and stable, and explicitly doesn't chase WM's feature stacking. AnySoftKeyboard / OpenBoard / Simple Keyboard / Thumb-Key Open source 2012–2023 1.5k–3.4k stars, mostly stalled Few features, slow maintenance PixelBoard Open source 2026-09 1,499 star A reskinned Gboard that unlocks Gemini dictation on all phones. It goes the opposite direction from WM by embracing Google's AI. - Where users come from
- Verified Reddit privacy community word of mouth (r/degoogle and others): 09-27 r/degoogle thread "WM Keyboard might be the best open source Gboard alternative" has about 179 upvotes, posted by someone who switched from FUTO. Afterward, people recommended it in threads on r/degoogle, r/opensource, r/termux, and r/flossdroid. From 09-21 onward, forks and issues clearly increased.
- Verified Open-source app stores and directories (F-Droid, IzzyOnDroid, Obtainium, alternativeto, fossdroid, Privacy Guides applications): about 09-23 listed on F-Droid, 09-14 on fossdroid; alternativeto lists it as a Gboard alternative; privacyguides/verified-apps has 09-15, 10-04, and 10-16 listing requests; starting with v0.5.12 (09-25), per-release GitHub downloads jumped from under 1,500 to 2,500–5,500.
- Inference Blog comparison: linuxundich published an FOSS keyboard comparison on 11-10, originating from an r/flossdroid discussion thread, and noted WM was "the favorite of that thread." The next day (11-11) stars rose by +66, the highest single day.
- Verified Early enthusiasts acting as unpaid promoters: cinnabar777 and Mokhyy opened 40 issues in the first week; Mokhyy went to the LeanType repo on 08-29 to recommend WM (Discussion #458); on 10-20 another user proposed copying WM's features into LeanType (#706).
- Verified riding an adjacent tech trend: 10-06 A post on r/LocalLLaMA about the Whistle voice model has someone saying WM has already integrated it; there is also a discussion thread on r/nintype
- Verified Self-run official social media: Instagram @wmkeyboardapp posts short videos (such as a Gboard comparison reel 11-03), X @wmkeyboard, and a Telegram group with 369 members. We didn't see any large accounts reposting it, and we couldn't read follower counts.
- Verified HN and aggregator sites: the HN submission got only 10-01 points with 2 comments; reposts exist on a Russian DevTrends site, the Chinese kuku site, hysenlabs, and Lemmy, but their impact was small.
Why wasi-master/wmkeyboard (WM Keyboard) took off
In one line: Wasi Master, a Bangladeshi student developer, used Claude Code as an assistant and pushed roughly 4,381 commits solo over 93 days to build a Kotlin/Compose Android keyboard from scratch: MIT-licensed, with its own swipe-typing engine, offline prediction and voice, 89 tools, and Lua plugins with a plugin repository. Its position is "the most feature-rich of the open-source Gboard replacements," and it spread by word of mouth in privacy and de-Googling circles like r/degoogle, F-Droid/IzzyOnDroid, and alternativeto. Stars rose at a steady 8–10 per day with no pullback; a single day of +66 on 11-11 most likely came from 11-10 German blog linuxundich's FOSS keyboard comparison.
1. Data
| items | Numbers | Source |
|---|---|---|
| Repo created | 2026-08-10 (v0.3.0 shipped the same day, suggesting a version had been written privately beforehand) | GitHub API |
| star | 10-09 484 → 10-22 605 → 11-10 781 → 11-11 847; 11-10 evening API read 875 | GitHub repo_day library, GitHub API |
| Daily adds | 10-09~11-10 mostly +3~21,11-11 per day; +66 was the highest day; last 7 days +136, first 7 days +67, last 30 days +329 | GitHub repo |
| trending | Only on the chart for 2 days (11-05, 11-06); never made the site-wide chart | github library repo_profile |
| fork | 53 in total; the first one clearly increased starting 09-05,09-21 | GitHub forks API |
| issue | About 1,225 issue numbers in total. Not authored by the maintainer: 08 first half of the month 50 (almost all by cinnabar777 and Mokhyy), 09 first half 136,09 second half 228,10 first half 228,10 second half 133 | GitHub issues API |
| Commits | 4,381 in total, 4,274 by the author, about 47 per day | GitHub API |
| GitHub release downloads | 41,877 cumulative. From v0.5.12 (09-25) onward, each release got 2,500–5,500 downloads; before that, each release had under 1,500. Includes Obtainium and in-app updates, so it doesn't equal user count. | GitHub releases API |
| Google Play | 5K+ downloads, 4.6 stars, 112 ratings; not in our googleplay library (never charted) | Play Store page (read via Jina, 2026-11-10) |
| Telegram group | 369 people | t.me/wmkeyboard |
| Author | Wasi Master, Pabna, Bangladesh, student, 214 GitHub followers; an older project 13ft (a self-hosted alternative to 12ft.io), 2022 years old, with 4,361 stars | GitHub API |
How to tell the stars are real: growth is very even, with no spike followed by a drop; fork accounts are normal developer accounts; the issue volume (450+ external issues in a month and a half) and Play reviews line up with the star count, and we see no signs of star inflation. The stargazers endpoint returned 404/403 for our token, so we couldn't check the individual starring accounts.
2. Competitors
| Name | Where | Launched | Scale | Differences from WM |
|---|---|---|---|---|
| Gboard | Big-company features / Android | 2013 | Play roughly 14B cumulative installs (googleplay library) | Closed source; search, statistics, and cloud voice all send data to Google. WM's focus is fully offline typing. |
| Microsoft SwiftKey | Android | 2010 | About 1.98B installs on Play | Backup and sync require a Microsoft account starting 2026-05-31 (linuxundich citing heise), and it keeps pushing Copilot. WM requires no account. |
| Ridmik Keyboard | Android (Bangla) | About 2015 | About 197M installs on Play | A long-established Bangladeshi input method with ads and network access. WM has Avro phonetic, Probhat, Jatiya, and other layouts, and adds Bangla swipe typing and prediction. |
| HeliBoard | Open source | 2022 (OpenBoard fork) | 6,553 star | A fork of old AOSP code; swipe typing requires Google's closed-source library and it has few tools. linuxundich rated it the most trustworthy. WM was rewritten from scratch, and its swipe engine is its own. |
| FlorisBoard | Open source | 2020 | 8,771 stars, +25 in the last 7 days | Swipe typing but long-running beta, no word suggestions (linuxundich). WM has more predictions, tools and themes |
| FUTO Keyboard | Open source (source-available) | 2024 | 3,464 star | Not an OSI-approved open source license, developed on an internal GitLab; no GIFs, bugs fixed slowly (r/degoogle users switched over for exactly this reason). WM is MIT-licensed and iterates much faster |
| AnySoftKeyboard / OpenBoard / Simple Keyboard / Thumb-Key | Open source | 2012–2023 | 1.5k–3.4k stars, mostly stalled | Few features, slow maintenance |
| LeanType | Open source (HeliBoard fork) | 2026-01 | 1,175 star | Same "HeliBoard + more features" approach, also AI-assisted; the author says they'll "slim down" and refuse to copy WM's features (LeanType #706) |
| PixelBoard | Open source | 2026-09 | 1,499 star | A reworked Gboard that unlocks Gemini voice dictation on all phones, going the opposite direction (you need Google's AI) |
| Expressive-Keyboard | Open source | 2026-10-23 | 119 star | Material 3 Expressive style, swipe + themes + JS plugins, positioned much like WM but on a far smaller scale |
Summary: The "private open source Android keyboard" niche is crowded, but each option has clear weak spots: the old AOSP forks have few features, FUTO's license isn't really open source, FlorisBoard has no suggestions, HeliBoard's swipe relies on a closed-source library. WM is the first open source keyboard written from scratch with features that can hold their own against Gboard.
3. Where users came from (by time)
- Launched 08-10, with two keyboard enthusiasts as seed users. cinnabar777 and Mokhyy filed over 40 issues in the first week. Mokhyy 08-29 also posted in the LeanType repo to recommend WM (LeanType Discussion #458). Couldn't find out how they discovered WM.
- 09 mid-to-late month, listed on privacy distribution channels. IzzyOnDroid, the F-Droid main repo (the F-Droid page was indexed around 09-23), fossdroid.com (09-14), Appteka (09-11). Someone submitted it for inclusion in Privacy Guides' verified-apps repo (09-15 secretmango, 10-04 domiden, 10-16 Italian version). AlternativeTo lists it as a Gboard alternative (user review: "most features, most actively developed").
- 09-27 r/degoogle post. Titled "WM Keyboard might be the best open source Gboard alternative for Android," about 179 upvotes (from the data card). The poster had been using FUTO but switched because FUTO lacked GIF support. The timing lines up with 09-21 forks rising, 09 issues peaking in the second half of the month, and a jump in v0.5.12 downloads. It has since been recommended in r/degoogle "alternative to gboard", r/opensource, r/termux and other threads.
- The author got exposure from other trends. 10-06 In r/LocalLLaMA's "Whistle: 16.9MB speech recognition" thread, someone said WM already integrates it; there is also a discussion in r/nintype. These ride the heat of adjacent tech communities.
- Reposted by aggregator sites in various countries, little impact. Russian DevTrends (10-11), a Chinese Kulu blog (10-09), hysenlabs (10-22), Lemmy/feddit r/opensource (10-16), a Nicheloom launch page. HN had a single 10-01 submission (bro4t, 2 points, 1 comments) that never took off.
- Official accounts run by the team. Instagram @wmkeyboardapp posts short videos (e.g. a Gboard comparison reel 11-03), X @wmkeyboard, a Telegram group with 369 members, SupportKori donations. No big accounts repost it; x-radar shows 0 posts on X.
- 11-10 linuxundich roundup, bringing 11-11 of +66. The article grew out of r/flossdroid's "FOSS keyboards for Android" thread, states that "WM Keyboard was the favorite of that thread," and tests it alongside HeliBoard, FUTO and LeanType. Its verdict recommends HeliBoard and is wary of WM: 44 permissions plus network permission, and a single person making a few dozen commits a week is hard to audit. The 11-11 peak falls on the day after the article, which matches.
- Plugin and theme community. Since 11-02, the wmkeyboard-community-addons repo has seen users submit themes and layouts daily, a signal of retention and secondary spread.
Not seen: ads, creator partnerships, a big Product Hunt push, tech media coverage. The HowToGeek 11-08 piece covers PixelBoard, not WM.
4. Why it took off
- Timing: In 2026, big-company keyboards moved toward AI and accounts (SwiftKey forcing a Microsoft account, Copilot replacing the Bing button; Gboard's Gemini dictation). Users who want to leave Google and care about privacy went looking for alternatives. At the same time FUTO was stuck on its license and old bugs, and FlorisBoard stayed in long-running beta. The r/degoogle post was literally "a FUTO user switching over."
- The product itself: A privacy-focused open source keyboard reached Gboard-level features: an in-house swipe engine (no closed-source library), offline Whisper and 7 other speech engines, local LLM rewriting, 89 tools, a theme editor, Lua plugins, 1,555 languages. FEATURES.md lists 2,288 capabilities, 500 of them marked RARE. In this niche, feature count is itself a talking point, and it's the reason AlternativeTo and Reddit most often cite.
- AI leverage: The README's "How this was made" section says Claude Code was used to plan and write boilerplate, and some features were handed off to it whole. A student making 4,381 commits in 93 days and dozens of releases couldn't iterate this fast without AI. Users file issues and get fixes shipped within days, and enthusiasts especially love that (Discussion #77).
- The wedge: The author needed Bengali. Avro phonetic input plus Bangla swipe, prediction and autocorrect is something no other open source keyboard offers. Play reviews and issues show a real Bengali user base, but GitHub stars are driven mainly by the Western privacy crowd. Bangla is the starting point, not the main source of stars.
- Distribution: It shipped on GitHub, F-Droid (reproducible builds), IzzyOnDroid, Obtainium and Play from the start, a low barrier for privacy crowds. The docs site is detailed ("every claim was checked against the code") and candid that ML Kit sends diagnostic data, which earned trust from this audience.
5. Differentiation
Compared with each open source rival, WM adds something: over HeliBoard it adds in-house swipe and tools, over FUTO it adds an OSI open source license and GIFs, over FlorisBoard it adds prediction, over Gboard it adds offline use and no account. In short, it doesn't trade off "open source / offline" against "full-featured." That is the direct reason it gets recommended; Reddit threads, AlternativeTo reviews and linuxundich all make this point.
The same thing is its risk. On linuxundich and Mastodon, some people were put off, even uninstalled, over feature bloat, permissions and AI-written code (Mastodon @strypey: "Eww. Uninstalled."). The LeanType author explicitly said they won't take this route. Among the people who care most about privacy, "most features" won over tinkerers and lost the most privacy-minded.
6. How visible it is
It's spreading in small circles. An r/degoogle post with 179 upvotes, AlternativeTo and F-Droid listings, a German blog roundup, and a Privacy Guides inclusion request. No big account on X has written about it (x-radar shows 0 posts), it didn't take off on HN, and no mainstream tech outlet has covered it.
Copycats: none explicitly copying it yet. LeanType users proposed copying it, and the author refused (#706). The newly launched Expressive-Keyboard (119 stars) is positioned similarly, but it doesn't look like a copy of WM.
7. What others can learn
- In the "big-company product + privacy concerns" niche: use AI coding to build features close to the big company's, then open source it. The feature list is itself marketing material (the RARE markers in FEATURES.md).
- Enter through your own native language or a niche need (Bangla), but aim the promotion at global privacy communities like r/degoogle and F-Droid.
- Full distribution coverage (F-Droid reproducible builds + IzzyOnDroid + Obtainium + Play), with docs that list every network call, to earn privacy users' trust.
- Disclose AI use upfront, before someone digs it up.
- Reply to issues the same day and ship a release every few days, turning early enthusiasts into unpaid promoters: Mokhyy went out of his way to recommend it in a competitor's repo.
- Open a plugin repo so users contribute themes, creating secondary spread.
8. Still unclear
- Before 10-09, we don't have the day-by-day star history for 484 stars, and the stargazers API can't pull it either. All we can do is infer the inflection point from issues, forks, and download counts, which points to late 09.
- Who posted the r/degoogle thread and its exact upvote count (Reddit blocks scraping; the 179 upvotes come from the data card).
- Whether all of the 11-11 +66 came from linuxundich, or whether an r/flossdroid thread or other reposts contributed too.
- What share of Play users are Bengali; the follower count and view numbers for the Instagram account were not retrieved.
- How the two seed users first discovered it.
Sources
- GitHub API: repos/wasi-master/wmkeyboard (README, releases, forks, issues, contributors), LeanBitLab/LeanType Discussion #458, Issue #706, wmkeyboard Discussion #77
- Our GitHub database: repo_profile, repo_day (2026-10-09 ~ 11-11); Google Play database: app_profile (Gboard / SwiftKey / Ridmik)
- www.reddit.com/r/degoogle/comments/1wrv52j/ (Brave search snippet, 2026-09-27)
- linuxundich.de/en/foss-keyboards-android-alternatives-gboard…(2026-11-10)
- play.google.com/store/apps/details?id=com.wasimaster.wmkeybo…
- f-droid.org/en/packages/com.wasimaster.wmkeyboard/, apt.izzysoft.de/fdroid/index/apk/com.wasimaster.wmkeyboard, alternativeto.net/software/wm-keyboard/about/
- news.ycombinator.com/item?id=49922608
- mastodon.nzoss.nz/@bigblen/117528385887652068
- www.reddit.com/r/LocalLLaMA/comments/1wyemcb/ (Brave snippet)
- GitHub privacyguides/verified-apps inclusion requests (09-15, 10-04, 10-16)
- t.me/wmkeyboard (369 members)