Date   
Re: Build 67

Sharon Kim
 

Okay so as of now, I'm a total fan of this newest update.
It makes it so much easier to manually type in a word, much easier
than switching between keyboards and all that.
I love it!!! yes, word echo after hitting space would indeed help, but
I'm sure there will be more changes to come. so far though, I just
have to say brilliant!!! Okay sorry for the raving, I'm done.

On 5/18/18, Benny Barber <rebelben@...> wrote:
Also, can we have word echo after a space? Thanks.

Benny

On May 18, 2018, at 1:03 AM, FlickType <@FlickType> wrote:

This is the very first, and still quite experimental, version of the
manual typing functionality. The approach we are taking is to start from
the basics, and expand as we go. As a first step, we simply bring the
Touch Typing style of the regular iOS keyboard right within FlickType, and
make it fast and easy to toggle between Flick Typing and Touch Typing
using the magic tap gesture. If you are not familiar, a magic tap is a
double tap with two fingers, and is used to perform the so-called
"most-intended" action, regardless of what element the VoiceOver cursor is
currently focused on.

Notes:
- You cannot yet use any flick gestures when Touch Typing, but you will be
able to in the future.
- You can now enter a new line with the Return key, just like with the iOS
keyboard. When you go back to Flick Typing, new lines will currently not
be announced when moving the cursor.
- The voice feedback for entered characters does not have a different
pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in
the main app. We're doing this for a couple of reasons: One is to make it
easier for new users to fall back to a familiar typing style when needed.
Two, manually typing longer words should be easier and faster this way. We
might not be there yet, but this is the reasoning behind the approach.





Build 67

Chuck Dean
 

Hi,
I have been playing with the new manual input, number and symbol entry, and with a few differences? I don't see much advantage with this system over just switching to the iOS keyboard.

The magic tap works very well, and the ability to flick right and left if I accidentally enter a wrong letter is nice, but I still need to go to the iOS keyboard to switch text fields and to send this email.
I understand this is the first incarnation of this feature, and I'm sure it will be improved in future builds, but at this thyme, at least for emails, I still prefer to use the app.

I typed this email with both the custom keyboard and the app, I was much faster with the app, and I could review what I had written with the raise to speak feature.

I also realize I am in the minority with my opinion but dealing with only the app seems more stream line than using three keyboards.


Chuck

Build 67

Chuck Dean
 

Build 67
Hi again,
The two things I really miss with the custom keyboard is the ability to capitalize letters and input lines with a simple gesture.
As I type this in the app, everything is only a simple gesture away.
The custom keyboard is fantastic for entering short amounts of text, and responding to messages and emails, but more than that, I revert to the app.



Chuck

Re: Build 67

Ed Worrell
 

I really feel that this is a very big step backwards from the original keyboard app. The two finger double tap works as described, but it honestly feels like you are trying to reinvent the wheel here. I really am not sure why you simply can’t make the behavior mirror the FlickType app. This style of typing seems like there is way to many steps to manually insert a word. I really am not a fan of this method. The others are correct in it is snappy between keyboards: the gesture keyboard works, manual keyboard works, and the symbols keyboard works. I really wish it was more like the FlickType stand alone application as far as the functionality is concerned.

Ed

On May 18, 2018, at 9:24 AM, Sharon Kim <sharon.mi.kim22@...> wrote:

Okay so as of now, I'm a total fan of this newest update.
It makes it so much easier to manually type in a word, much easier
than switching between keyboards and all that.
I love it!!! yes, word echo after hitting space would indeed help, but
I'm sure there will be more changes to come. so far though, I just
have to say brilliant!!! Okay sorry for the raving, I'm done.

On 5/18/18, Benny Barber <rebelben@...> wrote:
Also, can we have word echo after a space?  Thanks.

Benny

On May 18, 2018, at 1:03 AM, FlickType <hello@...> wrote:

This is the very first, and still quite experimental, version of the
manual typing functionality. The approach we are taking is to start from
the basics, and expand as we go. As a first step, we simply bring the
Touch Typing style of the regular iOS keyboard right within FlickType, and
make it fast and easy to toggle between Flick Typing and Touch Typing
using the magic tap gesture. If you are not familiar, a magic tap is a
double tap with two fingers, and is used to perform the so-called
"most-intended" action, regardless of what element the VoiceOver cursor is
currently focused on.

Notes:
- You cannot yet use any flick gestures when Touch Typing, but you will be
able to in the future.
- You can now enter a new line with the Return key, just like with the iOS
keyboard. When you go back to Flick Typing, new lines will currently not
be announced when moving the cursor.
- The voice feedback for entered characters does not have a different
pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in
the main app. We're doing this for a couple of reasons: One is to make it
easier for new users to fall back to a familiar typing style when needed.
Two, manually typing longer words should be easier and faster this way. We
might not be there yet, but this is the reasoning behind the approach.










Re: Build 67

David Nason
 

I don't like to be negative and I fully understand that this is the first build with manual entry, but as of right now I'm with Ed and Chuck, in not being particularly a fan of the approach.
I don't see any real advantage to switching the mode with the magic tap versus just switching to the standard iOS keyboard. And in fact, I can do the latter with a one finger gesture. I much prefer the approach of the main app, with it all integrated into one. And perhaps that is the long term plan.
Regarding the manual entry itself, I have also been confused by how the shift key works, or announces itself.

Dave
 


On 18 May 2018, at 18:10, Ed Worrell <ed.worrell@...> wrote:

I really feel that this is a very big step backwards from the original keyboard app. The two finger double tap works as described, but it honestly feels like you are trying to reinvent the wheel here. I really am not sure why you simply can’t make the behavior mirror the FlickType app. This style of typing seems like there is way to many steps to manually insert a word. I really am not a fan of this method. The others are correct in it is snappy between keyboards: the gesture keyboard works, manual keyboard works, and the symbols keyboard works. I really wish it was more like the FlickType stand alone application as far as the functionality is concerned.

Ed

On May 18, 2018, at 9:24 AM, Sharon Kim <sharon.mi.kim22@...> wrote:

Okay so as of now, I'm a total fan of this newest update.
It makes it so much easier to manually type in a word, much easier
than switching between keyboards and all that.
I love it!!! yes, word echo after hitting space would indeed help, but
I'm sure there will be more changes to come. so far though, I just
have to say brilliant!!! Okay sorry for the raving, I'm done.

On 5/18/18, Benny Barber <rebelben@...> wrote:
Also, can we have word echo after a space?  Thanks.

Benny

On May 18, 2018, at 1:03 AM, FlickType <hello@...> wrote:

This is the very first, and still quite experimental, version of the
manual typing functionality. The approach we are taking is to start from
the basics, and expand as we go. As a first step, we simply bring the
Touch Typing style of the regular iOS keyboard right within FlickType, and
make it fast and easy to toggle between Flick Typing and Touch Typing
using the magic tap gesture. If you are not familiar, a magic tap is a
double tap with two fingers, and is used to perform the so-called
"most-intended" action, regardless of what element the VoiceOver cursor is
currently focused on.

Notes:
- You cannot yet use any flick gestures when Touch Typing, but you will be
able to in the future.
- You can now enter a new line with the Return key, just like with the iOS
keyboard. When you go back to Flick Typing, new lines will currently not
be announced when moving the cursor.
- The voice feedback for entered characters does not have a different
pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in
the main app. We're doing this for a couple of reasons: One is to make it
easier for new users to fall back to a familiar typing style when needed.
Two, manually typing longer words should be easier and faster this way. We
might not be there yet, but this is the reasoning behind the approach.










Re: Build 67

Macster
 

I agree that having the symbols, numbers etc on the top row in the app is my preferred solution. This is probably partly down to pure habit though. I think using the two finger double tap is much better than going back to the standard keyboard for manual entry. Its quicker and feels more crisp. The problem I had before I took out the emoji keyboard was that the next keyboard button wasn't in the same place on that, it was slightly more to the left. But as an early first version, this works well I think, even if it wasn't the familiar layout I was expecting. I'm sure Kosta will be adding and amending it as we go on so I'm trying to look past my habits. My only gripe is the keyboard echo which drives me up the wall but I'm sure that's a relatively easy fix! A good weekend to one and all. Macky

On 18 May 2018, at 07:03, FlickType <@FlickType> wrote:

This is the very first, and still quite experimental, version of the manual typing functionality. The approach we are taking is to start from the basics, and expand as we go. As a first step, we simply bring the Touch Typing style of the regular iOS keyboard right within FlickType, and make it fast and easy to toggle between Flick Typing and Touch Typing using the magic tap gesture. If you are not familiar, a magic tap is a double tap with two fingers, and is used to perform the so-called "most-intended" action, regardless of what element the VoiceOver cursor is currently focused on.

Notes:
- You cannot yet use any flick gestures when Touch Typing, but you will be able to in the future.
- You can now enter a new line with the Return key, just like with the iOS keyboard. When you go back to Flick Typing, new lines will currently not be announced when moving the cursor.
- The voice feedback for entered characters does not have a different pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in the main app. We're doing this for a couple of reasons: One is to make it easier for new users to fall back to a familiar typing style when needed. Two, manually typing longer words should be easier and faster this way. We might not be there yet, but this is the reasoning behind the approach.


Re: Build 67

Paul Sutton
 

Hi all, to be honest I don't mind performing a magic tap to perform manual entry. For he it's just like flicking to the iOS keyboard but only more easy. Of course it would be quicker to have manual entry on the FlickType screen but I wouldn't mind if that wasn't possible.

On 18 May 2018, at 18:50, Macster <@Macster> wrote:

I agree that having the symbols, numbers etc on the top row in the app is my preferred solution. This is probably partly down to pure habit though. I think using the two finger double tap is much better than going back to the standard keyboard for manual entry. Its quicker and feels more crisp. The problem I had before I took out the emoji keyboard was that the next keyboard button wasn't in the same place on that, it was slightly more to the left. But as an early first version, this works well I think, even if it wasn't the familiar layout I was expecting. I'm sure Kosta will be adding and amending it as we go on so I'm trying to look past my habits. My only gripe is the keyboard echo which drives me up the wall but I'm sure that's a relatively easy fix! A good weekend to one and all. Macky
On 18 May 2018, at 07:03, FlickType <@FlickType> wrote:

This is the very first, and still quite experimental, version of the manual typing functionality. The approach we are taking is to start from the basics, and expand as we go. As a first step, we simply bring the Touch Typing style of the regular iOS keyboard right within FlickType, and make it fast and easy to toggle between Flick Typing and Touch Typing using the magic tap gesture. If you are not familiar, a magic tap is a double tap with two fingers, and is used to perform the so-called "most-intended" action, regardless of what element the VoiceOver cursor is currently focused on.

Notes:
- You cannot yet use any flick gestures when Touch Typing, but you will be able to in the future.
- You can now enter a new line with the Return key, just like with the iOS keyboard. When you go back to Flick Typing, new lines will currently not be announced when moving the cursor.
- The voice feedback for entered characters does not have a different pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in the main app. We're doing this for a couple of reasons: One is to make it easier for new users to fall back to a familiar typing style when needed. Two, manually typing longer words should be easier and faster this way. We might not be there yet, but this is the reasoning behind the approach.



Re: Build 67

Chanelle Allen
 

Hello Kosta, Ashley, and Group,
this is an excellent FlickType build! I like the magic tap gesture for switching between flick and touch typing; it was a brilliant idea, and tapping twice with two fingers is so easy and familiar. Here are my thoughts (the only message I have read thus far is Kosta's).
If possible, at some point later in the future after other plans/features have been implemented, I would like the ability to disable echoing of entered characters while touch typing. This is more of a nit picky request, but hopefully, my FlickType keyboard experience will be as similar to my iOS VoiceOver touch typing settings as reasonably possible. I have VoiceOver typing feedback set to words. There are some people on this list who prefer typing feedback set to characters, so a customizable setting would be useful.
I have noticed that my text replacements do not work when using FlickType touch typing. I assume that this problem will be addressed soon if you are not already aware of it.
Thank you again for developing another great FlickType release.
Chanelle

On May 18, 2018, at 01:03, FlickType <@FlickType> wrote:

This is the very first, and still quite experimental, version of the manual typing functionality. The approach we are taking is to start from the basics, and expand as we go. As a first step, we simply bring the Touch Typing style of the regular iOS keyboard right within FlickType, and make it fast and easy to toggle between Flick Typing and Touch Typing using the magic tap gesture. If you are not familiar, a magic tap is a double tap with two fingers, and is used to perform the so-called "most-intended" action, regardless of what element the VoiceOver cursor is currently focused on.

Notes:
- You cannot yet use any flick gestures when Touch Typing, but you will be able to in the future.
- You can now enter a new line with the Return key, just like with the iOS keyboard. When you go back to Flick Typing, new lines will currently not be announced when moving the cursor.
- The voice feedback for entered characters does not have a different pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in the main app. We're doing this for a couple of reasons: One is to make it easier for new users to fall back to a familiar typing style when needed. Two, manually typing longer words should be easier and faster this way. We might not be there yet, but this is the reasoning behind the approach.


Re: Build 67

Ed Worrell
 

Hello All,

I am really not a fan of the current build. I think that the manual typing feature should be implemented in to the main typing methodology, but I understand that you have to start somewhere. The two step process to manually insert works/characters seems a little like a waste of time to me. I kind of like the two finger double tap to switch to symbols/numbers and potentially emojis in the future. As I said in a previous email it just seems like a small step backwards in progress.

Ed Worrell

On May 18, 2018, at 1:36 PM, Chanelle Allen <chanellem.allen@...> wrote:

Hello Kosta, Ashley, and Group,
this is an excellent FlickType build! I like the magic tap gesture for switching between flick and touch typing; it was a brilliant idea, and tapping twice with two fingers is so easy and familiar. Here are my thoughts (the only message I have read thus far is Kosta's).
If possible, at some point later in the future after other plans/features have been implemented, I would like the ability to disable echoing of entered characters while touch typing. This is more of a nit picky request, but hopefully, my FlickType keyboard experience will be as similar to my iOS VoiceOver touch typing settings as reasonably possible. I have VoiceOver typing feedback set to words. There are some people on this list who prefer typing feedback set to characters, so a customizable setting would be useful.
I have noticed that my text replacements do not work when using FlickType touch typing. I assume that this problem will be addressed soon if you are not already aware of it.
Thank you again for developing another great FlickType release.
Chanelle

On May 18, 2018, at 01:03, FlickType <@FlickType> wrote:

This is the very first, and still quite experimental, version of the manual typing functionality. The approach we are taking is to start from the basics, and expand as we go. As a first step, we simply bring the Touch Typing style of the regular iOS keyboard right within FlickType, and make it fast and easy to toggle between Flick Typing and Touch Typing using the magic tap gesture. If you are not familiar, a magic tap is a double tap with two fingers, and is used to perform the so-called "most-intended" action, regardless of what element the VoiceOver cursor is currently focused on.

Notes:
- You cannot yet use any flick gestures when Touch Typing, but you will be able to in the future.
- You can now enter a new line with the Return key, just like with the iOS keyboard. When you go back to Flick Typing, new lines will currently not be announced when moving the cursor.
- The voice feedback for entered characters does not have a different pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in the main app. We're doing this for a couple of reasons: One is to make it easier for new users to fall back to a familiar typing style when needed. Two, manually typing longer words should be easier and faster this way. We might not be there yet, but this is the reasoning behind the approach.



Re: Build 67

Benny Barber
 

I use both character and word echo. Thanks.

On May 18, 2018, at 2:36 PM, Chanelle Allen <chanellem.allen@...> wrote:

Hello Kosta, Ashley, and Group,
this is an excellent FlickType build! I like the magic tap gesture for switching between flick and touch typing; it was a brilliant idea, and tapping twice with two fingers is so easy and familiar. Here are my thoughts (the only message I have read thus far is Kosta's).
If possible, at some point later in the future after other plans/features have been implemented, I would like the ability to disable echoing of entered characters while touch typing. This is more of a nit picky request, but hopefully, my FlickType keyboard experience will be as similar to my iOS VoiceOver touch typing settings as reasonably possible. I have VoiceOver typing feedback set to words. There are some people on this list who prefer typing feedback set to characters, so a customizable setting would be useful.
I have noticed that my text replacements do not work when using FlickType touch typing. I assume that this problem will be addressed soon if you are not already aware of it.
Thank you again for developing another great FlickType release.
Chanelle

On May 18, 2018, at 01:03, FlickType <@FlickType> wrote:

This is the very first, and still quite experimental, version of the manual typing functionality. The approach we are taking is to start from the basics, and expand as we go. As a first step, we simply bring the Touch Typing style of the regular iOS keyboard right within FlickType, and make it fast and easy to toggle between Flick Typing and Touch Typing using the magic tap gesture. If you are not familiar, a magic tap is a double tap with two fingers, and is used to perform the so-called "most-intended" action, regardless of what element the VoiceOver cursor is currently focused on.

Notes:
- You cannot yet use any flick gestures when Touch Typing, but you will be able to in the future.
- You can now enter a new line with the Return key, just like with the iOS keyboard. When you go back to Flick Typing, new lines will currently not be announced when moving the cursor.
- The voice feedback for entered characters does not have a different pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in the main app. We're doing this for a couple of reasons: One is to make it easier for new users to fall back to a familiar typing style when needed. Two, manually typing longer words should be easier and faster this way. We might not be there yet, but this is the reasoning behind the approach.



Re: Build 67

George Cham
 

Okay, I like the touch typing feature. Why not put the white bar to represent  bottom and top rows,   mode . And maybe a  symbol to show where the enter key is and  backspace.

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 19, 2018 2:34:28 AM
To: Alpha
Subject: [FlickType-alpha] Build 67
 
Build 67
Hi again,
The two things I really miss with the custom keyboard is the ability to capitalize letters and input lines with a simple gesture.
As I type this in the app, everything is only a simple gesture away.
The custom keyboard is fantastic for entering short amounts of text, and responding to messages and emails, but more than that, I revert to the app.



Chuck


Re: Build 67

George Cham
 

 The other thing i'd like to see, when finishing a sentence, the next sentence
Should start with a capitalletter.
I’m also having problems with  finding   the toggle between numbers symbols and letters, there should be something visual to indicate these.  

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of George Cham <George.cham@...>
Sent: Saturday, May 19, 2018 6:48:30 AM
To: alpha@flicktype.groups.io; Alpha
Subject: Re: [FlickType-alpha] Build 67
 
Okay, I like the touch typing feature. Why not put the white bar to represent  bottom and top rows,   mode . And maybe a  symbol to show where the enter key is and  backspace.

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 19, 2018 2:34:28 AM
To: Alpha
Subject: [FlickType-alpha] Build 67
 
Build 67
Hi again,
The two things I really miss with the custom keyboard is the ability to capitalize letters and input lines with a simple gesture.
As I type this in the app, everything is only a simple gesture away.
The custom keyboard is fantastic for entering short amounts of text, and responding to messages and emails, but more than that, I revert to the app.



Chuck


Build 67

Chuck Dean
 

Build 67
Hi all, I just got off a cross country flight and did some typing along the way.
Personally, I don't see any way to beat the typing experience in the FlickType app. If this keyboard, with its manual entry, numbers and symbols, could be incorporated into a half screen, system wide keyboard, I think the blind and visually impaired community would be pretty happy with the end product. Look at the very positive response the app got when it went public.

I know you said you wanted to keep the manual input close to the iOS experience... But why? Unless you are planning a general public release, I see no reason for this. If the app style keyboard could be incorporated as a system wide keyboard, after very little use it would be my default keyboard and the iOS keyboard would become a piece of nostalgia.

Just my opinion...



Chuck

Re: Build 67

Ed Worrell
 

Hey there chuck,
I couldn't agree with you more. I would love to see the keyboard become a half screen effort. This would be great to me as well. Ed

On May 18, 2018, at 5:08 PM, Chuck Dean <cadean329@...> wrote:

Build 67
Hi all, I just got off a cross country flight and did some typing along the way.
Personally, I don't see any way to beat the typing experience in the FlickType app. If this keyboard, with its manual entry, numbers and symbols, could be incorporated into a half screen, system wide keyboard, I think the blind and visually impaired community would be pretty happy with the end product. Look at the very positive response the app got when it went public.

I know you said you wanted to keep the manual input close to the iOS experience... But why? Unless you are planning a general public release, I see no reason for this. If the app style keyboard could be incorporated as a system wide keyboard, after very little use it would be my default keyboard and the iOS keyboard would become a piece of nostalgia.

Just my opinion...



Chuck

Re: Build 67

Chuck Dean
 

With the half screen keyboard there would be much less need for switching to the iOS keyboard, as it would be easy to move the cursor in various text fields.


Don't get me wrong, I think the custom keyboard is pretty amazing, but the half screen would fit my personal needs better.


Chuck

On May 18, 2018, at 4:23 PM, Ed Worrell <ed.worrell@...> wrote:


Hey there chuck,
I couldn't agree with you more. I would love to see the keyboard become a half screen effort. This would be great to me as well. Ed
On May 18, 2018, at 5:08 PM, Chuck Dean <cadean329@...> wrote:

Build 67
Hi all, I just got off a cross country flight and did some typing along the way.
Personally, I don't see any way to beat the typing experience in the FlickType app. If this keyboard, with its manual entry, numbers and symbols, could be incorporated into a half screen, system wide keyboard, I think the blind and visually impaired community would be pretty happy with the end product. Look at the very positive response the app got when it went public.

I know you said you wanted to keep the manual input close to the iOS experience... But why? Unless you are planning a general public release, I see no reason for this. If the app style keyboard could be incorporated as a system wide keyboard, after very little use it would be my default keyboard and the iOS keyboard would become a piece of nostalgia.

Just my opinion...



Chuck


Re: Build 67

George Cham
 

i agree with you . I think  the half screen keyboard is better,because we can see what we are   typing.. also, from memory in build  50 , the   white bar was put there to represent the top and bottomrows. This should be brought back

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 19, 2018 10:00:56 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

With the half screen keyboard there would be much less need for switching to the iOS keyboard, as it would be easy to move the cursor in various text fields.


Don't get me wrong, I think the custom keyboard is pretty amazing, but the half screen would fit my personal needs better.


Chuck

> On May 18, 2018, at 4:23 PM, Ed Worrell <ed.worrell@...> wrote:
>
>
> Hey there chuck,
> I couldn't agree with you more. I would love to see the keyboard become a half screen effort. This would be great to me as well. Ed
>> On May 18, 2018, at 5:08 PM, Chuck Dean <cadean329@...> wrote:
>>
>> Build 67
>> Hi all, I just got off a cross country flight and did some typing along the way.
>> Personally, I don't see any way to beat the typing experience in the FlickType app. If this keyboard, with its manual entry, numbers and symbols, could be incorporated into a half screen, system wide keyboard, I think the blind and visually impaired community would be pretty happy with the end product. Look at the very positive response the app got when it went public.
>>
>> I know you said you wanted to keep the manual input close to the iOS experience... But why? Unless you are planning a general public release, I see no reason for this. If the app style keyboard could be incorporated as a system wide keyboard, after very little use it would be my default keyboard and the iOS keyboard would become a piece of nostalgia.
>>
>> Just my opinion...
>>
>>
>>
>> Chuck
>>
>>
>
>
>



Re: Build 67

Chuck Dean
 


I am not really worried about the look of the keyboard, even though I have some sight, I do very little eyeballing.


Chuck

On May 18, 2018, at 5:17 PM, George Cham <George.cham@...> wrote:

i agree with you . I think  the half screen keyboard is better,because we can see what we are   typing.. also, from memory in build  50 , the   white bar was put there to represent the top and bottomrows. This should be brought back

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 19, 2018 10:00:56 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

With the half screen keyboard there would be much less need for switching to the iOS keyboard, as it would be easy to move the cursor in various text fields.


Don't get me wrong, I think the custom keyboard is pretty amazing, but the half screen would fit my personal needs better.


Chuck

> On May 18, 2018, at 4:23 PM, Ed Worrell <ed.worrell@...> wrote:
>
>
> Hey there chuck,
> I couldn't agree with you more. I would love to see the keyboard become a half screen effort. This would be great to me as well. Ed
>> On May 18, 2018, at 5:08 PM, Chuck Dean <cadean329@...> wrote:
>>
>> Build 67
>> Hi all, I just got off a cross country flight and did some typing along the way.
>> Personally, I don't see any way to beat the typing experience in the FlickType app. If this keyboard, with its manual entry, numbers and symbols, could be incorporated into a half screen, system wide keyboard, I think the blind and visually impaired community would be pretty happy with the end product. Look at the very positive response the app got when it went public.
>>
>> I know you said you wanted to keep the manual input close to the iOS experience... But why? Unless you are planning a general public release, I see no reason for this. If the app style keyboard could be incorporated as a system wide keyboard, after very little use it would be my default keyboard and the iOS keyboard would become a piece of nostalgia.
>>
>> Just my opinion...
>>
>>
>>
>> Chuck
>>
>>
>
>
>



Re: Build 67

Benny Barber
 


I too have very little sight, so the way the screen looks is not important to me. I need audible feedback to know what I am typing. Thanks.

Benny

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

i agree with you . I think  the half screen keyboard is better,because we can see what we are   typing.. also, from memory in build  50 , the   white bar was put there to represent the top and bottomrows. This should be brought back

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 19, 2018 10:00:56 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

With the half screen keyboard there would be much less need for switching to the iOS keyboard, as it would be easy to move the cursor in various text fields.


Don't get me wrong, I think the custom keyboard is pretty amazing, but the half screen would fit my personal needs better.


Chuck

> On May 18, 2018, at 4:23 PM, Ed Worrell <ed.worrell@...> wrote:
>
>
> Hey there chuck,
> I couldn't agree with you more. I would love to see the keyboard become a half screen effort. This would be great to me as well. Ed
>> On May 18, 2018, at 5:08 PM, Chuck Dean <cadean329@...> wrote:
>>
>> Build 67
>> Hi all, I just got off a cross country flight and did some typing along the way.
>> Personally, I don't see any way to beat the typing experience in the FlickType app. If this keyboard, with its manual entry, numbers and symbols, could be incorporated into a half screen, system wide keyboard, I think the blind and visually impaired community would be pretty happy with the end product. Look at the very positive response the app got when it went public.
>>
>> I know you said you wanted to keep the manual input close to the iOS experience... But why? Unless you are planning a general public release, I see no reason for this. If the app style keyboard could be incorporated as a system wide keyboard, after very little use it would be my default keyboard and the iOS keyboard would become a piece of nostalgia.
>>
>> Just my opinion...
>>
>>
>>
>> Chuck
>>
>>
>
>
>



Re: Build 67

George Cham
 

ok,but i think the flick gesture  after typing should be introduced in this new build. This makes it easier then trying to find Space in return

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Benny Barber <rebelben@...>
Sent: Saturday, May 19, 2018 10:41:18 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

I too have very little sight, so the way the screen looks is not important to me. I need audible feedback to know what I am typing. Thanks.

Benny

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

i agree with you . I think  the half screen keyboard is better,because we can see what we are   typing.. also, from memory in build  50 , the   white bar was put there to represent the top and bottomrows. This should be brought back

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Saturday, May 19, 2018 10:00:56 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

With the half screen keyboard there would be much less need for switching to the iOS keyboard, as it would be easy to move the cursor in various text fields.


Don't get me wrong, I think the custom keyboard is pretty amazing, but the half screen would fit my personal needs better.


Chuck

> On May 18, 2018, at 4:23 PM, Ed Worrell <ed.worrell@...> wrote:
>
>
> Hey there chuck,
> I couldn't agree with you more. I would love to see the keyboard become a half screen effort. This would be great to me as well. Ed
>> On May 18, 2018, at 5:08 PM, Chuck Dean <cadean329@...> wrote:
>>
>> Build 67
>> Hi all, I just got off a cross country flight and did some typing along the way.
>> Personally, I don't see any way to beat the typing experience in the FlickType app. If this keyboard, with its manual entry, numbers and symbols, could be incorporated into a half screen, system wide keyboard, I think the blind and visually impaired community would be pretty happy with the end product. Look at the very positive response the app got when it went public.
>>
>> I know you said you wanted to keep the manual input close to the iOS experience... But why? Unless you are planning a general public release, I see no reason for this. If the app style keyboard could be incorporated as a system wide keyboard, after very little use it would be my default keyboard and the iOS keyboard would become a piece of nostalgia.
>>
>> Just my opinion...
>>
>>
>>
>> Chuck
>>
>>
>
>
>



Re: Build 67

Benny Barber
 

Kosta,

Currently as the custom keyboard stands, I have 2 issues that are a
hinderance to me.

1. Let's use the letter "x" as an example for this first issue. As I stated
in an earlier message, the shift key is confusing to me. In my humble
opinion, I think that at the beginning of a document the keyboard should
always be in "Caps" mode. When that first letter is entered the feedback
should be "Cap x" and then go into lower case mode. When you want to type
an upper case letter in the middle of a document or sentence and you touch
the shift key, the feedback when lifting the finger should be "Caps" to let
you know that you have entered the upper case mode. Then when you touch a
letter the feedback should be "Cap x". Conversely, when you want to change
the mode from upper case to lower case and touching the shift key, the
feedback should be "lower case" when you lift your finger. Currently it is
backwards.

2. As a user of FlickType, I have very limited sight and do not use any
sight to use the keyboard. I depend on the audible feedback exclusively.
With that said, all the feedback I can get assists me greatly in the typing
experience. I need character feedback and word feedback. Currently on the
direct input of letters you do not get word feedback when you space. This
is a hinderance in my typing. I need the confirmation that I have typed the
previous word correctly.

Thanks for all that you and Ashley have done. I greatly appreciate your
efforts.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of FlickType
Sent: Friday, May 18, 2018 1:04 AM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 67

This is the very first, and still quite experimental, version of the manual
typing functionality. The approach we are taking is to start from the
basics, and expand as we go. As a first step, we simply bring the Touch
Typing style of the regular iOS keyboard right within FlickType, and make it
fast and easy to toggle between Flick Typing and Touch Typing using the
magic tap gesture. If you are not familiar, a magic tap is a double tap with
two fingers, and is used to perform the so-called "most-intended" action,
regardless of what element the VoiceOver cursor is currently focused on.

Notes:
- You cannot yet use any flick gestures when Touch Typing, but you will be
able to in the future.
- You can now enter a new line with the Return key, just like with the iOS
keyboard. When you go back to Flick Typing, new lines will currently not be
announced when moving the cursor.
- The voice feedback for entered characters does not have a different pitch.
- You can only switch to the iOS keyboard when Flick Typing.

As you can tell, this is very different from the way manual input works in
the main app. We're doing this for a couple of reasons: One is to make it
easier for new users to fall back to a familiar typing style when needed.
Two, manually typing longer words should be easier and faster this way. We
might not be there yet, but this is the reasoning behind the approach.