Date   

Re: Introducing the FlickType custom keyboard

Chuck Dean
 

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

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

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



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

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

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

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

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

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

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

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


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

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

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

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








Re: Introducing the FlickType custom keyboard

Chuck Dean
 

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

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

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

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

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

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

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

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

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


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

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

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

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







Re: Introducing the FlickType custom keyboard

David Nason
 

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

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

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

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

Dave

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

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

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


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

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

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

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






Re: Introducing the FlickType custom keyboard

Chuck Dean
 

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

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


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

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

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

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





Re: Introducing the FlickType custom keyboard

Paul Sutton
 

stupidly I forgot about accessing the suggestion list. Your right, the single swipe down does indeed need to be left as it is.

On 1 May 2018, at 20:24, Chuck Dean <cadean329@gmail.com> wrote:

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

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

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




Re: Introducing the FlickType custom keyboard

Chuck Dean
 

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

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

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



Re: Introducing the FlickType custom keyboard

Chuck Dean
 

On May 1, 2018, at 12:13 PM, Ed Worrell <ed.worrell@icloud.com> wrote:

Hey Paul and Listers,

I agree with this suggestion. I think that is a very elegant way to solve the gesture dilemma.

Ed

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

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




What gesture would be used for going through the additional suggestions?


Re: Introducing the FlickType custom keyboard

Ed Worrell
 

Hey Paul and Listers,

I agree with this suggestion. I think that is a very elegant way to solve the gesture dilemma.

Ed

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

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



The custom keyboard would need some type of cursor control.

Chuck Dean
 

The custom keyboard would need some type of cursor control.
Hello, I have been sending emails and messages with the custom keyboard. If it is a full screen keyboard; there will be a need for some type of cursor control, like a tab key with voice feedback so we will know where we are typing.
Especially in emails, entering the contact, subject, and text body; the keyboard has to be dismissed each time.

Chuck


Re: Introducing the FlickType custom keyboard

Paul Sutton
 

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


Build 50 system keyboard

George Cham
 

After using the system keyboard, I think a dictionary should be added, because there are words that the app does not recognise.


Get Outlook for iOS<https://aka.ms/o0ukef>


Re: Joining Alpha TestFlight Channel

Matthew Janusauskas
 

Hi Kosta,

Yes, the build did finally show up in TestFlight. When I was seeing the emails but not the build I thought I might have been on the beta distribution channel in TestFlight. Sorry for my confusion.

The system-wide extension appears to already be off to an excellent start and I am excited for what is to come!

Regards,

Matthew

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

Hi Matthew,

It looks like you're already part of the alpha group on TestFlight. Did you receive build 50 on TestFlight? Also, are you receiving the related emails about the new custom keyboard version since yesterday?

Kosta



Re: Introducing the FlickType custom keyboard

Alex Hiironen
 

Hey, all,
If possible I'd love to see a forced landscape mode?

I used Braille screen input in landscape but have my orientation locked to ensure everything else is portrait.

SO far, this keyboard is just great. I'm excited for what's to come.

Cheers,
Alex


Re: Built 50

Santiago
 

I personally would prefer to use it as a half screen keyboard, especially when opening apps that automatically launch the keyboard, such as What'sApp, Messenger, and sometimes, Messages.

On Apr 28, 2018, at 9:40 AM, Salman Haider <salmanhaider.purdue@gmail.com> wrote:

Hi Kosta and everyone else,

I personally agree with the option of having both a full screen as
well as a half screen keyboard available, with a gesture to switch
between them being introduced. I can see the pros and cons for both so
having the option available would provide for a happy medium.
Back in the day, once Fleksy was introduced as a system wide keyboard,
among the gazillion issues it had, one of the issues I remember I
always had with the half screen keyboard was, Voiceover focus
frequently jumping out of the keyboard area when attempting to type,
as my finger could sometimes hit a spot outside of the top row of keys
by mistake. I think a full screen keyboard does allow for more leeway
in that regard, since even with that happening, the FlickType
prediction engine still determines what word you meant to type.
But the half screen keyboard may be a little less forgiving in that regard.
Sure, like anything, one could and should be able to get more
comfortable and accurate with it over time, but its still something to
consider.
That said, as many have pointed out, a half screen keyboard would be
useful in reviewing typed text. Although, I think introducing various
gestures in the full screen version to do so, should take care of that
too.
Also, not to forget, the full screen keyboard may be more suitable for
low vision users like you said in your message, for the ideas that you
have for it.

As far as the gesture to dismiss the keyboard is concerned, I prefer
the two finger swipe down gesture as it is the direction that the
keyboard moves to when dismissed.

For entering a new line, here's a suggestion. How about a one finger
swipe right and hold? This was implemented in the older Fleksy if I
remember correctly, and I personally found it to be quite convenient.
Would be interesting to hear your and everyone else's opinions on that.

One thing I have noticed is, going back and forth between keyboards is
somewhat inconsistent. When I perform the current tap and hold gesture
to return to the iOS keyboard, sometimes, I get taken to the Emoji
keyboard, other times I get taken to the regular iOS keyboard.
I don't think this is a FlickType issue. Rather it probably has to do
with the implementation of the third party keyboard functionality in
iOS itself. Do you have any suggestion or advice on how I can achieve
some sense of consistency in this regard?
I have also reorderd my keyboards under the Keyboards option in
Settings, but this still seems to happen.

Thanks,

Salman

On 4/27/18, FlickType <hello@flicktype.com> wrote:
Thank you for the feedback.

A gesture for entering new line will be added soon. Regarding the gesture to
dismiss, and how it is different from the main app, my thinking is that we
should experiment starting from a blank state and not be tied to how things
are currently done in the main app. In fact, it’s very possible that some
things will change in the main app to reflect our findings from the custom
keyboard, because I agree that they should be unified. As some have already
pointed out, flicking down with two fingers seems more appropriate since
this is the direction where the keyboard moves towards when it is dismissed,
but I am definitely open to hearing arguments on why the flick up might be
more appropriate.

On having an option to make the keyboard half screen rather than full
screen, it’s definitely something we’d like to offer as soon as the full
screen experience becomes usable and reliable, because it simplifies a lot
of things on the development side. I’ve also previously expressed my opinion
that full screen would generally be a better experience, but if this proves
to be such a popular request we might even make the default be half screen
with the option of making it full screen. To determine that we will probably
need to get feedback from the larger beta group, and the key might be to
provide an easy gesture to change that on the fly, like a three finger flick
up or down. Another related factor here is that I have some ideas on how to
further help folks that have some vision, and this would require FlickType
to be full screen.

Kosta




--
Muhammad Salman Haider
(765) 586-6840



Re: Built 50

Chuck Dean
 

Hello,
The reason I changed my mind and came over to the half screen idea started when I tried to send an email with the custom keyboard. I had to dismiss the keyboard to put the cursor in the recipients box, then I used FlickType to enter the contact. Then I had to dismiss the keyboard to change the focus to the subject, and then bring it back to fill in the subject line.
Again I had to dismiss the keyboard to change the cursor focus to the text body.
I don't know of any other way to do this... Unless I am missing something.

Chuck

On Apr 28, 2018, at 9:40 AM, Salman Haider <salmanhaider.purdue@gmail.com> wrote:

Hi Kosta and everyone else,

I personally agree with the option of having both a full screen as
well as a half screen keyboard available, with a gesture to switch
between them being introduced. I can see the pros and cons for both so
having the option available would provide for a happy medium.
Back in the day, once Fleksy was introduced as a system wide keyboard,
among the gazillion issues it had, one of the issues I remember I
always had with the half screen keyboard was, Voiceover focus
frequently jumping out of the keyboard area when attempting to type,
as my finger could sometimes hit a spot outside of the top row of keys
by mistake. I think a full screen keyboard does allow for more leeway
in that regard, since even with that happening, the FlickType
prediction engine still determines what word you meant to type.
But the half screen keyboard may be a little less forgiving in that regard.
Sure, like anything, one could and should be able to get more
comfortable and accurate with it over time, but its still something to
consider.
That said, as many have pointed out, a half screen keyboard would be
useful in reviewing typed text. Although, I think introducing various
gestures in the full screen version to do so, should take care of that
too.
Also, not to forget, the full screen keyboard may be more suitable for
low vision users like you said in your message, for the ideas that you
have for it.

As far as the gesture to dismiss the keyboard is concerned, I prefer
the two finger swipe down gesture as it is the direction that the
keyboard moves to when dismissed.

For entering a new line, here's a suggestion. How about a one finger
swipe right and hold? This was implemented in the older Fleksy if I
remember correctly, and I personally found it to be quite convenient.
Would be interesting to hear your and everyone else's opinions on that.

One thing I have noticed is, going back and forth between keyboards is
somewhat inconsistent. When I perform the current tap and hold gesture
to return to the iOS keyboard, sometimes, I get taken to the Emoji
keyboard, other times I get taken to the regular iOS keyboard.
I don't think this is a FlickType issue. Rather it probably has to do
with the implementation of the third party keyboard functionality in
iOS itself. Do you have any suggestion or advice on how I can achieve
some sense of consistency in this regard?
I have also reorderd my keyboards under the Keyboards option in
Settings, but this still seems to happen.

Thanks,

Salman

On 4/27/18, FlickType <hello@flicktype.com> wrote:
Thank you for the feedback.

A gesture for entering new line will be added soon. Regarding the gesture to
dismiss, and how it is different from the main app, my thinking is that we
should experiment starting from a blank state and not be tied to how things
are currently done in the main app. In fact, it’s very possible that some
things will change in the main app to reflect our findings from the custom
keyboard, because I agree that they should be unified. As some have already
pointed out, flicking down with two fingers seems more appropriate since
this is the direction where the keyboard moves towards when it is dismissed,
but I am definitely open to hearing arguments on why the flick up might be
more appropriate.

On having an option to make the keyboard half screen rather than full
screen, it’s definitely something we’d like to offer as soon as the full
screen experience becomes usable and reliable, because it simplifies a lot
of things on the development side. I’ve also previously expressed my opinion
that full screen would generally be a better experience, but if this proves
to be such a popular request we might even make the default be half screen
with the option of making it full screen. To determine that we will probably
need to get feedback from the larger beta group, and the key might be to
provide an easy gesture to change that on the fly, like a three finger flick
up or down. Another related factor here is that I have some ideas on how to
further help folks that have some vision, and this would require FlickType
to be full screen.

Kosta




--
Muhammad Salman Haider
(765) 586-6840



Re: Built 50

Salman Haider
 

Hi Kosta and everyone else,

I personally agree with the option of having both a full screen as
well as a half screen keyboard available, with a gesture to switch
between them being introduced. I can see the pros and cons for both so
having the option available would provide for a happy medium.
Back in the day, once Fleksy was introduced as a system wide keyboard,
among the gazillion issues it had, one of the issues I remember I
always had with the half screen keyboard was, Voiceover focus
frequently jumping out of the keyboard area when attempting to type,
as my finger could sometimes hit a spot outside of the top row of keys
by mistake. I think a full screen keyboard does allow for more leeway
in that regard, since even with that happening, the FlickType
prediction engine still determines what word you meant to type.
But the half screen keyboard may be a little less forgiving in that regard.
Sure, like anything, one could and should be able to get more
comfortable and accurate with it over time, but its still something to
consider.
That said, as many have pointed out, a half screen keyboard would be
useful in reviewing typed text. Although, I think introducing various
gestures in the full screen version to do so, should take care of that
too.
Also, not to forget, the full screen keyboard may be more suitable for
low vision users like you said in your message, for the ideas that you
have for it.

As far as the gesture to dismiss the keyboard is concerned, I prefer
the two finger swipe down gesture as it is the direction that the
keyboard moves to when dismissed.

For entering a new line, here's a suggestion. How about a one finger
swipe right and hold? This was implemented in the older Fleksy if I
remember correctly, and I personally found it to be quite convenient.
Would be interesting to hear your and everyone else's opinions on that.

One thing I have noticed is, going back and forth between keyboards is
somewhat inconsistent. When I perform the current tap and hold gesture
to return to the iOS keyboard, sometimes, I get taken to the Emoji
keyboard, other times I get taken to the regular iOS keyboard.
I don't think this is a FlickType issue. Rather it probably has to do
with the implementation of the third party keyboard functionality in
iOS itself. Do you have any suggestion or advice on how I can achieve
some sense of consistency in this regard?
I have also reorderd my keyboards under the Keyboards option in
Settings, but this still seems to happen.

Thanks,

Salman

On 4/27/18, FlickType <hello@flicktype.com> wrote:
Thank you for the feedback.

A gesture for entering new line will be added soon. Regarding the gesture to
dismiss, and how it is different from the main app, my thinking is that we
should experiment starting from a blank state and not be tied to how things
are currently done in the main app. In fact, it’s very possible that some
things will change in the main app to reflect our findings from the custom
keyboard, because I agree that they should be unified. As some have already
pointed out, flicking down with two fingers seems more appropriate since
this is the direction where the keyboard moves towards when it is dismissed,
but I am definitely open to hearing arguments on why the flick up might be
more appropriate.

On having an option to make the keyboard half screen rather than full
screen, it’s definitely something we’d like to offer as soon as the full
screen experience becomes usable and reliable, because it simplifies a lot
of things on the development side. I’ve also previously expressed my opinion
that full screen would generally be a better experience, but if this proves
to be such a popular request we might even make the default be half screen
with the option of making it full screen. To determine that we will probably
need to get feedback from the larger beta group, and the key might be to
provide an easy gesture to change that on the fly, like a three finger flick
up or down. Another related factor here is that I have some ideas on how to
further help folks that have some vision, and this would require FlickType
to be full screen.

Kosta



--
Muhammad Salman Haider
(765) 586-6840


Re: Introducing the FlickType custom keyboard

Benny Barber
 

I guess this has been mentioned, but when I delete a partial word, the previous word is deleted as well. Thanks

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: Introducing the FlickType custom keyboard

Benny Barber
 

OK, I have just started playing with build 50. I started using it in the
notes app. I typed a few words and exited FlickType with the 2 finger flick
down. When I returned to the notes app, I noticed the iOS cursor is at the
beginning of the text written. I then returned to FlickType and the cursor
is at the beginning of the text there as well. To continue typing at the
correct place, I have to advance the cursor to the end of the text. Is this
common with others? Am I doing something wrong? Any assistance please.
Thanks.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, April 27, 2018 12:07 AM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Introducing the FlickType custom keyboard

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

Andrew McKay
 

Hello,

Just concurring with some earlier feedback--One of my most major issues with the first alpha build is that I also highly desire to see a standard size keyboard--AKA half screen. I find the whole screen keyboard very bothersome for reviewing information while typing in a field.

Andrew

-----Original Message-----
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> On Behalf Of FlickType
Sent: Friday, April 27, 2018 3:46 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Built 50

Thank you for the feedback.

A gesture for entering new line will be added soon. Regarding the gesture to dismiss, and how it is different from the main app, my thinking is that we should experiment starting from a blank state and not be tied to how things are currently done in the main app. In fact, it’s very possible that some things will change in the main app to reflect our findings from the custom keyboard, because I agree that they should be unified. As some have already pointed out, flicking down with two fingers seems more appropriate since this is the direction where the keyboard moves towards when it is dismissed, but I am definitely open to hearing arguments on why the flick up might be more appropriate.

On having an option to make the keyboard half screen rather than full screen, it’s definitely something we’d like to offer as soon as the full screen experience becomes usable and reliable, because it simplifies a lot of things on the development side. I’ve also previously expressed my opinion that full screen would generally be a better experience, but if this proves to be such a popular request we might even make the default be half screen with the option of making it full screen. To determine that we will probably need to get feedback from the larger beta group, and the key might be to provide an easy gesture to change that on the fly, like a three finger flick up or down. Another related factor here is that I have some ideas on how to further help folks that have some vision, and this would require FlickType to be full screen.

Kosta


Re: Joining Alpha TestFlight Channel

 

Hi Matthew,

It looks like you're already part of the alpha group on TestFlight. Did you receive build 50 on TestFlight? Also, are you receiving the related emails about the new custom keyboard version since yesterday?

Kosta

1861 - 1880 of 2168