Date   

Re: Build 69

Benny Barber
 

You simply touch the screen to continue touch typing. Thanks.

On May 20, 2018, at 8:07 AM, Chanelle Allen <chanellem.allen@...> wrote:


Hello,
as someone who heavily relies on touch typing for symbol entry, Benny's idea of having a flick right gesture return to flick typing would not be helpful to me. Still, a method for switching back to flick typing without needing to find the "style" button would be great but not absolutely essential.
By the way, thank you Kosta and Ashley, for another new FlickType build. I can't believe how quickly the releases have been coming lately. Manual typing is so natural that I forget to switch back to flick typing. Maybe Kosta and Ashley will inadvertently turn us into accurate typists by making the transition between modes so seamless. ☺️ it could be just my experience, but I find that the magic tap gesture to dismiss the FlickType keyboard is better than the old gesture at placing my cursor exactly where I intend it to be. That being said, after writing the previous sentence and dismissing FlickType, their was a VoiceOver focus issue, but when I got back on track, my cursor was at the end of the sentence, which I wanted.
Keep up the awesome work! 😀 I eagerly look forward to getting TestFlight notifications, and am so excited to find out what each new build has in store.
(My TestFlight notifications and email announcements are no longer a build behind). Thank you.
Chanelle

On May 20, 2018, at 06:33, Benny Barber <rebelben@...> wrote:

Was just thinking, when in the touch type mode, would it be possible to just
simply use the flick right jesture for returning to the FlickType mode as
well as entering the word we just typed letter by letter?If one needs to
return to the touch type mode, they would touch and hold again. This would
eliminate having to tap the style key. Not sure how this would work if one
needs to add punctuation or a symbol after the touch typed word. I'm sure
you could figure this out Kosta. Thanks.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Saturday, May 19, 2018 7:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 69

- Allow the same long press gesture that triggers Touch Typing to continue
the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch
Typing mode.

Please continue providing as much feedback as possible, thank you all for
being so awesome!

- Kosta







Re: Build 69

Chanelle Allen
 

Hello,
as someone who heavily relies on touch typing for symbol entry, Benny's idea of having a flick right gesture return to flick typing would not be helpful to me. Still, a method for switching back to flick typing without needing to find the "style" button would be great but not absolutely essential.
By the way, thank you Kosta and Ashley, for another new FlickType build. I can't believe how quickly the releases have been coming lately. Manual typing is so natural that I forget to switch back to flick typing. Maybe Kosta and Ashley will inadvertently turn us into accurate typists by making the transition between modes so seamless. ☺️ it could be just my experience, but I find that the magic tap gesture to dismiss the FlickType keyboard is better than the old gesture at placing my cursor exactly where I intend it to be. That being said, after writing the previous sentence and dismissing FlickType, their was a VoiceOver focus issue, but when I got back on track, my cursor was at the end of the sentence, which I wanted.
Keep up the awesome work! 😀 I eagerly look forward to getting TestFlight notifications, and am so excited to find out what each new build has in store.
(My TestFlight notifications and email announcements are no longer a build behind). Thank you.
Chanelle

On May 20, 2018, at 06:33, Benny Barber <rebelben@...> wrote:

Was just thinking, when in the touch type mode, would it be possible to just
simply use the flick right jesture for returning to the FlickType mode as
well as entering the word we just typed letter by letter?If one needs to
return to the touch type mode, they would touch and hold again. This would
eliminate having to tap the style key. Not sure how this would work if one
needs to add punctuation or a symbol after the touch typed word. I'm sure
you could figure this out Kosta. Thanks.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Saturday, May 19, 2018 7:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 69

- Allow the same long press gesture that triggers Touch Typing to continue
the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch
Typing mode.

Please continue providing as much feedback as possible, thank you all for
being so awesome!

- Kosta






Re: Build 69

David Nason
 

You might be on to something there Benny .

Dave

On 20 May 2018, at 12:33, Benny Barber <rebelben@...> wrote:

Was just thinking, when in the touch type mode, would it be possible to just
simply use the flick right jesture for returning to the FlickType mode as
well as entering the word we just typed letter by letter?If one needs to
return to the touch type mode, they would touch and hold again. This would
eliminate having to tap the style key. Not sure how this would work if one
needs to add punctuation or a symbol after the touch typed word. I'm sure
you could figure this out Kosta. Thanks.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Saturday, May 19, 2018 7:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 69

- Allow the same long press gesture that triggers Touch Typing to continue
the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch
Typing mode.

Please continue providing as much feedback as possible, thank you all for
being so awesome!

- Kosta






Re: Build 69

Benny Barber
 

Was just thinking, when in the touch type mode, would it be possible to just
simply use the flick right jesture for returning to the FlickType mode as
well as entering the word we just typed letter by letter?If one needs to
return to the touch type mode, they would touch and hold again. This would
eliminate having to tap the style key. Not sure how this would work if one
needs to add punctuation or a symbol after the touch typed word. I'm sure
you could figure this out Kosta. Thanks.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Saturday, May 19, 2018 7:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 69

- Allow the same long press gesture that triggers Touch Typing to continue
the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch
Typing mode.

Please continue providing as much feedback as possible, thank you all for
being so awesome!

- Kosta


Re: Build 69

David Nason
 

I'm a little on the fence about the choice of gestures. I do definitely prefer the tap and hold to the magic tap, but the fact that you can't use the same gesture to go back from the touch typing mode to the flick mode is arguably a problem. My brain would prefer if I could use the same gesture to go both ways.

I really like what you've done in this build though, in that I can tap and hold, and navigate to the key I want, all in one go. Superb. 

I too like the idea of a half screen option. But I also see that this could be difficult for some users. Many people cannot see enough to be as targeted as others in there taps, so the full screen keyboard allows them much more ability to type successfully. So if implemented, it would have to be optional. The same fact is true for the discussion yesterday about typing accuracy. Of course user training and practice is necessary, but its easier for those of us who have some usable sight to be accurate than those who don't. So lets not dismiss the need to keep that conversation in mind.

Dave
 


On 20 May 2018, at 03:08, Chuck Dean <cadean329@...> wrote:


This is another reason for the half screen keyboard. If the top half is the iOS screen, we could use the rotor to edit text and to change the cursor position; leaving the FlickType area for the same gestures as the app's keyboard.


Chuck

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

If thats the case , after flicking right for space, can we have a flick gesture down for symbles  and numbers ?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Ed Worrell <ed.worrell@...>
Sent: Sunday, May 20, 2018 11:57:33 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 69
 
I think we will have the same manual typing as the keyboard in the future.

Ed
I believe at some point there will be no difference between the modes. I think the short cuts are simply there to return to the gesture keyboard at this point and time. I think we will have the same manual typing as the keyboard in the future.
> On May 19, 2018, at 7:02 PM, Benny Barber <rebelben@...> wrote:
>
>
> I prefer the magic tap to return to the iOS keyboard and tap and hold for direct typing. Thanks.
>
> Benny
>
>> On May 19, 2018, at 7:16 PM, FlickType <hello@...> wrote:
>>
>> - Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
>> - Fix shift sometimes not being in the correct state upon entering Touch Typing mode.
>>
>> Please continue providing as much feedback as possible, thank you all for being so awesome!
>>
>> - Kosta
>>
>>
>>
>
>
>
>




Re: Build 69

Chuck Dean
 


This is another reason for the half screen keyboard. If the top half is the iOS screen, we could use the rotor to edit text and to change the cursor position; leaving the FlickType area for the same gestures as the app's keyboard.


Chuck

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

If thats the case , after flicking right for space, can we have a flick gesture down for symbles  and numbers ?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Ed Worrell <ed.worrell@...>
Sent: Sunday, May 20, 2018 11:57:33 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 69
 
I think we will have the same manual typing as the keyboard in the future.

Ed
I believe at some point there will be no difference between the modes. I think the short cuts are simply there to return to the gesture keyboard at this point and time. I think we will have the same manual typing as the keyboard in the future.
> On May 19, 2018, at 7:02 PM, Benny Barber <rebelben@...> wrote:
>
>
> I prefer the magic tap to return to the iOS keyboard and tap and hold for direct typing. Thanks.
>
> Benny
>
>> On May 19, 2018, at 7:16 PM, FlickType <hello@...> wrote:
>>
>> - Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
>> - Fix shift sometimes not being in the correct state upon entering Touch Typing mode.
>>
>> Please continue providing as much feedback as possible, thank you all for being so awesome!
>>
>> - Kosta
>>
>>
>>
>
>
>
>




Re: Build 69

George Cham
 

If thats the case , after flicking right for space, can we have a flick gesture down for symbles  and numbers ?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Ed Worrell <ed.worrell@...>
Sent: Sunday, May 20, 2018 11:57:33 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 69
 
I think we will have the same manual typing as the keyboard in the future.

Ed
I believe at some point there will be no difference between the modes. I think the short cuts are simply there to return to the gesture keyboard at this point and time. I think we will have the same manual typing as the keyboard in the future.
> On May 19, 2018, at 7:02 PM, Benny Barber <rebelben@...> wrote:
>
>
> I prefer the magic tap to return to the iOS keyboard and tap and hold for direct typing. Thanks.
>
> Benny
>
>> On May 19, 2018, at 7:16 PM, FlickType <hello@...> wrote:
>>
>> - Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
>> - Fix shift sometimes not being in the correct state upon entering Touch Typing mode.
>>
>> Please continue providing as much feedback as possible, thank you all for being so awesome!
>>
>> - Kosta
>>
>>
>>
>
>
>
>




Re: Build 69

Ed Worrell
 

I think we will have the same manual typing as the keyboard in the future.

Ed
I believe at some point there will be no difference between the modes. I think the short cuts are simply there to return to the gesture keyboard at this point and time. I think we will have the same manual typing as the keyboard in the future.

On May 19, 2018, at 7:02 PM, Benny Barber <rebelben@...> wrote:


I prefer the magic tap to return to the iOS keyboard and tap and hold for direct typing. Thanks.

Benny

On May 19, 2018, at 7:16 PM, FlickType <@FlickType> wrote:

- Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch Typing mode.

Please continue providing as much feedback as possible, thank you all for being so awesome!

- Kosta





Re: Build 69

Benny Barber
 

I prefer the magic tap to return to the iOS keyboard and tap and hold for direct typing. Thanks.

Benny

On May 19, 2018, at 7:16 PM, FlickType <@FlickType> wrote:

- Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch Typing mode.

Please continue providing as much feedback as possible, thank you all for being so awesome!

- Kosta



Re: Build 69

George Cham
 

I prefer the long press as well  to switch between flick type and ios keyboard .

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Sunday, May 20, 2018 10:38:28 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 69
 

Hi all,
I prefer the tap and hold for changing to the touch type keyboard and the magic tap for going to the iOS keyboard.

The tap and hold perfectly blends to the first selection on the keyboard. If it were reversed I think it would be kind of clumsy.


Chuck

> On May 19, 2018, at 5:16 PM, FlickType <hello@...> wrote:
>
> - Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
> - Fix shift sometimes not being in the correct state upon entering Touch Typing mode.
>
> Please continue providing as much feedback as possible, thank you all for being so awesome!
>
> - Kosta
>
>
>




Re: Build 69

Chuck Dean
 

Hi all,
I prefer the tap and hold for changing to the touch type keyboard and the magic tap for going to the iOS keyboard.

The tap and hold perfectly blends to the first selection on the keyboard. If it were reversed I think it would be kind of clumsy.


Chuck

On May 19, 2018, at 5:16 PM, FlickType <@FlickType> wrote:

- Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch Typing mode.

Please continue providing as much feedback as possible, thank you all for being so awesome!

- Kosta



Re: Build 69

Ed Worrell
 

Hello,

I would love to hear phonetics after you hold on a character to manually type. This would be helpful on the bottom row of keys. Otherwise well done you two.

Ed

On May 19, 2018, at 6:16 PM, FlickType <@FlickType> wrote:

- Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch Typing mode.

Please continue providing as much feedback as possible, thank you all for being so awesome!

- Kosta



Re: Build 69

Chuck Dean
 

Ok, the tap and hold is much better.

A little easier to insert line breaks. I also tried some manual input, like my cat's name... MoTown.


Chuck

On May 19, 2018, at 5:16 PM, FlickType <@FlickType> wrote:

- Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch Typing mode.

Please continue providing as much feedback as possible, thank you all for being so awesome!

- Kosta



Re: Build 69

Benny Barber
 

Getting better all the time. Thanks, Kosta.

On May 19, 2018, at 7:16 PM, FlickType <@FlickType> wrote:

- Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch Typing mode.

Please continue providing as much feedback as possible, thank you all for being so awesome!

- Kosta



Build 69

 

- Allow the same long press gesture that triggers Touch Typing to continue the exploration, so you don't have to start a second press every time.
- Fix shift sometimes not being in the correct state upon entering Touch Typing mode.

Please continue providing as much feedback as possible, thank you all for being so awesome!

- Kosta


Re: Build 68

Chanelle Allen
 


Hello, 
 actually, in its current state, I find that the FlickType keyboard works quite well in search fields. After performing the magic tap gesture to dismiss the keyboard, I place my finger near the bottom right of my phone to locate the "search" button. Sometimes, I forget to switch between typing modes, use flick typing behavior when I am in touch typing mode, or accidentally toggle flick typing on before I am ready to do so. I like the magic tap gesture for switching between keyboards just as I found it convenient for switching between modes, so I hope that it will be incorporated somehow into the final version of FlickType. Perhaps I prefer the magic tap gesture because I either am less likely or have more confidence in my ability to transition without pressing extra keys. Rather than spending a few seconds to look/feel for a button, I gain access immediately to the next mode or keyboard via a simple double tap. What I am talking about will have no bearing upon the final FlickType release, but I thought that I would explain to myself and others (writing is helpful for bringing greater clarification and self-awareness) why I am in the minority. I have used the iPhone since the 3GS with VoiceOver was first available, so I have no difficulty performing touch and hold gestures. 
My preferences aside, I am very glad that we now have manual typing available to fully utilize. Whether the FlickType keyboard becomes more like the app, or whether the same development course is continued and modified, I think that I will enjoy the FlickType experience. Flicktype is one of many tools in my productivity toolbox, so regardless of what happens, I will have a use for it, and maybe, it will become my primary iPhone typing tool.
Thank you. 
Chanelle

On May 19, 2018, at 17:46, Ed Worrell <ed.worrell@...> wrote:

Hello, 

I actually am ok with this current build. I can finally start to see what direction you guys are trying to go with the keyboard. Nice job so far. I can't wait to start testing new builds. I am seeing a little lab when typing quickly, but the lab doesn't happen all the time. I still would love to see a two finger swipe down to enter a new line. At some point in the future I also would like to see compatibility with search fields. The keyboard actually feels very close to a daily driver. Keep up the great work! 

Ed 


On May 19, 2018, at 4:35 PM, FlickType <hello@...> wrote:

Thank you all for the helpful feedback. Just a quick reminder that you can always revert to one of the previous builds from TestFlight at any time.

Thanks,
Kosta

- To join our beta, please send an email here
- Browse all our forum topics
Post to our forum
Join our forum
Help & support
- Follow us on Twitter




On Sat, May 19, 2018 at 3:33 PM, Sharon Kim <sharon.mi.kim22@...> wrote:
Hello all,
Okay I have to say I am so not a fan for this latest update. to say
I'm not a fan would be an understatement.
1. The hold and tap gesture, has to go. The magic tap was much better.
Mostly because it was much quicker, and much more responsive.
2. also, there is now ay to switch keyboards, once you enter flick
type. It is very annoying, especially since I'm used to the tap and
hold gesture to switch to the next keyboard, and that is now gone.
I know it's a work in progress, but over all, not a fan. I've reverted
to using the main app due to this last change.


On 5/19/18, Alex Hiironen <l000b2a@...> wrote:
> On a note regarding accuracy, I've noticed that the custom keyboard still
> seems a bit laggy. if I type reasonably fast, it misses almost all the
> letters. I need to crawl type to get things to show up properly.
>
> Not complaining, just pointing it out.
> As always thx Kosta and Ashley for a solid release nonetheless. A lot of
> potential here. :)
>
>
>
> Alex
>
>> On May 19, 2018, at 2:46 PM, Chanelle Allen <chanellem.allen@...>
>> wrote:
>>
>>
>> Hi Dave and List,
>> I am having problems with typing accuracy today. Shorter words often take
>> FlickType a few tries to guess, but even words that it gets right are
>> taking some time to come up. A while back, I think that I also had a
>> problem with the word "read." longer words are always easier for FlickType
>> to guess. Sometimes, my problem is not spacing out my taps correctly,
>> because I am more accustomed to the iOS keyboard occupying less of the
>> screen. Aiming correctly requires more concentration though, and once I
>> get going, the typing engine and I become less in sync. The feature that
>> learns our particular typing habits will be a real time saver once it is
>> developed.
>> It's interesting that Dabe's difficult FlickType words are being less
>> troublesome today while I am experiencing more problems. For me, the words
>> FlickType has difficulty guessing vary by day. Today, they are "guess" and
>> "words. " Another reason I could be struggling a bit has to do with the
>> fact that in other emails, I had to switch frequently to touch typing. The
>> magic tap gesture for switching modes just made so much more sense to me,
>> but soon the issue will be irrelevant.
>> Until Dave mentioned the subject, I did not want FlickType to attempt to
>> guess or suggest words based on context. In the light of improving typing
>> accuracy, I have changed my opinion. Anything that speeds up
>> writing/typing is very welcome.
>> Chanelle
>>
>>
>>> On May 19, 2018, at 12:34, David Nason <dnason@...> wrote:
>>>
>>>
>>> On a separate note, how are people finding the accuracy of the typing
>>> engine itself these days? I'm sure it's an ongoing part of the
>>> development.
>>> For me, its mostly really good, but I do still sometimes run into
>>> frustrations. Long words are generally very successful, so long as I know
>>> how to spell the word.
>>> I do still have some problems at times with shorter words, where of
>>> course there are far more possible words for the engine to recommend. In
>>> recent days for example, I recall trying to type the words "read" and
>>> "date", and for whatever reason, for the life of me, I could not get the
>>> engine to suggest them, even with multiple swipes down. But just now, I
>>> was able to type them just fine.
>>> Some of this is clearly down to the user, but frustrating when it does
>>> happen. I wonder if there is scope for the engine, while still primarily
>>> making its recommendations based on the typing pattern, to have some
>>> level of context based predictions, like the iOS keyboard does, albeit
>>> implemented very differently.
>>> On the whole I'm extremely happy with it though.
>>>
>>> Dave
>>>> On 19 May 2018, at 17:31, Chuck Dean <cadean329@...> wrote:
>>>>
>>>> Btw to insert a new line using the custom keyboard, do a single tap and
>>>> hold, which will open the touch typing keyboard, now find the return key
>>>> in the bottom right corner and tap. Your new line will be entered, like
>>>> this,
>>>>
>>>>
>>>> I just put in three new lines.
>>>> To go back to the custom keyboard, fine the style key, which is on the
>>>> bottom, and is the second key from the left between the more numbers key
>>>> and the space key.
>>>>
>>>>
>>>> Chuck
>>>>
>>>>> On May 19, 2018, at 9:21 AM, Chuck Dean <cadean329@...> wrote:
>>>>>
>>>>>
>>>>> Hello Alex, you are indeed the lucky guy, as I tried to duplicate your
>>>>> problem, and could not.
>>>>> I did notice the landscape lock, left, did not work in the custom
>>>>> keyboard. In other words, the setting had no effect on the custom
>>>>> keyboard. When I went back to the app, the keyboard was locked in
>>>>> landscape, left.
>>>>> By guess is landscape lock is only in the app version.
>>>>> I hope this helps,
>>>>>
>>>>>
>>>>> Chuck
>>>>>
>>>>>> On May 19, 2018, at 8:50 AM, Alex Hiironen <l000b2a@...> wrote:
>>>>>>
>>>>>> Hey Kosta and all, so far I am getting used to this new way of
>>>>>> topping. However, there are two things still annoying me. First, I
>>>>>> still can't get new lines to work in the custom keyboards. Second, I
>>>>>> am still having issues with the main app just not showing up properly.
>>>>>> I completely removed FlickType and waited days to install it again, no
>>>>>> dice. I have my orientation set to landscape left and it's showing up
>>>>>> in portrait of or only taking up the first half of the screen. When I
>>>>>> open settings, it will eventually switch to landscape as it should
>>>>>> appear. Is anyone else experience this issue, or am I the lucky guy
>>>>>> for this bug? Cheers and as always thanks for such frequent updates.
>>>>>>
>>>>>> Alex
>>>>>>
>>>>>>> On May 19, 2018, at 7:07 AM, Chanelle Allen
>>>>>>> <chanellem.allen@...> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hello Kosta, Ashley, and Group,
>>>>>>> it's impressive that Kosta has gotten another FlickType release out
>>>>>>> to us so quickly. Thank you. Here are my initial thoughts.
>>>>>>> The new flick gestures--especially the one to capitalize a letter are
>>>>>>> useful. Using FlickType touch typing to go back by character to
>>>>>>> ensure a word is capitalized or spelled correctly is convenient.
>>>>>>> I preferred the magic tap gesture for switching between flick and
>>>>>>> touch typing modes. Frequently when touch typing, I accidentally
>>>>>>> press the "typing style" when intending to press space or the "more
>>>>>>> numbers" button. I might be in the minority, but for me, it would be
>>>>>>> nice to go back to having the magic tap gesture switch between modes.
>>>>>>> With time, I can become accustomed to anything though. I thought that
>>>>>>> FlickType was taking a while to come up with the right word for me in
>>>>>>> the flick typing mode, but I think that it is me just taking time to
>>>>>>> get warmed up to the keyboard. I will report back if I have further
>>>>>>> trouble.
>>>>>>> Chanelle
>>>>>>>
>>>>>>>
>>>>>>>> On May 19, 2018, at 02:39, FlickType <hello@...> wrote:
>>>>>>>>
>>>>>>>> Thank you for the feedback, we always read all of your posts to the
>>>>>>>> group, so please keep it coming. This is still work-in-progress, and
>>>>>>>> eventually there will be a manual input mode similar to the main
>>>>>>>> app.
>>>>>>>>
>>>>>>>> Touch Typing related changes:
>>>>>>>> - Swapped magic tap and tap and hold gestures for changing keyboard
>>>>>>>> or typing style. When Touch Typing, there is now a button to change
>>>>>>>> back to Flick Typing. Note that upon entering Touch Typing, you will
>>>>>>>> need to release your touch and tap again to start exploring. This is
>>>>>>>> annoying but will be addressed soon.
>>>>>>>> - Added one and two finger flick gestures when Touch Typing. Flick
>>>>>>>> left will delete the last character, flick right will add a space,
>>>>>>>> flick up and down will change the current character's case. Two
>>>>>>>> finger flick left or right will move the cursor by character.
>>>>>>>> - Fixed inverted shift state announcement bug
>>>>>>>> - Shift will automatically be selected and unselected as needed.
>>>>>>>> - Character echo will now respect the setting from the main app
>>>>>>>> - Added word echo
>>>>>>>>
>>>>>>>> Kosta
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>





Re: Build 68

Chuck Dean
 

Actually, if I have a third priority it is the ability to enter words into the dictionary, without having to go to the app.


Chuck

On May 19, 2018, at 4:22 PM, George Cham <George.cham@...> wrote:

can I add ,it's great to be typing with this version , and not having to rely on the flick type dictionary  .

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 George Cham <George.cham@...>
Sent: Sunday, May 20, 2018 9:13:25 AM
To: alpha@flicktype.groups.io; alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 68
 
I agree ,i would like to be able to flick down to invoke a new line .As i write this i have to flick right instead of finding the space . That said, i'm typing this on iphone 8 .   and remember that it's a smaller screen then the i pad.  

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 Chuck Dean <cadean329@...>
Sent: Sunday, May 20, 2018 9:02:41 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 68
 

I agree, Ed, the ability to add a new line and add a cap letter with a gesture are the two things I miss most. 


Chuck

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

Hello, 

I actually am ok with this current build. I can finally start to see what direction you guys are trying to go with the keyboard. Nice job so far. I can't wait to start testing new builds. I am seeing a little lab when typing quickly, but the lab doesn't happen all the time. I still would love to see a two finger swipe down to enter a new line. At some point in the future I also would like to see compatibility with search fields. The keyboard actually feels very close to a daily driver. Keep up the great work! 

Ed 


On May 19, 2018, at 4:35 PM, FlickType <hello@...> wrote:

Thank you all for the helpful feedback. Just a quick reminder that you can always revert to one of the previous builds from TestFlight at any time.

Thanks,
Kosta

- To join our beta, please send an email here
- Browse all our forum topics
Post to our forum
Join our forum
Help & support
- Follow us on Twitter




On Sat, May 19, 2018 at 3:33 PM, Sharon Kim <sharon.mi.kim22@...> wrote:
Hello all,
Okay I have to say I am so not a fan for this latest update. to say
I'm not a fan would be an understatement.
1. The hold and tap gesture, has to go. The magic tap was much better.
Mostly because it was much quicker, and much more responsive.
2. also, there is now ay to switch keyboards, once you enter flick
type. It is very annoying, especially since I'm used to the tap and
hold gesture to switch to the next keyboard, and that is now gone.
I know it's a work in progress, but over all, not a fan. I've reverted
to using the main app due to this last change.


On 5/19/18, Alex Hiironen <l000b2a@...> wrote:
> On a note regarding accuracy, I've noticed that the custom keyboard still
> seems a bit laggy. if I type reasonably fast, it misses almost all the
> letters. I need to crawl type to get things to show up properly.
>
> Not complaining, just pointing it out.
> As always thx Kosta and Ashley for a solid release nonetheless. A lot of
> potential here. :)
>
>
>
> Alex
>
>> On May 19, 2018, at 2:46 PM, Chanelle Allen <chanellem.allen@...>
>> wrote:
>>
>>
>> Hi Dave and List,
>> I am having problems with typing accuracy today. Shorter words often take
>> FlickType a few tries to guess, but even words that it gets right are
>> taking some time to come up. A while back, I think that I also had a
>> problem with the word "read." longer words are always easier for FlickType
>> to guess. Sometimes, my problem is not spacing out my taps correctly,
>> because I am more accustomed to the iOS keyboard occupying less of the
>> screen. Aiming correctly requires more concentration though, and once I
>> get going, the typing engine and I become less in sync. The feature that
>> learns our particular typing habits will be a real time saver once it is
>> developed.
>> It's interesting that Dabe's difficult FlickType words are being less
>> troublesome today while I am experiencing more problems. For me, the words
>> FlickType has difficulty guessing vary by day. Today, they are "guess" and
>> "words. " Another reason I could be struggling a bit has to do with the
>> fact that in other emails, I had to switch frequently to touch typing. The
>> magic tap gesture for switching modes just made so much more sense to me,
>> but soon the issue will be irrelevant.
>> Until Dave mentioned the subject, I did not want FlickType to attempt to
>> guess or suggest words based on context. In the light of improving typing
>> accuracy, I have changed my opinion. Anything that speeds up
>> writing/typing is very welcome.
>> Chanelle
>>
>>
>>> On May 19, 2018, at 12:34, David Nason <dnason@...> wrote:
>>>
>>>
>>> On a separate note, how are people finding the accuracy of the typing
>>> engine itself these days? I'm sure it's an ongoing part of the
>>> development.
>>> For me, its mostly really good, but I do still sometimes run into
>>> frustrations. Long words are generally very successful, so long as I know
>>> how to spell the word.
>>> I do still have some problems at times with shorter words, where of
>>> course there are far more possible words for the engine to recommend. In
>>> recent days for example, I recall trying to type the words "read" and
>>> "date", and for whatever reason, for the life of me, I could not get the
>>> engine to suggest them, even with multiple swipes down. But just now, I
>>> was able to type them just fine.
>>> Some of this is clearly down to the user, but frustrating when it does
>>> happen. I wonder if there is scope for the engine, while still primarily
>>> making its recommendations based on the typing pattern, to have some
>>> level of context based predictions, like the iOS keyboard does, albeit
>>> implemented very differently.
>>> On the whole I'm extremely happy with it though.
>>>
>>> Dave
>>>> On 19 May 2018, at 17:31, Chuck Dean <cadean329@...> wrote:
>>>>
>>>> Btw to insert a new line using the custom keyboard, do a single tap and
>>>> hold, which will open the touch typing keyboard, now find the return key
>>>> in the bottom right corner and tap. Your new line will be entered, like
>>>> this,
>>>>
>>>>
>>>> I just put in three new lines.
>>>> To go back to the custom keyboard, fine the style key, which is on the
>>>> bottom, and is the second key from the left between the more numbers key
>>>> and the space key.
>>>>
>>>>
>>>> Chuck
>>>>
>>>>> On May 19, 2018, at 9:21 AM, Chuck Dean <cadean329@...> wrote:
>>>>>
>>>>>
>>>>> Hello Alex, you are indeed the lucky guy, as I tried to duplicate your
>>>>> problem, and could not.
>>>>> I did notice the landscape lock, left, did not work in the custom
>>>>> keyboard. In other words, the setting had no effect on the custom
>>>>> keyboard. When I went back to the app, the keyboard was locked in
>>>>> landscape, left.
>>>>> By guess is landscape lock is only in the app version.
>>>>> I hope this helps,
>>>>>
>>>>>
>>>>> Chuck
>>>>>
>>>>>> On May 19, 2018, at 8:50 AM, Alex Hiironen <l000b2a@...> wrote:
>>>>>>
>>>>>> Hey Kosta and all, so far I am getting used to this new way of
>>>>>> topping. However, there are two things still annoying me. First, I
>>>>>> still can't get new lines to work in the custom keyboards. Second, I
>>>>>> am still having issues with the main app just not showing up properly.
>>>>>> I completely removed FlickType and waited days to install it again, no
>>>>>> dice. I have my orientation set to landscape left and it's showing up
>>>>>> in portrait of or only taking up the first half of the screen. When I
>>>>>> open settings, it will eventually switch to landscape as it should
>>>>>> appear. Is anyone else experience this issue, or am I the lucky guy
>>>>>> for this bug? Cheers and as always thanks for such frequent updates.
>>>>>>
>>>>>> Alex
>>>>>>
>>>>>>> On May 19, 2018, at 7:07 AM, Chanelle Allen
>>>>>>> <chanellem.allen@...> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hello Kosta, Ashley, and Group,
>>>>>>> it's impressive that Kosta has gotten another FlickType release out
>>>>>>> to us so quickly. Thank you. Here are my initial thoughts.
>>>>>>> The new flick gestures--especially the one to capitalize a letter are
>>>>>>> useful. Using FlickType touch typing to go back by character to
>>>>>>> ensure a word is capitalized or spelled correctly is convenient.
>>>>>>> I preferred the magic tap gesture for switching between flick and
>>>>>>> touch typing modes. Frequently when touch typing, I accidentally
>>>>>>> press the "typing style" when intending to press space or the "more
>>>>>>> numbers" button. I might be in the minority, but for me, it would be
>>>>>>> nice to go back to having the magic tap gesture switch between modes.
>>>>>>> With time, I can become accustomed to anything though. I thought that
>>>>>>> FlickType was taking a while to come up with the right word for me in
>>>>>>> the flick typing mode, but I think that it is me just taking time to
>>>>>>> get warmed up to the keyboard. I will report back if I have further
>>>>>>> trouble.
>>>>>>> Chanelle
>>>>>>>
>>>>>>>
>>>>>>>> On May 19, 2018, at 02:39, FlickType <hello@...> wrote:
>>>>>>>>
>>>>>>>> Thank you for the feedback, we always read all of your posts to the
>>>>>>>> group, so please keep it coming. This is still work-in-progress, and
>>>>>>>> eventually there will be a manual input mode similar to the main
>>>>>>>> app.
>>>>>>>>
>>>>>>>> Touch Typing related changes:
>>>>>>>> - Swapped magic tap and tap and hold gestures for changing keyboard
>>>>>>>> or typing style. When Touch Typing, there is now a button to change
>>>>>>>> back to Flick Typing. Note that upon entering Touch Typing, you will
>>>>>>>> need to release your touch and tap again to start exploring. This is
>>>>>>>> annoying but will be addressed soon.
>>>>>>>> - Added one and two finger flick gestures when Touch Typing. Flick
>>>>>>>> left will delete the last character, flick right will add a space,
>>>>>>>> flick up and down will change the current character's case. Two
>>>>>>>> finger flick left or right will move the cursor by character.
>>>>>>>> - Fixed inverted shift state announcement bug
>>>>>>>> - Shift will automatically be selected and unselected as needed.
>>>>>>>> - Character echo will now respect the setting from the main app
>>>>>>>> - Added word echo
>>>>>>>>
>>>>>>>> Kosta
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>





Re: iPhone X bug in build 68

David Nason
 

Ok yes, a restart seems to have fixed the issue.
It just started at some point during the day today, not even straight away after installing build 68. I'll let you know if it happens again at all.

Dave

On 19 May 2018, at 23:33, FlickType <@FlickType> wrote:

Thanks for the report. I can't seem to be able to reproduce this on my iPhone X. Did this only start happening with build 68? And have you tried restarting your device?

- Kosta



Re: Build 68

George Cham
 

can I add ,it's great to be typing with this version , and not having to rely on the flick type dictionary  .

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 George Cham <George.cham@...>
Sent: Sunday, May 20, 2018 9:13:25 AM
To: alpha@flicktype.groups.io; alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 68
 
I agree ,i would like to be able to flick down to invoke a new line .As i write this i have to flick right instead of finding the space . That said, i'm typing this on iphone 8 .   and remember that it's a smaller screen then the i pad.  

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 Chuck Dean <cadean329@...>
Sent: Sunday, May 20, 2018 9:02:41 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 68
 

I agree, Ed, the ability to add a new line and add a cap letter with a gesture are the two things I miss most. 


Chuck

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

Hello, 

I actually am ok with this current build. I can finally start to see what direction you guys are trying to go with the keyboard. Nice job so far. I can't wait to start testing new builds. I am seeing a little lab when typing quickly, but the lab doesn't happen all the time. I still would love to see a two finger swipe down to enter a new line. At some point in the future I also would like to see compatibility with search fields. The keyboard actually feels very close to a daily driver. Keep up the great work! 

Ed 


On May 19, 2018, at 4:35 PM, FlickType <hello@...> wrote:

Thank you all for the helpful feedback. Just a quick reminder that you can always revert to one of the previous builds from TestFlight at any time.

Thanks,
Kosta

- To join our beta, please send an email here
- Browse all our forum topics
Post to our forum
Join our forum
Help & support
- Follow us on Twitter




On Sat, May 19, 2018 at 3:33 PM, Sharon Kim <sharon.mi.kim22@...> wrote:
Hello all,
Okay I have to say I am so not a fan for this latest update. to say
I'm not a fan would be an understatement.
1. The hold and tap gesture, has to go. The magic tap was much better.
Mostly because it was much quicker, and much more responsive.
2. also, there is now ay to switch keyboards, once you enter flick
type. It is very annoying, especially since I'm used to the tap and
hold gesture to switch to the next keyboard, and that is now gone.
I know it's a work in progress, but over all, not a fan. I've reverted
to using the main app due to this last change.


On 5/19/18, Alex Hiironen <l000b2a@...> wrote:
> On a note regarding accuracy, I've noticed that the custom keyboard still
> seems a bit laggy. if I type reasonably fast, it misses almost all the
> letters. I need to crawl type to get things to show up properly.
>
> Not complaining, just pointing it out.
> As always thx Kosta and Ashley for a solid release nonetheless. A lot of
> potential here. :)
>
>
>
> Alex
>
>> On May 19, 2018, at 2:46 PM, Chanelle Allen <chanellem.allen@...>
>> wrote:
>>
>>
>> Hi Dave and List,
>> I am having problems with typing accuracy today. Shorter words often take
>> FlickType a few tries to guess, but even words that it gets right are
>> taking some time to come up. A while back, I think that I also had a
>> problem with the word "read." longer words are always easier for FlickType
>> to guess. Sometimes, my problem is not spacing out my taps correctly,
>> because I am more accustomed to the iOS keyboard occupying less of the
>> screen. Aiming correctly requires more concentration though, and once I
>> get going, the typing engine and I become less in sync. The feature that
>> learns our particular typing habits will be a real time saver once it is
>> developed.
>> It's interesting that Dabe's difficult FlickType words are being less
>> troublesome today while I am experiencing more problems. For me, the words
>> FlickType has difficulty guessing vary by day. Today, they are "guess" and
>> "words. " Another reason I could be struggling a bit has to do with the
>> fact that in other emails, I had to switch frequently to touch typing. The
>> magic tap gesture for switching modes just made so much more sense to me,
>> but soon the issue will be irrelevant.
>> Until Dave mentioned the subject, I did not want FlickType to attempt to
>> guess or suggest words based on context. In the light of improving typing
>> accuracy, I have changed my opinion. Anything that speeds up
>> writing/typing is very welcome.
>> Chanelle
>>
>>
>>> On May 19, 2018, at 12:34, David Nason <dnason@...> wrote:
>>>
>>>
>>> On a separate note, how are people finding the accuracy of the typing
>>> engine itself these days? I'm sure it's an ongoing part of the
>>> development.
>>> For me, its mostly really good, but I do still sometimes run into
>>> frustrations. Long words are generally very successful, so long as I know
>>> how to spell the word.
>>> I do still have some problems at times with shorter words, where of
>>> course there are far more possible words for the engine to recommend. In
>>> recent days for example, I recall trying to type the words "read" and
>>> "date", and for whatever reason, for the life of me, I could not get the
>>> engine to suggest them, even with multiple swipes down. But just now, I
>>> was able to type them just fine.
>>> Some of this is clearly down to the user, but frustrating when it does
>>> happen. I wonder if there is scope for the engine, while still primarily
>>> making its recommendations based on the typing pattern, to have some
>>> level of context based predictions, like the iOS keyboard does, albeit
>>> implemented very differently.
>>> On the whole I'm extremely happy with it though.
>>>
>>> Dave
>>>> On 19 May 2018, at 17:31, Chuck Dean <cadean329@...> wrote:
>>>>
>>>> Btw to insert a new line using the custom keyboard, do a single tap and
>>>> hold, which will open the touch typing keyboard, now find the return key
>>>> in the bottom right corner and tap. Your new line will be entered, like
>>>> this,
>>>>
>>>>
>>>> I just put in three new lines.
>>>> To go back to the custom keyboard, fine the style key, which is on the
>>>> bottom, and is the second key from the left between the more numbers key
>>>> and the space key.
>>>>
>>>>
>>>> Chuck
>>>>
>>>>> On May 19, 2018, at 9:21 AM, Chuck Dean <cadean329@...> wrote:
>>>>>
>>>>>
>>>>> Hello Alex, you are indeed the lucky guy, as I tried to duplicate your
>>>>> problem, and could not.
>>>>> I did notice the landscape lock, left, did not work in the custom
>>>>> keyboard. In other words, the setting had no effect on the custom
>>>>> keyboard. When I went back to the app, the keyboard was locked in
>>>>> landscape, left.
>>>>> By guess is landscape lock is only in the app version.
>>>>> I hope this helps,
>>>>>
>>>>>
>>>>> Chuck
>>>>>
>>>>>> On May 19, 2018, at 8:50 AM, Alex Hiironen <l000b2a@...> wrote:
>>>>>>
>>>>>> Hey Kosta and all, so far I am getting used to this new way of
>>>>>> topping. However, there are two things still annoying me. First, I
>>>>>> still can't get new lines to work in the custom keyboards. Second, I
>>>>>> am still having issues with the main app just not showing up properly.
>>>>>> I completely removed FlickType and waited days to install it again, no
>>>>>> dice. I have my orientation set to landscape left and it's showing up
>>>>>> in portrait of or only taking up the first half of the screen. When I
>>>>>> open settings, it will eventually switch to landscape as it should
>>>>>> appear. Is anyone else experience this issue, or am I the lucky guy
>>>>>> for this bug? Cheers and as always thanks for such frequent updates.
>>>>>>
>>>>>> Alex
>>>>>>
>>>>>>> On May 19, 2018, at 7:07 AM, Chanelle Allen
>>>>>>> <chanellem.allen@...> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hello Kosta, Ashley, and Group,
>>>>>>> it's impressive that Kosta has gotten another FlickType release out
>>>>>>> to us so quickly. Thank you. Here are my initial thoughts.
>>>>>>> The new flick gestures--especially the one to capitalize a letter are
>>>>>>> useful. Using FlickType touch typing to go back by character to
>>>>>>> ensure a word is capitalized or spelled correctly is convenient.
>>>>>>> I preferred the magic tap gesture for switching between flick and
>>>>>>> touch typing modes. Frequently when touch typing, I accidentally
>>>>>>> press the "typing style" when intending to press space or the "more
>>>>>>> numbers" button. I might be in the minority, but for me, it would be
>>>>>>> nice to go back to having the magic tap gesture switch between modes.
>>>>>>> With time, I can become accustomed to anything though. I thought that
>>>>>>> FlickType was taking a while to come up with the right word for me in
>>>>>>> the flick typing mode, but I think that it is me just taking time to
>>>>>>> get warmed up to the keyboard. I will report back if I have further
>>>>>>> trouble.
>>>>>>> Chanelle
>>>>>>>
>>>>>>>
>>>>>>>> On May 19, 2018, at 02:39, FlickType <hello@...> wrote:
>>>>>>>>
>>>>>>>> Thank you for the feedback, we always read all of your posts to the
>>>>>>>> group, so please keep it coming. This is still work-in-progress, and
>>>>>>>> eventually there will be a manual input mode similar to the main
>>>>>>>> app.
>>>>>>>>
>>>>>>>> Touch Typing related changes:
>>>>>>>> - Swapped magic tap and tap and hold gestures for changing keyboard
>>>>>>>> or typing style. When Touch Typing, there is now a button to change
>>>>>>>> back to Flick Typing. Note that upon entering Touch Typing, you will
>>>>>>>> need to release your touch and tap again to start exploring. This is
>>>>>>>> annoying but will be addressed soon.
>>>>>>>> - Added one and two finger flick gestures when Touch Typing. Flick
>>>>>>>> left will delete the last character, flick right will add a space,
>>>>>>>> flick up and down will change the current character's case. Two
>>>>>>>> finger flick left or right will move the cursor by character.
>>>>>>>> - Fixed inverted shift state announcement bug
>>>>>>>> - Shift will automatically be selected and unselected as needed.
>>>>>>>> - Character echo will now respect the setting from the main app
>>>>>>>> - Added word echo
>>>>>>>>
>>>>>>>> Kosta
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>





Re: Build 68

George Cham
 

I agree ,i would like to be able to flick down to invoke a new line .As i write this i have to flick right instead of finding the space . That said, i'm typing this on iphone 8 .   and remember that it's a smaller screen then the i pad.  

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 Chuck Dean <cadean329@...>
Sent: Sunday, May 20, 2018 9:02:41 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 68
 

I agree, Ed, the ability to add a new line and add a cap letter with a gesture are the two things I miss most. 


Chuck

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

Hello, 

I actually am ok with this current build. I can finally start to see what direction you guys are trying to go with the keyboard. Nice job so far. I can't wait to start testing new builds. I am seeing a little lab when typing quickly, but the lab doesn't happen all the time. I still would love to see a two finger swipe down to enter a new line. At some point in the future I also would like to see compatibility with search fields. The keyboard actually feels very close to a daily driver. Keep up the great work! 

Ed 


On May 19, 2018, at 4:35 PM, FlickType <hello@...> wrote:

Thank you all for the helpful feedback. Just a quick reminder that you can always revert to one of the previous builds from TestFlight at any time.

Thanks,
Kosta

- To join our beta, please send an email here
- Browse all our forum topics
Post to our forum
Join our forum
Help & support
- Follow us on Twitter




On Sat, May 19, 2018 at 3:33 PM, Sharon Kim <sharon.mi.kim22@...> wrote:
Hello all,
Okay I have to say I am so not a fan for this latest update. to say
I'm not a fan would be an understatement.
1. The hold and tap gesture, has to go. The magic tap was much better.
Mostly because it was much quicker, and much more responsive.
2. also, there is now ay to switch keyboards, once you enter flick
type. It is very annoying, especially since I'm used to the tap and
hold gesture to switch to the next keyboard, and that is now gone.
I know it's a work in progress, but over all, not a fan. I've reverted
to using the main app due to this last change.


On 5/19/18, Alex Hiironen <l000b2a@...> wrote:
> On a note regarding accuracy, I've noticed that the custom keyboard still
> seems a bit laggy. if I type reasonably fast, it misses almost all the
> letters. I need to crawl type to get things to show up properly.
>
> Not complaining, just pointing it out.
> As always thx Kosta and Ashley for a solid release nonetheless. A lot of
> potential here. :)
>
>
>
> Alex
>
>> On May 19, 2018, at 2:46 PM, Chanelle Allen <chanellem.allen@...>
>> wrote:
>>
>>
>> Hi Dave and List,
>> I am having problems with typing accuracy today. Shorter words often take
>> FlickType a few tries to guess, but even words that it gets right are
>> taking some time to come up. A while back, I think that I also had a
>> problem with the word "read." longer words are always easier for FlickType
>> to guess. Sometimes, my problem is not spacing out my taps correctly,
>> because I am more accustomed to the iOS keyboard occupying less of the
>> screen. Aiming correctly requires more concentration though, and once I
>> get going, the typing engine and I become less in sync. The feature that
>> learns our particular typing habits will be a real time saver once it is
>> developed.
>> It's interesting that Dabe's difficult FlickType words are being less
>> troublesome today while I am experiencing more problems. For me, the words
>> FlickType has difficulty guessing vary by day. Today, they are "guess" and
>> "words. " Another reason I could be struggling a bit has to do with the
>> fact that in other emails, I had to switch frequently to touch typing. The
>> magic tap gesture for switching modes just made so much more sense to me,
>> but soon the issue will be irrelevant.
>> Until Dave mentioned the subject, I did not want FlickType to attempt to
>> guess or suggest words based on context. In the light of improving typing
>> accuracy, I have changed my opinion. Anything that speeds up
>> writing/typing is very welcome.
>> Chanelle
>>
>>
>>> On May 19, 2018, at 12:34, David Nason <dnason@...> wrote:
>>>
>>>
>>> On a separate note, how are people finding the accuracy of the typing
>>> engine itself these days? I'm sure it's an ongoing part of the
>>> development.
>>> For me, its mostly really good, but I do still sometimes run into
>>> frustrations. Long words are generally very successful, so long as I know
>>> how to spell the word.
>>> I do still have some problems at times with shorter words, where of
>>> course there are far more possible words for the engine to recommend. In
>>> recent days for example, I recall trying to type the words "read" and
>>> "date", and for whatever reason, for the life of me, I could not get the
>>> engine to suggest them, even with multiple swipes down. But just now, I
>>> was able to type them just fine.
>>> Some of this is clearly down to the user, but frustrating when it does
>>> happen. I wonder if there is scope for the engine, while still primarily
>>> making its recommendations based on the typing pattern, to have some
>>> level of context based predictions, like the iOS keyboard does, albeit
>>> implemented very differently.
>>> On the whole I'm extremely happy with it though.
>>>
>>> Dave
>>>> On 19 May 2018, at 17:31, Chuck Dean <cadean329@...> wrote:
>>>>
>>>> Btw to insert a new line using the custom keyboard, do a single tap and
>>>> hold, which will open the touch typing keyboard, now find the return key
>>>> in the bottom right corner and tap. Your new line will be entered, like
>>>> this,
>>>>
>>>>
>>>> I just put in three new lines.
>>>> To go back to the custom keyboard, fine the style key, which is on the
>>>> bottom, and is the second key from the left between the more numbers key
>>>> and the space key.
>>>>
>>>>
>>>> Chuck
>>>>
>>>>> On May 19, 2018, at 9:21 AM, Chuck Dean <cadean329@...> wrote:
>>>>>
>>>>>
>>>>> Hello Alex, you are indeed the lucky guy, as I tried to duplicate your
>>>>> problem, and could not.
>>>>> I did notice the landscape lock, left, did not work in the custom
>>>>> keyboard. In other words, the setting had no effect on the custom
>>>>> keyboard. When I went back to the app, the keyboard was locked in
>>>>> landscape, left.
>>>>> By guess is landscape lock is only in the app version.
>>>>> I hope this helps,
>>>>>
>>>>>
>>>>> Chuck
>>>>>
>>>>>> On May 19, 2018, at 8:50 AM, Alex Hiironen <l000b2a@...> wrote:
>>>>>>
>>>>>> Hey Kosta and all, so far I am getting used to this new way of
>>>>>> topping. However, there are two things still annoying me. First, I
>>>>>> still can't get new lines to work in the custom keyboards. Second, I
>>>>>> am still having issues with the main app just not showing up properly.
>>>>>> I completely removed FlickType and waited days to install it again, no
>>>>>> dice. I have my orientation set to landscape left and it's showing up
>>>>>> in portrait of or only taking up the first half of the screen. When I
>>>>>> open settings, it will eventually switch to landscape as it should
>>>>>> appear. Is anyone else experience this issue, or am I the lucky guy
>>>>>> for this bug? Cheers and as always thanks for such frequent updates.
>>>>>>
>>>>>> Alex
>>>>>>
>>>>>>> On May 19, 2018, at 7:07 AM, Chanelle Allen
>>>>>>> <chanellem.allen@...> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hello Kosta, Ashley, and Group,
>>>>>>> it's impressive that Kosta has gotten another FlickType release out
>>>>>>> to us so quickly. Thank you. Here are my initial thoughts.
>>>>>>> The new flick gestures--especially the one to capitalize a letter are
>>>>>>> useful. Using FlickType touch typing to go back by character to
>>>>>>> ensure a word is capitalized or spelled correctly is convenient.
>>>>>>> I preferred the magic tap gesture for switching between flick and
>>>>>>> touch typing modes. Frequently when touch typing, I accidentally
>>>>>>> press the "typing style" when intending to press space or the "more
>>>>>>> numbers" button. I might be in the minority, but for me, it would be
>>>>>>> nice to go back to having the magic tap gesture switch between modes.
>>>>>>> With time, I can become accustomed to anything though. I thought that
>>>>>>> FlickType was taking a while to come up with the right word for me in
>>>>>>> the flick typing mode, but I think that it is me just taking time to
>>>>>>> get warmed up to the keyboard. I will report back if I have further
>>>>>>> trouble.
>>>>>>> Chanelle
>>>>>>>
>>>>>>>
>>>>>>>> On May 19, 2018, at 02:39, FlickType <hello@...> wrote:
>>>>>>>>
>>>>>>>> Thank you for the feedback, we always read all of your posts to the
>>>>>>>> group, so please keep it coming. This is still work-in-progress, and
>>>>>>>> eventually there will be a manual input mode similar to the main
>>>>>>>> app.
>>>>>>>>
>>>>>>>> Touch Typing related changes:
>>>>>>>> - Swapped magic tap and tap and hold gestures for changing keyboard
>>>>>>>> or typing style. When Touch Typing, there is now a button to change
>>>>>>>> back to Flick Typing. Note that upon entering Touch Typing, you will
>>>>>>>> need to release your touch and tap again to start exploring. This is
>>>>>>>> annoying but will be addressed soon.
>>>>>>>> - Added one and two finger flick gestures when Touch Typing. Flick
>>>>>>>> left will delete the last character, flick right will add a space,
>>>>>>>> flick up and down will change the current character's case. Two
>>>>>>>> finger flick left or right will move the cursor by character.
>>>>>>>> - Fixed inverted shift state announcement bug
>>>>>>>> - Shift will automatically be selected and unselected as needed.
>>>>>>>> - Character echo will now respect the setting from the main app
>>>>>>>> - Added word echo
>>>>>>>>
>>>>>>>> Kosta
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>