Date   

Re: Build 67

Benny Barber
 

The upper and lower case setting is very confusing to me. Maybe it is me, but I don't know if I am typing in upper or lower case. If possible the echo needs to mirror the iOS echo. 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.



Re: Build 67

Macster
 

Hi George, 

Punctuation is now available. If you use the two finger double tap to enter touch typing mode, the more button is at the bottom left and will allow access to all the punctuation in the same layout as the standard keyboard. Its very responsive and works well. Macky 


On 18 May 2018, at 09:39, George Cham <George.cham@...> wrote:

Wow! I’m typing  a lot faster. I’d like The ability  to add punctuation while  touch typing within the system wide    keyboard

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of George Cham <George.cham@...>
Sent: Friday, May 18, 2018 6:29:27 PM
To: alpha@flicktype.groups.io; alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 
ok got it, but how do I add a. At the end of a sentence and punctuations?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Paul Sutton <sutty_p@...>
Sent: Friday, May 18, 2018 6:18:35 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

Hi George, when in touch typing mode, drag your finger over the keyboard until you here the letter you want and then lift your finger. 
Regards, Paul


On 18 May 2018, at 08:57, George Cham <George.cham@...> wrote:

I don't understand how the touch typing works in this new release. I did the magic tap, started typing, but the letters  did not come out the way I wanted. Can someone explain how to use the touch typing feature?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Paul Sutton <sutty_p@...>
Sent: Friday, May 18, 2018 5:36:10 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 67
 



Begin forwarded message:

From: Paul Sutton <sutty_p@...>
Date: 18 May 2018 at 08:23:07 BST
To: "alpha@flicktype.groups.io" <alpha@flicktype.groups.io>
Subject: Re: [FlickType-alpha] Build 67

Hi, well done. This seems very stable at the moment. I can't find any problems at the moment. One suggestion that I have would be too maybe allow for another tap on the shift key to enable caps loch.
Once again, well done for this new release.
Regards, Paul.



On 18 May 2018, at 07:03, 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
 

Wow, great job Kosta! The manual keyboard works a treat. Its crisp and changing between the flick keyboard and manual mode is very responsive too. I said the manual keyboard will tip the scales for me using the custom version more than the app and that has already been the case this morning since installation. Its now only a matter of time before I delete the standard keyboard from my active list.

I've only found a couple of drawbacks so far...

1 - if there is a word in my dictionary that sometimes needs a capital and sometimes does not, ie mark and my nephew's name Mark, there isn't a way to capitalize the M using the flick keyboard at the moment, so I have to type it manually. Is there a way around this?

2 - The first time I used the shift key, the letters didn't say cap before entry but they do now. Not sure what happened on the maiden voyage. The shift key itself however announces the state of what the next press will be, instead of what the press that has just occurred has done. It works perfectly, but maybe the announcement could be reversed?

3 - This isn't a bug as such, but I have the echo effect set to off in the app but the echo is present in the manual keyboard.. Could this be connected so the echo can be turned off?

The punctuation is fantastic and is in the same layout as the standard keyboard so no problems finding anything, and I think the manual keyboard is more responsive than the standard one already so good job!

I know you said this is the early stages but it's already very useable. Thank you.

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

George Cham
 

Wow! I’m typing  a lot faster. I’d like The ability  to add punctuation while  touch typing within the system wide    keyboard

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of George Cham <George.cham@...>
Sent: Friday, May 18, 2018 6:29:27 PM
To: alpha@flicktype.groups.io; alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 
ok got it, but how do I add a. At the end of a sentence and punctuations?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Paul Sutton <sutty_p@...>
Sent: Friday, May 18, 2018 6:18:35 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

Hi George, when in touch typing mode, drag your finger over the keyboard until you here the letter you want and then lift your finger. 
Regards, Paul


On 18 May 2018, at 08:57, George Cham <George.cham@...> wrote:

I don't understand how the touch typing works in this new release. I did the magic tap, started typing, but the letters  did not come out the way I wanted. Can someone explain how to use the touch typing feature?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Paul Sutton <sutty_p@...>
Sent: Friday, May 18, 2018 5:36:10 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 67
 



Begin forwarded message:

From: Paul Sutton <sutty_p@...>
Date: 18 May 2018 at 08:23:07 BST
To: "alpha@flicktype.groups.io" <alpha@flicktype.groups.io>
Subject: Re: [FlickType-alpha] Build 67

Hi, well done. This seems very stable at the moment. I can't find any problems at the moment. One suggestion that I have would be too maybe allow for another tap on the shift key to enable caps loch.
Once again, well done for this new release.
Regards, Paul.



On 18 May 2018, at 07:03, 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

George Cham
 

ok got it, but how do I add a. At the end of a sentence and punctuations?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Paul Sutton <sutty_p@...>
Sent: Friday, May 18, 2018 6:18:35 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 67
 

Hi George, when in touch typing mode, drag your finger over the keyboard until you here the letter you want and then lift your finger. 
Regards, Paul


On 18 May 2018, at 08:57, George Cham <George.cham@...> wrote:

I don't understand how the touch typing works in this new release. I did the magic tap, started typing, but the letters  did not come out the way I wanted. Can someone explain how to use the touch typing feature?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Paul Sutton <sutty_p@...>
Sent: Friday, May 18, 2018 5:36:10 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 67
 



Begin forwarded message:

From: Paul Sutton <sutty_p@...>
Date: 18 May 2018 at 08:23:07 BST
To: "alpha@flicktype.groups.io" <alpha@flicktype.groups.io>
Subject: Re: [FlickType-alpha] Build 67

Hi, well done. This seems very stable at the moment. I can't find any problems at the moment. One suggestion that I have would be too maybe allow for another tap on the shift key to enable caps loch.
Once again, well done for this new release.
Regards, Paul.



On 18 May 2018, at 07:03, 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

Paul Sutton
 


Hi George, when in touch typing mode, drag your finger over the keyboard until you here the letter you want and then lift your finger. 
Regards, Paul


On 18 May 2018, at 08:57, George Cham <George.cham@...> wrote:

I don't understand how the touch typing works in this new release. I did the magic tap, started typing, but the letters  did not come out the way I wanted. Can someone explain how to use the touch typing feature?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Paul Sutton <sutty_p@...>
Sent: Friday, May 18, 2018 5:36:10 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 67
 



Begin forwarded message:

From: Paul Sutton <sutty_p@...>
Date: 18 May 2018 at 08:23:07 BST
To: "alpha@flicktype.groups.io" <alpha@flicktype.groups.io>
Subject: Re: [FlickType-alpha] Build 67

Hi, well done. This seems very stable at the moment. I can't find any problems at the moment. One suggestion that I have would be too maybe allow for another tap on the shift key to enable caps loch.
Once again, well done for this new release.
Regards, Paul.



On 18 May 2018, at 07:03, 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

George Cham
 

I don't understand how the touch typing works in this new release. I did the magic tap, started typing, but the letters  did not come out the way I wanted. Can someone explain how to use the touch typing feature?

Kind Regards,

George Cham



From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Paul Sutton <sutty_p@...>
Sent: Friday, May 18, 2018 5:36:10 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 67
 



Begin forwarded message:

From: Paul Sutton <sutty_p@...>
Date: 18 May 2018 at 08:23:07 BST
To: "alpha@flicktype.groups.io" <alpha@flicktype.groups.io>
Subject: Re: [FlickType-alpha] Build 67

Hi, well done. This seems very stable at the moment. I can't find any problems at the moment. One suggestion that I have would be too maybe allow for another tap on the shift key to enable caps loch.
Once again, well done for this new release.
Regards, Paul.



On 18 May 2018, at 07:03, 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.




Build 67

Paul Sutton
 




Begin forwarded message:

From: Paul Sutton <sutty_p@...>
Date: 18 May 2018 at 08:23:07 BST
To: "alpha@flicktype.groups.io" <alpha@flicktype.groups.io>
Subject: Re: [FlickType-alpha] Build 67

Hi, well done. This seems very stable at the moment. I can't find any problems at the moment. One suggestion that I have would be too maybe allow for another tap on the shift key to enable caps loch.
Once again, well done for this new release.
Regards, Paul.



On 18 May 2018, at 07:03, 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.




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.


Re: Build 66.

Chuck Dean
 

And in a perfect world... If possible, the ability to add symbols that we use often, such as the degree symbol, or copyright symbol, would be fantastic!


Chuck

On May 17, 2018, at 3:30 PM, Chanelle Allen <chanellem.allen@...> wrote:


Hello,Ditto to the last two messages. :) An area of symbols above the letters in manual typing mode would be convenient.
Thank you.
Chanelle

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

I'm with chuck on this one. I would use that top row a ton. I would love to have that ability whilst using twitter.
Ed
On May 17, 2018, at 12:41 PM, Chuck Dean <cadean329@...> wrote:

Build 66.
Hi,
I was wondering if the line of symbols and shortcuts above the qwerty keys will be available once manual text input is working.
I use those a lot.
:)



Chuck




Re: Build 66.

Chanelle Allen
 

Hello,Ditto to the last two messages. :) An area of symbols above the letters in manual typing mode would be convenient.
Thank you.
Chanelle

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

I'm with chuck on this one. I would use that top row a ton. I would love to have that ability whilst using twitter.
Ed
On May 17, 2018, at 12:41 PM, Chuck Dean <cadean329@...> wrote:

Build 66.
Hi,
I was wondering if the line of symbols and shortcuts above the qwerty keys will be available once manual text input is working.
I use those a lot.
:)



Chuck



Re: Manual typing #poll

Chanelle Allen
 


It was very difficult to choose. I almost voted for #1. I also switch to the iOS keyboard frequently to enter new lines.
Chanelle

On May 17, 2018, at 10:14, Benny Barber <rebelben@...> wrote:

I voted for number two, 
but number one is just as important.

On May 17, 2018, at 9:41 AM, David Nason <dnason@...> wrote:


I voted for number one, but honestly it's hard to choose, as it really is both. Dave



On 17 May 2018, at 13:09, Michael Maslo <michaelmaslo04@...> wrote:

I chose number two.

Sincerely,, mike 


On May 16, 2018 at 18:08, <FlickType> wrote:

A new poll has been created:

What do you most often need to type manually in the main app?

1. Something very short, for example a single character such as a quote, parenthesis, hashtag or @ symbol, or a small number like 12
2. Something longer, like a word not in the dictionary, a phone number, a website or an email address
3. Other (please specify)

Vote Now


Re: Build 66.

Ed Worrell
 

I'm with chuck on this one. I would use that top row a ton. I would love to have that ability whilst using twitter.
Ed

On May 17, 2018, at 12:41 PM, Chuck Dean <cadean329@...> wrote:

Build 66.
Hi,
I was wondering if the line of symbols and shortcuts above the qwerty keys will be available once manual text input is working.
I use those a lot.
:)



Chuck


Build 66.

Chuck Dean
 

Build 66.
Hi,
I was wondering if the line of symbols and shortcuts above the qwerty keys will be available once manual text input is working.
I use those a lot.
:)



Chuck


Re: Manual typing #poll

Ed Worrell
 

I selected the third option as I feel that special characters, numbers and manual entry are all important. I use twitter a lot, and I need the ability to do all of the options.


On May 17, 2018, at 9:14 AM, Benny Barber <rebelben@...> wrote:

I voted for number two, 
but number one is just as important.

On May 17, 2018, at 9:41 AM, David Nason <dnason@...> wrote:


I voted for number one, but honestly it's hard to choose, as it really is both. Dave



On 17 May 2018, at 13:09, Michael Maslo <michaelmaslo04@...> wrote:

I chose number two.

Sincerely,, mike 


On May 16, 2018 at 18:08, <FlickType> wrote:

A new poll has been created:

What do you most often need to type manually in the main app?

1. Something very short, for example a single character such as a quote, parenthesis, hashtag or @ symbol, or a small number like 12
2. Something longer, like a word not in the dictionary, a phone number, a website or an email address
3. Other (please specify)

Vote Now


Re: Manual typing #poll

Benny Barber
 

I voted for number two, 
but number one is just as important.

On May 17, 2018, at 9:41 AM, David Nason <dnason@...> wrote:


I voted for number one, but honestly it's hard to choose, as it really is both. Dave



On 17 May 2018, at 13:09, Michael Maslo <michaelmaslo04@...> wrote:

I chose number two.

Sincerely,, mike 


On May 16, 2018 at 18:08, <FlickType> wrote:

A new poll has been created:

What do you most often need to type manually in the main app?

1. Something very short, for example a single character such as a quote, parenthesis, hashtag or @ symbol, or a small number like 12
2. Something longer, like a word not in the dictionary, a phone number, a website or an email address
3. Other (please specify)

Vote Now


Re: Manual typing #poll

David Nason
 


I voted for number one, but honestly it's hard to choose, as it really is both. Dave



On 17 May 2018, at 13:09, Michael Maslo <michaelmaslo04@...> wrote:

I chose number two.

Sincerely,, mike 


On May 16, 2018 at 18:08, <FlickType> wrote:

A new poll has been created:

What do you most often need to type manually in the main app?

1. Something very short, for example a single character such as a quote, parenthesis, hashtag or @ symbol, or a small number like 12
2. Something longer, like a word not in the dictionary, a phone number, a website or an email address
3. Other (please specify)

Vote Now


Re: Manual typing #poll

Michael Maslo
 

I chose number two.

Sincerely,, mike 


On May 16, 2018 at 18:08, <FlickType> wrote:

A new poll has been created:

What do you most often need to type manually in the main app?

1. Something very short, for example a single character such as a quote, parenthesis, hashtag or @ symbol, or a small number like 12
2. Something longer, like a word not in the dictionary, a phone number, a website or an email address
3. Other (please specify)

Vote Now


Manual typing #poll

 

What do you most often need to type manually in the main app?

Results

See Who Responded


Re: Build 66

 

FYI, build 66 has just been released to beta.