https://twitter.com/GrapheneOS/status/1584022806735781888
Our thread at https://twitter.com/GrapheneOS/status/1580679185923964928 explains why we're so reluctant to bundle third party apps and that includes replacing these AOSP apps with an actively developed third party keyboard. We've been considering switching to shipping FlorisBoard but it's not quite ready to go.
We don't currently have the resources to develop our own keyboard app so we can either ship AOSP keyboard or a third party keyboard app with only minor changes to whatever we choose. It must have Direct Boot support, which we implemented and submitted for FlorisBoard already.
Direct Boot support enables using keyboard before the first unlock of the profile using it. It needs to be able to function when the profile's data is still at rest and not available to the OS to fully replace AOSP keyboard. FlorisBoard can do that now, but has features missing.
https://twitter.com/GrapheneOS/status/1601437948133904384
FlorisBoard is what we eventually plan to use instead of AOSP keyboard but FlorisBoard isn't at version 1 yet and is missing some basic features despite having advanced stuff like swipe typing working already.
It's AOSP keyboard with minor modifications such as disabling learning based on your typing by default for improved privacy. You can use any other keyboard including the stock Pixel OS one which is Gboard. We may one day bundle FlorisBoard instead but it's missing some things.
https://twitter.com/GrapheneOS/status/1759231287724794316
If you want a keyboard with more features than the one included in GrapheneOS, consider using FlorisBoard. We may eventually be able to switch to a new keyboard as the basis for the one in GrapheneOS. At the moment, no third party keyboard meets our requirements.