Re: Build 67

Chuck Dean

 I agree; this is why I continue to use the app... It just works so well. 


On May 18, 2018, at 10:24 PM, Ed Worrell <ed.worrell@...> wrote:

Yeah, that's the way I understand it too. I hope at some point the manual and gesture based keyboard are unified. This would be fantastic to see. I understand there is a process to development I just hope the they consider combining the two options. I feel this would speed up productivity. 


On May 18, 2018, at 11:09 PM, Chuck Dean <cadean329@...> wrote:

My understanding is that the FlickType app's keyboard is a clone of the old FleksyVO and because it has had so many different people's hands in it that it is almost impossible to duplicate, so Kosta is starting from scratch. He also would like to find the very best approach for the blind and visually impaired.
It may take a while, but I'd bet money that by this time next year we are going to have an incredible tool!


On May 18, 2018, at 9:57 PM, Ed Worrell <ed.worrell@...> wrote:

Thanks. That's what I thought. I dong think I would mind the current functionality if we eventually get the same functions of the default keyboard. I really would like to see the gesture keyboard and manual keyboard in one keyboard. This would make the productivity much quicker and simplify too. I guess we will have to wait and see what we get. 


On May 18, 2018, at 10:45 PM, George Cham <George.cham@...> wrote:

just tried searching on appstore using manual typing ,but i had to go  back to ios keyboard to do the search.aSo the answer at this time is no.

Kind regards,

George Cham

‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
Numbers 6:24-26
Get Outlook for iOS

From: <> on behalf of Ed Worrell <ed.worrell@...>
Sent: Saturday, May 19, 2018 2:25:08 PM
Subject: Re: [FlickType-alpha] Build 67
I have been using the manual entry portion of the keyboard. Using this in the app store works except for there is no way to make a search go through. Has anyone found a work around, short of switching back to the default keyboard? Their doesn't seem to be anyway to activate the search option. 


On May 18, 2018, at 9:18 PM, Chuck Dean <cadean329@...> wrote:

 I agree, the shift key's verbal feedback seems backwards. 


On May 18, 2018, at 8:11 PM, Benny Barber <rebelben@...> wrote:

I believe in the iOS keyboard and the FlickType app they are capitalized.  No big deal.  My main issue was the shift key. The feedback is confusing to me. To each his own. Take care. 


On May 18, 2018, at 9:42 PM, George Cham <George.cham@...> wrote:

as i type this reply,the first  letter,was not a capital .

Kind Regards,

George Cham

From: <> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
Subject: Re: [FlickType-alpha] Build 67
You are correct.

On May 18, 2018, at 9:28 PM, Chuck Dean <cadean329@...> wrote:

Hi mike, I think the password issue is moot, because I'm pretty sure that iOS will not allow third party keyboards to input sensitive information.


On May 18, 2018, at 7:08 PM, Michael Maslo <michaelmaslo04@...> wrote:

Hello, I do not agree with those suggestions. The reason I personally do not want the first letter capitalize is because when I am typing a email address it is usually all small letters. Also a lot of my passwords are small letters. It would make things harder. Secondly, if I am using manual input and I am typing a word that way, I hear every letter I typed. I do not need to hear the word again especially since I typed it out letter by letter. To me it would be a annoyance to hear it twice. Again this is my opinion only.

Sincerely,, mike 

On May 18, 2018 at 20:42, <Benny Barber> wrote:


Currently as the custom keyboard stands, I have 2 issues that are a
hinderance to me.

1. Let's use the letter "x" as an example for this first issue. As I stated
in an earlier message, the shift key is confusing to me. In my humble
opinion, I think that at the beginning of a document the keyboard should
always be in "Caps" mode. When that first letter is entered the feedback
should be "Cap x" and then go into lower case mode. When you want to type
an upper case letter in the middle of a document or sentence and you touch
the shift key, the feedback when lifting the finger should be "Caps" to let
you know that you have entered the upper case mode. Then when you touch a
letter the feedback should be "Cap x". Conversely, when you want to change
the mode from upper case to lower case and touching the shift key, the
feedback should be "lower case" when you lift your finger. Currently it is

2. As a user of FlickType, I have very limited sight and do not use any
sight to use the keyboard. I depend on the audible feedback exclusively.
With that said, all the feedback I can get assists me greatly in the typing
experience. I need character feedback and word feedback. Currently on the
direct input of letters you do not get word feedback when you space. This
is a hinderance in my typing. I need the confirmation that I have typed the
previous word correctly.

Thanks for all that you and Ashley have done. I greatly appreciate your


-----Original Message-----
From: [] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
Subject: [FlickType-alpha] Build 67

This is the very first, and still quite experimental, version of the manual
typing functionality. The approach we are taking is to start from the
basics, and expand as we go. As a first step, we simply bring the Touch
Typing style of the regular iOS keyboard right within FlickType, and make it
fast and easy to toggle between Flick Typing and Touch Typing using the
magic tap gesture. If you are not familiar, a magic tap is a double tap with
two fingers, and is used to perform the so-called "most-intended" action,
regardless of what element the VoiceOver cursor is currently focused on.

- You cannot yet use any flick gestures when Touch Typing, but you will be
able to in the future.
- You can now enter a new line with the Return key, just like with the iOS
keyboard. When you go back to Flick Typing, new lines will currently not be
announced when moving the cursor.
- The voice feedback for entered characters does not have a different pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in
the main app. We're doing this for a couple of reasons: One is to make it
easier for new users to fall back to a familiar typing style when needed.
Two, manually typing longer words should be easier and faster this way. We
might not be there yet, but this is the reasoning behind the approach.

Join to automatically receive all group messages.