Date   

Re: Build 71

David Nason
 

Hi Kosta and all,

on the whole, this is a great build, well done again.

I really like the new one finger flick and hold gestures. They are all working flawlessly for me. I really think the key is not to start the gesture at the very bottom or top of the screen, and to remember that the flick can be quite short, like just an inch is plenty.
I would agree that it would be good to add a flick left and hold for multiple word delete.

You won't be surprised to read that I do not like the gesture for getting a capital letter. I much much preferred when I could just type the letter and flick up to capitalize it. It can be done with one finger and is far more intuitive than the two finger tap. Why oh why would you take that away?😀

I love the emoji. I'm sure you plan to add more emoji to this, and let us configure which ones we have in our list, and in which order they appear. I look forward to that very much.

I'm experiencing a bug when I enter words manually. I will type it out, only to find it has put a space either after the first letter, or if there is a word within the word, it might do it there. Its not happening every time though.
My current working theory is that it is happening on words that are not in my dictionary. For example, when I typed "flawlessly" above using manual entry, it changed it to "flaw lessly", and when I tried to type the name "Wes", it changed it to "w es".

On that topic, it would be good to have the ability to add words to the dictionary, or perhaps this could be done automatically after manually entering a new word?

I do switch the keyboard rather than dismiss it. I do not like FlickType to be the keyboard that pops up when I first enter a text field.
The reason for this is that FlickType is full screen, and I can not navigate to other elements on the screen, or move the cursor to where I want it etc. For example, I read an email, then press the reply button. The new mail screen pops up, and FlickType pops up. I cannot check, or change which text field I am in, ie. recipient, subject or the body, or ensure that the cursor is at the beginning of that text field.

When I have on occasion used the flick down and hold gesture to dismiss the keyboard, I have noticed a significant lag, where everything freezes up for several seconds.
However, so far I have only seen this in the Mail app, and as I also see similar behaviour in the Mail app on other occasions for several versions of iOS now, this may well be Apple;s issue rather than yours.

Dave

On 25 May 2018, at 21:40, Ed Worrell <ed.worrell@...> wrote:

The gestured work great after awhile of using them.

I really am liking the new line gesture, I love the new manual typing: it works flawlessly.

I still am not sold on the keyboard dismiss gestures. I have had issues from the begining with them on my iPhone x. I have had the app close, after opening the app again ie. Messages the text I just entered is gone or I can no longer edit the text in the text field.

I am starting to see the dismissing of the keyboard become sluggish. This problem wasn't there with the three finger swipe down. That was a flawless experience for me. The single finger swipes seem to take longer than simply reaching up with three fingers and dragging down to dismiss the keyboard.

Maybe the three finger swipe down can be added back as an alternative gesture for those who prefer that gesture. A threw three finger swipe could be added as an alternative gesture for those who prefer it as well, to switch to the iOS keyboard. Other than the two keyboard dismiss gestures the build is great.


Ed
On May 25, 2018, at 2:22 PM, Paul Sutton <sutty_p@...> wrote:


Hi everyone,
I have only just started to have a play with this build and at the moment I am more than happy with the new gestures that have been implemented. They are all running smooth for me.
I would love to see a way of flicking through one letter at a time but I absolutely love this version.
As usual I can't wait until the tap sounds play on touch down rather than touch up.
Regards, Paul.
On 25 May 2018, at 20:53, Chuck Dean <cadean329@...> wrote:

I also like the new gestures. They work great for me.


Chuck

On May 25, 2018, at 12:41 PM, Matthew Janusauskas <mjanusauskas@...> wrote:


I respectfully disagree with Ed’s comments. I am finding the current gestures to be simple, logical and somewhat intuitive. They are working well for me and I am using an iPhone X.

Matthew


On May 25, 2018, at 2:23 PM, Ed Worrell <ed.worrell@...> wrote:

Hello All,


I am not really a fan of the new sgestures introduced in this build. I am having some very big issue with the flick and hold gestures. I don’t mind the new line gesture, that seems to work well. I how ever don;t know why we keep going back to the one finger flick and hold gestures in the keyboard to dismiss, and switch back to the iOs keyboard. We tried these in the first rebuilds of the keyboard app and they were problematic then. I think that if those gestures make it out the public, if infact the do, there will be tons of issues. People will stop uising the keyboard as they will always acsidently invoking the control center or draggin the notification center down. I have done this on my iPhone10 several times on this build. I really think that the three finger swipes were better suited for the purpose of switching to the iOS keyboard or dismissing the keyboard. I find the one finger swipe and hold to be much slower of a step then simply dragging down with three fingers. I might actually revert back to the last build as the current state of the gestures really isn;t any better then the previous to me. I however do like the new gestures to switch to symbols and numbers. The capitalization gesture was a little hard to understand at first, but I am good with it know. I do think it woud be nice to make the function more like a true shift as in resetting to lower case letters after one letter is ttyped. Maybe a three finger tap could be used to invoke a caps lock mode. I really simply don;t like the dismisial gestures of the current build.


Sorry for the long email.

Ed
On May 25, 2018, at 11:11 AM, Benny Barber <rebelben@...> wrote:

Kosta,

Will we not need the iOS keyboard active in a text message to have a send button? Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.


Re: Build 71

Ed Worrell
 

The gestured work great after awhile of using them.

I really am liking the new line gesture, I love the new manual typing: it works flawlessly.

I still am not sold on the keyboard dismiss gestures. I have had issues from the begining with them on my iPhone x. I have had the app close, after opening the app again ie. Messages the text I just entered is gone or I can no longer edit the text in the text field.

I am starting to see the dismissing of the keyboard become sluggish. This problem wasn't there with the three finger swipe down. That was a flawless experience for me. The single finger swipes seem to take longer than simply reaching up with three fingers and dragging down to dismiss the keyboard.

Maybe the three finger swipe down can be added back as an alternative gesture for those who prefer that gesture. A threw three finger swipe could be added as an alternative gesture for those who prefer it as well, to switch to the iOS keyboard. Other than the two keyboard dismiss gestures the build is great.


Ed

On May 25, 2018, at 2:22 PM, Paul Sutton <sutty_p@...> wrote:


Hi everyone,
I have only just started to have a play with this build and at the moment I am more than happy with the new gestures that have been implemented. They are all running smooth for me.
I would love to see a way of flicking through one letter at a time but I absolutely love this version.
As usual I can't wait until the tap sounds play on touch down rather than touch up.
Regards, Paul.
On 25 May 2018, at 20:53, Chuck Dean <cadean329@...> wrote:

I also like the new gestures. They work great for me.


Chuck

On May 25, 2018, at 12:41 PM, Matthew Janusauskas <mjanusauskas@...> wrote:


I respectfully disagree with Ed’s comments. I am finding the current gestures to be simple, logical and somewhat intuitive. They are working well for me and I am using an iPhone X.

Matthew


On May 25, 2018, at 2:23 PM, Ed Worrell <ed.worrell@...> wrote:

Hello All,


I am not really a fan of the new sgestures introduced in this build. I am having some very big issue with the flick and hold gestures. I don’t mind the new line gesture, that seems to work well. I how ever don;t know why we keep going back to the one finger flick and hold gestures in the keyboard to dismiss, and switch back to the iOs keyboard. We tried these in the first rebuilds of the keyboard app and they were problematic then. I think that if those gestures make it out the public, if infact the do, there will be tons of issues. People will stop uising the keyboard as they will always acsidently invoking the control center or draggin the notification center down. I have done this on my iPhone10 several times on this build. I really think that the three finger swipes were better suited for the purpose of switching to the iOS keyboard or dismissing the keyboard. I find the one finger swipe and hold to be much slower of a step then simply dragging down with three fingers. I might actually revert back to the last build as the current state of the gestures really isn;t any better then the previous to me. I however do like the new gestures to switch to symbols and numbers. The capitalization gesture was a little hard to understand at first, but I am good with it know. I do think it woud be nice to make the function more like a true shift as in resetting to lower case letters after one letter is ttyped. Maybe a three finger tap could be used to invoke a caps lock mode. I really simply don;t like the dismisial gestures of the current build.


Sorry for the long email.

Ed
On May 25, 2018, at 11:11 AM, Benny Barber <rebelben@...> wrote:

Kosta,

Will we not need the iOS keyboard active in a text message to have a send button? Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.













Re: Build 71

Paul Sutton
 

Hi everyone,
I have only just started to have a play with this build and at the moment I am more than happy with the new gestures that have been implemented. They are all running smooth for me.
I would love to see a way of flicking through one letter at a time but I absolutely love this version.
As usual I can't wait until the tap sounds play on touch down rather than touch up.
Regards, Paul.

On 25 May 2018, at 20:53, Chuck Dean <cadean329@...> wrote:

I also like the new gestures. They work great for me.


Chuck

On May 25, 2018, at 12:41 PM, Matthew Janusauskas <mjanusauskas@...> wrote:


I respectfully disagree with Ed’s comments. I am finding the current gestures to be simple, logical and somewhat intuitive. They are working well for me and I am using an iPhone X.

Matthew


On May 25, 2018, at 2:23 PM, Ed Worrell <ed.worrell@...> wrote:

Hello All,


I am not really a fan of the new sgestures introduced in this build. I am having some very big issue with the flick and hold gestures. I don’t mind the new line gesture, that seems to work well. I how ever don;t know why we keep going back to the one finger flick and hold gestures in the keyboard to dismiss, and switch back to the iOs keyboard. We tried these in the first rebuilds of the keyboard app and they were problematic then. I think that if those gestures make it out the public, if infact the do, there will be tons of issues. People will stop uising the keyboard as they will always acsidently invoking the control center or draggin the notification center down. I have done this on my iPhone10 several times on this build. I really think that the three finger swipes were better suited for the purpose of switching to the iOS keyboard or dismissing the keyboard. I find the one finger swipe and hold to be much slower of a step then simply dragging down with three fingers. I might actually revert back to the last build as the current state of the gestures really isn;t any better then the previous to me. I however do like the new gestures to switch to symbols and numbers. The capitalization gesture was a little hard to understand at first, but I am good with it know. I do think it woud be nice to make the function more like a true shift as in resetting to lower case letters after one letter is ttyped. Maybe a three finger tap could be used to invoke a caps lock mode. I really simply don;t like the dismisial gestures of the current build.


Sorry for the long email.

Ed
On May 25, 2018, at 11:11 AM, Benny Barber <rebelben@...> wrote:

Kosta,

Will we not need the iOS keyboard active in a text message to have a send button? Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.












Re: Build 71

Michael Maslo
 

Hello, 
 
 I personally like the three finger to dismiss the keyboard. Although I like it, I am trying the new gestured to get used of it. 

Sincerely,, mike 


On May 25, 2018 at 14:23, <Ed Worrell> wrote:

Hello All,



I am not really a fan of the new sgestures introduced in this build. I am having some very big issue with the flick and hold gestures. I don’t mind the new line gesture, that seems to work well. I how ever don;t know why we keep going back to the one finger flick and hold gestures in the keyboard to dismiss, and switch back to the iOs keyboard. We tried these in the first rebuilds of the keyboard app and they were problematic then. I think that if those gestures make it out the public, if infact the do, there will be tons of issues. People will stop uising the keyboard as they will always acsidently invoking the control center or draggin the notification center down. I have done this on my iPhone10 several times on this build. I really think that the three finger swipes were better suited for the purpose of switching to the iOS keyboard or dismissing the keyboard. I find the one finger swipe and hold to be much slower of a step then simply dragging down with three fingers. I might actually revert back to the last build as the current state of the gestures really isn;t any better then the previous to me. I however do like the new gestures to switch to symbols and numbers. The capitalization gesture was a little hard to understand at first, but I am good with it know. I do think it woud be nice to make the function more like a true shift as in resetting to lower case letters after one letter is ttyped. Maybe a three finger tap could be used to invoke a caps lock mode. I really simply don;t like the dismisial gestures of the current build.


Sorry for the long email.

Ed
> On May 25, 2018, at 11:11 AM, Benny Barber <rebelben@...> wrote:
>
> Kosta,
>
> Will we not need the iOS keyboard active in a text message to have a send button? Thanks.
>
> Benny
>
>> On May 25, 2018, at 12:04 PM, FlickType <hello@...> wrote:
>>
>> Thank you all for the feedback.
>>
>> There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.
>>
>> The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.
>>
>> Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.
>>
>> Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.
>>
>> Warmly,
>> Kosta and Ashley
>>
>>
>>> On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:
>>>
>>> Kosta,
>>>
>>> I love the new build, but I am having a few issues that I am listing below.
>>>
>>> 1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
>>> 2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
>>> 3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.
>>>
>>> Benny
>>>
>>>> On May 24, 2018, at 7:17 PM, FlickType <hello@...> wrote:
>>>>
>>>> - Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
>>>> - Magic tap to toggle the primary layout, between letters and numbers.
>>>> - Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
>>>> - Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
>>>> - Flick down and hold to dismiss, or up and hold for next keyboard.
>>>> - Flick right and hold for new line / return.
>>>> - Three finger tap and hold to read back.
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>




Re: Build 71

Chuck Dean
 

I also like the new gestures. They work great for me.


Chuck

On May 25, 2018, at 12:41 PM, Matthew Janusauskas <mjanusauskas@...> wrote:


I respectfully disagree with Ed’s comments. I am finding the current gestures to be simple, logical and somewhat intuitive. They are working well for me and I am using an iPhone X.

Matthew


On May 25, 2018, at 2:23 PM, Ed Worrell <ed.worrell@...> wrote:

Hello All,


I am not really a fan of the new sgestures introduced in this build. I am having some very big issue with the flick and hold gestures. I don’t mind the new line gesture, that seems to work well. I how ever don;t know why we keep going back to the one finger flick and hold gestures in the keyboard to dismiss, and switch back to the iOs keyboard. We tried these in the first rebuilds of the keyboard app and they were problematic then. I think that if those gestures make it out the public, if infact the do, there will be tons of issues. People will stop uising the keyboard as they will always acsidently invoking the control center or draggin the notification center down. I have done this on my iPhone10 several times on this build. I really think that the three finger swipes were better suited for the purpose of switching to the iOS keyboard or dismissing the keyboard. I find the one finger swipe and hold to be much slower of a step then simply dragging down with three fingers. I might actually revert back to the last build as the current state of the gestures really isn;t any better then the previous to me. I however do like the new gestures to switch to symbols and numbers. The capitalization gesture was a little hard to understand at first, but I am good with it know. I do think it woud be nice to make the function more like a true shift as in resetting to lower case letters after one letter is ttyped. Maybe a three finger tap could be used to invoke a caps lock mode. I really simply don;t like the dismisial gestures of the current build.


Sorry for the long email.

Ed
On May 25, 2018, at 11:11 AM, Benny Barber <rebelben@...> wrote:

Kosta,

Will we not need the iOS keyboard active in a text message to have a send button? Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.











Re: Build 71

Matthew Janusauskas
 

I respectfully disagree with Ed’s comments. I am finding the current gestures to be simple, logical and somewhat intuitive. They are working well for me and I am using an iPhone X.

Matthew

On May 25, 2018, at 2:23 PM, Ed Worrell <ed.worrell@...> wrote:

Hello All,


I am not really a fan of the new sgestures introduced in this build. I am having some very big issue with the flick and hold gestures. I don’t mind the new line gesture, that seems to work well. I how ever don;t know why we keep going back to the one finger flick and hold gestures in the keyboard to dismiss, and switch back to the iOs keyboard. We tried these in the first rebuilds of the keyboard app and they were problematic then. I think that if those gestures make it out the public, if infact the do, there will be tons of issues. People will stop uising the keyboard as they will always acsidently invoking the control center or draggin the notification center down. I have done this on my iPhone10 several times on this build. I really think that the three finger swipes were better suited for the purpose of switching to the iOS keyboard or dismissing the keyboard. I find the one finger swipe and hold to be much slower of a step then simply dragging down with three fingers. I might actually revert back to the last build as the current state of the gestures really isn;t any better then the previous to me. I however do like the new gestures to switch to symbols and numbers. The capitalization gesture was a little hard to understand at first, but I am good with it know. I do think it woud be nice to make the function more like a true shift as in resetting to lower case letters after one letter is ttyped. Maybe a three finger tap could be used to invoke a caps lock mode. I really simply don;t like the dismisial gestures of the current build.


Sorry for the long email.

Ed
On May 25, 2018, at 11:11 AM, Benny Barber <rebelben@...> wrote:

Kosta,

Will we not need the iOS keyboard active in a text message to have a send button? Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.









Re: Build 71

Ed Worrell
 

Hello All,


I am not really a fan of the new sgestures introduced in this build. I am having some very big issue with the flick and hold gestures. I don’t mind the new line gesture, that seems to work well. I how ever don;t know why we keep going back to the one finger flick and hold gestures in the keyboard to dismiss, and switch back to the iOs keyboard. We tried these in the first rebuilds of the keyboard app and they were problematic then. I think that if those gestures make it out the public, if infact the do, there will be tons of issues. People will stop uising the keyboard as they will always acsidently invoking the control center or draggin the notification center down. I have done this on my iPhone10 several times on this build. I really think that the three finger swipes were better suited for the purpose of switching to the iOS keyboard or dismissing the keyboard. I find the one finger swipe and hold to be much slower of a step then simply dragging down with three fingers. I might actually revert back to the last build as the current state of the gestures really isn;t any better then the previous to me. I however do like the new gestures to switch to symbols and numbers. The capitalization gesture was a little hard to understand at first, but I am good with it know. I do think it woud be nice to make the function more like a true shift as in resetting to lower case letters after one letter is ttyped. Maybe a three finger tap could be used to invoke a caps lock mode. I really simply don;t like the dismisial gestures of the current build.


Sorry for the long email.

Ed

On May 25, 2018, at 11:11 AM, Benny Barber <rebelben@...> wrote:

Kosta,

Will we not need the iOS keyboard active in a text message to have a send button? Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.








Build 71, a problem with Notes

Chuck Dean
 

Hi Kosta,
I was typing in notes and got the repeated text after I dismiss the keyboard to see what I typed, but when I started to type again my original text was replaced by what I was typing now.

I replicated this by dismissing the keyboard, touching a line of text, and then going back to type some more. Whatever I have touched and put the focus on gets replaced. Note: I am not doing a double tap, just a single tap to read that sentence.

I hope I have made myself clear.


Chuck


Re: Build 71

Chuck Dean
 

I agree, all of the gestures work fine with me.
Very intuitive and easy to execute.
( mighty big words )😎


Chuck

On May 25, 2018, at 11:21 AM, Benny Barber <rebelben@...> wrote:


I have no issues with all gestures. Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.








Re: Build 71

Benny Barber
 

I have no issues with all gestures. Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.






Re: Build 71

Chuck Dean
 


Hi George, 
 try doing your flick on the fly, by starting to move your finger to the right before you are actually touching the screen. Then once you are touching the screen stop and hold to insert a new line. 
 It takes a little practice, but once you get it, it will be easy to do. 


Chuck

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

Hi costa, I'm finding the gesture for new line is a bit tricky. The reason I say this is because the tap and hold is setting off another letter.

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 26, 2018 3:41:17 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 71
 

Hi Kosta,
 at this time my main reason for going to the iOS keyboard is to insert my text replacement.
 
 There have also been times when I have used the text selection feature to move or delete large blocks of text.


Chuck

> On May 25, 2018, at 10:04 AM, FlickType <hello@...> wrote:
>
> Thank you all for the feedback.
>
> There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.
>
> The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.
>
> Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.
>
> Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.
>
> Warmly,
> Kosta and Ashley
>
>
>> On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:
>>
>> Kosta,
>>
>> I love the new build, but I am having a few issues that I am listing below.
>>
>> 1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
>> 2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
>> 3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.
>>
>> Benny
>>
>>> On May 24, 2018, at 7:17 PM, FlickType <hello@...> wrote:
>>>
>>> - Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
>>> - Magic tap to toggle the primary layout, between letters and numbers.
>>> - Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
>>> - Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
>>> - Flick down and hold to dismiss, or up and hold for next keyboard.
>>> - Flick right and hold for new line / return.
>>> - Three finger tap and hold to read back.
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>




Re: Build 71

George Cham
 

Hi costa, I'm finding the gesture for new line is a bit tricky. The reason I say this is because the tap and hold is setting off another letter.

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 26, 2018 3:41:17 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 71
 

Hi Kosta,
 at this time my main reason for going to the iOS keyboard is to insert my text replacement.
 
 There have also been times when I have used the text selection feature to move or delete large blocks of text.


Chuck

> On May 25, 2018, at 10:04 AM, FlickType <hello@...> wrote:
>
> Thank you all for the feedback.
>
> There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.
>
> The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.
>
> Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.
>
> Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.
>
> Warmly,
> Kosta and Ashley
>
>
>> On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:
>>
>> Kosta,
>>
>> I love the new build, but I am having a few issues that I am listing below.
>>
>> 1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
>> 2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
>> 3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.
>>
>> Benny
>>
>>> On May 24, 2018, at 7:17 PM, FlickType <hello@...> wrote:
>>>
>>> - Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
>>> - Magic tap to toggle the primary layout, between letters and numbers.
>>> - Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
>>> - Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
>>> - Flick down and hold to dismiss, or up and hold for next keyboard.
>>> - Flick right and hold for new line / return.
>>> - Three finger tap and hold to read back.
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>




Re: Build 71

Chuck Dean
 

Btw,
I notice my emails are looking much better now that I can easily insert a new line, something I couldn't do with either the custom keyboard or Fleksy.
Thanks!


Chuck

On May 25, 2018, at 10:41 AM, Chuck Dean <cadean329@...> wrote:


Hi Kosta,
at this time my main reason for going to the iOS keyboard is to insert my text replacement.

There have also been times when I have used the text selection feature to move or delete large blocks of text.


Chuck

On May 25, 2018, at 10:04 AM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.







Re: Build 71

Sharon Kim
 

Hello all,
Noticed another little bug.
whenever you put in a symbol or number, there is a space automatically
added, and there's not really a way to get rid of the space, without
switching back to the IOS keyboard.
For example, if I wrote something like the following:
She said, "I have to go home."
I had to use quotes just today, it'll come out that there's a space
between the quotes. So for those with sight, it'll look like this.
She said, " I have to go home. "
Which isn't what I want.
As far as switching keyboards, yes I do have a need. It has nothing to
do with flicktype.
It's just that I from time to time, teach others how to use the
I-Phone. Sometimes, dictation and all that is one of them.
So I do flip back and forth.
Also on a personal note, I switch back to the IOS keyboard, because
the screen layout is different and I like it the way it is on a normal
keyboard, because it's what I'm used to. Thirdly, I sometimes, rarely,
use the record audio thing, and obviously, I can't use that feature
with flicktype as the main keyboard.
For these reasons, I usually tend to switch back to the IOS keyboard,
before sending my message.
anyways, that's it for me.

On 5/25/18, Chuck Dean <cadean329@...> wrote:

Hi Kosta,
I notice the line repeating happened occasionally, when I would rock
between the FlickType and iOS keyboard, or if I left the app I was typing in
and went to the FlickType app to enter a word into the dictionary.




Chuck

On May 25, 2018, at 10:04 AM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the
two finger single tap should act as a shift rather than a caps lock. All
that will be addressed soon, and thankfully these are the easier problems
to solve.

The repetition of some text is an odd one, but I suspect it has to do with
new lines. New lines have proven to be quite tricky due to how iOS handles
them but hopefully we’ll be able to address the issue. Any specific steps
to reproduce would be helpful. Also this may be more likely to happen on
an iPhone X when moving the voiceover cursor focus from the keyboard to
the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the
gestures. If a particular gesture is not working for you, please describe
as specifically as possible what happens when you attempt to perform that
gesture. For example, if you end up accidentally triggering another
gesture, please tell us what that other gesture is, and any additional
information that might be helpful for us to consider as we review the
current mapping of gestures to actions. Similarly, if you feel that some
gesture is hard to remember, or you’d prefer a different gesture, please
explain your reasoning in as much detail as possible. There are a lot of
factors we need to consider, and the more specific input we have, the
better.

Regarding the most frequent way to exit the FlickType keyboard, we are
hoping that most people will be dismissing the keyboard entirely rather
than switch to the iOS keyboard. If you keep needing to switch to the iOS
keyboard, please let us know why so we can assess if there’s something we
can improve in FlickType so you don’t have to switch as much. Note that
text replacement shortcuts and full emoji support are coming soon,
although dictation isn’t. Hopefully the combination of emoji, text
replacements, cursor control by word or sentence and the new read back
function mean that you don’t have to switch to iOS as often, but we’d love
to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing
below.

1. A two finger single tap in letters works as a caps lock rather than a
shift key. I tend to forget to go back to lower case after I go into
upper case and type a letter. I wished it only worked as a shift key for
a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is
upper case or lower case. When starting to touch type at the beginning of
a document, the first letter does not announce as upper case until I lift
my finger. The same is true when starting a new sentence in touch typing
after a period. The first letter only announces cap after you lift your
finger. If you 2 finger single tap to put you into upper case though, the
letter is announced as a cap as soon as you touch the screen. That is
more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper
case letter. The delete feedback is the same for lower case and upper
case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a
spacebar, delete, style toggle or shift key when exploring the keyboard.
If you are in numbers or symbols, entering a space will always return
you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In
letters, this switches between lowercase and uppercase. In numbers, it
switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick
up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.








Re: Build 71

Chuck Dean
 

Hi Kosta,
at this time my main reason for going to the iOS keyboard is to insert my text replacement.

There have also been times when I have used the text selection feature to move or delete large blocks of text.


Chuck

On May 25, 2018, at 10:04 AM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.






Re: Build 71

Chuck Dean
 

Hi Kosta,
I notice the line repeating happened occasionally, when I would rock between the FlickType and iOS keyboard, or if I left the app I was typing in and went to the FlickType app to enter a word into the dictionary.




Chuck

On May 25, 2018, at 10:04 AM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.






Re: Build 71

Chuck Dean
 

Hi BENNIE,
after you type your text message, simply dismiss the FlickType keyboard by doing a flick down and hold. Then you will be able to access the send button.
The same is true for emails.
I hope this helps,


Chuck

On May 25, 2018, at 10:11 AM, Benny Barber <rebelben@...> wrote:

Kosta,

Will we not need the iOS keyboard active in a text message to have a send button? Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.








Re: Build 71

Benny Barber
 

Kosta,

Will we not need the iOS keyboard active in a text message to have a send button? Thanks.

Benny

On May 25, 2018, at 12:04 PM, FlickType <@FlickType> wrote:

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley


On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.






Re: Build 71

 

Thank you all for the feedback.

There are known issues with casing of letters, including the fact that the two finger single tap should act as a shift rather than a caps lock. All that will be addressed soon, and thankfully these are the easier problems to solve.

The repetition of some text is an odd one, but I suspect it has to do with new lines. New lines have proven to be quite tricky due to how iOS handles them but hopefully we’ll be able to address the issue. Any specific steps to reproduce would be helpful. Also this may be more likely to happen on an iPhone X when moving the voiceover cursor focus from the keyboard to the area below it where the next keyboard button sits.

Perhaps the most important area that we’d like more feedback on are the gestures. If a particular gesture is not working for you, please describe as specifically as possible what happens when you attempt to perform that gesture. For example, if you end up accidentally triggering another gesture, please tell us what that other gesture is, and any additional information that might be helpful for us to consider as we review the current mapping of gestures to actions. Similarly, if you feel that some gesture is hard to remember, or you’d prefer a different gesture, please explain your reasoning in as much detail as possible. There are a lot of factors we need to consider, and the more specific input we have, the better.

Regarding the most frequent way to exit the FlickType keyboard, we are hoping that most people will be dismissing the keyboard entirely rather than switch to the iOS keyboard. If you keep needing to switch to the iOS keyboard, please let us know why so we can assess if there’s something we can improve in FlickType so you don’t have to switch as much. Note that text replacement shortcuts and full emoji support are coming soon, although dictation isn’t. Hopefully the combination of emoji, text replacements, cursor control by word or sentence and the new read back function mean that you don’t have to switch to iOS as often, but we’d love to know if you think you will still need to do that on a regular basis.

Warmly,
Kosta and Ashley

On May 25, 2018, at 08:52, Benny Barber <rebelben@...> wrote:

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.





Re: Build 71

Benny Barber
 

Kosta,

I love the new build, but I am having a few issues that I am listing below.

1. A two finger single tap in letters works as a caps lock rather than a shift key. I tend to forget to go back to lower case after I go into upper case and type a letter. I wished it only worked as a shift key for a letter at a time and we had another gesture to do a caps lock.
2. There is a little inconsistency in announcing whether a letter is upper case or lower case. When starting to touch type at the beginning of a document, the first letter does not announce as upper case until I lift my finger. The same is true when starting a new sentence in touch typing after a period. The first letter only announces cap after you lift your finger. If you 2 finger single tap to put you into upper case though, the letter is announced as a cap as soon as you touch the screen. That is more preferable to me.
3. When deleting letters I would like to know when I am deleting an upper case letter. The delete feedback is the same for lower case and upper case. Thanks so much.

Benny

On May 24, 2018, at 7:17 PM, FlickType <@FlickType> wrote:

- Merged touch typing and flick typing styles. There is no longer a spacebar, delete, style toggle or shift key when exploring the keyboard. If you are in numbers or symbols, entering a space will always return you to letters.
- Magic tap to toggle the primary layout, between letters and numbers.
- Single tap with two fingers to toggle the secondary layout. In letters, this switches between lowercase and uppercase. In numbers, it switches between numbers and symbols.
- Added emoji shortcuts 😎. Flick right to enter a period, then flick up. These will be configurable in the future.
- Flick down and hold to dismiss, or up and hold for next keyboard.
- Flick right and hold for new line / return.
- Three finger tap and hold to read back.