Date   

Build 54

Chuck Dean
 

Build 54
Is anyone getting the memory warning! Dialogue when typing for long periods of time with the custom keyboard? I am getting this message about every third word. I had this problem last night and had to reboot the iPhone to get it to stop.


Chuck


Re: Build 54

Chuck Dean
 

this only happens when I reply to an email... All other times are ok.

Chuck

On May 2, 2018, at 2:29 PM, George Cham <George.cham@...> wrote:

I have no problems with the first letter starting with a capital. However when I'm typing I'm not seen the letters appearing straightaway. There is seems to be a bit of a delay between typing and when the words appear on the screen. I'm not relying on the words on the screen, as I am using voice-over, but entering words is becoming more more difficult because I have to swipe down through a whole heap of suggestions even though I'm typing the words accurately. Still don't like the white background representing the two rows of keys.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Thursday, May 3, 2018 7:15:39 AM
To: Alpha
Subject: [FlickType-alpha] Build 54

Build 54
Hi Kosta,
I tried replying to a few emails to myself, and on all of the replies, the first letter is never capitalized.

Also, in a previous email I asked if the delete taps could be incorporated in the app, I meant clear taps.
Thanks,


Chuck






Re: Build 54

George Cham
 

I have no problems with the first letter starting with a capital. However when I'm typing I'm not seen the letters appearing straightaway. There is seems to be a bit of a delay between typing and when the words appear on the screen. I'm not relying on the words on the screen, as I am using voice-over, but entering words is becoming more more difficult because I have to swipe down through a whole heap of suggestions even though I'm typing the words accurately. Still don't like the white background representing the two rows of keys.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Thursday, May 3, 2018 7:15:39 AM
To: Alpha
Subject: [FlickType-alpha] Build 54

Build 54
Hi Kosta,
I tried replying to a few emails to myself, and on all of the replies, the first letter is never capitalized.

Also, in a previous email I asked if the delete taps could be incorporated in the app, I meant clear taps.
Thanks,


Chuck


Build 54

Chuck Dean
 

Build 54
Hi Kosta,
I tried replying to a few emails to myself, and on all of the replies, the first letter is never capitalized.

Also, in a previous email I asked if the delete taps could be incorporated in the app, I meant clear taps.
Thanks,


Chuck


Build 54

Chuck Dean
 

Build 54
Hi Kosta,
I noticed when I use the custom keyboard to reply to an email; the first letter in the reply is not capitalized.


Chuck


Re: Build 53

Benny Barber
 

I’m using a 5s with 11.3.1 and it doesn’t work.

On May 2, 2018, at 3:23 PM, Chuck Dean <cadean329@...> wrote:

that's strange. It speaks the sentence when I do a three finger flick.
I just tried it with this email; it worked perfectly. I am using an iPhone 8,
Running ios 11.3.1.

Chuck

On May 2, 2018, at 1:08 PM, Benny Barber <rebelben@...> wrote:

The word is read aloud on the 2 finger flick, but nothing is read aloud with the 3 finger flick.

On May 2, 2018, at 2:51 PM, Chuck Dean <cadean329@...> wrote:

Hi Bennie,
When you move the cursor, the word or sentence will be red aloud, so you will know exactly where you are.
Try it, works great! :)

Chuck

On May 2, 2018, at 12:24 PM, Benny Barber <rebelben@...> wrote:

Thanks, Chuck. It seems like I would like to hear something. Maybe the first word of the sentence where you moved to. Thanks again.

Benny

On May 2, 2018, at 2:05 PM, Chuck Dean <cadean329@...> wrote:

Hello Bennie,
There is really no need for verbal feedback when using the cursor. If you flick left with two fingers; you are moving the cursor back one word. If you flick right with two fingers; you are moving the cursor one word forward.

If you flick left with three fingers; you are moving the cursor back one sentence. If you slick right with three fingers you are moving the cursor forward one sentence.

Chuck

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

Hello,

I don't remember reading about the 3finger flick right and left to advance the cursor a sentence at a time. Is this a new gesture? If so, can we get some verbal feedback such as; back 1sentence and forward 1sentence? Thanks so much.

Benny

On May 1, 2018, at 9:52 PM, FlickType <@FlickType> wrote:

This took longer than expected. Changes since the previous build:

- This is a major rewrite. Among other differences, the previous build would only change the underlying textfield when you exited the FlickType keyboard, not while you typed. FlickType will now immediately perform all edits in the current field, such as inserting, deleting or changing words. This paves the way for an optional half-screen mode in the near future.
- Reduced memory consumption to address crashing. Unfortunately iOS only allows very little active memory for keyboards compared to regular apps, and aggressively terminates any keyboard that crosses the threshold.
- You now also need to enable "Full Access" in the FlickType settings under the iOS settings app. This is for FlickType to be able to play any sound effects such as taps. The previous method of playing taps was using a private API and was likely to be rejected if submitted to the App Store. Currently, if you don't enable "Full Access" the keyboard will crash. This is a good opportunity to share our very short privacy policy: http://www.flicktype.com/privacy
- If you have some pending taps and flick left to delete, FlickType will now announce "Cleared taps" instead of deleting the previous word.
- You can now move the cursor and navigate the entire current document, not just the current sentence. This should make it more usable for writing longer pieces of text.
- Added a visual keyboard indicator for low-vision folks, in the form of 2 horizontal white bars representing the top and bottom rows.
- Introducing the FlickType "visual announcements", designed to better help low-vision and hearing-impaired folks use the product. All VoiceOver typing announcements for inserting, deleting and changing words will now also be displayed as high-contrast text using the largest possible font size that fits the entire screen above the keyboard area. This replaces the text view that was previously used for debugging.
- The gesture to dismiss the keyboard has been changed to a 3 finger flick down.

We are both really looking forward to hearing what you all think, smile!

Warmly,
Kosta & Ashley












Re: Build 53

Chuck Dean
 

that's strange. It speaks the sentence when I do a three finger flick.
I just tried it with this email; it worked perfectly. I am using an iPhone 8,
Running ios 11.3.1.

Chuck

On May 2, 2018, at 1:08 PM, Benny Barber <rebelben@...> wrote:

The word is read aloud on the 2 finger flick, but nothing is read aloud with the 3 finger flick.

On May 2, 2018, at 2:51 PM, Chuck Dean <cadean329@...> wrote:

Hi Bennie,
When you move the cursor, the word or sentence will be red aloud, so you will know exactly where you are.
Try it, works great! :)

Chuck

On May 2, 2018, at 12:24 PM, Benny Barber <rebelben@...> wrote:

Thanks, Chuck. It seems like I would like to hear something. Maybe the first word of the sentence where you moved to. Thanks again.

Benny

On May 2, 2018, at 2:05 PM, Chuck Dean <cadean329@...> wrote:

Hello Bennie,
There is really no need for verbal feedback when using the cursor. If you flick left with two fingers; you are moving the cursor back one word. If you flick right with two fingers; you are moving the cursor one word forward.

If you flick left with three fingers; you are moving the cursor back one sentence. If you slick right with three fingers you are moving the cursor forward one sentence.

Chuck

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

Hello,

I don't remember reading about the 3finger flick right and left to advance the cursor a sentence at a time. Is this a new gesture? If so, can we get some verbal feedback such as; back 1sentence and forward 1sentence? Thanks so much.

Benny

On May 1, 2018, at 9:52 PM, FlickType <@FlickType> wrote:

This took longer than expected. Changes since the previous build:

- This is a major rewrite. Among other differences, the previous build would only change the underlying textfield when you exited the FlickType keyboard, not while you typed. FlickType will now immediately perform all edits in the current field, such as inserting, deleting or changing words. This paves the way for an optional half-screen mode in the near future.
- Reduced memory consumption to address crashing. Unfortunately iOS only allows very little active memory for keyboards compared to regular apps, and aggressively terminates any keyboard that crosses the threshold.
- You now also need to enable "Full Access" in the FlickType settings under the iOS settings app. This is for FlickType to be able to play any sound effects such as taps. The previous method of playing taps was using a private API and was likely to be rejected if submitted to the App Store. Currently, if you don't enable "Full Access" the keyboard will crash. This is a good opportunity to share our very short privacy policy: http://www.flicktype.com/privacy
- If you have some pending taps and flick left to delete, FlickType will now announce "Cleared taps" instead of deleting the previous word.
- You can now move the cursor and navigate the entire current document, not just the current sentence. This should make it more usable for writing longer pieces of text.
- Added a visual keyboard indicator for low-vision folks, in the form of 2 horizontal white bars representing the top and bottom rows.
- Introducing the FlickType "visual announcements", designed to better help low-vision and hearing-impaired folks use the product. All VoiceOver typing announcements for inserting, deleting and changing words will now also be displayed as high-contrast text using the largest possible font size that fits the entire screen above the keyboard area. This replaces the text view that was previously used for debugging.
- The gesture to dismiss the keyboard has been changed to a 3 finger flick down.

We are both really looking forward to hearing what you all think, smile!

Warmly,
Kosta & Ashley











Re: Build 53

Ed Worrell
 

Hello,

It might be nice to hear begening of line with the three finger swipe to the left and end of line for the three finger swipe to the right. This might help with the spacial awareness and where the cursor actually is.

Just a thought.

Ed Worrell

On May 2, 2018, at 2:08 PM, Benny Barber <rebelben@...> wrote:

The word is read aloud on the 2 finger flick, but nothing is read aloud with the 3 finger flick.

On May 2, 2018, at 2:51 PM, Chuck Dean <cadean329@...> wrote:

Hi Bennie,
When you move the cursor, the word or sentence will be red aloud, so you will know exactly where you are.
Try it, works great! :)

Chuck

On May 2, 2018, at 12:24 PM, Benny Barber <rebelben@...> wrote:

Thanks, Chuck. It seems like I would like to hear something. Maybe the first word of the sentence where you moved to. Thanks again.

Benny

On May 2, 2018, at 2:05 PM, Chuck Dean <cadean329@...> wrote:

Hello Bennie,
There is really no need for verbal feedback when using the cursor. If you flick left with two fingers; you are moving the cursor back one word. If you flick right with two fingers; you are moving the cursor one word forward.

If you flick left with three fingers; you are moving the cursor back one sentence. If you slick right with three fingers you are moving the cursor forward one sentence.

Chuck

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

Hello,

I don't remember reading about the 3finger flick right and left to advance the cursor a sentence at a time. Is this a new gesture? If so, can we get some verbal feedback such as; back 1sentence and forward 1sentence? Thanks so much.

Benny

On May 1, 2018, at 9:52 PM, FlickType <@FlickType> wrote:

This took longer than expected. Changes since the previous build:

- This is a major rewrite. Among other differences, the previous build would only change the underlying textfield when you exited the FlickType keyboard, not while you typed. FlickType will now immediately perform all edits in the current field, such as inserting, deleting or changing words. This paves the way for an optional half-screen mode in the near future.
- Reduced memory consumption to address crashing. Unfortunately iOS only allows very little active memory for keyboards compared to regular apps, and aggressively terminates any keyboard that crosses the threshold.
- You now also need to enable "Full Access" in the FlickType settings under the iOS settings app. This is for FlickType to be able to play any sound effects such as taps. The previous method of playing taps was using a private API and was likely to be rejected if submitted to the App Store. Currently, if you don't enable "Full Access" the keyboard will crash. This is a good opportunity to share our very short privacy policy: http://www.flicktype.com/privacy
- If you have some pending taps and flick left to delete, FlickType will now announce "Cleared taps" instead of deleting the previous word.
- You can now move the cursor and navigate the entire current document, not just the current sentence. This should make it more usable for writing longer pieces of text.
- Added a visual keyboard indicator for low-vision folks, in the form of 2 horizontal white bars representing the top and bottom rows.
- Introducing the FlickType "visual announcements", designed to better help low-vision and hearing-impaired folks use the product. All VoiceOver typing announcements for inserting, deleting and changing words will now also be displayed as high-contrast text using the largest possible font size that fits the entire screen above the keyboard area. This replaces the text view that was previously used for debugging.
- The gesture to dismiss the keyboard has been changed to a 3 finger flick down.

We are both really looking forward to hearing what you all think, smile!

Warmly,
Kosta & Ashley










Re: Build 54

Paul Sutton
 

Hey, sorry if this has already been brought up but I haven't had chance to check other peoples feedback yet.
When using the system wide keyboard, I have noticed that sometimes when I am flicking through the list of suggestions the word that is being spoken stutters. Also in the stand alone app is becoming a little sluggish.
Keep up the good work,
Paul.


Re: Build 53

Benny Barber
 

The word is read aloud on the 2 finger flick, but nothing is read aloud with the 3 finger flick.

On May 2, 2018, at 2:51 PM, Chuck Dean <cadean329@...> wrote:

Hi Bennie,
When you move the cursor, the word or sentence will be red aloud, so you will know exactly where you are.
Try it, works great! :)

Chuck

On May 2, 2018, at 12:24 PM, Benny Barber <rebelben@...> wrote:

Thanks, Chuck. It seems like I would like to hear something. Maybe the first word of the sentence where you moved to. Thanks again.

Benny

On May 2, 2018, at 2:05 PM, Chuck Dean <cadean329@...> wrote:

Hello Bennie,
There is really no need for verbal feedback when using the cursor. If you flick left with two fingers; you are moving the cursor back one word. If you flick right with two fingers; you are moving the cursor one word forward.

If you flick left with three fingers; you are moving the cursor back one sentence. If you slick right with three fingers you are moving the cursor forward one sentence.

Chuck

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

Hello,

I don't remember reading about the 3finger flick right and left to advance the cursor a sentence at a time. Is this a new gesture? If so, can we get some verbal feedback such as; back 1sentence and forward 1sentence? Thanks so much.

Benny

On May 1, 2018, at 9:52 PM, FlickType <@FlickType> wrote:

This took longer than expected. Changes since the previous build:

- This is a major rewrite. Among other differences, the previous build would only change the underlying textfield when you exited the FlickType keyboard, not while you typed. FlickType will now immediately perform all edits in the current field, such as inserting, deleting or changing words. This paves the way for an optional half-screen mode in the near future.
- Reduced memory consumption to address crashing. Unfortunately iOS only allows very little active memory for keyboards compared to regular apps, and aggressively terminates any keyboard that crosses the threshold.
- You now also need to enable "Full Access" in the FlickType settings under the iOS settings app. This is for FlickType to be able to play any sound effects such as taps. The previous method of playing taps was using a private API and was likely to be rejected if submitted to the App Store. Currently, if you don't enable "Full Access" the keyboard will crash. This is a good opportunity to share our very short privacy policy: http://www.flicktype.com/privacy
- If you have some pending taps and flick left to delete, FlickType will now announce "Cleared taps" instead of deleting the previous word.
- You can now move the cursor and navigate the entire current document, not just the current sentence. This should make it more usable for writing longer pieces of text.
- Added a visual keyboard indicator for low-vision folks, in the form of 2 horizontal white bars representing the top and bottom rows.
- Introducing the FlickType "visual announcements", designed to better help low-vision and hearing-impaired folks use the product. All VoiceOver typing announcements for inserting, deleting and changing words will now also be displayed as high-contrast text using the largest possible font size that fits the entire screen above the keyboard area. This replaces the text view that was previously used for debugging.
- The gesture to dismiss the keyboard has been changed to a 3 finger flick down.

We are both really looking forward to hearing what you all think, smile!

Warmly,
Kosta & Ashley









Build 54

Chuck Dean
 

Build 54
Hi Kosta,
This is not a priority request; but could the "delete taps " voice feedback be included in the app version of FlickType? I find it very helpful.

Also while your under the hood, a way to move the cursor, like in the custom keyboard would be great.
I know your concentration is on the custom keyboard, but I know myself, and I'll probably use the stand alone app... You can't teach an old dog new tricks. :)


Chuck


Re: Build 53

Chuck Dean
 

Hi Bennie,
When you move the cursor, the word or sentence will be red aloud, so you will know exactly where you are.
Try it, works great! :)

Chuck

On May 2, 2018, at 12:24 PM, Benny Barber <rebelben@...> wrote:

Thanks, Chuck. It seems like I would like to hear something. Maybe the first word of the sentence where you moved to. Thanks again.

Benny

On May 2, 2018, at 2:05 PM, Chuck Dean <cadean329@...> wrote:

Hello Bennie,
There is really no need for verbal feedback when using the cursor. If you flick left with two fingers; you are moving the cursor back one word. If you flick right with two fingers; you are moving the cursor one word forward.

If you flick left with three fingers; you are moving the cursor back one sentence. If you slick right with three fingers you are moving the cursor forward one sentence.

Chuck

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

Hello,

I don't remember reading about the 3finger flick right and left to advance the cursor a sentence at a time. Is this a new gesture? If so, can we get some verbal feedback such as; back 1sentence and forward 1sentence? Thanks so much.

Benny

On May 1, 2018, at 9:52 PM, FlickType <@FlickType> wrote:

This took longer than expected. Changes since the previous build:

- This is a major rewrite. Among other differences, the previous build would only change the underlying textfield when you exited the FlickType keyboard, not while you typed. FlickType will now immediately perform all edits in the current field, such as inserting, deleting or changing words. This paves the way for an optional half-screen mode in the near future.
- Reduced memory consumption to address crashing. Unfortunately iOS only allows very little active memory for keyboards compared to regular apps, and aggressively terminates any keyboard that crosses the threshold.
- You now also need to enable "Full Access" in the FlickType settings under the iOS settings app. This is for FlickType to be able to play any sound effects such as taps. The previous method of playing taps was using a private API and was likely to be rejected if submitted to the App Store. Currently, if you don't enable "Full Access" the keyboard will crash. This is a good opportunity to share our very short privacy policy: http://www.flicktype.com/privacy
- If you have some pending taps and flick left to delete, FlickType will now announce "Cleared taps" instead of deleting the previous word.
- You can now move the cursor and navigate the entire current document, not just the current sentence. This should make it more usable for writing longer pieces of text.
- Added a visual keyboard indicator for low-vision folks, in the form of 2 horizontal white bars representing the top and bottom rows.
- Introducing the FlickType "visual announcements", designed to better help low-vision and hearing-impaired folks use the product. All VoiceOver typing announcements for inserting, deleting and changing words will now also be displayed as high-contrast text using the largest possible font size that fits the entire screen above the keyboard area. This replaces the text view that was previously used for debugging.
- The gesture to dismiss the keyboard has been changed to a 3 finger flick down.

We are both really looking forward to hearing what you all think, smile!

Warmly,
Kosta & Ashley








Re: Build 53

Benny Barber
 

Thanks, Chuck. It seems like I would like to hear something. Maybe the first word of the sentence where you moved to. Thanks again.

Benny

On May 2, 2018, at 2:05 PM, Chuck Dean <cadean329@...> wrote:

Hello Bennie,
There is really no need for verbal feedback when using the cursor. If you flick left with two fingers; you are moving the cursor back one word. If you flick right with two fingers; you are moving the cursor one word forward.

If you flick left with three fingers; you are moving the cursor back one sentence. If you slick right with three fingers you are moving the cursor forward one sentence.

Chuck

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

Hello,

I don't remember reading about the 3finger flick right and left to advance the cursor a sentence at a time. Is this a new gesture? If so, can we get some verbal feedback such as; back 1sentence and forward 1sentence? Thanks so much.

Benny

On May 1, 2018, at 9:52 PM, FlickType <@FlickType> wrote:

This took longer than expected. Changes since the previous build:

- This is a major rewrite. Among other differences, the previous build would only change the underlying textfield when you exited the FlickType keyboard, not while you typed. FlickType will now immediately perform all edits in the current field, such as inserting, deleting or changing words. This paves the way for an optional half-screen mode in the near future.
- Reduced memory consumption to address crashing. Unfortunately iOS only allows very little active memory for keyboards compared to regular apps, and aggressively terminates any keyboard that crosses the threshold.
- You now also need to enable "Full Access" in the FlickType settings under the iOS settings app. This is for FlickType to be able to play any sound effects such as taps. The previous method of playing taps was using a private API and was likely to be rejected if submitted to the App Store. Currently, if you don't enable "Full Access" the keyboard will crash. This is a good opportunity to share our very short privacy policy: http://www.flicktype.com/privacy
- If you have some pending taps and flick left to delete, FlickType will now announce "Cleared taps" instead of deleting the previous word.
- You can now move the cursor and navigate the entire current document, not just the current sentence. This should make it more usable for writing longer pieces of text.
- Added a visual keyboard indicator for low-vision folks, in the form of 2 horizontal white bars representing the top and bottom rows.
- Introducing the FlickType "visual announcements", designed to better help low-vision and hearing-impaired folks use the product. All VoiceOver typing announcements for inserting, deleting and changing words will now also be displayed as high-contrast text using the largest possible font size that fits the entire screen above the keyboard area. This replaces the text view that was previously used for debugging.
- The gesture to dismiss the keyboard has been changed to a 3 finger flick down.

We are both really looking forward to hearing what you all think, smile!

Warmly,
Kosta & Ashley






Re: Build 53

Chuck Dean
 

Hello Bennie,
There is really no need for verbal feedback when using the cursor. If you flick left with two fingers; you are moving the cursor back one word. If you flick right with two fingers; you are moving the cursor one word forward.

If you flick left with three fingers; you are moving the cursor back one sentence. If you slick right with three fingers you are moving the cursor forward one sentence.

Chuck

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

Hello,

I don't remember reading about the 3finger flick right and left to advance the cursor a sentence at a time. Is this a new gesture? If so, can we get some verbal feedback such as; back 1sentence and forward 1sentence? Thanks so much.

Benny

On May 1, 2018, at 9:52 PM, FlickType <@FlickType> wrote:

This took longer than expected. Changes since the previous build:

- This is a major rewrite. Among other differences, the previous build would only change the underlying textfield when you exited the FlickType keyboard, not while you typed. FlickType will now immediately perform all edits in the current field, such as inserting, deleting or changing words. This paves the way for an optional half-screen mode in the near future.
- Reduced memory consumption to address crashing. Unfortunately iOS only allows very little active memory for keyboards compared to regular apps, and aggressively terminates any keyboard that crosses the threshold.
- You now also need to enable "Full Access" in the FlickType settings under the iOS settings app. This is for FlickType to be able to play any sound effects such as taps. The previous method of playing taps was using a private API and was likely to be rejected if submitted to the App Store. Currently, if you don't enable "Full Access" the keyboard will crash. This is a good opportunity to share our very short privacy policy: http://www.flicktype.com/privacy
- If you have some pending taps and flick left to delete, FlickType will now announce "Cleared taps" instead of deleting the previous word.
- You can now move the cursor and navigate the entire current document, not just the current sentence. This should make it more usable for writing longer pieces of text.
- Added a visual keyboard indicator for low-vision folks, in the form of 2 horizontal white bars representing the top and bottom rows.
- Introducing the FlickType "visual announcements", designed to better help low-vision and hearing-impaired folks use the product. All VoiceOver typing announcements for inserting, deleting and changing words will now also be displayed as high-contrast text using the largest possible font size that fits the entire screen above the keyboard area. This replaces the text view that was previously used for debugging.
- The gesture to dismiss the keyboard has been changed to a 3 finger flick down.

We are both really looking forward to hearing what you all think, smile!

Warmly,
Kosta & Ashley





Re: Introducing the FlickType custom keyboard

Michael Maslo
 

Hi chin, I agree with you. Why are people wanting single flick gestured. The operating system already allows multi gesture input and voice over used them too. I fund it furious..


On May 1, 2018 at 17:47, <Chuck Dean (mailto:cadean329@...)> wrote:



Personally have no problem with multi -finger gestures, but it seems that many want single finger operation.
I find this a bit curious, considering that using the iPhone with voice over requires many multi -finger gestures; like three finger swipe to scroll; and a three finger quad tap to copy the last spoken text.



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

I am probably the od man out here. One finger gestures seem to be making the interface unusually complicated to use. I really think that there needs to be some multi fingered gestures. I feel that the two finger flick down should be used to do a new line, two finger swipe right/left should be used for the curser control, a three finger swipe right/left should be used to change keyboard functions: such as symbols, numbers, and emojis in the future. Manual typing should be restored. I almost feel that the one fingered hold should be replaced with a two finger hold to switch back to the system keyboard.

Just my thoughts on the gesture topic after thinking about it a little more.


Ed

On May 1, 2018, at 4:05 PM, Chuck Dean <cadean329@...> wrote:

I notice the pass through gesture; the double tap and hold; is not used in FlickType. Perhaps it could be used to go to the iOS keyboard; as most visually impaired people are comfortable using it.




On May 1, 2018, at 2:57 PM, Chuck Dean <cadean329@...> wrote:

Hi Dave,
It might be worth looking into, although I have a friend who is visually impaired and has diminished motor skills, so these gestures may be difficult for her. When I showed her FlickType, the one thing she marveled at more than anything was that it really didn't matter where she hit the screen, it worked every time.
I understand there are many one handed typers out there so single finger gestures are prefered... Even by Kosta. He has expressed a desire to have all one finger gestures.
I think the one finger flick and hold may be another alternative.
Chuck



On May 1, 2018, at 2:26 PM, David Nason <dnason@...> wrote:

Personally I would like one finger gestures for as many functions as possible, particularly for the most commonly used ones, including going to a new line.
How would people feel about a one finger swipe on the left side of the screen having a different function to a swipe on the right side of the screen?

I too quickly noticed the issue when deleting a partially typed word.

We will definitely need the option to type words manually and add words to the dictionary back, but of course I understand that this is a very early version.
I would also like to be able to access emojis from within FlickType. Perhaps even just a a selection of favourite emojis once that top row of keys is returned to the keyboard. Thoughts?
I know you can switch to the emoji keyboard, but this process is a bit rubbish, which is Apple's fault, and I feel having them inside FlickType would be much easier.

The general experience of typing is very good though for a first version.

Dave
On 1 May 2018, at 20:39, Chuck Dean <cadean329@...> wrote:

Yeah, I come up with all kind of ideas to improve the keyboard; only to realize that it isn't such a good idea after all.
I guess that's why I'm not an app developer. :)

On May 1, 2018, at 12:33 PM, Paul Sutton <sutty_p@...> wrote:


stupidly I forgot about accessing the suggestion list. Your right, the single swipe down does indeed need to be left as it is.
On 1 May 2018, at 20:24, Chuck Dean <cadean329@...> wrote:

As I think about your suggestion, I would rather have the one finger flick down to remain as the next suggestion gesture as I use this much more than any other function.
Chuck

On May 1, 2018, at 12:04 PM, Paul Sutton <sutty_p@...> wrote:

Hi everyone, I just thought I would come in with a suggestion. Maybe it would be more simple to have a single finger swipe down for dismissing the keyboard, a 2 finger swipe down to insert a new line and a 3 finger swipe down for switching the keyboard. Personally I would find that simpler.
Just my thoughts anyway.
Paul.













Re: Build 53

Michael Maslo
 

list, I have been testing the latest build and I have the following observations. I am using the iPhone ten and the only thing I have noticed so far is the fact that when I flick down I sometimes get where the suggestions repeat themselves once. It is not a regular occurring but it happens on occasions. The other thing is the dictionary does not seem to be complete. I hate the vibration when I type so I will be turning that off. Also I am unsure if this has been implemented yet but I an unable to type manually still. Outside of that I love this keyboard. Keep up the awesome job.


On May 2, 2018 at 11:56, <Sharon Kim (mailto:sharon.mi.kim22@...)> wrote:



hello all,
I hope this email finds you well.
So I have the latest update of flicktype, and here are my observations.
Now I'm aware, that some of these things are things that you guys are
already aware of, but I'll just put it down here, in case one slips
through the cracks.
1. It appears to be rather laggy.
I don't know why, but whenever I use the system wide keyboard, it just
seems slow, and clunky to me. It almost feels like I'd save more time
by switching back and forth between apps.
2. When you change to the flicktype keyboard, there is a bit of time
where nothing happens. No tap sounds, voice over doesn't talk, it's
almost like the phone freezes, but this only happens when I change to
another keyboard. What I have to do, is to make random gestures,
swiping, just random things, tapping, till it starts talking to me.
Usually it will within like five seconds or so, but in that time,
there is no feedback, no nothing. it's just like frozen in time or
something. lol.
3. Now this is a big one for me. We are not able to use the words we
have put in the custom dictionary.
The reason why this is a big one is because, with the dictionary you
guys are using, and I know there is an intended change, but with the
dictionary that's being used now, there are actual words missing from
it. I gave you guys several examples in a couple tweets a week or so
back. Because of this, I have added those words to my custom
dictionary, which I cannot use if I use the system wide keyboard.
All in all, I think this is a great start, but I think there has to
definitely be an increase in response time. It's not just about the
tap sounds coming in slower, it's just everything. The entire keyboard
feels to me, a bit clunky and laggy.
So for now, I'm switching back and forth between apps, but I'm sure
given time this will improve.
That's all from me.
I hope you all havea lovely day.

On 5/2/18, Chanelle Allen <chanellem.allen@...> wrote:
Hello Maxter and List,
On my phone, flicking right after a word also does not announce a full stop.
For me though, this behavior only occurred in the Mail app but not in Notes
or Messages.
Chanelle

On May 2, 2018, at 00:20, George Cham <George.cham@...> wrote:

Ok, is there a way of giving the user the option of decreasing the text
size it they wish?

Kind Regards,

George Cham

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

Get Outlook<https://aka.ms/qtex0l> for iOS
________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of
Macster <@Macster>
Sent: Wednesday, May 2, 2018 3:09:18 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 53

Good morning guys.

Great effort on another build with multiple improvements. Here are my very
early thoughts.

When typing, each word I type is announced with a pitch change, the pitch
going up as I would expect it to do if I was deleting. The only time
normal pitch is heard is when flicking right for a full stop then the last
word of the sentence is as expected....

Unfortunately flicking right for a full stop doesn't announce full stop.
It is inserted, as I noticed if I flick down then the comma, colon etc are
announced and if I flick back up then full stop is heard, just not on the
initial flick right.

The three fingers swipe... I really like the flick left and right to
navigate sentences. This could become a very powerful tool, alongside the
two fingers left and right to navigate words. And the 3 finger flick down
works as expected to dismiss the keyboard. My only concern here is screen
space if a half screen keyboard is implemented in future. As I'm currently
using an SE, if I put 3 fingers on the screen vertically they take up very
nearly half the screen. This should be ok for left and right gestures but
leaves less margin for error for the 3 finger swipe down, and more so if
someone uses landscape mode as default. (I use portrait) Sorry, I know
I've used my flux capacitor here and identified a potential problem that
doesn't exist yet or may never exist but just a thought that crossed my
mind.

I like being able to change the keyboard sound as I've been using the
marimba effect as standard for a while now.

Apologies I can’t comment on the visual changes.



I know it's early days, but I'm very excited at the potential of this
extension and I'm looking forward to its journey through development!

Macky










Re: Build 53

Benny Barber
 

Hello,

I don't remember reading about the 3finger flick right and left to advance the cursor a sentence at a time. Is this a new gesture? If so, can we get some verbal feedback such as; back 1sentence and forward 1sentence? Thanks so much.

Benny

On May 1, 2018, at 9:52 PM, FlickType <@FlickType> wrote:

This took longer than expected. Changes since the previous build:

- This is a major rewrite. Among other differences, the previous build would only change the underlying textfield when you exited the FlickType keyboard, not while you typed. FlickType will now immediately perform all edits in the current field, such as inserting, deleting or changing words. This paves the way for an optional half-screen mode in the near future.
- Reduced memory consumption to address crashing. Unfortunately iOS only allows very little active memory for keyboards compared to regular apps, and aggressively terminates any keyboard that crosses the threshold.
- You now also need to enable "Full Access" in the FlickType settings under the iOS settings app. This is for FlickType to be able to play any sound effects such as taps. The previous method of playing taps was using a private API and was likely to be rejected if submitted to the App Store. Currently, if you don't enable "Full Access" the keyboard will crash. This is a good opportunity to share our very short privacy policy: http://www.flicktype.com/privacy
- If you have some pending taps and flick left to delete, FlickType will now announce "Cleared taps" instead of deleting the previous word.
- You can now move the cursor and navigate the entire current document, not just the current sentence. This should make it more usable for writing longer pieces of text.
- Added a visual keyboard indicator for low-vision folks, in the form of 2 horizontal white bars representing the top and bottom rows.
- Introducing the FlickType "visual announcements", designed to better help low-vision and hearing-impaired folks use the product. All VoiceOver typing announcements for inserting, deleting and changing words will now also be displayed as high-contrast text using the largest possible font size that fits the entire screen above the keyboard area. This replaces the text view that was previously used for debugging.
- The gesture to dismiss the keyboard has been changed to a 3 finger flick down.

We are both really looking forward to hearing what you all think, smile!

Warmly,
Kosta & Ashley



Build 54

Chuck Dean
 

Build 54
BTW, I like the white bars indicating the key rows, but they are a little too bright. Perhaps, in the future, we could have the option to change color of the bars. I


Chuck


Build 54

Chuck Dean
 

Build 54
Hello,
I tried the two and three finger flick right and left to move the cursor. This feature works great! I can review my typing and edit my mistakes; which are many... :)
Good job!


Chuck


Re: Build 53

Sharon Kim
 

hello all,
I hope this email finds you well.
So I have the latest update of flicktype, and here are my observations.
Now I'm aware, that some of these things are things that you guys are
already aware of, but I'll just put it down here, in case one slips
through the cracks.
1. It appears to be rather laggy.
I don't know why, but whenever I use the system wide keyboard, it just
seems slow, and clunky to me. It almost feels like I'd save more time
by switching back and forth between apps.
2. When you change to the flicktype keyboard, there is a bit of time
where nothing happens. No tap sounds, voice over doesn't talk, it's
almost like the phone freezes, but this only happens when I change to
another keyboard. What I have to do, is to make random gestures,
swiping, just random things, tapping, till it starts talking to me.
Usually it will within like five seconds or so, but in that time,
there is no feedback, no nothing. it's just like frozen in time or
something. lol.
3. Now this is a big one for me. We are not able to use the words we
have put in the custom dictionary.
The reason why this is a big one is because, with the dictionary you
guys are using, and I know there is an intended change, but with the
dictionary that's being used now, there are actual words missing from
it. I gave you guys several examples in a couple tweets a week or so
back. Because of this, I have added those words to my custom
dictionary, which I cannot use if I use the system wide keyboard.
All in all, I think this is a great start, but I think there has to
definitely be an increase in response time. It's not just about the
tap sounds coming in slower, it's just everything. The entire keyboard
feels to me, a bit clunky and laggy.
So for now, I'm switching back and forth between apps, but I'm sure
given time this will improve.
That's all from me.
I hope you all havea lovely day.

On 5/2/18, Chanelle Allen <chanellem.allen@...> wrote:
Hello Maxter and List,
On my phone, flicking right after a word also does not announce a full stop.
For me though, this behavior only occurred in the Mail app but not in Notes
or Messages.
Chanelle

On May 2, 2018, at 00:20, George Cham <George.cham@...> wrote:

Ok, is there a way of giving the user the option of decreasing the text
size it they wish?

Kind Regards,

George Cham

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

Get Outlook<https://aka.ms/qtex0l> for iOS
________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of
Macster <@Macster>
Sent: Wednesday, May 2, 2018 3:09:18 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 53

Good morning guys.

Great effort on another build with multiple improvements. Here are my very
early thoughts.

When typing, each word I type is announced with a pitch change, the pitch
going up as I would expect it to do if I was deleting. The only time
normal pitch is heard is when flicking right for a full stop then the last
word of the sentence is as expected....

Unfortunately flicking right for a full stop doesn't announce full stop.
It is inserted, as I noticed if I flick down then the comma, colon etc are
announced and if I flick back up then full stop is heard, just not on the
initial flick right.

The three fingers swipe... I really like the flick left and right to
navigate sentences. This could become a very powerful tool, alongside the
two fingers left and right to navigate words. And the 3 finger flick down
works as expected to dismiss the keyboard. My only concern here is screen
space if a half screen keyboard is implemented in future. As I'm currently
using an SE, if I put 3 fingers on the screen vertically they take up very
nearly half the screen. This should be ok for left and right gestures but
leaves less margin for error for the 3 finger swipe down, and more so if
someone uses landscape mode as default. (I use portrait) Sorry, I know
I've used my flux capacitor here and identified a potential problem that
doesn't exist yet or may never exist but just a thought that crossed my
mind.

I like being able to change the keyboard sound as I've been using the
marimba effect as standard for a while now.

Apologies I can’t comment on the visual changes.



I know it's early days, but I'm very excited at the potential of this
extension and I'm looking forward to its journey through development!

Macky