Date   
Re: Great built with some questions...

Ed Worrell
 

I think the emoji short cut only works after you put punctuation in you your text. I'm not sure but this seems to be the only time they show up. So I think the flick up might still work to add a word to the dictionary after manual entry. 
 
 Ed 


On May 27, 2018, at 4:58 PM, Paul Sutton <sutty_p@...> wrote:


 Hi Chuck, 
 You may have a point there. Swiping the same way is definitely more practical and simple. But you would still have to use 2 fingers to swipe as a single finger swipe up is reserved for emoji’s.
Regards, Paul. 


On 27 May 2018, at 21:40, Chuck Dean <cadean329@...> wrote:


Hi Paul, 
 Personally, I like how it is done in the app. A flick up to enter or delete a word. Simple and elegant. 


Chuck

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


Hi all, 
 How would people feel about having the 2 finger swipe up to add a word to the dictionary and a 2 finger swipe down to remove. 
 Just a thought, Paul. 


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

Hi George, 
 
 The 3D touch should capitalize the letter. 


Chuck

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

Ok, I've tried the 3 d touch when in the custom keyboard. I get a letter. Not  sure what  the 3 d touch is suppose to do. Got iPhone8

Kind regards,

George Cham

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

From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Sharon Kim <sharon.mi.kim22@...>
Sent: Monday, May 28, 2018 4:39:57 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Great built with some questions...
 
Hello all,
Okay the vanishing text bit... has never happened to me. Not going to lie.
I love the current build, thank you so very much for putting in the
next button. It is greatly appreciated.
One other thing, the 3d touch thing confuses me. I just sooner not
deal with it, especially if the gestures are going to be there.
I hope anyways, you wont' take out the gestures for the 3d things.
Because... no clue what those are.
anyways, hope this helps.


On 5/27/18, Chuck Dean <cadean329@...> wrote:
>
>  Hi Kosta,
>  My text has only vanished twice, and I do a lot of typing. It is not a deal
> breaker for me.
>
>
> Chuck
>
>> On May 27, 2018, at 11:07 AM, FlickType <hello@...> wrote:
>>
>> Thanks for the comments.
>>
>> On low vision color schemes, as well as the visual appearance of the
>> keyboard, we are planning to improve those soon, but probably not before
>> the custom keyboard launches on the App Store.
>>
>> On 3D Touch not working for you Ed, it could be the iOS beta that's
>> causing the issue, but you can try adjusting the 3D Touch sensitivity from
>> the Accessibility settings. Also the pressure required for this to work in
>> FlickType may be more than you are used to - if so I might need to reduce
>> that threshold a bit. I should also add here that 3D Touch is not a main
>> area of focus right now, and in fact I mostly wanted to make sure that
>> nobody accidentally triggers it when they don't intend to. The actual
>> action may change, for example it could switch between letters and numbers
>> or symbols, and the action might even be configurable in the future.
>>
>> On full emoji support within FlickType: this is definitely planned, but
>> might not make it before launching on the App Store. However, customizing
>> the emoji shortcuts should be there soon, before we launch.
>>
>> On the shortcut options in the main app, are you referring to number or
>> symbol entry? We are currently assessing what we could do with an extra
>> row above the letters, and this could be a number row, or a common symbols
>> row, or something similar to the current app, but we want to make sure the
>> learning curve is not as steep as what's in the main app today. This will
>> probably be something we add post-launch. Also, it would be very helpful
>> if you could tell us the top few use cases that you love about it as it is
>> in the app now. And one final note on this, for email fields we will soon
>> make the @ and period symbols available in the main layout, similar to the
>> iOS keyboard.
>>
>> Phonetics when performing manual input are coming soon.
>>
>> On sometimes getting an adjacent letter entered when lifting your finger
>> to do manual input: this was not the case before, but I had to temporarily
>> disable the code that prevented that as it was making selecting the
>> numbers, next keyboard, dismiss and return keys harder to select. This
>> should be fixed soon.
>>
>> On vanishing text: I am investigating this right now, and is I think the
>> biggest problem we are currently experiencing. One thing I'd love to
>> better assess, is how common this occurrence is. I understand that losing
>> your text even just once can be a very poor experience, but is it
>> currently happening enough that you'd rather use the iOS keyboard
>> instead?
>>
>> Thanks for your continued feedback, much appreciated, smile.
>>
>> - Kosta
>>
>>
>>
>>
>
>
>
>



Re: Vanishing text

Sharon Kim
 

That might be the case too, since I always switch back to the IOS
keyboard, and as I've said before, I've never had the text vanish on
me.

On 5/27/18, Ed Worrell <ed.worrell@...> wrote:
Hey Kosta and chuck,

I can confirm that finding. One of the last emails that I composed I too
dismissed the keyboard and my text vanished. I also had to try again. In the
second attempt I switched to the iOS keyboard. The text then populated the
text field as it should have.

Ed
On May 27, 2018, at 4:04 PM, Chuck Dean <cadean329@...> wrote:


Hello Kosta, while typing this reply, my screen flashed and all that I had
just typed, vanished.

What I think I've discovered, is that the repeating lines only happen when
I dismiss the FlickType keyboard, and not when I go to the iOS keyboard.
This is preliminary, but I haven't had any text repeat as long as I go to
the iOS keyboard.

I'll keep you posted if this turns out to be untrue.



Chuck

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

Hi Kosta,

In the last half hour I have a had my text vanish four times!
I just restarted my phone, thinking that may be the problem. The last
time I was typing in my journal, and as I was typing, the screen flashed,
and all the text I had just typed disappeared.

The text that I had typed previously was still there.

I am dictating this, to make sure that it doesn’t vanished on me.


Chuck




Repeating text solution?

Chuck Dean
 

Hello Kosta,
I have been trying different apps and shutting down and returning to text etc. In the three apps I have been having the repeated text problems... Notes, journal, and mail.

I have not had any repeated text in any app as long as I go to the iOS keyboard, instead of dismissing FlickType. My uneducated conclusion is that the dismiss function is the culprit.

Btw, no text has vanished during the time of these tests. Could the dismiss also be the cause of that problem too?


Chuck

Re: Great built with some questions...

Paul Sutton
 


 Hi Chuck, 
 You may have a point there. Swiping the same way is definitely more practical and simple. But you would still have to use 2 fingers to swipe as a single finger swipe up is reserved for emoji’s.
Regards, Paul. 


On 27 May 2018, at 21:40, Chuck Dean <cadean329@...> wrote:


Hi Paul, 
 Personally, I like how it is done in the app. A flick up to enter or delete a word. Simple and elegant. 


Chuck

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


Hi all, 
 How would people feel about having the 2 finger swipe up to add a word to the dictionary and a 2 finger swipe down to remove. 
 Just a thought, Paul. 


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

Hi George, 
 
 The 3D touch should capitalize the letter. 


Chuck

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

Ok, I've tried the 3 d touch when in the custom keyboard. I get a letter. Not  sure what  the 3 d touch is suppose to do. Got iPhone8

Kind regards,

George Cham

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

From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Sharon Kim <sharon.mi.kim22@...>
Sent: Monday, May 28, 2018 4:39:57 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Great built with some questions...
 
Hello all,
Okay the vanishing text bit... has never happened to me. Not going to lie.
I love the current build, thank you so very much for putting in the
next button. It is greatly appreciated.
One other thing, the 3d touch thing confuses me. I just sooner not
deal with it, especially if the gestures are going to be there.
I hope anyways, you wont' take out the gestures for the 3d things.
Because... no clue what those are.
anyways, hope this helps.


On 5/27/18, Chuck Dean <cadean329@...> wrote:
>
>  Hi Kosta,
>  My text has only vanished twice, and I do a lot of typing. It is not a deal
> breaker for me.
>
>
> Chuck
>
>> On May 27, 2018, at 11:07 AM, FlickType <hello@...> wrote:
>>
>> Thanks for the comments.
>>
>> On low vision color schemes, as well as the visual appearance of the
>> keyboard, we are planning to improve those soon, but probably not before
>> the custom keyboard launches on the App Store.
>>
>> On 3D Touch not working for you Ed, it could be the iOS beta that's
>> causing the issue, but you can try adjusting the 3D Touch sensitivity from
>> the Accessibility settings. Also the pressure required for this to work in
>> FlickType may be more than you are used to - if so I might need to reduce
>> that threshold a bit. I should also add here that 3D Touch is not a main
>> area of focus right now, and in fact I mostly wanted to make sure that
>> nobody accidentally triggers it when they don't intend to. The actual
>> action may change, for example it could switch between letters and numbers
>> or symbols, and the action might even be configurable in the future.
>>
>> On full emoji support within FlickType: this is definitely planned, but
>> might not make it before launching on the App Store. However, customizing
>> the emoji shortcuts should be there soon, before we launch.
>>
>> On the shortcut options in the main app, are you referring to number or
>> symbol entry? We are currently assessing what we could do with an extra
>> row above the letters, and this could be a number row, or a common symbols
>> row, or something similar to the current app, but we want to make sure the
>> learning curve is not as steep as what's in the main app today. This will
>> probably be something we add post-launch. Also, it would be very helpful
>> if you could tell us the top few use cases that you love about it as it is
>> in the app now. And one final note on this, for email fields we will soon
>> make the @ and period symbols available in the main layout, similar to the
>> iOS keyboard.
>>
>> Phonetics when performing manual input are coming soon.
>>
>> On sometimes getting an adjacent letter entered when lifting your finger
>> to do manual input: this was not the case before, but I had to temporarily
>> disable the code that prevented that as it was making selecting the
>> numbers, next keyboard, dismiss and return keys harder to select. This
>> should be fixed soon.
>>
>> On vanishing text: I am investigating this right now, and is I think the
>> biggest problem we are currently experiencing. One thing I'd love to
>> better assess, is how common this occurrence is. I understand that losing
>> your text even just once can be a very poor experience, but is it
>> currently happening enough that you'd rather use the iOS keyboard
>> instead?
>>
>> Thanks for your continued feedback, much appreciated, smile.
>>
>> - Kosta
>>
>>
>>
>>
>
>
>
>



_._,_._,_

Groups.io Links:

You receive all messages sent to this group.
You automatically follow any topics you start or reply to.

View/Reply Online (#1015) | Reply To Group | Reply To Sender | Mute This Topic | New Topic

Change Your Subscription
Group Home
Contact Group Owner
Terms Of Service
Unsubscribe From This Group

_._,_. 

Re: Build 72

Chuck Dean
 

I would also like to see the return of the top row of symbols and shortcuts. I used them when needed, and while I have been working around not having them, they are very convenient.


Chuck

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

Hello all,

I too really prefer this layout from the FlickType main application. I think this would be great to have the same layout option as the app. I would love to have this row of options for use with twitter.

Ed
On May 27, 2018, at 12:57 PM, Benny Barber <rebelben@...> wrote:


Kosta,

As far as the extra row of numbers / symbols, I love the layout of the app. The symbols across the top row of letters and 0 through 12 above the letter p with the ability to flick up and down through the options. Just my opinion. Thanks

Benny

On May 27, 2018, at 1:51 AM, FlickType <@FlickType> wrote:

- Added a "Next Keyboard" button for those having trouble with the flick up & hold gesture. If you don't need the button, you can disable it from the main app settings.
- Also added a setting for a "Dismiss" button similar to the above, but this one is off by default since most people didn't seem to have trouble with the flick down & hold gesture. If you do have trouble performing that gesture, you can enable this button from the settings.
- The shift state now resets after entering a single character, so it behaves more like a shift key rather than a caps lock.
- The shift state now affects words that were not manually typed, meaning that if you switch to uppercase in the middle of a sentence and type a word like "banana", it will be capitalized.
- Words will be capitalized after a new line.
- On devices that support 3D Touch, pressing down harder while exploring the keyboard will toggle the secondary layout, meaning the state of shift if you are in letters, or switch between numbers and symbols if you are in either numbers or symbols.





Re: Build 72

Ed Worrell
 

Hello all,

I too really prefer this layout from the FlickType main application. I think this would be great to have the same layout option as the app. I would love to have this row of options for use with twitter.

Ed

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


Kosta,

As far as the extra row of numbers / symbols, I love the layout of the app. The symbols across the top row of letters and 0 through 12 above the letter p with the ability to flick up and down through the options. Just my opinion. Thanks

Benny

On May 27, 2018, at 1:51 AM, FlickType <@FlickType> wrote:

- Added a "Next Keyboard" button for those having trouble with the flick up & hold gesture. If you don't need the button, you can disable it from the main app settings.
- Also added a setting for a "Dismiss" button similar to the above, but this one is off by default since most people didn't seem to have trouble with the flick down & hold gesture. If you do have trouble performing that gesture, you can enable this button from the settings.
- The shift state now resets after entering a single character, so it behaves more like a shift key rather than a caps lock.
- The shift state now affects words that were not manually typed, meaning that if you switch to uppercase in the middle of a sentence and type a word like "banana", it will be capitalized.
- Words will be capitalized after a new line.
- On devices that support 3D Touch, pressing down harder while exploring the keyboard will toggle the secondary layout, meaning the state of shift if you are in letters, or switch between numbers and symbols if you are in either numbers or symbols.




Re: Vanishing text

Ed Worrell
 

Hey Kosta and chuck,

I can confirm that finding. One of the last emails that I composed I too dismissed the keyboard and my text vanished. I also had to try again. In the second attempt I switched to the iOS keyboard. The text then populated the text field as it should have.

Ed

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


Hello Kosta, while typing this reply, my screen flashed and all that I had just typed, vanished.

What I think I've discovered, is that the repeating lines only happen when I dismiss the FlickType keyboard, and not when I go to the iOS keyboard.
This is preliminary, but I haven't had any text repeat as long as I go to the iOS keyboard.

I'll keep you posted if this turns out to be untrue.



Chuck

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

Hi Kosta,

In the last half hour I have a had my text vanish four times!
I just restarted my phone, thinking that may be the problem. The last time I was typing in my journal, and as I was typing, the screen flashed, and all the text I had just typed disappeared.

The text that I had typed previously was still there.

I am dictating this, to make sure that it doesn’t vanished on me.


Chuck


Re: Vanishing text

Chuck Dean
 

Hello Kosta, while typing this reply, my screen flashed and all that I had just typed, vanished.

What I think I've discovered, is that the repeating lines only happen when I dismiss the FlickType keyboard, and not when I go to the iOS keyboard.
This is preliminary, but I haven't had any text repeat as long as I go to the iOS keyboard.

I'll keep you posted if this turns out to be untrue.



Chuck

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

Hi Kosta,

In the last half hour I have a had my text vanish four times!
I just restarted my phone, thinking that may be the problem. The last time I was typing in my journal, and as I was typing, the screen flashed, and all the text I had just typed disappeared.

The text that I had typed previously was still there.

I am dictating this, to make sure that it doesn’t vanished on me.


Chuck

Vanishing text

Chuck Dean
 

Hi Kosta,

In the last half hour I have a had my text vanish four times!
I just restarted my phone, thinking that may be the problem. The last time I was typing in my journal, and as I was typing, the screen flashed, and all the text I had just typed disappeared.

The text that I had typed previously was still there.

I am dictating this, to make sure that it doesn’t vanished on me.


Chuck

Re: Great built with some questions...

Chuck Dean
 

I can understand that. I have been relying on my ears for so long, I consider my eyes a secondary sense, and not very reliable.


Chuck

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

Hey chuck,

I agree. Not to cause an argument here. I have found in the 10 years I have been working with visually impaired users: if they have a little sight they use it for as much stuff as they can. He is visually impaired, but he has tremendous sight. He actually sees quite well. His vision is due to a birth defect, and it will never degrade. He loves the gesture aspect of the keyboard but he actually gets confused when simply relying on audio feedback for typing. He is very tech savvy and doesn't get frustrated often. At the current build that I've let him use. Its rough for him to say the least.

Ed
On May 27, 2018, at 3:17 PM, Chuck Dean <cadean329@...> wrote:


Hi Ed,
As a low vision user, I find I do very little eye balling while using the FlickType keyboard.
Perhaps, if your co-worker would practice with the current version, the need for low vision schemes may become moot.


Chuck

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

Hey Kosta,

I just decreased the level of pressure for 3D touch from firm to medium. The gesture works as expected now. That's great! I love this feature.😎

My business partner will be happy to hear that low vision options are on the road map.

As always great job.👍

Ed
On May 27, 2018, at 12:07 PM, FlickType <@FlickType> wrote:

Thanks for the comments.

On low vision color schemes, as well as the visual appearance of the keyboard, we are planning to improve those soon, but probably not before the custom keyboard launches on the App Store.

On 3D Touch not working for you Ed, it could be the iOS beta that's causing the issue, but you can try adjusting the 3D Touch sensitivity from the Accessibility settings. Also the pressure required for this to work in FlickType may be more than you are used to - if so I might need to reduce that threshold a bit. I should also add here that 3D Touch is not a main area of focus right now, and in fact I mostly wanted to make sure that nobody accidentally triggers it when they don't intend to. The actual action may change, for example it could switch between letters and numbers or symbols, and the action might even be configurable in the future.

On full emoji support within FlickType: this is definitely planned, but might not make it before launching on the App Store. However, customizing the emoji shortcuts should be there soon, before we launch.

On the shortcut options in the main app, are you referring to number or symbol entry? We are currently assessing what we could do with an extra row above the letters, and this could be a number row, or a common symbols row, or something similar to the current app, but we want to make sure the learning curve is not as steep as what's in the main app today. This will probably be something we add post-launch. Also, it would be very helpful if you could tell us the top few use cases that you love about it as it is in the app now. And one final note on this, for email fields we will soon make the @ and period symbols available in the main layout, similar to the iOS keyboard.

Phonetics when performing manual input are coming soon.

On sometimes getting an adjacent letter entered when lifting your finger to do manual input: this was not the case before, but I had to temporarily disable the code that prevented that as it was making selecting the numbers, next keyboard, dismiss and return keys harder to select. This should be fixed soon.

On vanishing text: I am investigating this right now, and is I think the biggest problem we are currently experiencing. One thing I'd love to better assess, is how common this occurrence is. I understand that losing your text even just once can be a very poor experience, but is it currently happening enough that you'd rather use the iOS keyboard instead?

Thanks for your continued feedback, much appreciated, smile.

- Kosta






Re: Great built with some questions...

Ed Worrell
 

Hey chuck,

I agree. Not to cause an argument here. I have found in the 10 years I have been working with visually impaired users: if they have a little sight they use it for as much stuff as they can. He is visually impaired, but he has tremendous sight. He actually sees quite well. His vision is due to a birth defect, and it will never degrade. He loves the gesture aspect of the keyboard but he actually gets confused when simply relying on audio feedback for typing. He is very tech savvy and doesn't get frustrated often. At the current build that I've let him use. Its rough for him to say the least.

Ed

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


Hi Ed,
As a low vision user, I find I do very little eye balling while using the FlickType keyboard.
Perhaps, if your co-worker would practice with the current version, the need for low vision schemes may become moot.


Chuck

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

Hey Kosta,

I just decreased the level of pressure for 3D touch from firm to medium. The gesture works as expected now. That's great! I love this feature.😎

My business partner will be happy to hear that low vision options are on the road map.

As always great job.👍

Ed
On May 27, 2018, at 12:07 PM, FlickType <@FlickType> wrote:

Thanks for the comments.

On low vision color schemes, as well as the visual appearance of the keyboard, we are planning to improve those soon, but probably not before the custom keyboard launches on the App Store.

On 3D Touch not working for you Ed, it could be the iOS beta that's causing the issue, but you can try adjusting the 3D Touch sensitivity from the Accessibility settings. Also the pressure required for this to work in FlickType may be more than you are used to - if so I might need to reduce that threshold a bit. I should also add here that 3D Touch is not a main area of focus right now, and in fact I mostly wanted to make sure that nobody accidentally triggers it when they don't intend to. The actual action may change, for example it could switch between letters and numbers or symbols, and the action might even be configurable in the future.

On full emoji support within FlickType: this is definitely planned, but might not make it before launching on the App Store. However, customizing the emoji shortcuts should be there soon, before we launch.

On the shortcut options in the main app, are you referring to number or symbol entry? We are currently assessing what we could do with an extra row above the letters, and this could be a number row, or a common symbols row, or something similar to the current app, but we want to make sure the learning curve is not as steep as what's in the main app today. This will probably be something we add post-launch. Also, it would be very helpful if you could tell us the top few use cases that you love about it as it is in the app now. And one final note on this, for email fields we will soon make the @ and period symbols available in the main layout, similar to the iOS keyboard.

Phonetics when performing manual input are coming soon.

On sometimes getting an adjacent letter entered when lifting your finger to do manual input: this was not the case before, but I had to temporarily disable the code that prevented that as it was making selecting the numbers, next keyboard, dismiss and return keys harder to select. This should be fixed soon.

On vanishing text: I am investigating this right now, and is I think the biggest problem we are currently experiencing. One thing I'd love to better assess, is how common this occurrence is. I understand that losing your text even just once can be a very poor experience, but is it currently happening enough that you'd rather use the iOS keyboard instead?

Thanks for your continued feedback, much appreciated, smile.

- Kosta





Re: Great built with some questions...

Chuck Dean
 

Hi Kosta,
While typing that last reply, my text vanished. I had typed my reply, and dismissed the keyboard to send, but realized I wanted to edit my text. I did a double tap to invoke the custom keyboard, and then did a two finger swipe left to find the cursor. It said beginning of document. So I did a two finger swipe right to move the cursor, it said, end of document. I went to the iOS keyboard, and all that I typed was gone.


Chuck

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

Hey Kosta,

I just decreased the level of pressure for 3D touch from firm to medium. The gesture works as expected now. That's great! I love this feature.😎

My business partner will be happy to hear that low vision options are on the road map.

As always great job.👍

Ed
On May 27, 2018, at 12:07 PM, FlickType <@FlickType> wrote:

Thanks for the comments.

On low vision color schemes, as well as the visual appearance of the keyboard, we are planning to improve those soon, but probably not before the custom keyboard launches on the App Store.

On 3D Touch not working for you Ed, it could be the iOS beta that's causing the issue, but you can try adjusting the 3D Touch sensitivity from the Accessibility settings. Also the pressure required for this to work in FlickType may be more than you are used to - if so I might need to reduce that threshold a bit. I should also add here that 3D Touch is not a main area of focus right now, and in fact I mostly wanted to make sure that nobody accidentally triggers it when they don't intend to. The actual action may change, for example it could switch between letters and numbers or symbols, and the action might even be configurable in the future.

On full emoji support within FlickType: this is definitely planned, but might not make it before launching on the App Store. However, customizing the emoji shortcuts should be there soon, before we launch.

On the shortcut options in the main app, are you referring to number or symbol entry? We are currently assessing what we could do with an extra row above the letters, and this could be a number row, or a common symbols row, or something similar to the current app, but we want to make sure the learning curve is not as steep as what's in the main app today. This will probably be something we add post-launch. Also, it would be very helpful if you could tell us the top few use cases that you love about it as it is in the app now. And one final note on this, for email fields we will soon make the @ and period symbols available in the main layout, similar to the iOS keyboard.

Phonetics when performing manual input are coming soon.

On sometimes getting an adjacent letter entered when lifting your finger to do manual input: this was not the case before, but I had to temporarily disable the code that prevented that as it was making selecting the numbers, next keyboard, dismiss and return keys harder to select. This should be fixed soon.

On vanishing text: I am investigating this right now, and is I think the biggest problem we are currently experiencing. One thing I'd love to better assess, is how common this occurrence is. I understand that losing your text even just once can be a very poor experience, but is it currently happening enough that you'd rather use the iOS keyboard instead?

Thanks for your continued feedback, much appreciated, smile.

- Kosta




Re: Great built with some questions...

Chuck Dean
 

Hi Ed,
As a low vision user, I find I do very little eye balling while using the FlickType keyboard.
Perhaps, if your co-worker would practice with the current version, the need for low vision schemes may become moot.


Chuck

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

Hey Kosta,

I just decreased the level of pressure for 3D touch from firm to medium. The gesture works as expected now. That's great! I love this feature.😎

My business partner will be happy to hear that low vision options are on the road map.

As always great job.👍

Ed
On May 27, 2018, at 12:07 PM, FlickType <@FlickType> wrote:

Thanks for the comments.

On low vision color schemes, as well as the visual appearance of the keyboard, we are planning to improve those soon, but probably not before the custom keyboard launches on the App Store.

On 3D Touch not working for you Ed, it could be the iOS beta that's causing the issue, but you can try adjusting the 3D Touch sensitivity from the Accessibility settings. Also the pressure required for this to work in FlickType may be more than you are used to - if so I might need to reduce that threshold a bit. I should also add here that 3D Touch is not a main area of focus right now, and in fact I mostly wanted to make sure that nobody accidentally triggers it when they don't intend to. The actual action may change, for example it could switch between letters and numbers or symbols, and the action might even be configurable in the future.

On full emoji support within FlickType: this is definitely planned, but might not make it before launching on the App Store. However, customizing the emoji shortcuts should be there soon, before we launch.

On the shortcut options in the main app, are you referring to number or symbol entry? We are currently assessing what we could do with an extra row above the letters, and this could be a number row, or a common symbols row, or something similar to the current app, but we want to make sure the learning curve is not as steep as what's in the main app today. This will probably be something we add post-launch. Also, it would be very helpful if you could tell us the top few use cases that you love about it as it is in the app now. And one final note on this, for email fields we will soon make the @ and period symbols available in the main layout, similar to the iOS keyboard.

Phonetics when performing manual input are coming soon.

On sometimes getting an adjacent letter entered when lifting your finger to do manual input: this was not the case before, but I had to temporarily disable the code that prevented that as it was making selecting the numbers, next keyboard, dismiss and return keys harder to select. This should be fixed soon.

On vanishing text: I am investigating this right now, and is I think the biggest problem we are currently experiencing. One thing I'd love to better assess, is how common this occurrence is. I understand that losing your text even just once can be a very poor experience, but is it currently happening enough that you'd rather use the iOS keyboard instead?

Thanks for your continued feedback, much appreciated, smile.

- Kosta




Re: Great built with some questions...

Ed Worrell
 

Hey Kosta,

I just decreased the level of pressure for 3D touch from firm to medium. The gesture works as expected now. That's great! I love this feature.😎

My business partner will be happy to hear that low vision options are on the road map.

As always great job.👍

Ed

On May 27, 2018, at 12:07 PM, FlickType <@FlickType> wrote:

Thanks for the comments.

On low vision color schemes, as well as the visual appearance of the keyboard, we are planning to improve those soon, but probably not before the custom keyboard launches on the App Store.

On 3D Touch not working for you Ed, it could be the iOS beta that's causing the issue, but you can try adjusting the 3D Touch sensitivity from the Accessibility settings. Also the pressure required for this to work in FlickType may be more than you are used to - if so I might need to reduce that threshold a bit. I should also add here that 3D Touch is not a main area of focus right now, and in fact I mostly wanted to make sure that nobody accidentally triggers it when they don't intend to. The actual action may change, for example it could switch between letters and numbers or symbols, and the action might even be configurable in the future.

On full emoji support within FlickType: this is definitely planned, but might not make it before launching on the App Store. However, customizing the emoji shortcuts should be there soon, before we launch.

On the shortcut options in the main app, are you referring to number or symbol entry? We are currently assessing what we could do with an extra row above the letters, and this could be a number row, or a common symbols row, or something similar to the current app, but we want to make sure the learning curve is not as steep as what's in the main app today. This will probably be something we add post-launch. Also, it would be very helpful if you could tell us the top few use cases that you love about it as it is in the app now. And one final note on this, for email fields we will soon make the @ and period symbols available in the main layout, similar to the iOS keyboard.

Phonetics when performing manual input are coming soon.

On sometimes getting an adjacent letter entered when lifting your finger to do manual input: this was not the case before, but I had to temporarily disable the code that prevented that as it was making selecting the numbers, next keyboard, dismiss and return keys harder to select. This should be fixed soon.

On vanishing text: I am investigating this right now, and is I think the biggest problem we are currently experiencing. One thing I'd love to better assess, is how common this occurrence is. I understand that losing your text even just once can be a very poor experience, but is it currently happening enough that you'd rather use the iOS keyboard instead?

Thanks for your continued feedback, much appreciated, smile.

- Kosta



Re: Great built with some questions...

Chuck Dean
 


Hi Paul, 
 Personally, I like how it is done in the app. A flick up to enter or delete a word. Simple and elegant. 


Chuck

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


Hi all, 
 How would people feel about having the 2 finger swipe up to add a word to the dictionary and a 2 finger swipe down to remove. 
 Just a thought, Paul. 


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

Hi George, 
 
 The 3D touch should capitalize the letter. 


Chuck

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

Ok, I've tried the 3 d touch when in the custom keyboard. I get a letter. Not  sure what  the 3 d touch is suppose to do. Got iPhone8

Kind regards,

George Cham

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

From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Sharon Kim <sharon.mi.kim22@...>
Sent: Monday, May 28, 2018 4:39:57 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Great built with some questions...
 
Hello all,
Okay the vanishing text bit... has never happened to me. Not going to lie.
I love the current build, thank you so very much for putting in the
next button. It is greatly appreciated.
One other thing, the 3d touch thing confuses me. I just sooner not
deal with it, especially if the gestures are going to be there.
I hope anyways, you wont' take out the gestures for the 3d things.
Because... no clue what those are.
anyways, hope this helps.


On 5/27/18, Chuck Dean <cadean329@...> wrote:
>
>  Hi Kosta,
>  My text has only vanished twice, and I do a lot of typing. It is not a deal
> breaker for me.
>
>
> Chuck
>
>> On May 27, 2018, at 11:07 AM, FlickType <hello@...> wrote:
>>
>> Thanks for the comments.
>>
>> On low vision color schemes, as well as the visual appearance of the
>> keyboard, we are planning to improve those soon, but probably not before
>> the custom keyboard launches on the App Store.
>>
>> On 3D Touch not working for you Ed, it could be the iOS beta that's
>> causing the issue, but you can try adjusting the 3D Touch sensitivity from
>> the Accessibility settings. Also the pressure required for this to work in
>> FlickType may be more than you are used to - if so I might need to reduce
>> that threshold a bit. I should also add here that 3D Touch is not a main
>> area of focus right now, and in fact I mostly wanted to make sure that
>> nobody accidentally triggers it when they don't intend to. The actual
>> action may change, for example it could switch between letters and numbers
>> or symbols, and the action might even be configurable in the future.
>>
>> On full emoji support within FlickType: this is definitely planned, but
>> might not make it before launching on the App Store. However, customizing
>> the emoji shortcuts should be there soon, before we launch.
>>
>> On the shortcut options in the main app, are you referring to number or
>> symbol entry? We are currently assessing what we could do with an extra
>> row above the letters, and this could be a number row, or a common symbols
>> row, or something similar to the current app, but we want to make sure the
>> learning curve is not as steep as what's in the main app today. This will
>> probably be something we add post-launch. Also, it would be very helpful
>> if you could tell us the top few use cases that you love about it as it is
>> in the app now. And one final note on this, for email fields we will soon
>> make the @ and period symbols available in the main layout, similar to the
>> iOS keyboard.
>>
>> Phonetics when performing manual input are coming soon.
>>
>> On sometimes getting an adjacent letter entered when lifting your finger
>> to do manual input: this was not the case before, but I had to temporarily
>> disable the code that prevented that as it was making selecting the
>> numbers, next keyboard, dismiss and return keys harder to select. This
>> should be fixed soon.
>>
>> On vanishing text: I am investigating this right now, and is I think the
>> biggest problem we are currently experiencing. One thing I'd love to
>> better assess, is how common this occurrence is. I understand that losing
>> your text even just once can be a very poor experience, but is it
>> currently happening enough that you'd rather use the iOS keyboard
>> instead?
>>
>> Thanks for your continued feedback, much appreciated, smile.
>>
>> - Kosta
>>
>>
>>
>>
>
>
>
>



Re: Great built with some questions...

Paul Sutton
 


Hi all, 
 How would people feel about having the 2 finger swipe up to add a word to the dictionary and a 2 finger swipe down to remove. 
 Just a thought, Paul. 


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

Hi George, 
 
 The 3D touch should capitalize the letter. 


Chuck

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

Ok, I've tried the 3 d touch when in the custom keyboard. I get a letter. Not  sure what  the 3 d touch is suppose to do. Got iPhone8

Kind regards,

George Cham

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

From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Sharon Kim <sharon.mi.kim22@...>
Sent: Monday, May 28, 2018 4:39:57 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Great built with some questions...
 
Hello all,
Okay the vanishing text bit... has never happened to me. Not going to lie.
I love the current build, thank you so very much for putting in the
next button. It is greatly appreciated.
One other thing, the 3d touch thing confuses me. I just sooner not
deal with it, especially if the gestures are going to be there.
I hope anyways, you wont' take out the gestures for the 3d things.
Because... no clue what those are.
anyways, hope this helps.


On 5/27/18, Chuck Dean <cadean329@...> wrote:
>
>  Hi Kosta,
>  My text has only vanished twice, and I do a lot of typing. It is not a deal
> breaker for me.
>
>
> Chuck
>
>> On May 27, 2018, at 11:07 AM, FlickType <hello@...> wrote:
>>
>> Thanks for the comments.
>>
>> On low vision color schemes, as well as the visual appearance of the
>> keyboard, we are planning to improve those soon, but probably not before
>> the custom keyboard launches on the App Store.
>>
>> On 3D Touch not working for you Ed, it could be the iOS beta that's
>> causing the issue, but you can try adjusting the 3D Touch sensitivity from
>> the Accessibility settings. Also the pressure required for this to work in
>> FlickType may be more than you are used to - if so I might need to reduce
>> that threshold a bit. I should also add here that 3D Touch is not a main
>> area of focus right now, and in fact I mostly wanted to make sure that
>> nobody accidentally triggers it when they don't intend to. The actual
>> action may change, for example it could switch between letters and numbers
>> or symbols, and the action might even be configurable in the future.
>>
>> On full emoji support within FlickType: this is definitely planned, but
>> might not make it before launching on the App Store. However, customizing
>> the emoji shortcuts should be there soon, before we launch.
>>
>> On the shortcut options in the main app, are you referring to number or
>> symbol entry? We are currently assessing what we could do with an extra
>> row above the letters, and this could be a number row, or a common symbols
>> row, or something similar to the current app, but we want to make sure the
>> learning curve is not as steep as what's in the main app today. This will
>> probably be something we add post-launch. Also, it would be very helpful
>> if you could tell us the top few use cases that you love about it as it is
>> in the app now. And one final note on this, for email fields we will soon
>> make the @ and period symbols available in the main layout, similar to the
>> iOS keyboard.
>>
>> Phonetics when performing manual input are coming soon.
>>
>> On sometimes getting an adjacent letter entered when lifting your finger
>> to do manual input: this was not the case before, but I had to temporarily
>> disable the code that prevented that as it was making selecting the
>> numbers, next keyboard, dismiss and return keys harder to select. This
>> should be fixed soon.
>>
>> On vanishing text: I am investigating this right now, and is I think the
>> biggest problem we are currently experiencing. One thing I'd love to
>> better assess, is how common this occurrence is. I understand that losing
>> your text even just once can be a very poor experience, but is it
>> currently happening enough that you'd rather use the iOS keyboard
>> instead?
>>
>> Thanks for your continued feedback, much appreciated, smile.
>>
>> - Kosta
>>
>>
>>
>>
>
>
>
>



Re: Great built with some questions...

Chuck Dean
 

Hi George, 
 
 The 3D touch should capitalize the letter. 


Chuck

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

Ok, I've tried the 3 d touch when in the custom keyboard. I get a letter. Not  sure what  the 3 d touch is suppose to do. Got iPhone8

Kind regards,

George Cham

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

From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Sharon Kim <sharon.mi.kim22@...>
Sent: Monday, May 28, 2018 4:39:57 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Great built with some questions...
 
Hello all,
Okay the vanishing text bit... has never happened to me. Not going to lie.
I love the current build, thank you so very much for putting in the
next button. It is greatly appreciated.
One other thing, the 3d touch thing confuses me. I just sooner not
deal with it, especially if the gestures are going to be there.
I hope anyways, you wont' take out the gestures for the 3d things.
Because... no clue what those are.
anyways, hope this helps.


On 5/27/18, Chuck Dean <cadean329@...> wrote:
>
>  Hi Kosta,
>  My text has only vanished twice, and I do a lot of typing. It is not a deal
> breaker for me.
>
>
> Chuck
>
>> On May 27, 2018, at 11:07 AM, FlickType <hello@...> wrote:
>>
>> Thanks for the comments.
>>
>> On low vision color schemes, as well as the visual appearance of the
>> keyboard, we are planning to improve those soon, but probably not before
>> the custom keyboard launches on the App Store.
>>
>> On 3D Touch not working for you Ed, it could be the iOS beta that's
>> causing the issue, but you can try adjusting the 3D Touch sensitivity from
>> the Accessibility settings. Also the pressure required for this to work in
>> FlickType may be more than you are used to - if so I might need to reduce
>> that threshold a bit. I should also add here that 3D Touch is not a main
>> area of focus right now, and in fact I mostly wanted to make sure that
>> nobody accidentally triggers it when they don't intend to. The actual
>> action may change, for example it could switch between letters and numbers
>> or symbols, and the action might even be configurable in the future.
>>
>> On full emoji support within FlickType: this is definitely planned, but
>> might not make it before launching on the App Store. However, customizing
>> the emoji shortcuts should be there soon, before we launch.
>>
>> On the shortcut options in the main app, are you referring to number or
>> symbol entry? We are currently assessing what we could do with an extra
>> row above the letters, and this could be a number row, or a common symbols
>> row, or something similar to the current app, but we want to make sure the
>> learning curve is not as steep as what's in the main app today. This will
>> probably be something we add post-launch. Also, it would be very helpful
>> if you could tell us the top few use cases that you love about it as it is
>> in the app now. And one final note on this, for email fields we will soon
>> make the @ and period symbols available in the main layout, similar to the
>> iOS keyboard.
>>
>> Phonetics when performing manual input are coming soon.
>>
>> On sometimes getting an adjacent letter entered when lifting your finger
>> to do manual input: this was not the case before, but I had to temporarily
>> disable the code that prevented that as it was making selecting the
>> numbers, next keyboard, dismiss and return keys harder to select. This
>> should be fixed soon.
>>
>> On vanishing text: I am investigating this right now, and is I think the
>> biggest problem we are currently experiencing. One thing I'd love to
>> better assess, is how common this occurrence is. I understand that losing
>> your text even just once can be a very poor experience, but is it
>> currently happening enough that you'd rather use the iOS keyboard
>> instead?
>>
>> Thanks for your continued feedback, much appreciated, smile.
>>
>> - Kosta
>>
>>
>>
>>
>
>
>
>



Re: Great built with some questions...

David Nason
 


I am also running the iOS 11.4 beta, so that is not the issue Ed. 
 Chuck you may be right. The 3 D touch gesture does work well, its possibly just that I was so used to the flick up gesture that I need to rewire my brain. The flick up is very intuitive tho. Kosta, while it's worth looking into other options for 3D Touch, for example it could reveal the numbers and punctuation, the capital letter thing does make good sense too. 
 Glad you're going to be able to address the issue with selecting the wrong character, this is the only real issue I'm having with this build. 
 While I have seen the disappearing text before, I don't think I've seen it since build 68. That might be dumb luck though. I think when it did happen to me, it was after switching between the FlickType and the iOS keyboard. But I couldn't quite reproduce it on demand. 
 
 Dave 
 


On 27 May 2018, at 19:45, George Cham <George.cham@...> wrote:

Ok, I've tried the 3 d touch when in the custom keyboard. I get a letter. Not  sure what  the 3 d touch is suppose to do. Got iPhone8

Kind regards,

George Cham

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

From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Sharon Kim <sharon.mi.kim22@...>
Sent: Monday, May 28, 2018 4:39:57 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Great built with some questions...
 
Hello all,
Okay the vanishing text bit... has never happened to me. Not going to lie.
I love the current build, thank you so very much for putting in the
next button. It is greatly appreciated.
One other thing, the 3d touch thing confuses me. I just sooner not
deal with it, especially if the gestures are going to be there.
I hope anyways, you wont' take out the gestures for the 3d things.
Because... no clue what those are.
anyways, hope this helps.


On 5/27/18, Chuck Dean <cadean329@...> wrote:
>
>  Hi Kosta,
>  My text has only vanished twice, and I do a lot of typing. It is not a deal
> breaker for me.
>
>
> Chuck
>
>> On May 27, 2018, at 11:07 AM, FlickType <hello@...> wrote:
>>
>> Thanks for the comments.
>>
>> On low vision color schemes, as well as the visual appearance of the
>> keyboard, we are planning to improve those soon, but probably not before
>> the custom keyboard launches on the App Store.
>>
>> On 3D Touch not working for you Ed, it could be the iOS beta that's
>> causing the issue, but you can try adjusting the 3D Touch sensitivity from
>> the Accessibility settings. Also the pressure required for this to work in
>> FlickType may be more than you are used to - if so I might need to reduce
>> that threshold a bit. I should also add here that 3D Touch is not a main
>> area of focus right now, and in fact I mostly wanted to make sure that
>> nobody accidentally triggers it when they don't intend to. The actual
>> action may change, for example it could switch between letters and numbers
>> or symbols, and the action might even be configurable in the future.
>>
>> On full emoji support within FlickType: this is definitely planned, but
>> might not make it before launching on the App Store. However, customizing
>> the emoji shortcuts should be there soon, before we launch.
>>
>> On the shortcut options in the main app, are you referring to number or
>> symbol entry? We are currently assessing what we could do with an extra
>> row above the letters, and this could be a number row, or a common symbols
>> row, or something similar to the current app, but we want to make sure the
>> learning curve is not as steep as what's in the main app today. This will
>> probably be something we add post-launch. Also, it would be very helpful
>> if you could tell us the top few use cases that you love about it as it is
>> in the app now. And one final note on this, for email fields we will soon
>> make the @ and period symbols available in the main layout, similar to the
>> iOS keyboard.
>>
>> Phonetics when performing manual input are coming soon.
>>
>> On sometimes getting an adjacent letter entered when lifting your finger
>> to do manual input: this was not the case before, but I had to temporarily
>> disable the code that prevented that as it was making selecting the
>> numbers, next keyboard, dismiss and return keys harder to select. This
>> should be fixed soon.
>>
>> On vanishing text: I am investigating this right now, and is I think the
>> biggest problem we are currently experiencing. One thing I'd love to
>> better assess, is how common this occurrence is. I understand that losing
>> your text even just once can be a very poor experience, but is it
>> currently happening enough that you'd rather use the iOS keyboard
>> instead?
>>
>> Thanks for your continued feedback, much appreciated, smile.
>>
>> - Kosta
>>
>>
>>
>>
>
>
>
>



Re: Build 72

Benny Barber
 

Kosta,

As far as the extra row of numbers / symbols, I love the layout of the app. The symbols across the top row of letters and 0 through 12 above the letter p with the ability to flick up and down through the options. Just my opinion. Thanks

Benny

On May 27, 2018, at 1:51 AM, FlickType <@FlickType> wrote:

- Added a "Next Keyboard" button for those having trouble with the flick up & hold gesture. If you don't need the button, you can disable it from the main app settings.
- Also added a setting for a "Dismiss" button similar to the above, but this one is off by default since most people didn't seem to have trouble with the flick down & hold gesture. If you do have trouble performing that gesture, you can enable this button from the settings.
- The shift state now resets after entering a single character, so it behaves more like a shift key rather than a caps lock.
- The shift state now affects words that were not manually typed, meaning that if you switch to uppercase in the middle of a sentence and type a word like "banana", it will be capitalized.
- Words will be capitalized after a new line.
- On devices that support 3D Touch, pressing down harder while exploring the keyboard will toggle the secondary layout, meaning the state of shift if you are in letters, or switch between numbers and symbols if you are in either numbers or symbols.


Re: Great built with some questions...

George Cham
 

Ok, I've tried the 3 d touch when in the custom keyboard. I get a letter. Not  sure what  the 3 d touch is suppose to do. Got iPhone8

Kind regards,

George Cham

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


From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Sharon Kim <sharon.mi.kim22@...>
Sent: Monday, May 28, 2018 4:39:57 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Great built with some questions...
 
Hello all,
Okay the vanishing text bit... has never happened to me. Not going to lie.
I love the current build, thank you so very much for putting in the
next button. It is greatly appreciated.
One other thing, the 3d touch thing confuses me. I just sooner not
deal with it, especially if the gestures are going to be there.
I hope anyways, you wont' take out the gestures for the 3d things.
Because... no clue what those are.
anyways, hope this helps.


On 5/27/18, Chuck Dean <cadean329@...> wrote:
>
>  Hi Kosta,
>  My text has only vanished twice, and I do a lot of typing. It is not a deal
> breaker for me.
>
>
> Chuck
>
>> On May 27, 2018, at 11:07 AM, FlickType <hello@...> wrote:
>>
>> Thanks for the comments.
>>
>> On low vision color schemes, as well as the visual appearance of the
>> keyboard, we are planning to improve those soon, but probably not before
>> the custom keyboard launches on the App Store.
>>
>> On 3D Touch not working for you Ed, it could be the iOS beta that's
>> causing the issue, but you can try adjusting the 3D Touch sensitivity from
>> the Accessibility settings. Also the pressure required for this to work in
>> FlickType may be more than you are used to - if so I might need to reduce
>> that threshold a bit. I should also add here that 3D Touch is not a main
>> area of focus right now, and in fact I mostly wanted to make sure that
>> nobody accidentally triggers it when they don't intend to. The actual
>> action may change, for example it could switch between letters and numbers
>> or symbols, and the action might even be configurable in the future.
>>
>> On full emoji support within FlickType: this is definitely planned, but
>> might not make it before launching on the App Store. However, customizing
>> the emoji shortcuts should be there soon, before we launch.
>>
>> On the shortcut options in the main app, are you referring to number or
>> symbol entry? We are currently assessing what we could do with an extra
>> row above the letters, and this could be a number row, or a common symbols
>> row, or something similar to the current app, but we want to make sure the
>> learning curve is not as steep as what's in the main app today. This will
>> probably be something we add post-launch. Also, it would be very helpful
>> if you could tell us the top few use cases that you love about it as it is
>> in the app now. And one final note on this, for email fields we will soon
>> make the @ and period symbols available in the main layout, similar to the
>> iOS keyboard.
>>
>> Phonetics when performing manual input are coming soon.
>>
>> On sometimes getting an adjacent letter entered when lifting your finger
>> to do manual input: this was not the case before, but I had to temporarily
>> disable the code that prevented that as it was making selecting the
>> numbers, next keyboard, dismiss and return keys harder to select. This
>> should be fixed soon.
>>
>> On vanishing text: I am investigating this right now, and is I think the
>> biggest problem we are currently experiencing. One thing I'd love to
>> better assess, is how common this occurrence is. I understand that losing
>> your text even just once can be a very poor experience, but is it
>> currently happening enough that you'd rather use the iOS keyboard
>> instead?
>>
>> Thanks for your continued feedback, much appreciated, smile.
>>
>> - Kosta
>>
>>
>>
>>
>
>
>
>