• General

  • Which keyboard is most likely to replace the AOSP keyboard on GrapheneOS?

  • [deleted]

  • Post #12
  • Edited

investigator I'm talking about the default keyboard on GrapheneOS. If you are aware of that, then please link me to the source where it says that FlorisBoard will not replace the AOSP keyboard.

    The default keyboard app may or may not be replaced in the future, but whether it will be Florisboard or something else that replaces it is still unknown.

    [deleted] This is where the talk about this ended: https://web.archive.org/web/20220803142758/https://github.com/florisboard/florisboard/issues/1921

    Which isn't very promising.

    The reason why that GitHub discussion is deleted and you had to find an archive of it is because things were talked out with Florisboard. We are not on bad terms with them. Just clearing the air there.

        • [deleted]

        • Post #15
        • Edited

        matchboxbananasynergy If I had to bet, I would bet on FlorisBoard. I'll switch to it so I get used to it until it's probably added to GrapheneOS (the AOSP keyboard doesn't suit my needs anymore anyway).

            Good lord. Either way Daniel doesn't lead the charge anymore, so his opinions are now his own and don't necessarily reflect anything GrapheneOS may do now or in the future. So it would be nice if we stopped bringing up old beef and focused on the future instead.

              • [deleted]

              • Post #17

              Ammako This is highly off topic. Nobody bringed that up, I was just curious about situation with FlorisBoard.

                Florisboard contains libraries under restrictive open-source licenses, which are not compatible with GrapheneOS. I rather think that, when the time comes, the devs will create a new keyboard based in part on florisboard.

                  • [deleted]

                  • Post #20

                  I have no problem using AOSP keyboard. But then again my expectations aren't high. (I don't rely on spell check and if make a mistake, I just apologize and move on) I presume, in terms of security it fares well otherwise it would have no place in GrapheneOS.

                  • [deleted]

                  • Post #21

                  investigator That's not correct. FlorisBaord ditched Nuspell for this exact reason.

                    • [deleted]

                    • Post #22
                    • Edited

                    SoulKeeper Did you try using FlorisBoard? The difference is huge.
                    More languages, more features, more customization, etc.

                      a month later

                      Any update on this?

                      FlorisBoard is awesome. Even in it's currents state it's way better than the stock keyboard.

                      • [deleted]

                      • Post #25
                      • Edited

                      investigator decentralized technology

                      *federated learning?

                        matchboxbananasynergy

                        Look at requiring the rights to the BlackBerry vkb . Needs updating but it may be using SwiftKey licences?? It's a great keyboard just the way it is now. I'm using it on my 6a.

                          • [deleted]

                          • Post #29
                          • Edited

                          Room101 Florisboard is not abandoned. I'm not a dev, but it looks like they are working through the issues of integrating a new NLP core.

                          https://github.com/florisboard/florisboard/issues/2218

                          Edit: also from github...

                          The current focus is on implementing next-word suggestions, which has become complicated/hit a snag and is taking more time than originally planned. Updates will come when this issue is resolved. Thank you for being patient.

                            7 months later

                            I think its best to have every app as a user app. AOSP keyboard is fine for setting up the phone.

                            The big UI improvement would be to show installable user apps on setup, where you can install apps not made or maintained by GrapheneOS.

                            GrapheneOS has a very bad UX out of the box but preinstalling big and hardly maintained apps has many disadvantages, with the restrictive licenses being the most obvious one.

                            I think this is all about Obtainum getting a Feed feature. Currently I use F-Droid basic with izzyondroid and more repos, just to get 90% of all Android FOSS apps to care about, where I can then copy the source URL into obtainium.

                            Having a secure appstore using official releases in the GrapheneOS appstore would be a big step