Parrotfish Keyboard – Better typing experience and fluent multi-language support

The keyboard was one of the main issues I had with SFOS, so following the same approach as Owlfish and Frogfish I vibecoded it with Claude to fit my needs (but possibly also other people’s needs):

  • automatic multi-language support: it follows the language word by word, so you can mix languages in the same message
  • good suggestions, prediction and autocorrect (three strengths)
  • learns your own words (a different set per language)
  • it looks very similar to the Jolla keyboard, so it doesn’t look out of place, but the keys are customizable (key fill, border, height, spacing, number row, etc.)
  • it’s just a keyboard: no additional features like a password manager, nothing that needs to access the internet, no system files modified and, most importantly, it doesn’t need root access

Supported languages: Dutch, English, French, German, Italian, Portuguese, Spanish.
Other experimental languages, in a separate package: Danish, Finnish, Norwegian, Romanian, Swedish.

Of course I could test it properly only in the 3 languages I know well, for the others I relied on automated tests on public texts. Feedback from native speakers would be very welcome.

I tested it on my Jolla Phone. The 32-bit build is untested, but it should work in theory. To be clear, I’m using this keyboard since a month already and I decided to publish it now because it eventually reached the level of quality I aimed for.

GitHub (license, install instructions, source): GitHub - ccontino84/parrotfish-keyboard: Better typing for the Sailfish OS keyboard, in several languages at once. · GitHub

I’ll add the OpenRepos link as soon as write access is restored (currently read-only due to the recent PHP vulnerability).

Interesting project, thanks for that - would certainly love to try that.
Have you thought about making the languages as opt in instead of distributing them all as a batch? The dictionaries apparently come from AOSP, would be great if you could provide the rest or a way to deploy them too but that can still be handled by a crafty user :slight_smile:

Great so far… For german language / qwertz layout i would wish that ä ö ü would be accesible through long press a o or u instead of being present all the time. like jolla qwertz layout. I enjoy having more space for the orher letters.
Thanks for the keyboard typin this post with it and works great

Simple efficient smart.
Many thanks for the work and nice apps.

Thanks! A screenshot or two would be nice.

Can you please also add the Slovenian language? It’s available in SFOS for a long time already with layout and all.

For French, I am very curious to know which keyboard is it? Bépo, Azerty, others?

Yes, I though about it, but one package per language is too much overhead for me. BTW adding a new language is not that trivial, the AOSP dictionaries are just one part of the job. You also need the language rules, word-pairs, etc.. I could add a guide to DEVELOPMENT.md

tl;dr AZERTY
Longer explanation: the thing is that you can type in any language you want with the layout that you prefer. For now the supported layouts are: QWERTY, QWERTZ and AZERTY. Never heard of Bépo but if simple to do it could be added.

Thanks all for the feedback! Some of the things you proposed might end up in the next release :+1:

Well Bépo works fine for me after installing this on my C2.

Thank you, great work. The Italian auto-suggest seems solid and the keyboard feels very nimble and responsive!

What features have you got in mind next? :slight_smile:
I have a bunch of conveniences I miss from gboard but I want to restrain myself from coming up with a laundry list :smiley:

Thanks! It would be cool to replace the memory button with a shortcut to the emoji keyboard. It’s a nice feature to be able to disable swype to change the keyboard but it makes it “harder” to use emojis.

Totally agree. I like to disable swipe for switch to emoji because I trigger it often on accident. So reachin emojis without long pressing space or swipe would be a nice thing

Most likely emojis will be the next big feature, I also miss it. After that probably voice recognition if doable without network access.

Swipe-typing is not available, correct? Or am I missing a setting somewhere? I like the overall phylosophy of this keyboard, but swipe to type is essential to me.

It’s not implemented, but it definitely fits the purpose of this keyboard, so I agree it should be added eventually

After trying out the Futo-KB-port since 14 days right now, I must say that Futo is setting a never-experienced level for Sailfish-KB-input.
It could be smarter in the long run focusing on what can be done and optimized to make Futo even better and more “Sailfishish”, than “challenging” it …. just a thought. :man_tipping_hand:

After the latest SFOS-updates completely impaired both Japanese keyboards ( both romaji and flick ) and trying fixinig it by means of symlinks and config-file modifications, I lost patience and gave Futo a chance. Almost a bit overloaded but also featuring lots of useful stuff and recognizable engineering hours ;). Password-safekeeping pop-ups can be a bit annoying if you don’t want it - but I’m sure this can be deactivated somehow. Pity, Japanese voice input is not working / available yet - but English and German work really well. I’ll have to give it further research these days ….

This is the BEST keyboard for my Jolla Phone 2026. I have tried FUTO but this outperforms it for me. Keep up the great work.

I agree with you on this.

Doable without network access, but in my recent experience maybe not ideally suited for a keyboard. I’m working on introducing (optional) voice message transcription in piirit with local whisper.cpp. You get okay transcription speeds, 1 second of voice input in takes 1 second to transcribe. Fine for voice message transcription on-demand or while connected to the charger, but not great for “feels instant” keyboard use.

In addition, with the model I ended up using, word error rates are below 15% only for six languages. More infos on my testing in the PR linked above.

If you end up implementing this and find a smarter way and/or yield better results, I’d love to hear about it! :folded_hands: