Date   

Re: Build 68

Macster
 

Wow, the speed at which you release each version never ceases to amaze me! I think you have addressed pretty much all of our moans from yesterday - the lack of a character echo is very welcome for me personally! The flick gestures in direct typing mode work very well for capitalisation and word completion in particular, and word announcement after flicking right works perfectly too. The shift key is sorted too, and it all feels as crisp as build 67 did. I did prefer the gesture to change between flick and touch modes instead of finding the button, but as you said your intention is to have a manual input method similar to the app so this won't be relevant long term anyway :)

With many thanks and appreciation as always for your hard work Kosta and Ashley.

Macky

On 19 May 2018, at 08:39, FlickType <@FlickType> wrote:

Thank you for the feedback, we always read all of your posts to the group, so please keep it coming. This is still work-in-progress, and eventually there will be a manual input mode similar to the main app.

Touch Typing related changes:
- Swapped magic tap and tap and hold gestures for changing keyboard or typing style. When Touch Typing, there is now a button to change back to Flick Typing. Note that upon entering Touch Typing, you will need to release your touch and tap again to start exploring. This is annoying but will be addressed soon.
- Added one and two finger flick gestures when Touch Typing. Flick left will delete the last character, flick right will add a space, flick up and down will change the current character's case. Two finger flick left or right will move the cursor by character.
- Fixed inverted shift state announcement bug
- Shift will automatically be selected and unselected as needed.
- Character echo will now respect the setting from the main app
- Added word echo

Kosta



Re: Build 68

George Cham
 

Ok working better    .  But can there be a flick gesture for symbles ?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 19, 2018 5:54:58 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 68
 
Ok, this is working better. It took me a while to find the button to go back to FlickType, which is in the same place as the globe button, just left of the space bar.



Chuck

> On May 19, 2018, at 12:39 AM, FlickType <hello@...> wrote:
>
> Thank you for the feedback, we always read all of your posts to the group, so please keep it coming. This is still work-in-progress, and eventually there will be a manual input mode similar to the main app.
>
> Touch Typing related changes:
> - Swapped magic tap and tap and hold gestures for changing keyboard or typing style. When Touch Typing, there is now a button to change back to Flick Typing. Note that upon entering Touch Typing, you will need to release your touch and tap again to start exploring. This is annoying but will be addressed soon.
> - Added one and two finger flick gestures when Touch Typing. Flick left will delete the last character, flick right will add a space, flick up and down will change the current character's case. Two finger flick left or right will move the cursor by character.
> - Fixed inverted shift state announcement bug
> - Shift will automatically be selected and unselected as needed.
> - Character echo will now respect the setting from the main app
> - Added word echo
>
> Kosta
>
>
>




Build 68

Chuck Dean
 

Hi Kosta, with these new gestures am I right in assuming that the space bar, shift, and delete keys will eventually be removed?


Chuck


Re: Build 68

Chuck Dean
 

Ok, this is working better. It took me a while to find the button to go back to FlickType, which is in the same place as the globe button, just left of the space bar.



Chuck

On May 19, 2018, at 12:39 AM, FlickType <@FlickType> wrote:

Thank you for the feedback, we always read all of your posts to the group, so please keep it coming. This is still work-in-progress, and eventually there will be a manual input mode similar to the main app.

Touch Typing related changes:
- Swapped magic tap and tap and hold gestures for changing keyboard or typing style. When Touch Typing, there is now a button to change back to Flick Typing. Note that upon entering Touch Typing, you will need to release your touch and tap again to start exploring. This is annoying but will be addressed soon.
- Added one and two finger flick gestures when Touch Typing. Flick left will delete the last character, flick right will add a space, flick up and down will change the current character's case. Two finger flick left or right will move the cursor by character.
- Fixed inverted shift state announcement bug
- Shift will automatically be selected and unselected as needed.
- Character echo will now respect the setting from the main app
- Added word echo

Kosta



Build 68

 

Thank you for the feedback, we always read all of your posts to the group, so please keep it coming. This is still work-in-progress, and eventually there will be a manual input mode similar to the main app.

Touch Typing related changes:
- Swapped magic tap and tap and hold gestures for changing keyboard or typing style. When Touch Typing, there is now a button to change back to Flick Typing. Note that upon entering Touch Typing, you will need to release your touch and tap again to start exploring. This is annoying but will be addressed soon.
- Added one and two finger flick gestures when Touch Typing. Flick left will delete the last character, flick right will add a space, flick up and down will change the current character's case. Two finger flick left or right will move the cursor by character.
- Fixed inverted shift state announcement bug
- Shift will automatically be selected and unselected as needed.
- Character echo will now respect the setting from the main app
- Added word echo

Kosta


Re: Build 67

Chuck Dean
 

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



Chuck

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. 

Ed


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!


Chuck

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. 

Ed


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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Ed Worrell <ed.worrell@...>
Sent: Saturday, May 19, 2018 2:25:08 PM
To: alpha@flicktype.groups.io
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. 

Ed


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

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



Chuck

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. 

Benny 

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
To: alpha@flicktype.groups.io
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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Ed Worrell
 

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. 

Ed


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!


Chuck

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. 

Ed


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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Ed Worrell <ed.worrell@...>
Sent: Saturday, May 19, 2018 2:25:08 PM
To: alpha@flicktype.groups.io
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. 

Ed


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

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



Chuck

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. 

Benny 

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
To: alpha@flicktype.groups.io
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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Chuck Dean
 

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!


Chuck

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. 

Ed


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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Ed Worrell <ed.worrell@...>
Sent: Saturday, May 19, 2018 2:25:08 PM
To: alpha@flicktype.groups.io
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. 

Ed


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

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



Chuck

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. 

Benny 

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
To: alpha@flicktype.groups.io
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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Ed Worrell
 

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. 

Ed


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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Ed Worrell <ed.worrell@...>
Sent: Saturday, May 19, 2018 2:25:08 PM
To: alpha@flicktype.groups.io
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. 

Ed


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

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



Chuck

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. 

Benny 

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
To: alpha@flicktype.groups.io
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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

George Cham
 

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Ed Worrell <ed.worrell@...>
Sent: Saturday, May 19, 2018 2:25:08 PM
To: alpha@flicktype.groups.io
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. 

Ed


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

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



Chuck

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. 

Benny 

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
To: alpha@flicktype.groups.io
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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Ed Worrell
 

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. 

Ed


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

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



Chuck

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. 

Benny 

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
To: alpha@flicktype.groups.io
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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Chuck Dean
 

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



Chuck

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. 

Benny 

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
To: alpha@flicktype.groups.io
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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Benny Barber
 

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. 

Benny 

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
To: alpha@flicktype.groups.io
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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

George Cham
 

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

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 12:35:44 PM
To: alpha@flicktype.groups.io
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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Benny Barber
 

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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Benny Barber
 

Aren't all first letters currently capitalized except email fields in the iOS keyboard? 

On May 18, 2018, at 9: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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Chuck Dean
 


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.


Chuck

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Michael Maslo
 

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:

Kosta,


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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.







Re: Build 67

Benny Barber
 

Kosta,

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
backwards.

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
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
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.

Notes:
- 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.


Re: Build 67

George Cham
 

ok,but i think the flick gesture  after typing should be introduced in this new build. This makes it easier then trying to find Space in return

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 10:41:18 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

I too have very little sight, so the way the screen looks is not important to me. I need audible feedback to know what I am typing. Thanks.

Benny

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

i agree with you . I think  the half screen keyboard is better,because we can see what we are   typing.. also, from memory in build  50 , the   white bar was put there to represent the top and bottomrows. This should be brought back

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 19, 2018 10:00:56 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

With the half screen keyboard there would be much less need for switching to the iOS keyboard, as it would be easy to move the cursor in various text fields.


Don't get me wrong, I think the custom keyboard is pretty amazing, but the half screen would fit my personal needs better.


Chuck

> On May 18, 2018, at 4:23 PM, Ed Worrell <ed.worrell@...> wrote:
>
>
> Hey there chuck,
> I couldn't agree with you more. I would love to see the keyboard become a half screen effort. This would be great to me as well. Ed
>> On May 18, 2018, at 5:08 PM, Chuck Dean <cadean329@...> wrote:
>>
>> Build 67
>> Hi all, I just got off a cross country flight and did some typing along the way.
>> Personally, I don't see any way to beat the typing experience in the FlickType app. If this keyboard, with its manual entry, numbers and symbols, could be incorporated into a half screen, system wide keyboard, I think the blind and visually impaired community would be pretty happy with the end product. Look at the very positive response the app got when it went public.
>>
>> I know you said you wanted to keep the manual input close to the iOS experience... But why? Unless you are planning a general public release, I see no reason for this. If the app style keyboard could be incorporated as a system wide keyboard, after very little use it would be my default keyboard and the iOS keyboard would become a piece of nostalgia.
>>
>> Just my opinion...
>>
>>
>>
>> Chuck
>>
>>
>
>
>