Hi all, Some people have been mentioning what they would like to see in terms of development. So I thought I'd send out my own wishlist. Larger dictionary. All too often I tap out relatively

High all, I tried out build 133, and I see no reason to use this version. I would like to see build 132 expanded and the features included in future versions. 133 is just like an ios keyboard, and I

Hi all, I am very much with chuck and Ed on this. If the half screen keyboard only does the manual typing method, then I really see absolutely no advantage to this over just switching to the

Hey Benny, Yes this is correct. I feel that this would give everyone the option to have the keyboard they want, or at least close... The unfortunate thing about this is a lot of work to do for

Hey chuck, As soon as you move to the application part of the window or change focus it could place the text. All though I would be happy with a half screen option that would function just like

Hi Ed, I too would. like a smaller version of FlickType that could use tap typing. But as I understand it, this is not possible with the current configuration. Here is how Kosta explained it:

Hello Ed, Am I understanding you correctly? You prefer to have a full screen and a standard screen that are exactly the same in function? Thanks. Benny

Hello all, I too like chuck use Fleksy and flicktype. I and really wanting to have a smaller version of flicktype. That's why I suggest a mode option... This could be implemented in the setting

Hi Benny, Yes, my vision, and probably most people's vision of a half screen keyboard is a smaller keyboard that can be used like FlickType's tap typing and still have the ability to interact with

Chuck, I understand what you are saying and I assume you would prefer a smaller full featured tap typing keyboard. I just don't know if smaller is a good idea for those of us with unusable or no

Chuck, I do not know or understand what your saying. I think it is a nice step forward. I find it extremely useful and for me the need to change keyboard less often being needed. Just because you do

Kosta, I like where you are going with this. I would like there to be consistency in the focus when the custom keyboard is invoked. Sometimes it will open, the initial announcements are spoken and

Hi kosta, I have played with Build 133 for a while, I really do not see an advantage with this keyboard over just switching between the FlickType and iOS keyboards. When I leave this email, I

Hello kosta, I love the new gesture to make the keyboard standard sized. That's as much as I like in this build. You're just teasing me Doug with the idea of a smaller keyboard...☺️ Things

Ok, I am learning that the 3 finger flick up or down must be short and quick. It should not be a long swipe. I'm getting better at it. Thanks. Benny

I wish we had the option to toggle off the announcements when FlickType is opened. The only announcement that I would like to hear is FlickType full screen or FlickType standard screen. The

Ok, I'm trying to buy into the latest version. Sometimes the 3 finger gesture does not always work. I have to do it multiple times to get it to work. Sometimes in the full screen, I will start to do

I would also like to see the half screen mode have the same ability as the full screen mode. I personally would like to see the text typed displayed smaller in the half screen version as well.

I like that it's smaller now, but aside from that it doesn't really achieve anything for me I'm afraid. With it just supporting touch typing, I may as well be switching to the standard iOS keyboard.

Apologies, I never replied back to you on this. Strangely, the issue seems to have stopped. Fingers crossed I don't see it again. I don't like deleting my messages if I can help it, so hopefully