Date   

Joining Alpha TestFlight Channel

Matthew Janusauskas
 

Now that the keyboard extension is ready for testing I would like to switch to the alpha builds channel in TestFlight please.

Regards,

Matthew


Re: Introducing the FlickType custom keyboard

Santiago
 

I agree with most of the points on here. Not to mention, it would be nice to be able to use the Flicktype keyboard without having to go back to the default keyboard.

Santiago

On Apr 27, 2018, at 6:47 PM, Alan Lemly <walemly@gmail.com> wrote:

Hi Kosta and Ashley,



I've played around with the FlickType custom keyboard and will list my comments below. I'm aware that some of what I'll list are stated issues in your below announcement email but you wanted our comments and suggestions on what we feel most strongly about so I'm sure I'll repeat some of your items.



1. The main difficulty I have with the current iteration is not being able to manually type words such as names that aren't in the dictionary. As soon as I rest my finger in order to explore the needed keys to manually enter them, I'm returned to the previous keyboard because the tap and hold gesture is designed to do just that. My preference would be to have a return to previous keyboard gesture that would not interfere with FlickType keyboard exploration and manual letter entry. It would really be nice if this gesture could act as a toggle allowing return to the previous keyboard from FlickType and back again to the FlickType keyboard but I expect Apple would not allow that.

2. I'm struggling a bit understanding when to use the 2 finger swipe down to exit the FlickType keyboard. I guess it is in order to return to a regular iOS screen containing no keyboard but I'm not sure when I'd use this. I believe I've found that tapping and holding on the screen you move to following a 2 finger swipe down will return you to the FlickType keyboard but the hold time seems somewhat longer than required wen doing it from the FlickType keyboard to return to the previous keyboard and it also only seems to work for me when done toward the bottom third of my screen. Again, I'd prefer a gesture that would let you toggle back and forth between the two states rather than two different gestures.

3. The click sound effect I'm getting when typing on the FlickType custom keyboard seems a good bit lower in volume than it is in the standalone FlickType app.

4. I noticed that when in the keyboard settings to review or add additional keyboards, nothing happens when double tapping on the FlickType entry whereas other keyboards open some sort of settings screen. You've mentioned this below so I know you're aware of it.

5. As others have mentioned, I'd prefer a keyboard presentation not unlike how it's presented in the standalone app when accessing the FlickType custom keyboard as opposed to a solid black screen currently being used. I do have some vision so that affects my preference. I don't know how this would impact the presentation of the typed words but I won't be using my vision to read those words so I don't need them to be in such a large font as currently presented. Obviously, those with more vision will have a different take on this.

6. I like how the 2 finger swipe right and left cycles through the typed words but is there a way to cycle through character by character? I expect that character editing might not be FlickType's forte and is probably better done with the iOS standard keyboard but I thought I'd mention it.



Thanks so much for all your hard work in getting the original app and this alpha system wide keyboard out so quickly.



Alan Lemly



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

 

Hi Kosta and Ashley,



I've played around with the FlickType custom keyboard and will list my comments below. I'm aware that some of what I'll list are stated issues in your below announcement email but you wanted our comments and suggestions on what we feel most strongly about so I'm sure I'll repeat some of your items.



1. The main difficulty I have with the current iteration is not being able to manually type words such as names that aren't in the dictionary. As soon as I rest my finger in order to explore the needed keys to manually enter them, I'm returned to the previous keyboard because the tap and hold gesture is designed to do just that. My preference would be to have a return to previous keyboard gesture that would not interfere with FlickType keyboard exploration and manual letter entry. It would really be nice if this gesture could act as a toggle allowing return to the previous keyboard from FlickType and back again to the FlickType keyboard but I expect Apple would not allow that.

2. I'm struggling a bit understanding when to use the 2 finger swipe down to exit the FlickType keyboard. I guess it is in order to return to a regular iOS screen containing no keyboard but I'm not sure when I'd use this. I believe I've found that tapping and holding on the screen you move to following a 2 finger swipe down will return you to the FlickType keyboard but the hold time seems somewhat longer than required wen doing it from the FlickType keyboard to return to the previous keyboard and it also only seems to work for me when done toward the bottom third of my screen. Again, I'd prefer a gesture that would let you toggle back and forth between the two states rather than two different gestures.

3. The click sound effect I'm getting when typing on the FlickType custom keyboard seems a good bit lower in volume than it is in the standalone FlickType app.

4. I noticed that when in the keyboard settings to review or add additional keyboards, nothing happens when double tapping on the FlickType entry whereas other keyboards open some sort of settings screen. You've mentioned this below so I know you're aware of it.

5. As others have mentioned, I'd prefer a keyboard presentation not unlike how it's presented in the standalone app when accessing the FlickType custom keyboard as opposed to a solid black screen currently being used. I do have some vision so that affects my preference. I don't know how this would impact the presentation of the typed words but I won't be using my vision to read those words so I don't need them to be in such a large font as currently presented. Obviously, those with more vision will have a different take on this.

6. I like how the 2 finger swipe right and left cycles through the typed words but is there a way to cycle through character by character? I expect that character editing might not be FlickType's forte and is probably better done with the iOS standard keyboard but I thought I'd mention it.



Thanks so much for all your hard work in getting the original app and this alpha system wide keyboard out so quickly.



Alan Lemly

-----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: Build 50

George Cham
 

Hi, I I'm finding that it I stop typing, to check what I've typed, and go back to the flick type on screen keyboard, the previous sentence is gone.

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<https://aka.ms/qtex0l> for iOS
________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@gmail.com>
Sent: Saturday, April 28, 2018 9:46:18 AM
To: Alpha
Subject: [FlickType-alpha] Build 50

Build 50
I found a bug which may only affect me. If I am typing in portrait mode and switch to landscapemode, the text I typed in portrait mode disappears... Sometimes. I tried to duplicate this and couldn't so I went back to typing and it did it to me again.
As long as I do not change modes everything works fine.
BTW the system wide keyboard types equally as well in landscape mode.


Chuck


Build 50

Chuck Dean
 

Build 50
I found a bug which may only affect me. If I am typing in portrait mode and switch to landscapemode, the text I typed in portrait mode disappears... Sometimes. I tried to duplicate this and couldn't so I went back to typing and it did it to me again.
As long as I do not change modes everything works fine.
BTW the system wide keyboard types equally as well in landscape mode.


Chuck


Re: Single word spell

Chanelle Allen
 

Hi Kosta,
I like your idea. Typing a word did interrupt spelling of the previous word, so nothing was broken on my end. Hearing the spelling sometimes interrupted my train of thought when deciding how to complete a sentence or express an idea, but that is no big deal. I have not disabled the spell words feature in FlickType, and I now have a good reason for leaving it on. I noticed that the word “characters” was spelled with an apostrophe s when typing with the FlickType keyboard and going back over my text. With spell words turned off, the only indication of an apostrophe would come from VoiceOver if punctuation was set to all. Right now, the FlickType keyboard does not spell out words. Having a way for FlickType to indicate whether its suggestions are capitalized or have an apostrophe might be helpful.
Your suggestion of the two finger flick to read and spell back provides a happy medium. As long as a two finger flick would cut off spelling if someone did not want to hear everything spelled back, the gesture could be useful. If a word is incorrect, we could either flick down for suggestions or return to the standard keyboard to fix it. Since we already have a gesture to dismiss the keyboard at the cursor location, we could just use VoiceOver rotor gestures to read the spelling of a word. I was just now able to flick two fingers left, tap and hold to switch back to the regular keyboard and then use the rotor to read back the characters of the last word I typed. The only problem is that not actually typing on the standard keyboard results in the Emoji keyboard being next to come up unless I delete it, which is tempting. I wish that Apple could provide a three finger flick right or left gesture to switch between keyboards or allowed us to create our own gesture to more efficiently switch keyboards and speed up the editing process.
revisiting the read and spell issue might be more beneficial at a later point after a few kings have been worked out and oncewe have had some time to get adjusted to the new keyboard.
Thank you.
Chanelle

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

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: Moving the cursor.

Chuck Dean
 

Ok, sounds good. A contrasting color indicating where the keyboardis located, would be a big help. Also if the home key row, A through L could be a highlighted color, that would also help, me at least, locate the proper area to type. As far as the actual letters on the keys... That would only be helpful to me if each key were 5 inches square. :)

Chuck

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

Thank you Chuck.

You are correct that you cannot type symbols or numbers right now, or enter a new line. These functions will definitely be added soon, once we nail down the fundamentals of typing first.

I am planning to at least make the keyboard area a different color in the next release, so that folks with some limited vision can use it as a cue to improve their accuracy. But it’s nice to know that even with nothing on the screen you can still type quite confidently. Displaying the actual letters of the keyboard on the screen is currently a lower priority.

Kosta



Re: Flick type doesn't show on iPad

George Cham
 

As I said, im impressed with the first alpha version of the system keyboard.
However, I'd like to see a on screen keyboard at the bottom of the app, that you're composing a message or email to just like the fleksy app.

Kind Regards,

George Cham


________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of FlickType <hello@flicktype.com>
Sent: Saturday, April 28, 2018 4:57:55 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] 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: Introducing the FlickType custom keyboard

Paul Sutton
 

Hey, I just wanted to say that I hope that the tap sounds can be fixed as the delay is quite distracting. I do know that you mentioned it when you released build 50 I just wanted to let you know my feeling's on it


Re: To those testing the system wide keyboard

Ed Worrell
 

hello. Yes you still have full access to the current built of the flick type application.

On Apr 27, 2018, at 12:46 PM, 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: Text does not scroll.

Sharon Kim
 

Hello all,
I hope this email finds you well.
Okay so I was a bit slow on the uptake, but I've updated to the latest
version of flicktype.
My only problem with it so far is, that it just generally seems a bit
laggy. Now I know this is something that you guys are probably aware
of, but I just wanted to put it out there. oddly enough, on my first
go, I prefer the app itself, I don't know why though. I guess because
it just seems a bit more responsive. That being said, this is a good
start, because everyone and their uncle wants a system wide keyboard,
myself included, so I'm extremely happy to be testing this.

On 4/27/18, Chuck Dean <cadean329@gmail.com> wrote:
Hi Kosta,
I only noticed that the text did not scroll when I was checking out the
layout under my CCTV, during normal operation I can not read the text on the
screen.
As a matter of fact, I used the Fleksy VO app right up until iOS went to 64
bit. Most of the app's features didn't work, and the text did not show on
the screen, and their was no way to review what I had just typed, but I
could copy and paste with it and it was still faster than the iOS keyboard.

So, I agree, there really is no need to be able to see the text while
typing.

Chuck


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

Thank you Chuck and George.

Even though there is no current way of entering a new line, the displayed
text will wrap at the edge of the screen and break into the next line. But
the underlying text field that you are typing into will not have any new
line.

The text should eventually scroll, thank you for pointing that out. I
should also say that currently, the only reason text is even displayed at
all is so that it’s easier for me to make sure things are working as
expected, smile. But I do have some ideas in this area that can really
help folks with limited vision, more to come soon on that.

Kosta





Re: Built 50

Michael Maslo
 

Hello, I just received beta fifty and I really like it a lot. I have seen a few items which may have been brought up before and if so I apologize. First sometimes when I try to delete a word, it will the I typing plus the word previous. I can type two words and flick to the right to hear the second word. When I flick left to delete the last word I heard deleted the word plus the word before an other words instead of just deleting one word it deleted both words. Secondly, after you make flick type my primary keyboard, it keeps back to a different keyboard when I open app or type a different text or even if I am trying to type a manual word. I hope these issues I have seen make sense.


On Apr 27, 2018 at 14:45, <FlickType (mailto: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




Re: Text does not scroll.

Chuck Dean
 

Hi Kosta,
I only noticed that the text did not scroll when I was checking out the layout under my CCTV, during normal operation I can not read the text on the screen.
As a matter of fact, I used the Fleksy VO app right up until iOS went to 64 bit. Most of the app's features didn't work, and the text did not show on the screen, and their was no way to review what I had just typed, but I could copy and paste with it and it was still faster than the iOS keyboard.
So, I agree, there really is no need to be able to see the text while typing.

Chuck

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

Thank you Chuck and George.

Even though there is no current way of entering a new line, the displayed text will wrap at the edge of the screen and break into the next line. But the underlying text field that you are typing into will not have any new line.

The text should eventually scroll, thank you for pointing that out. I should also say that currently, the only reason text is even displayed at all is so that it’s easier for me to make sure things are working as expected, smile. But I do have some ideas in this area that can really help folks with limited vision, more to come soon on that.

Kosta



Re: Ignore my last email...

 

Thank you Chuck, this is good feedback.

I am hoping that the raise to read back feature will be possible in a custom keyboard, I should know soon.

Kosta


Re: 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: Default keyboard?

 

Almost all issues that you notice are fixable. The main focus right now will be to figure out which are the ones that are not fixable, and figure out what the best workarounds will be.

Regarding FlickType popping up as the default keyboard: I believe this has to do with whatever keyboard was used last in that particular text field. And if you usually end your typing by tapping and holding to switch to the standard keyboard, the standard keyboard will pop up next time you use that text field. But if you instead dismiss it by flicking down with two fingers, next time you type in that field you should have FlickType pop up as the default one. Another related point here is that at least in the past, which keyboard would pop up would sometimes appear to be random, but I think the keyboard iOS API is now better.

Dictionary words are currently unsupported.

Michael, you should now have build 50 available on TestFlight, please let us know if not.

Kosta


Re: Text does not scroll.

 

Thank you Chuck and George.

Even though there is no current way of entering a new line, the displayed text will wrap at the edge of the screen and break into the next line. But the underlying text field that you are typing into will not have any new line.

The text should eventually scroll, thank you for pointing that out. I should also say that currently, the only reason text is even displayed at all is so that it’s easier for me to make sure things are working as expected, smile. But I do have some ideas in this area that can really help folks with limited vision, more to come soon on that.

Kosta


Re: To those testing the system wide keyboard

Chuck Dean
 

My bet.
Hi Kosta and Alan,
I should have reported to the group last night that the app was working perfectly after the build 50 install. I'll try to be more responsive in the future

Chuck

On Apr 27, 2018, at 12:07 PM, Alan Lemly <walemly@gmail.com> wrote:

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: Moving the cursor.

 

Thank you Chuck.

You are correct that you cannot type symbols or numbers right now, or enter a new line. These functions will definitely be added soon, once we nail down the fundamentals of typing first.

I am planning to at least make the keyboard area a different color in the next release, so that folks with some limited vision can use it as a cue to improve their accuracy. But it’s nice to know that even with nothing on the screen you can still type quite confidently. Displaying the actual letters of the keyboard on the screen is currently a lower priority.

Kosta


Re: To those testing the system wide keyboard

Paul Sutton
 

Hi, I am testing 50 and yes, I can access the stand alone app.

On 27 Apr 2018, at 19:46, 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


1881 - 1900 of 2168