Date   

Potential beta release, and other responses

 

Hi all, and thank you for the insightful comments.

Regarding a potential release to beta, there is no right and wrong answer here since software quality is hard to objectively measure, let alone for shipping something to beta rather than an actual release. But I believe setting the right expectations and using the right wording in our announcement can bring all of the benefits of an extended pool of testers with almost none of the drawbacks. In particular, the biggest benefit will be ensuring that we are always working on the most impactful work item, rather than get sidetracked with a potentially lower priority item that might just have happened in a smaller group by chance. To that end, I have further updated the wiki page to include the appropriate introduction, as well as order the known issues according to a rough estimate of importance to users. I'd love to hear your thoughts on this, in particular on what should be at the very top of the list. It's currently manual input mode, and if that does become the next main thing to work on, I'd also love to better understand what the most common use case is so I can better design it around that. For example, is it a non-dictionary word? Is it numbers? Symbols? Emoji? Text replacement shortcuts? Link to the wiki page: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard

Michael, Shinji, and Matthew, thank you for offering to help. I have now added you as moderators to the beta group.

I'd also like to hear if anyone has been experiencing any crashes with build 63. I do get some crash reports back from TestFlight, but it's hard to tell what is due to iOS issues or bugs and what is due to my own code, as well as how much of a user impact these crashes have. For example, if the keyboard crashed and restarted while you were not using it, you probably won't even notice. So, is stability an issue right now, or not?

Below are some responses to your earlier points and questions:

- FlickType not correcting spelling errors: definitely a known issue, I have some ideas on how to tackle it but it would need a full rewrite of the internal correction engine which is months away. Ultimately, FlickType will probably always expect the input to be spelled better than other keyboards, on average, but I do think there are ways to improve the current situation significantly.
- Direct touch issue reported by Chanelle and a couple of others in the past: I am not aware of an option to toggle "Direct touch" in general, but I'm assuming this refers to the "Direct touch typing" option which in general does not seem to not affect FlickType. If anyone has a reliable way to actually reproduce the problem, rather than how to get out of it, I'd love to know the steps so I can investigate.
- Lack of read back function: hopefully sentence navigation using the cursor can help as a workaround for now. Flick left or right with 3 fingers. Sometimes you might not be able to move past sentence boundaries though, particularly after switching to the iOS keyboard. Once manual entry is supported right from within FlickType, this should almost never happen.
- Matthew reporting an issue with the Zoom number field: it's strange that the tap & hold didn't work, I will try to reproduce it, thanks. FlickType does lack a number keypad which should be the one to automatically popup in that case, and this should be addressed soon. It's also actually a requirement by Apple, before we release to the App Store.
- Having multiple keyboards such as FlickType, the standard iOS keyboard, as well as the emoji keyboard, can make the keyboard switching erratic due to iOS issues. It should not be long before emojis are built right into FlickType, as well as manual entry mode, so eventually this should not be a problem.
- George, you mentioned: "Was just listening to eyes on success and FlickType. I then started thinking, is it possible to make FlickType the The Default keyboard?" What did you mean by that exactly?
- Also George, on build 62, you said: "Wow! That's a big change." Were you referring to the new keyboard colors, or was it something else?
- Chuck, on gestures to alternate between keyboards: FlickType can only control the gesture that you use to advance to the next keyboard, whichever keyboard that may be in the list of installed keyboards. Once you are out of FlickType, there is nothing we can do to affect the behavior of other keyboards, including how to switch to the next keyboard again. Also note that there is no API for switching to the previous, rather than next keyboard. However, once symbols, numbers and emoji are added right into FlickType, we can control the entire experience, including doing something similar to what you are suggesting.
- Tap volume issues: this definitely sounds solvable (pun intended). But I think there's a few other items we need to tackle before that. Thank you for the feedback, and hopefully the discovered workarounds can be shared with others if needed.
- On having to add a space when switching back to the iOS keyboard: that might sometimes not be desired, and in fact we've had requests asking that we do not leave a trailing space at the end of your typing sessions. Hopefully this won't matter soon when you no longer need to switch to the iOS keyboard apart from when you are completely done with composing your text.
- I updated the wiki page to include some missing known issues, such as lack of capitalization control and the inability to enter a new line.

Thank you,
Kosta


Custom keyboard versus main app #poll

 

We know there are still severe limitations with the custom keyboard, but we'd like to better understand exactly how useful it is for you in its current state.

So the burning question is: which do you use more, the custom keyboard or the main app?

Results

See Who Responded


Re: Build 63 and beta release plan

Chanelle Allen
 

Hello Kosta and list,
I agree with others that say this FlickType build should be released to the beta group. I sympathize with the concern that FlickType could be portrayed negatively; on the other hand, Kosta and Ashley have put in so much work already into making FlickType a usable keyboard once you get the hang of it. The learning curve may be steep, so maybe beta users should know that in advance to make an informed decision, but we don't want to discourage anyone at the same time. With practice, integrating FlickType into the flow of your iDevice activity becomes less effortless.
I can't reproduce the FlickType glitch that I experienced the other day. Still, maybe beta users should be told to use the rotor only when the FlickType keyboard is not being used. For example, if I wanted to change the volume or rate of VoiceOver, I would switch to the iOS keyboard from FlickType, adjust the rotor, and switch back. Right now, the rotor gesture has no effect when the FlickType keyboard is in use, which is a great thing, so it could be that I turned off direct touch in another app.
I am not sure if this could be considered as a known issue, but when switching from the FlickType keyboard to the iOS keyboard, I must remember to input a space before manually typing a word or number.
I hope that the beta release is successful!
Chanelle

On May 10, 2018, at 10:48, Matthew Janusauskas <mjanusauskas@...> wrote:

Hi Kosta,

I will be happy to help answer questions in the beta group and to help however I can.

Regards,

Matthew


On May 9, 2018, at 9:16 PM, FlickType <@FlickType> wrote:

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.





Re: Build 63 tap volume in main app very low.

Chanelle Allen
 

Hello,
I have been using the custom keyboard much more because the volume has been lower although I attributed this behavior to turning on stereo effect again, which diminishes the volume. Sound settings seen just like low vision settings; everyone has different needs or preferences. Is it possible to create a version of FlickType that gives users further customization of volume? If not, one thing I have done is raise the VoiceOver volume (I have added volume to my rotor) while pressing on the volume down button on the side of my iPhone. Anyone who wishes to hear FlickType at a louder volume would do the reverse (set the rotor to volume, flick down to quiet VoiceOver if desired and increase the loudness of the phone).
Just a thought.
Chanelle

On May 10, 2018, at 10:46, Chuck Dean <cadean329@...> wrote:


I set the Effects Playback Mode, to Customizable.
I set the Effects Playback Mode, to Customizable.
It is better, but still seems a little quiet for one hundred percent.


Chuck

On May 10, 2018, at 8:33 AM, Chuck Dean <cadean329@...> wrote:


Actually, the tap sounds are also low in the custom keyboard, too. I have tried every setting and I restarted my iPhone.


Chuck

On May 10, 2018, at 7:43 AM, Chuck Dean <cadean329@...> wrote:

Build 63 tap volume in main app very low.
Hi Kosta,
The tap sound volume is very low while using the main app. I have set it at 100% and I can hardly hear the taps.
Outside the app click sounds are normal.



Chuck


Re: Build 63 and beta release plan

Matthew Janusauskas
 

Hi Kosta,

I will be happy to help answer questions in the beta group and to help however I can.

Regards,

Matthew

On May 9, 2018, at 9:16 PM, FlickType <@FlickType> wrote:

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.



Re: Build 63 tap volume in main app very low.

Chuck Dean
 

I set the Effects Playback Mode, to Customizable.
I set the Effects Playback Mode, to Customizable.
It is better, but still seems a little quiet for one hundred percent.


Chuck

On May 10, 2018, at 8:33 AM, Chuck Dean <cadean329@...> wrote:


Actually, the tap sounds are also low in the custom keyboard, too. I have tried every setting and I restarted my iPhone.


Chuck

On May 10, 2018, at 7:43 AM, Chuck Dean <cadean329@...> wrote:

Build 63 tap volume in main app very low.
Hi Kosta,
The tap sound volume is very low while using the main app. I have set it at 100% and I can hardly hear the taps.
Outside the app click sounds are normal.



Chuck


Re: Build 63 tap volume in main app very low.

Chuck Dean
 

Actually, the tap sounds are also low in the custom keyboard, too. I have tried every setting and I restarted my iPhone.


Chuck

On May 10, 2018, at 7:43 AM, Chuck Dean <cadean329@...> wrote:

Build 63 tap volume in main app very low.
Hi Kosta,
The tap sound volume is very low while using the main app. I have set it at 100% and I can hardly hear the taps.
Outside the app click sounds are normal.



Chuck


Build 63 tap volume in main app very low.

Chuck Dean
 

Build 63 tap volume in main app very low.
Hi Kosta,
The tap sound volume is very low while using the main app. I have set it at 100% and I can hardly hear the taps.
Outside the app click sounds are normal.



Chuck


Re: Build 63 and beta release

 

Paul,

Thanks for setting me straight. It has been a long time since I accessed app settings by accessing them through that main screen and I had forgotten you could do that. I've got over two hundred apps on my iPhone so perusing that screen can be a bit daunting.

Alan Lemly

On May 10, 2018, at 6:44 AM, Paul Sutton <sutty_p@...> wrote:

Hi Alan, after following the instructions from costa, I have realized that he is correct in the steps he has described. He was referring to the FlickType settings located in the main settings menu where all the other apps are located. Within that FlickType setting you can indeed access the keyboard settings.
regards, Paul.s the keyboard settings. Kind regards, Paul.
On 10 May 2018, at 06:12, Alan Lemly <@walemly> wrote:

Hi Kosta,

Build 1.1.-63 is working fine for me. I would suggest that you change the second bullet under your instructions found at your below link. Right now it says:

To install the custom keyboard, go to iOS Settings, FlickType, Keyboard and then enable it. You also need to enable "Full Access" right below that.

I think it would be clearer to say:

To install the custom keyboard, go to Settings, General, Keyboard, Keyboards, Add new keyboard, and select FlickType. Once installed, double tap on FlickType and turn on the Allow full access setting.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Wednesday, May 09, 2018 9:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 63 and beta release plan

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.







Re: Build 63 and beta release plan

Paul Sutton
 

Sane here, everyone who is installing these builds should be aware that it is only a beta and the more people testing
it the better really.

On 10 May 2018, at 14:25, Michael Maslo <michaelmaslo04@...> wrote:




I agree. Beta means that it is not complete. Let it go and get more suggestions.



Sincerely,, mike





On May 10, 2018 at 08:16, <Benny Barber (mailto:rebelben@...)> wrote:



I say let the beta testers have a shot at trying the custom keyboard. I'm sure they will understand that this is not a finished product. Thanks.

Benny

On May 9, 2018, at 9:16 PM, FlickType <@FlickType> wrote:

of





Re: Build 63 and beta release plan

Michael Maslo
 

I agree. Beta means that it is not complete. Let it go and get more suggestions.



Sincerely,, mike


On May 10, 2018 at 08:16, <Benny Barber (mailto:rebelben@...)> wrote:



I say let the beta testers have a shot at trying the custom keyboard. I'm sure they will understand that this is not a finished product. Thanks.

Benny

On May 9, 2018, at 9:16 PM, FlickType <@FlickType> wrote:

of




Re: Build 63 and beta release plan

Benny Barber
 

I say let the beta testers have a shot at trying the custom keyboard. I'm sure they will understand that this is not a finished product. Thanks.

Benny

On May 9, 2018, at 9:16 PM, FlickType <@FlickType> wrote:

of


Re: Build 63 and beta release plan

Serina Gilbert
 

I think the general community would rather wait until manual input is available before testing. Just my opinion.

Serina

On May 9, 2018, at 8:16 PM, FlickType <@FlickType> wrote:

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.



Re: Build 63 and beta release

Paul Sutton
 

Lol as you can tell I am still getting the hang of switching between keyboards

On 10 May 2018, at 12:44, Paul Sutton <sutty_p@...> wrote:

Hi Alan, after following the instructions from costa, I have realized that he is correct in the steps he has described. He was referring to the FlickType settings located in the main settings menu where all the other apps are located. Within that FlickType setting you can indeed access the keyboard settings.
regards, Paul.s the keyboard settings. Kind regards, Paul.
On 10 May 2018, at 06:12, Alan Lemly <@walemly> wrote:

Hi Kosta,

Build 1.1.-63 is working fine for me. I would suggest that you change the second bullet under your instructions found at your below link. Right now it says:

To install the custom keyboard, go to iOS Settings, FlickType, Keyboard and then enable it. You also need to enable "Full Access" right below that.

I think it would be clearer to say:

To install the custom keyboard, go to Settings, General, Keyboard, Keyboards, Add new keyboard, and select FlickType. Once installed, double tap on FlickType and turn on the Allow full access setting.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Wednesday, May 09, 2018 9:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 63 and beta release plan

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.







Re: Build 63 and beta release

Paul Sutton
 

Hi Alan, after following the instructions from costa, I have realized that he is correct in the steps he has described. He was referring to the FlickType settings located in the main settings menu where all the other apps are located. Within that FlickType setting you can indeed access the keyboard settings.
regards, Paul.s the keyboard settings. Kind regards, Paul.

On 10 May 2018, at 06:12, Alan Lemly <@walemly> wrote:

Hi Kosta,

Build 1.1.-63 is working fine for me. I would suggest that you change the second bullet under your instructions found at your below link. Right now it says:

To install the custom keyboard, go to iOS Settings, FlickType, Keyboard and then enable it. You also need to enable "Full Access" right below that.

I think it would be clearer to say:

To install the custom keyboard, go to Settings, General, Keyboard, Keyboards, Add new keyboard, and select FlickType. Once installed, double tap on FlickType and turn on the Allow full access setting.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Wednesday, May 09, 2018 9:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 63 and beta release plan

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.






Re: Build 63 and beta release plan

Nozi <noziphokhanda@...>
 

The latest build is working well for me. Like chuck, I also think that the beta group might focus on the things that are missing like typing numbers and insertingb new lines etc. I was wondering if that all shouldn't be in the known issues?


Re: Build 63 and beta release plan

Shinji Sakiyama
 

Hi! List I’m Shinji.
I would be happy answer any questions from beta group.
Thank you.


iPhoneから送信

2018/05/10 午前11:16、FlickType <@FlickType>のメール:

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.



Re: Build 63 and beta release plan

 

Hi Kosta,

Build 1.1.-63 is working fine for me. I would suggest that you change the second bullet under your instructions found at your below link. Right now it says:

To install the custom keyboard, go to iOS Settings, FlickType, Keyboard and then enable it. You also need to enable "Full Access" right below that.

I think it would be clearer to say:

To install the custom keyboard, go to Settings, General, Keyboard, Keyboards, Add new keyboard, and select FlickType. Once installed, double tap on FlickType and turn on the Allow full access setting.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Wednesday, May 09, 2018 9:17 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 63 and beta release plan

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.


Re: Build 63 and beta release plan

Chuck Dean
 

Hi Kosta,
I thought you may be close to a beta release when I read the description of the current build.
Isn't this beta release a little premature? I fear the bulk of questions from beta testers will involve how to manually input text, how to cap a letter, how to enter numbers, etc.
I also worry about word of mouth that may discourage people from FlickType if they hear that these things are not available.

I thought the beta would be a version much closer to the public release. I may be wrong, but I thought the current build of the custom keyboard is fairly far from a finished product.

I may be totally off base here, this is my first alpha and beta test.


Chuck

On May 9, 2018, at 7:16 PM, FlickType <@FlickType> wrote:

Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.



Re: Build 63 and beta release plan

Michael Maslo
 

Hello, I would be willing to help answer questions or help on list if you need it. I am always willing to help.



Sincerely,, mike


On May 9, 2018 at 21:16, <FlickType (mailto:@FlickType)> wrote:



Hi all,

The only change in this build, apart from some internal code reshuffling, is to announce the need to open the main FlickType app before the first use of the custom keyboard. As you can probably guess, we are very eager to share this build with the larger beta group, smile. To do this, we need to cover three things:

First, we need to make sure that there's no major usability issues, apart from the functionality that's still missing. If something is majorly broken, or if things are working perfectly, please let us know either way.
Second, we need to make sure that the experience for new users is acceptable, keeping in mind this is still very much in beta. To ensure a good on-boarding experience, we'd love your input on the updated instructions here: https://flicktype.groups.io/g/alpha/wiki/FlickType-custom-keyboard . If there's anything that doesn't make sense, is missing, or could otherwise be expressed more clearly, please let us know. And if there's any issues you notice with the update flow from the App Store build to this build, we'd love to know that as well.
Finally, we expect a large number of questions to come from the beta group during the first few days. If anyone would like to help us answer the common questions, please let us know so we can make you a moderator in the beta group. We'd love to have as much help there as possible, smile.

And if there's anything else you want to bring up regarding the upcoming beta release, we'd love to hear. In the event that everything is ready and working smoothly, we'd love to release to beta as soon as tomorrow, smile.

Thank you,
Kosta & Ashley

PS: I will shortly answer your questions and comments from the last day or so in a separate email.