Re: As I play with the menu gesture, I feel that the single finger flick up will not work for me.
Hi Chuck, Chanelle,
We appreciate the feedback. Due to a bug with iOS we were not able to implement the single flick up gesture the way we wanted on non-iPhone X devices, therefore we're exploring other options. Though the two-finger flick gesture is reliable, we want to enable one-handed use across the entire app which is why we're exploring other options. If we do not find a reliable one-handed solution we will stick with the 2-finger flick up gesture.
Thanks!
Ashley
We appreciate the feedback. Due to a bug with iOS we were not able to implement the single flick up gesture the way we wanted on non-iPhone X devices, therefore we're exploring other options. Though the two-finger flick gesture is reliable, we want to enable one-handed use across the entire app which is why we're exploring other options. If we do not find a reliable one-handed solution we will stick with the 2-finger flick up gesture.
Thanks!
Ashley
Re: As I play with the menu gesture, I feel that the single finger flick up will not work for me.
Chanelle Allen
Hello,
I like the single flick up from bottom gesture to bring up the menu, but I also agree that the two finger flick up should remain in place. I don't have an iPhone 10, but I thought that gestures to bring up the home screen and app switcher require a tap, hold and slide movement whereas bringing up the FlickType menu is a quick flick motion above where the physical home button would be. Am I wrong, and if so, could someone explain? If I am correct, it seems that FlickType should be able to distinguish between these seemingly different gestures. I also like the idea of 3-D touch being used to bring up export options.
Chanelle
toggle quoted message
Show quoted text
I like the single flick up from bottom gesture to bring up the menu, but I also agree that the two finger flick up should remain in place. I don't have an iPhone 10, but I thought that gestures to bring up the home screen and app switcher require a tap, hold and slide movement whereas bringing up the FlickType menu is a quick flick motion above where the physical home button would be. Am I wrong, and if so, could someone explain? If I am correct, it seems that FlickType should be able to distinguish between these seemingly different gestures. I also like the idea of 3-D touch being used to bring up export options.
Chanelle
On Apr 18, 2018, at 10:34, Chuck Dean <cadean329@...> wrote:
As I play with the menu gesture, I feel that the single finger flick up will not work for me. The two finger swipe up works 100% of the time. There was some mention of eliminating this gesture in the future. Unless a better gesture is found for opening the menu, I suggest it stays.
Chuck
I notice when I delete partial words, mistakes for example, FlickType does not announce the delete, ...
Chuck Dean
I notice when I delete partial words, mistakes for example, FlickType does not announce the delete, so I have a tendency to flick left again which deletes the previous word.
Also, I turned on audio ducking to test the tap stereo feature and noticed a lag from when I type and the announcement.
I am using an iPhone 8 running iOS 11.3.
Chuck
Also, I turned on audio ducking to test the tap stereo feature and noticed a lag from when I type and the announcement.
I am using an iPhone 8 running iOS 11.3.
Chuck
As I play with the menu gesture, I feel that the single finger flick up will not work for me.
Chuck Dean
As I play with the menu gesture, I feel that the single finger flick up will not work for me. The two finger swipe up works 100% of the time. There was some mention of eliminating this gesture in the future. Unless a better gesture is found for opening the menu, I suggest it stays.
Chuck
Chuck
Hello, I am also having the problem with the single flick up from the bottom to invoke the menu.
Chuck Dean
Hello, I am also having the problem with the single flick up from the bottom to invoke the menu. In both landscape and portrait modes, when I flick up, it opens the control center.
I didn't have this problem initially, but it is 100% of the time now.
Chuck
I didn't have this problem initially, but it is 100% of the time now.
Chuck
Re: Build 39
Justin Thornton
Just a quick note.
The new menu gesture swiping up from the bottom of the screen is affecting my ability to go home on the iPhone X with voiceover on.
I can no longer do this.
toggle quoted message
Show quoted text
The new menu gesture swiping up from the bottom of the screen is affecting my ability to go home on the iPhone X with voiceover on.
I can no longer do this.
On Apr 18, 2018, at 3:34 AM, FlickType <hello@...> wrote:
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
In this release:
- Fixed incorrect word announcements when punctuation announcement was off. Words with an apostrophe would be split into two parts, as if the apostrophe became a space. For example, "don't" would be pronounced as "don tee".
- Apostrophes and hyphens will no longer be included in word announcements, unless there is potential for confusion between candidates. For example, the contraction for "it is" will always include the apostrophe in the announcement, to distinguish from the possessive "its". But words like "isn't", "doesn't" and "don't" will be announced normally, without the apostrophe being spoken.
- Apostrophes and hyphens will no longer be included in word deletion announcements.
- Fixed incorrect announcement when deleting a new line.
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
Kosta & Ashley
Build 39
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
In this release:
- Fixed incorrect word announcements when punctuation announcement was off. Words with an apostrophe would be split into two parts, as if the apostrophe became a space. For example, "don't" would be pronounced as "don tee".
- Apostrophes and hyphens will no longer be included in word announcements, unless there is potential for confusion between candidates. For example, the contraction for "it is" will always include the apostrophe in the announcement, to distinguish from the possessive "its". But words like "isn't", "doesn't" and "don't" will be announced normally, without the apostrophe being spoken.
- Apostrophes and hyphens will no longer be included in word deletion announcements.
- Fixed incorrect announcement when deleting a new line.
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
Kosta & Ashley
In this release:
- Fixed incorrect word announcements when punctuation announcement was off. Words with an apostrophe would be split into two parts, as if the apostrophe became a space. For example, "don't" would be pronounced as "don tee".
- Apostrophes and hyphens will no longer be included in word announcements, unless there is potential for confusion between candidates. For example, the contraction for "it is" will always include the apostrophe in the announcement, to distinguish from the possessive "its". But words like "isn't", "doesn't" and "don't" will be announced normally, without the apostrophe being spoken.
- Apostrophes and hyphens will no longer be included in word deletion announcements.
- Fixed incorrect announcement when deleting a new line.
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
Kosta & Ashley
Re: Build 37 out to alpha
Chanelle Allen
Hello,
I do not have an option in TestFlight to update to FlickType 0.1.37. I am currently using FlickType 0.1.35. Has anyone else not received the update? Perhaps I was invited to the alpha group without being invited to test alpha builds of FlickType.
While typing this message in FlickType and looking for numbers, I find that I am accidentally pressing an area where the menu is activated. I will need to look for punctuation further down on the keyboard since I invoke the menu when attempting to type a period. I am thinking of future FlickType users and wondering if activating the menu by tapping above the keyboard is a useful feature.
I am looking forward to testing more versions of FlickType.
Chanelle
toggle quoted message
Show quoted text
I do not have an option in TestFlight to update to FlickType 0.1.37. I am currently using FlickType 0.1.35. Has anyone else not received the update? Perhaps I was invited to the alpha group without being invited to test alpha builds of FlickType.
While typing this message in FlickType and looking for numbers, I find that I am accidentally pressing an area where the menu is activated. I will need to look for punctuation further down on the keyboard since I invoke the menu when attempting to type a period. I am thinking of future FlickType users and wondering if activating the menu by tapping above the keyboard is a useful feature.
I am looking forward to testing more versions of FlickType.
Chanelle
On Apr 17, 2018, at 14:22, FlickType <hello@...> wrote:
Thank you all for the feedback. A new build #38 is now out to alpha, which only includes a couple of small internal changes, hence I won't start a new topic. We are planning to release this to the beta group later today, while we still work on fixes and improvements for the next version. The web help page now has updated instructions, which should be very similar to what was in the app before.
I will respond to some of the additional feedback points in a separate message shortly.
Warmly,
Kosta
Re: Build 37 out to alpha
Following up on some specific points folks have brought up. I would also like to take the opportunity and remind everyone that we would like to strike a good balance between polishing this standalone app and working on the new system-wide version of the keyboard. Many, perhaps most, of the current issues will not even exist at all as we are developing the system-wide version entirely from scratch.
We will consider re-assigning the 2 finger flick up and down gestures if the swipe of from the bottom edge of the screen is well-received. Thank you for the suggestions. We will likely add a setting for iPhone X users to disable the new gesture if they wish. We'd also love to hear more details about the conflict with the control center gesture.
The echo when typing some symbols or numbers is a known issue and should be fixed in a future release.
Manual entry of words that include symbols such as apostrophe, and adding those words to the dictionary is known to be broken, and quite tricky to fix with the current code.
Thank you all for testing and for your continued support.
- Kosta
We will consider re-assigning the 2 finger flick up and down gestures if the swipe of from the bottom edge of the screen is well-received. Thank you for the suggestions. We will likely add a setting for iPhone X users to disable the new gesture if they wish. We'd also love to hear more details about the conflict with the control center gesture.
The echo when typing some symbols or numbers is a known issue and should be fixed in a future release.
Manual entry of words that include symbols such as apostrophe, and adding those words to the dictionary is known to be broken, and quite tricky to fix with the current code.
Thank you all for testing and for your continued support.
- Kosta
Re: Build 37 out to alpha
Nozi <noziphokhanda@...>
Costa and Ashley, thank you so much for the work that you’re doing on the app. I’ve just tryed the new gesture for bringing up the menu. It seems to be conflicting with a gesture that brings up the control centre on the iPhone 6. I’m using iOS 11.3 anyone else experiencing this?
Re: Build 37 out to alpha
Thank you all for the feedback. A new build #38 is now out to alpha, which only includes a couple of small internal changes, hence I won't start a new topic. We are planning to release this to the beta group later today, while we still work on fixes and improvements for the next version. The web help page now has updated instructions, which should be very similar to what was in the app before.
I will respond to some of the additional feedback points in a separate message shortly.
Warmly,
Kosta
I will respond to some of the additional feedback points in a separate message shortly.
Warmly,
Kosta
Re: Build 37 out to alpha
Ed Worrell <ed.worrell@...>
Hello Kasta,
I am really enjoying the new gesture for invoking the menu options. I actually love the new command as I am no longer accidentally bringing up the app switcher. I personally don’t mind that I have to take one more step to exit back to the home screen. This is a trade off I am willing to make. I am wondering if the two finger swipe up can be used just the default VoiceOver command of read from top. Just a thought.
Keep up the great work!
Ed
toggle quoted message
Show quoted text
I am really enjoying the new gesture for invoking the menu options. I actually love the new command as I am no longer accidentally bringing up the app switcher. I personally don’t mind that I have to take one more step to exit back to the home screen. This is a trade off I am willing to make. I am wondering if the two finger swipe up can be used just the default VoiceOver command of read from top. Just a thought.
Keep up the great work!
Ed
On Apr 17, 2018, at 2:28 AM, FlickType <hello@...> wrote:
Thank you Andrew, this is good feedback. Did you feel like you could previously distinguish between the home and app switcher gestures before ending your swipe up? Or did that not matter?
- Kosta
Re: Build 37 out to alpha
Here are my comments on build 0.1-37:
1. I very much like the settings option to turn off the key echo when entering things manually and that it is turned off by default. Would it be possible to include a setting to turn off the echo when entering numbers manually on the numeric keypad that opens with a 2 finger swipe right? I find the echo when entering numbers to be very distracting.
2. Are you still planning on adding the ability to manually enter words containing apostrophes or hyphens so they can be added to the user dictionary? Now, when entering such words, only what is typed after the apostrophe or hyphen is spoken. I'm not sure what would be entered in the dictionary if you single finger swipe up after entering but my request is that the entire word which was typed be entered in the dictionary including what came before the apostrophe/hyphen. Maybe the real request is for FlickType to speak the entire word when swiping right, not just what comes after the special character.
3. I've noticed that the help tutorial section about using FlickType seems to have been re-written with less information. I didn't see any mention in the help of how to capitalize a letter when manually typing and think this used to be there. I thought a single finger swipe up after entering a letter would capitalize it but this must have changed with your implementation of accessing the FlickType menu with a single finger swipe up. A single finger swipe down will also capitalize a manually entered letter so could this be mentioned in the help?
4. When entering a word manually that is the first word in a sentence, FlickType automatically capitalizes the first letter entered but doesn't speak cap when announcing the entry. I thought in one of the previous builds it did announce capitalization when doing this. I think it would be nice for it to announce it if possible because I've had numerous entries where I single finger swiped to change the capitalization only to turn something already capitalized into lower case and then having to undo it.
5. If I get a notification at the top of the screen when entering text with FlickType, touching that notification still behaves as if Voiceover is turned off and the app associated with the notification launches without speaking anything or waiting for a double tap. And, since I have copy and clear on exit turned on, anything I have typed is lost.
I'm using an iPhone 7 running iOS 11.3.
Thanks for all your hard work.
Alan Lemly
toggle quoted message
Show quoted text
1. I very much like the settings option to turn off the key echo when entering things manually and that it is turned off by default. Would it be possible to include a setting to turn off the echo when entering numbers manually on the numeric keypad that opens with a 2 finger swipe right? I find the echo when entering numbers to be very distracting.
2. Are you still planning on adding the ability to manually enter words containing apostrophes or hyphens so they can be added to the user dictionary? Now, when entering such words, only what is typed after the apostrophe or hyphen is spoken. I'm not sure what would be entered in the dictionary if you single finger swipe up after entering but my request is that the entire word which was typed be entered in the dictionary including what came before the apostrophe/hyphen. Maybe the real request is for FlickType to speak the entire word when swiping right, not just what comes after the special character.
3. I've noticed that the help tutorial section about using FlickType seems to have been re-written with less information. I didn't see any mention in the help of how to capitalize a letter when manually typing and think this used to be there. I thought a single finger swipe up after entering a letter would capitalize it but this must have changed with your implementation of accessing the FlickType menu with a single finger swipe up. A single finger swipe down will also capitalize a manually entered letter so could this be mentioned in the help?
4. When entering a word manually that is the first word in a sentence, FlickType automatically capitalizes the first letter entered but doesn't speak cap when announcing the entry. I thought in one of the previous builds it did announce capitalization when doing this. I think it would be nice for it to announce it if possible because I've had numerous entries where I single finger swiped to change the capitalization only to turn something already capitalized into lower case and then having to undo it.
5. If I get a notification at the top of the screen when entering text with FlickType, touching that notification still behaves as if Voiceover is turned off and the app associated with the notification launches without speaking anything or waiting for a double tap. And, since I have copy and clear on exit turned on, anything I have typed is lost.
I'm using an iPhone 7 running iOS 11.3.
Thanks for all your hard work.
Alan Lemly
-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Tuesday, April 17, 2018 2:46 AM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 37 out to alpha
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
In this release:
- Swipe up from the bottom edge of the screen to invoke the menu! This replaces the tap & hold gesture above the keyboard. The two finger flick up remains available but may be removed in the future.
- Added "Echo entered characters" setting. Off by default.
- Removed Facebook option from the Share sheet, as it did not work properly.
- Removed Copy option from the Share sheet. Please use the dedicated "Copy & Clear" option directly from the menu.
In the previous release:
- Attempt to fix lost feedback on tap & hold mode. Please let us know if the issue is fixed.
- Slightly reduced delay to enter tap & hold mode.
- Fixed tap & hold characters sometimes not being announced when releasing to enter them.
- Renamed some settings and added descriptions.
- Brought back the previous unduckable sound effect playback mode as a setting, on by default. Please test this & other sound settings as much as possible and report latency, volume or any other sound issues and feedback.
- Merged deletion feedback settings.
- Haptic setting now only appears on supported devices.
- Settings are now dismissible using the scrub / back gesture.
- Removed quick reply link setting as it caused confusion and was rarely used.
- Replaced menu options "Instructions", "We love feedback!", "Tell-a-friend" and "FlickType on the web" with a single "Help & Support" web redirect option.
- Two finger double tap when the menu is open, also known as "magic tap", will now select the "Export text" option.
- Use higher-quality voice (if available) when VoiceOver is disabled
- Updated dictionary
- Fixed crashes
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
Kosta & Ashley
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Tuesday, April 17, 2018 2:46 AM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 37 out to alpha
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
In this release:
- Swipe up from the bottom edge of the screen to invoke the menu! This replaces the tap & hold gesture above the keyboard. The two finger flick up remains available but may be removed in the future.
- Added "Echo entered characters" setting. Off by default.
- Removed Facebook option from the Share sheet, as it did not work properly.
- Removed Copy option from the Share sheet. Please use the dedicated "Copy & Clear" option directly from the menu.
In the previous release:
- Attempt to fix lost feedback on tap & hold mode. Please let us know if the issue is fixed.
- Slightly reduced delay to enter tap & hold mode.
- Fixed tap & hold characters sometimes not being announced when releasing to enter them.
- Renamed some settings and added descriptions.
- Brought back the previous unduckable sound effect playback mode as a setting, on by default. Please test this & other sound settings as much as possible and report latency, volume or any other sound issues and feedback.
- Merged deletion feedback settings.
- Haptic setting now only appears on supported devices.
- Settings are now dismissible using the scrub / back gesture.
- Removed quick reply link setting as it caused confusion and was rarely used.
- Replaced menu options "Instructions", "We love feedback!", "Tell-a-friend" and "FlickType on the web" with a single "Help & Support" web redirect option.
- Two finger double tap when the menu is open, also known as "magic tap", will now select the "Export text" option.
- Use higher-quality voice (if available) when VoiceOver is disabled
- Updated dictionary
- Fixed crashes
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
Kosta & Ashley
Re: Build 37 out to alpha
Dan Lococo
This is the latest version of this app and it seems to work quite well. I enjoy how fast it is and how accurate it is. I don't seem to have to slip up and down, mostly down, to get to the words I'm trying to type. That's a big deal for an app like this. Great job!
Dan LococoBarrier Knocker Downer
414.333.5846
toggle quoted message
Show quoted text
Dan LococoBarrier Knocker Downer
414.333.5846
On Apr 17, 2018, at 2:45 AM, FlickType <hello@...> wrote:
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
In this release:
- Swipe up from the bottom edge of the screen to invoke the menu! This replaces the tap & hold gesture above the keyboard. The two finger flick up remains available but may be removed in the future.
- Added "Echo entered characters" setting. Off by default.
- Removed Facebook option from the Share sheet, as it did not work properly.
- Removed Copy option from the Share sheet. Please use the dedicated "Copy & Clear" option directly from the menu.
In the previous release:
- Attempt to fix lost feedback on tap & hold mode. Please let us know if the issue is fixed.
- Slightly reduced delay to enter tap & hold mode.
- Fixed tap & hold characters sometimes not being announced when releasing to enter them.
- Renamed some settings and added descriptions.
- Brought back the previous unduckable sound effect playback mode as a setting, on by default. Please test this & other sound settings as much as possible and report latency, volume or any other sound issues and feedback.
- Merged deletion feedback settings.
- Haptic setting now only appears on supported devices.
- Settings are now dismissible using the scrub / back gesture.
- Removed quick reply link setting as it caused confusion and was rarely used.
- Replaced menu options "Instructions", "We love feedback!", "Tell-a-friend" and "FlickType on the web" with a single "Help & Support" web redirect option.
- Two finger double tap when the menu is open, also known as "magic tap", will now select the "Export text" option.
- Use higher-quality voice (if available) when VoiceOver is disabled
- Updated dictionary
- Fixed crashes
Please report all your feedback by replying to this topic. Thank you for testing FlickType!
Kosta & Ashley
Re: Build 37 out to alpha
Andrew McKay <awmckay@...>
Morning,
So, maybe I should offer context. I am not a huge user of the app in its current state; I don't find it functional as a stand alone app but I try to provide feedback from the perspective one day soon the keyboard willb e a third party keyboard integrated into other apps.
All that said, I will say that I don't think either option is nominal, but I definitely am opposed to breaking built-in IOS gestures. I don't think that is a good user experience to break such a core gesture from working; at least previously, while you didn't get haptic feedback, it still worked. Furthermore, I must say with the best of intentions, even though I find the typing experience faster than the regular keyboard, both symptoms (new and old) would be core enough problems that I wouldn’t use the keyboard once we reach the point of a third party keyboard. Lastly, I will say that I believe that other apps that use direct touch (the blindfold games come to mind) the haptic feedback bug is present. My hope is developers are reporting this to Apple as a bug.
Thanks,
Andrew
toggle quoted message
Show quoted text
So, maybe I should offer context. I am not a huge user of the app in its current state; I don't find it functional as a stand alone app but I try to provide feedback from the perspective one day soon the keyboard willb e a third party keyboard integrated into other apps.
All that said, I will say that I don't think either option is nominal, but I definitely am opposed to breaking built-in IOS gestures. I don't think that is a good user experience to break such a core gesture from working; at least previously, while you didn't get haptic feedback, it still worked. Furthermore, I must say with the best of intentions, even though I find the typing experience faster than the regular keyboard, both symptoms (new and old) would be core enough problems that I wouldn’t use the keyboard once we reach the point of a third party keyboard. Lastly, I will say that I believe that other apps that use direct touch (the blindfold games come to mind) the haptic feedback bug is present. My hope is developers are reporting this to Apple as a bug.
Thanks,
Andrew
-----Original Message-----
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> On Behalf Of FlickType
Sent: Tuesday, April 17, 2018 4:28 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 37 out to alpha
Thank you Andrew, this is good feedback. Did you feel like you could previously distinguish between the home and app switcher gestures before ending your swipe up? Or did that not matter?
- Kosta
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> On Behalf Of FlickType
Sent: Tuesday, April 17, 2018 4:28 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 37 out to alpha
Thank you Andrew, this is good feedback. Did you feel like you could previously distinguish between the home and app switcher gestures before ending your swipe up? Or did that not matter?
- Kosta