Date   

Re: Single word spell

 

Thanks for the feedback.

Spelling of the last word should be interrupted by the typing of the next one, but it seems this is currently broken and quite annoying. I will try to fix that soon.

On having a gesture to spell the last word, I will definitely consider that once we nail down the more fundamental set of gestures in the new custom keyboard. One additional thought here is that since you will be able to move the cursor, maybe always spelling the current word after the cursor moves could provide a happy medium, where there’s no extra gesture, and you can keep the spell words turned off. Moving the cursor back and then forward again would effectively be the gesture to both read back as well as spell the last entered word. Would love to hear thoughts on that.

Kosta


Re: To those testing the system wide keyboard

 

Kosta,

Many thanks for the quick reply and I apologize for asking a question you no doubt addressed previously. I'm just having a hard time delineating what feels like two separate apps housed in one. This is probably leftover from my previous Fleksy experience.

I'll get to testing the system wide FlickType keyboard.

Alan Lemly

On Apr 27, 2018, at 1:57 PM, FlickType <hello@flicktype.com> wrote:

Hi Alan, build 50 simply includes the additional custom keyboard, so you’ll still be able to use the main app as usual. This will always be the case.

Also in case you were not aware, you can always revert back to a previous build from TestFlight.

-Kosta



Re: To those testing the system wide keyboard

Chuck Dean
 

Yes, the FlickType app is available and running perfectly.

Chuck

On Apr 27, 2018, at 11:46 AM, Alan Lemly <walemly@gmail.com> wrote:

Would one of you who have already installed and are testing the system wide FlickType keyboard build 1.1-50 let me know if you still have access to the original FlickType keyboard app? I've already posted this question once but have yet to see a reply.

Thanks.

Alan Lemly



Re: Flick type doesn't show on iPad

 

Lack of iPad support for the custom keyboard was not intentional. Thanks for the feedback, I will address that hopefully with the next release.
Kosta


Re: To those testing the system wide keyboard

 

Hi Alan, build 50 simply includes the additional custom keyboard, so you’ll still be able to use the main app as usual. This will always be the case.

Also in case you were not aware, you can always revert back to a previous build from TestFlight.

-Kosta


To those testing the system wide keyboard

 

Would one of you who have already installed and are testing the system wide FlickType keyboard build 1.1-50 let me know if you still have access to the original FlickType keyboard app? I've already posted this question once but have yet to see a reply.

Thanks.

Alan Lemly


Re: Flick type doesn't show on iPad

Chuck Dean
 

Hi George,
I noticed that build 50 isn't on my iPad mini 2 either. I think the iPhone is the primary target and the iPad will be supported eventually.

Chuck

On Apr 27, 2018, at 11:33 AM, George Cham <George.cham@hotmail.com> wrote:

Hi costa,
Do you have any idea why the built 50 system wide keyboard is not showing up on my I pad pro, and therefore I can not access the system keyboard?
Its working ok on my I phone 8.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@gmail.com>
Sent: Friday, April 27, 2018 5:35:56 PM
To: Alpha
Subject: [FlickType-alpha] Flick type doesn't show on iPad


I tried installing flick type on my iPad mini two, when I went to settings it wasn't their. I did the same procedure as I did on the iPhone. I notice when I type incorrectly and swipe left to erase, sometimes the previous word is also deleted. I also noticed the word flick type is not in the app

Chuck







Re: Flick type doesn't show on iPad

George Cham
 

Hi costa,
Do you have any idea why the built 50 system wide keyboard is not showing up on my I pad pro, and therefore I can not access the system keyboard?
Its working ok on my I phone 8.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@gmail.com>
Sent: Friday, April 27, 2018 5:35:56 PM
To: Alpha
Subject: [FlickType-alpha] Flick type doesn't show on iPad


I tried installing flick type on my iPad mini two, when I went to settings it wasn't their. I did the same procedure as I did on the iPhone. I notice when I type incorrectly and swipe left to erase, sometimes the previous word is also deleted. I also noticed the word flick type is not in the app

Chuck


Re: Introducing the FlickType custom keyboard

Chanelle Allen
 

Thank you, costa and Ashley, for getting the FlickType keyboard ready so quickly for us to test. I have not encountered glitches other than those stated in your introductory message. I am enjoying putting the new keyboard through its paces. :)
One slightly annoying nuisance occurs when I dismiss the keyboard after typing a text message. I cannot find the send button unless I double tap the text edit field and then either flick right or look for the send button. My work around is to press and hold on an area of the keyboard near where I think the send button should be and then move my finger around until I find it. I am not sure as to whether FlickType is set to behave differently or if I am experiencing a bug, but I cannot seen to get it through my head that deleting a partial word also deletes the previous word. Also, in regards to typing, as a result of writing this email, I am noticing that I need to be a bit more accurate with my typing or finger placement than I did when using the stand-alone FlickType app. This is especially noticeable when words have letters close together. Of course, making the observation in the last few sentences and writing it down has inadvertently caused FlickType to behave. I appreciate the fact though that FlickType now offers more word suggestions.
In case people are still wondering how to enter a new line, we need to find the return key as if pressing and holding to enter a letter manually.
I completely understand the need to access search suggestions and other parts of apps which the full-screen FlickType keyboard hides. However, my concern is that I could accidentally touch a part of an app screen or activate a button without meaning to do so if FlickType occupied only half of the screen. The great advantage of FlickType is that where my finger taps the keyboard does not need to be totally accurate —I just need to aim in the general direction of a Qwerty layout. Even though I am able to picture a computer keyboard, I struggle with spatial orientation and judging distances. That being said, I still think that testing FlickType as a half screen keyboard would be an interesting experiment. I am not sure if it makes a difference, but I prefer to use my phone and type with both FlickType and the standard keyboard in portrait orientation so that I can hold my phone with one hand. Chanelle

On Apr 27, 2018, at 12:03, FlickType <hello@flicktype.com> wrote:

Some folks in this group were not added to the TestFlight alpha group. Sorry about that, you should all have build 50 on TestFlight now. If not, please let us know. More to come soon.

Thanks!
Kosta



Re: Introducing the FlickType custom keyboard

Salman Haider
 

Yes, I see it there now.
Thanks. Will try it out soon.

On 4/27/18, FlickType <hello@flicktype.com> wrote:
Some folks in this group were not added to the TestFlight alpha group. Sorry
about that, you should all have build 50 on TestFlight now. If not, please
let us know. More to come soon.

Thanks!
Kosta



--
Muhammad Salman Haider
(765) 586-6840


Re: Introducing the FlickType custom keyboard

Chuck Dean
 

Please remember that this is the very first alpha version... Which is very rough and buggy. As with the stand alone app, this will be greatly improved in the near future.
As an alpha tester let the developers know where you are having problems and how you think it can be improved.
At this time, this build is not refined enough to use as a default keyboard.

Chuck

On Apr 27, 2018, at 10:38 AM, Dan Lococo <dan.lococo@gmail.com> wrote:

If I can get my head around this keyboard, I think I'll like it. The
problem is that there seems to be a big learning curve associated with
using this as a third party keyboard. I know I can do that bud I don't know
that it's worth the effort. I'm probably wrong about that. The trade-off is
having to climb the learning curve with a number of apps or just get
proficient at the native fliptype keyboard along with the swipe of and
export to my favorite apps. I'm not sure where I'll fall on this one. One
thing is certain: the developers of this keyboard are amazing and have
produced a fantastic tool. Please, please, know your work is greatly
appreciated. Thank you and thank you again.
On Fri, Apr 27, 2018 at 12:07 AM FlickType <hello@flicktype.com> wrote:

We are super excited to share with you the first ever version of the
FlickType custom keyboard, which can be used inside every app. We really
can't wait to hear what you all think! Smile.

Please note: this is a very early version. We expect to go through many
iterations and significant changes before even releasing this to the wider
beta group. Things to keep in mind:

- As soon as you update to this build, you must first launch the FlickType
app once before attempting to use it as a custom keyboard.
- To install as a custom keyboard, go to the iOS Settings, FlickType,
Keyboard and turn it on.
- To use, go to any textfield such as a note or mail field and double tap
to edit. Switch to FlickType from the "Next keyboard" icon towards the
bottom left of the iOS keyboard.
- To dismiss FlickType, flick down with two fingers. This gesture may
change.
- To control the cursor, flick left or right with two fingers. Currently
the cursor moves one word or punctuation at a time. You can also edit the
selected suggestion of previously typed words or punctuation marks.
- There is currently no way to explore the keyboard and type characters
accurately. Instead, the usual tap and hold will switch you back to the iOS
keyboard where you can perform that task and come back. This also means
there is no custom dictionary management at the moment, and your existing
words will not work yet.
- There are no settings to configure, neither is any functionality of the
main app settings present, such as spelling or raise to read back.
- Fast typing with multiple fingers may result in missed taps.
- Tap sound effects are a bit delayed as they play on touch up rather than
touch down.
- Flick gestures do not have any sound effects.
- There is no flick left and hold gesture to delete faster.
- The first ever word you type may take a couple of seconds to be
announced.
- When beginning to edit a textfield with existing text, only the current
sentence will be editable within FlickType. You may hear "beginning of
document" or "end of document" as you navigate using the cursor. This does
not necessarily indicate there is no more text in the textfield, you just
can't navigate to it right from within FlickType.
- There is no keyboard displayed on the screen.
- Works in landscape mode.

There's probably a lot more things that are missing or different. By
becoming more integrated into your flow, there's also a lot of things that
we are looking to learn from this release. Please experiment as much as
possible, tell us what works well, but also tell us what the biggest pain
points are. Finally, this is completely uncharted territory, so besides
positive and negative feedback we are also hoping to hear your more general
ideas about what the ideal FlickType custom keyboard could be, so that we
can make it happen.

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

Warmly,
Kosta & Ashley



--
Dan Lococo
414.333.5846



Re: Introducing the FlickType custom keyboard

Dan Lococo
 

If I can get my head around this keyboard, I think I'll like it. The
problem is that there seems to be a big learning curve associated with
using this as a third party keyboard. I know I can do that bud I don't know
that it's worth the effort. I'm probably wrong about that. The trade-off is
having to climb the learning curve with a number of apps or just get
proficient at the native fliptype keyboard along with the swipe of and
export to my favorite apps. I'm not sure where I'll fall on this one. One
thing is certain: the developers of this keyboard are amazing and have
produced a fantastic tool. Please, please, know your work is greatly
appreciated. Thank you and thank you again.
On Fri, Apr 27, 2018 at 12:07 AM FlickType <hello@flicktype.com> wrote:

We are super excited to share with you the first ever version of the
FlickType custom keyboard, which can be used inside every app. We really
can't wait to hear what you all think! Smile.

Please note: this is a very early version. We expect to go through many
iterations and significant changes before even releasing this to the wider
beta group. Things to keep in mind:

- As soon as you update to this build, you must first launch the FlickType
app once before attempting to use it as a custom keyboard.
- To install as a custom keyboard, go to the iOS Settings, FlickType,
Keyboard and turn it on.
- To use, go to any textfield such as a note or mail field and double tap
to edit. Switch to FlickType from the "Next keyboard" icon towards the
bottom left of the iOS keyboard.
- To dismiss FlickType, flick down with two fingers. This gesture may
change.
- To control the cursor, flick left or right with two fingers. Currently
the cursor moves one word or punctuation at a time. You can also edit the
selected suggestion of previously typed words or punctuation marks.
- There is currently no way to explore the keyboard and type characters
accurately. Instead, the usual tap and hold will switch you back to the iOS
keyboard where you can perform that task and come back. This also means
there is no custom dictionary management at the moment, and your existing
words will not work yet.
- There are no settings to configure, neither is any functionality of the
main app settings present, such as spelling or raise to read back.
- Fast typing with multiple fingers may result in missed taps.
- Tap sound effects are a bit delayed as they play on touch up rather than
touch down.
- Flick gestures do not have any sound effects.
- There is no flick left and hold gesture to delete faster.
- The first ever word you type may take a couple of seconds to be
announced.
- When beginning to edit a textfield with existing text, only the current
sentence will be editable within FlickType. You may hear "beginning of
document" or "end of document" as you navigate using the cursor. This does
not necessarily indicate there is no more text in the textfield, you just
can't navigate to it right from within FlickType.
- There is no keyboard displayed on the screen.
- Works in landscape mode.

There's probably a lot more things that are missing or different. By
becoming more integrated into your flow, there's also a lot of things that
we are looking to learn from this release. Please experiment as much as
possible, tell us what works well, but also tell us what the biggest pain
points are. Finally, this is completely uncharted territory, so besides
positive and negative feedback we are also hoping to hear your more general
ideas about what the ideal FlickType custom keyboard could be, so that we
can make it happen.

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

Warmly,
Kosta & Ashley



--
Dan Lococo
414.333.5846


Build 50

Chuck Dean
 

Build 50
I am rethinking my opposition to a half screen keyboard. I can now see where it may be useful.
In the Fleksy app a minimal keyboard is available which is a half screen keyboard. I used it for a long time, and it worked well, its main flaw was an inability to switch keyboards easily and consistently. It had a two step process that was hit or miss. Otherwise, the keyboard worked well... Until about a year ago when for some reason the word predictions were failing. Every word I typed was wrong and it took two or more swipes to find the correct word.

Perhaps, in the future, FlickType could have a toggle for a full or half screen keyboard?

Another major flaw with the minimal Fleksy keyboard was the new line button was also a long press to bring up an emoji keyboard, so about 80% of the time I was in the wrong keyboard. :)


Chuck


Re: Introducing the FlickType custom keyboard

 

Some folks in this group were not added to the TestFlight alpha group. Sorry about that, you should all have build 50 on TestFlight now. If not, please let us know. More to come soon.

Thanks!
Kosta


Ignore my last email...

Chuck Dean
 

I just realized that swipe left and hold gesture to erase more than one word isn't working at this time.

I think we need a way to review the text while typing, like the raise to speak feature. I didn't realize how much I use it, but I am placing my hand over the microphone a lot.

Chuck


Re: Introducing the FlickType custom keyboard

Paul Sutton
 

Hi, the only thing I can suggest is close down test flight and reopen it. If that doesn't work close it down again, switch off your phone, turn it back on and then try test flight again. Hope this helps.

On 27 Apr 2018, at 17:48, Michael Maslo <michaelmaslo04@gmail.com> wrote:




I also had the same problem. Can somebody help








On Apr 27, 2018 at 10:47, <Benny Barber (mailto:rebelben@bellsouth.net)> wrote:



Kosta,

I can't give you any feedback because I cannot access build 50 through test flight. It only shows build 45 available. I was added to the alpha group from the beta group. Thanks

Benny

On Apr 27, 2018, at 12:07 AM, FlickType <hello@flicktype.com> wrote:

We are super excited to share with you the first ever version of the FlickType custom keyboard, which can be used inside every app. We really can't wait to hear what you all think! Smile.

Please note: this is a very early version. We expect to go through many iterations and significant changes before even releasing this to the wider beta group. Things to keep in mind:

- As soon as you update to this build, you must first launch the FlickType app once before attempting to use it as a custom keyboard.
- To install as a custom keyboard, go to the iOS Settings, FlickType, Keyboard and turn it on.
- To use, go to any textfield such as a note or mail field and double tap to edit. Switch to FlickType from the "Next keyboard" icon towards the bottom left of the iOS keyboard.
- To dismiss FlickType, flick down with two fingers. This gesture may change.
- To control the cursor, flick left or right with two fingers. Currently the cursor moves one word or punctuation at a time. You can also edit the selected suggestion of previously typed words or punctuation marks.
- There is currently no way to explore the keyboard and type characters accurately. Instead, the usual tap and hold will switch you back to the iOS keyboard where you can perform that task and come back. This also means there is no custom dictionary management at the moment, and your existing words will not work yet.
- There are no settings to configure, neither is any functionality of the main app settings present, such as spelling or raise to read back.
- Fast typing with multiple fingers may result in missed taps.
- Tap sound effects are a bit delayed as they play on touch up rather than touch down.
- Flick gestures do not have any sound effects.
- There is no flick left and hold gesture to delete faster.
- The first ever word you type may take a couple of seconds to be announced.
- When beginning to edit a textfield with existing text, only the current sentence will be editable within FlickType. You may hear "beginning of document" or "end of document" as you navigate using the cursor. This does not necessarily indicate there is no more text in the textfield, you just can't navigate to it right from within FlickType.
- There is no keyboard displayed on the screen.
- Works in landscape mode.

There's probably a lot more things that are missing or different. By becoming more integrated into your flow, there's also a lot of things that we are looking to learn from this release. Please experiment as much as possible, tell us what works well, but also tell us what the biggest pain points are. Finally, this is completely uncharted territory, so besides positive and negative feedback we are also hoping to hear your more general ideas about what the ideal FlickType custom keyboard could be, so that we can make it happen.

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

Warmly,
Kosta & Ashley







Build 50

Chuck Dean
 

Build 50
Hello, if I am switching between keyboards, and want to erase some text, I can only erase the text typed since the FlickType keyboard was continued. Its as if each time I switch keyboards a new session is launched.
Just an observation, no big deal.


Chuck


Re: Introducing the FlickType custom keyboard

Michael Maslo
 

I also had the same problem. Can somebody help


On Apr 27, 2018 at 10:47, <Benny Barber (mailto:rebelben@bellsouth.net)> wrote:



Kosta,

I can't give you any feedback because I cannot access build 50 through test flight. It only shows build 45 available. I was added to the alpha group from the beta group. Thanks

Benny

On Apr 27, 2018, at 12:07 AM, FlickType <hello@flicktype.com> wrote:

We are super excited to share with you the first ever version of the FlickType custom keyboard, which can be used inside every app. We really can't wait to hear what you all think! Smile.

Please note: this is a very early version. We expect to go through many iterations and significant changes before even releasing this to the wider beta group. Things to keep in mind:

- As soon as you update to this build, you must first launch the FlickType app once before attempting to use it as a custom keyboard.
- To install as a custom keyboard, go to the iOS Settings, FlickType, Keyboard and turn it on.
- To use, go to any textfield such as a note or mail field and double tap to edit. Switch to FlickType from the "Next keyboard" icon towards the bottom left of the iOS keyboard.
- To dismiss FlickType, flick down with two fingers. This gesture may change.
- To control the cursor, flick left or right with two fingers. Currently the cursor moves one word or punctuation at a time. You can also edit the selected suggestion of previously typed words or punctuation marks.
- There is currently no way to explore the keyboard and type characters accurately. Instead, the usual tap and hold will switch you back to the iOS keyboard where you can perform that task and come back. This also means there is no custom dictionary management at the moment, and your existing words will not work yet.
- There are no settings to configure, neither is any functionality of the main app settings present, such as spelling or raise to read back.
- Fast typing with multiple fingers may result in missed taps.
- Tap sound effects are a bit delayed as they play on touch up rather than touch down.
- Flick gestures do not have any sound effects.
- There is no flick left and hold gesture to delete faster.
- The first ever word you type may take a couple of seconds to be announced.
- When beginning to edit a textfield with existing text, only the current sentence will be editable within FlickType. You may hear "beginning of document" or "end of document" as you navigate using the cursor. This does not necessarily indicate there is no more text in the textfield, you just can't navigate to it right from within FlickType.
- There is no keyboard displayed on the screen.
- Works in landscape mode.

There's probably a lot more things that are missing or different. By becoming more integrated into your flow, there's also a lot of things that we are looking to learn from this release. Please experiment as much as possible, tell us what works well, but also tell us what the biggest pain points are. Finally, this is completely uncharted territory, so besides positive and negative feedback we are also hoping to hear your more general ideas about what the ideal FlickType custom keyboard could be, so that we can make it happen.

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

Warmly,
Kosta & Ashley






Re: Built 50

Chuck Dean
 

When you need to return to the app you are typing in, simply tap and hold anywhere on the screen to diminish the FlickType keyboard and switch to another keyboard. Then after you do what you need to do, go to the switch keyboard button and open FlickType again.
This will be a new way to type., so we need to think outside the box. :)

Chuck

On Apr 27, 2018, at 8:43 AM, Ed Worrell <ed.worrell@icloud.com> wrote:



the point of flicktype is to type quickly and efficiently. I believe there should maybe be an option to make the keyboard half scream. To some the extra gestures slow down the experience. Just my thoughts. Ed
On Apr 27, 2018, at 9:29 AM, Chuck Dean <cadean329@gmail.com> wrote:

Built 50
Hello, I have been using the system wide keyboard for a while and I thought of the following:
I would like to see the two finger swipe down to return as the add a new line gesture. I keep doing it by habit.
The two finger swipe left and right to move the cursor works well, but I would also like these gestures to be returned to their previous jobs. I don't think I'll be moving the cursor very often, so a different gesture, like a three finger swipe, or double tap and hold may be a better option. When using the stand alone app I use the two finger swipe up to invoke the menu, so I think this would be a better choice for closing FlickType instead of the two finger swipe down.

I disagree with those who want the keyboard to take half the screen, I think they are missing the point of FlickType. In those situations when they must see the screen they can revert back to the iOS keyboard.


Thanks for all your good work,


Chuck





Build 50

Chuck Dean
 

Build 50
Hello, I really like the tap and hold to switch keyboards, but I realize this will interfere with manual text input. One of the reasons I didn't use the Fleksy system wide keyboard in minimal mode was it was too hard to go back to the iOS keyboard.
I would like to see a similar simple gesture in the future to accomplish this task perhaps the flick down and hold gesture? This particular task is very important to me. Many times I need to go to the iOS keyboard, if this can't be accomplished easily and consistently, I see myself staying with the stand alone keyboard.
Thanks,


Chuck

1901 - 1920 of 2168