App keyboard, very noob question about how to hide keyboard

General
1

I can’t figure it out how you hide keyboard, for example in native Yottagram (Telegram) when you write message to person or group, keyboard stays open and I can’t figure out how to hide it?

Feels stupid, this should be no brainer but can’t figure it out.

Same problem with android apps like WhatsApp, how you hide keyboard once you have written something? Yes I know that as workaround is to go previous screen and then back but that’s not very user friendly.

There should be arrow or some other way to hide in same way, for ex. tapping other part of screen to hide it or something…

And of course I miss a lot lack of biometric/fingerprint support for android app, most for banking and password managers (using 1password, and enpass) but maybe I migrate to Bitwarden if that has native app for SOF.

And for end thanks people, this has been already very interesting journey as I started to use/learn my new Jolla Phone 2026 as daily driver (had zero exp from SOF before). Takes some effort have to say but I understand that as its small alternative for android/iOS. There is lot of work to do make it perfect.

2

Just swipe down over the keyboard

10 Likes
3

Bitwarden has a excellent native client called Bitsailor. Highly recommend it, it also has fingerprint authentication feature :wink:

2 Likes
4

You can mark the message by @throwaway69 as a solution for future readers, as it should be the answer you were looking for.

3 Likes
5

Slightly adding to confusion, there’s also Sailwarden. I can’t tell you how they compare, however, both have their threads here for user experience and support.

6

About the keyboard: a swipe down that starts above the keys, otherwise it gets misinterpreted as input. Or a tap on an empty area above the keyboard.

7

It is perfectly possible to start on the keys. As long as you don’t release before having swiped down, you won’t have any keystrokes registered.

1 Like
8

Might be that ohnonot uses okboard that could explain the difference

9

Then s/he should know that and not make general recommendations based on it.

10

One thing I have noticed is that swiping down on the keyboard is somewhat more finicky on the Jolla Phone 2026 than on any other Sailfish devices so far. It tries to interpret the swipe as possible text input too often. On previous devices I encountered a failed swipe down maybe 1/100 times, but on the Jolla Phone 2026 it’s about 1/10 times if not even more often. It needs some more tweaking, just like the gesture to change keyboards, which has the reverse problem that text input is often interpreted as a swipe to the sides.

1 Like
11

What makes hiding of keyboard slightly unintuitive is that nothing happens until finger slips away from the edge of the screen.

Many hide something or get rid of something actions are such the things are moving immediately when you start swiping, so that you know that something is going to happen. When hiding keyboard nothing indicates that something is about to happen until swipe is complete. Not a problem when you are familiar with it but not so easy to find just by trying.

3 Likes
12

I can. One was written and source is available, and the other one is probably vibe coded and closed source.

Feel free to ask the dev regarding vibe coding or the source so that he can completely avoid answering your question.

2 Likes
13

Definitely it would be way that way, similar like when swiping apps from bottom.

And thanks @throwaway69 for the solution, I know it should be some simple but didn’t find it out :smiley:

14

hmm, looks like BitSailor doesn’t show custom fields and looks like info you can add for example for card is very limited.

15

You can continue giving feedback and feature requests for BitSailor at BitSailor support thread

2 Likes
16

If it did, you could not use swipe input. Not that I ever use it.

17

If it did, you could not use swipe input. Not that I ever use it.

aaah, you mean that input method where you move finger around keyboard without lifting it. Never learned to use it, so forgotten.

But maybe it would be possible to have only top edge of keyboard sensitive for grabbing…?

18

OKBoard might affect my experience