# Best Android keyboard? **URL:** https://discuss.privacyguides.net/t/best-android-keyboard/41733 **Category:** General **Created:** 2026-10-25T20:36:36Z **Posts:** 26 ## Post 1 by @Malachi — 2026-10-25T20:36:36Z What are you favorite Android keyboards? Please also add some information about them, like link, Signing key, license etc. --- ## Post 2 by @null — 2026-10-25T20:57:42Z There are alot of topic about Android keyboards. :slightly_smiling_face: --- ## Post 3 by @not-wittingly — 2026-10-25T21:19:50Z I think people mostly use FUTO and Heliboard. For me honestly they haven’t cut it. I’ve tried them for months at a time and then I use someone elses phone and think “damn this is a way better experience” and then go back to Gboard. Though on GrapheneOS you can mitigate things a bit more but turning off all the permissions, including network. --- ## Post 4 by @SilverMeteor91 — 2026-10-25T21:27:03Z I have both a stock Android phone as well as an iOS phone, and I do not find FUTO to be inferior to either of those keyboards in any way that’s important to me. Somewhat the opposite in fact, I think I prefer FUTO. Heliboard on the other hand (and all the other open source Android keyboards you see regularly recommended) I find essentially unusable and horrible to look at. FUTO is the way. --- ## Post 5 by @not-wittingly — 2026-10-25T21:29:33Z Interesting. It’s been a while since I’ve tried FUTO, maybe a couple years. I’ll give it another go. --- ## Post 6 by @Lukas — 2026-10-25T22:26:28Z I’m just using the default AOSP Keyboard on GrapheneOS. But FlorisBoard is also good. --- ## Post 7 by @Olly — 2026-10-26T01:33:16Z Agreed. I’ve tried quite a few on GOS and have found FUTO the best for me. I love to swype tho and their recent release seems to nail this pretty well --- ## Post 8 by @mentalfoss — 2026-10-26T11:44:29Z [Florisboard](https://github.com/florisboard/florisboard) is pretty good with strong AI policy [(evidence)](https://github.com/florisboard/florisboard/blob/fe1241f4921b3eae923571ff7a3e113a7e10d677/AI_POLICY.md) and will be the go to keyboard for GrapheneOS when it goes out of beta. [Flickboard](https://codeberg.org/natkr/flickboard) is another special keyboard with strong AI policy too [(evidence)](https://codeberg.org/natkr/flickboard/src/branch/main/CONTRIBUTING.md#ai-policy) that if it is your style you ll love it. Heliboard is good too with an OKish AI policy and frequently updated. I wouldn’t trust any FUTO projects, especially something sensitive like an android keyboard. --- ## Post 9 by @Lukas — 2026-10-26T11:51:28Z > [@mentalfoss](#): > > [Florisboard](https://github.com/florisboard/florisboard) is pretty good with strong AI policy [(evidence)](https://github.com/florisboard/florisboard/blob/fe1241f4921b3eae923571ff7a3e113a7e10d677/AI_POLICY.md) and will be the go to keyboard for GrapheneOS when it goes out of beta. 1. This AI policy is a red flag in today’s world. 2. It’s not a confirmed fact that FlorisBoard will be the replacement. --- ## Post 10 by @Acephali — 2026-10-26T13:10:33Z For years, SwiftKey was my go-to keyboard. It was solid, reliable, the autocorrect worked like it should. Then Microsoft bought it . The app became bloated. Now I’m back with GBoard, and honestly, the user experience is just better. Everything runs smoothly, the predictions are reliable, and the app doesn’t feel like a resource hog. But I’m open! If anyone knows a good open-source keyboard that actually works well, bring it on. I absolutely don’t need all those swipe or gesture gimmicks. A classic, reliable keyboard with decent autocorrect and prediction is all I need. Any recommendations? :thinking: --- ## Post 11 by @Archer — 2026-10-26T20:29:45Z > [@Malachi](#): > > What are you favorite Android keyboards? > [@Acephali](#): > > But I’m open! If anyone knows a good open-source keyboard that actually works well, bring it on. I absolutely don’t need all those swipe or gesture gimmicks. A classic, reliable keyboard with decent autocorrect and prediction is all I need. > > Any recommendations? :thinking: I think Heliboard works very well and can also be customized with additional buttons like one that pasts a timestamp. > [@Malachi](#): > > Please also add some information about them, like link, Signing key, license etc. Link: > **[HeliBoard | F-Droid - Free and Open Source Android App Repository](https://f-droid.org/packages/helium314.keyboard/)** > > Customizable open-source keyboard Signing Certificate (from App Verifier (not internal database) installed with Accrescent) helium314.keyboard 5E:C0:A5:31:3A:A4:35:58:EE:75:B2:0B:58:CC:D8:19:4C:DB:F0:66:DF:94:A4:3B:A2:88:D9:33:D6:0B:86:CE License: GPLv3-only --- ## Post 12 by @Aflame-Blighted — 2026-10-27T22:30:19Z I’ve been trying to persist with FUTO on GOS for months after the recommendations on here, but the fact is that I get so many more incorrect button presses compared to Gboard. I hate having to go back to fix spelling mistakes. --- ## Post 13 by @ZenByte — 2026-10-27T23:36:02Z Have you tweaked the settings? Under advanced parameters, you can set the transformer strength and autocorrect threshold. I set mine to always use the transformer LM and set the autocorrect threshold to 4.0. I often type by using word suggestions and the suggestions for me have been very accurate. --- ## Post 14 by @JaneDoe — 2026-10-28T00:12:51Z fcitx5 > **[GitHub - fcitx5-android/fcitx5-android: Fcitx5 input method framework and engines ported...](https://github.com/fcitx5-android/fcitx5-android)** > > Fcitx5 input method framework and engines ported to Android > **[GitHub - fcitx/fcitx5: Next generation of fcitx, cross-platform input...](https://github.com/fcitx/fcitx5)** > > Next generation of fcitx, cross-platform input method framework. uses LGPL license --- ## Post 15 by @Aflame-Blighted — 2026-10-28T04:41:16Z That’s what I have, so it must be the default. Perhaps playing with these may help. I’ve always been a fast typer, but I feel the button edges of FUTO are less forgiving than Gboard, or even back when I was on iOS with my 6s, which is frustrating. I think I used to use SwiftKey as well, pre and post Microsoft. --- ## Post 16 by @ZenByte — 2026-10-28T04:58:10Z I also turned off popup on keypress since I didn’t like the implementation compared to Gboard. I’ve got used to not having it. I also changed automatic spaces mode to legacy since I was having issues with the default. I can’t help with swipe typing since I’ve never used that. --- ## Post 17 by @Malachi — 2026-10-28T23:31:49Z > [@null](#): > > There are alot of topic about Android keyboards. :slightly_smiling_face: But they are als old --- ## Post 18 by @Malachi — 2026-10-29T00:49:56Z > [@not-wittingly](#): > > I think people mostly use FUTO and Heliboard. > [@mentalfoss](#): > > Heliboard is good too with an OKish AI policy and frequently updated What is the AI policy of HeliBoard? > [@mentalfoss](#): > > I wouldn’t trust any FUTO projects, Why? --- ## Post 19 by @not-wittingly — 2026-10-29T00:55:00Z > [@Malachi](#): > > What is the AI policy of HeliBoard? Why what are you concerned about. --- ## Post 20 by @pine — 2026-10-29T07:44:21Z > [@Malachi](#): > > What is the AI policy of HeliBoard? Since it’s linked in the reply you quoted, is there anything you feel is ambiguous after reading it? --- ## Post 22 by @MichaelJohn — 2026-10-29T11:40:30Z > [@mentalfoss](#): > > wouldn’t trust any FUTO projects, especially something sensitive like an android keyboard. The app has no network permission, so what about the FUTO keyboard has you concerned? --- ## Post 23 by @EsperZero — 2026-10-29T11:45:18Z Basically unnecessarily political > **About the term quote: “Fashware”** > > _Can’t believe we now made up a term over some petty political post just because a specific individual is associated_ block them or ignore and move on --- ## Post 24 by @MichaelJohn — 2026-10-29T12:10:12Z Understood. Just had a glance through that URL, what a sad little compilation. I wonder what that blogger’s life is when they seem so interested in hyperfocusing on a the few things that people in the FOSS space might have done/said in the past that might be reprehensible. Its usually these people who are later caught with skeletons in their own closet. Even sadder to take said compilation seriously, considering the accusations have nothing to do with the topic of privacy and/or security. --- ## Post 25 by @Colter — 2026-10-29T14:14:21Z > [@MichaelJohn](#): > > Understood. Just had a glance through that URL, what a sad little compilation. Its sad that people want to harm the FOSS and privacy project that way, but at the same time we can use this link as an example how much people with none “political correct” views, contribute to FOSS and privacy. I see this ccollection as a good argument for a big tent for privacy --- ## Post 26 by @Malachi — 2026-10-29T22:34:57Z > [@not-wittingly](#): > > ![](https://forum-cdn.privacyguides.net/user_avatar/discuss.privacyguides.net/malachi/48/11842_2.png) Malachi: > > > What is the AI policy of HeliBoard? > > Why what are you concerned about. I just asked because they mentioned it > [@pine](#): > > Since it’s linked in the reply you quoted, is there anything you feel is ambiguous after reading it? ??