Typing speed, perspective of a person with very limited vision
|
Field, S. (Scott)
Hi I have both Flicktype Beta as well as Fleksy installed as third party keyboards. I did a test this weekend to see which one I can type faster with. This test was done in a quiet environment where it was easy to hear the voiceover feedback. The result is that Fleksy is still faster due to two reasons only. FlickType is better than Fleksy in all other ways::
Yesterday I was in a noisy restaurant and found it was a pleasure to type out a short message using FlickType as I could see the large typed words and didn’t need to read it back, that was the most pleasant experience I have had when typing out a message on my phone in a noisy area. The app is getting better with every release and it is clear that Kosta and Ashley are working hard to get it right for the blind and low vision community, the efforts are truly appreciated. Thank you Scott field
Nedbank
disclaimer and confidentiality notice: ********************
|
|
|
|
Chuck Dean
Hello Scot, If you manually type a word in flicktype, that word will be entered into the dictionary once you finish the typing session. The only problem with this is if you need to type the same word more then once in a session. As a fomer fleksy user, I am curious, what keyboard configuration are you using? Are you using the space bar or minimal keyboard? Also, when you type with fleksy do you get a stuttering speech when it reads back a word? Also, if you are using the minimal keyboard, how do you insert a new line, and how do you change to the iOS keyboard. These were the main problems I had with fleksy besides the prediction engine didn't seem as accurate. ChuckF
On Aug 26, 2018, at 11:08 PM, Field, S. (Scott) <ScottF@...> wrote:
|
|
|
|
Hi Scott,
toggle quoted messageShow quoted text
Sincerely appreciate the thoughtful review and comparison, thank you! In regards to your first point with the unintentional invocation of the shift shortcut, we've been considering this issue for fast two-handed typists like yourself and we think we may have come up with a simple solution where we require a little longer two-finger tap to invoke shift, that way the system doesn't misunderstand quick successive taps. We will be implementing a fix for this soon. As for your second issue, we agree that the dictionary is not as extensive as we'd like. Due to the nature of our autocorrect engine and ranking system it is quite a large undertaking to update the existing dictionary, though this is high on our list of goals it will take us a little bit of time to get there. We hope the convenience of adding words to the dictionary helps a little bit in counteracting this shortcoming. Thanks, again! Ashley
On Sun, Aug 26, 2018 at 11:09 PM, Field, S. (Scott) wrote:
|
|
|
|
Field, S. (Scott)
Hi Ashley
Thank you so much for the prompt response. I honestly didn't know that words were automatically added to the dictionary when you slow press them, that is certainly helpful, so with more extensive use it will get better and better. Great to hear that you will be implementing a change to mitigate the accidental two finger tap. As always, the app just get better and better. Regards Scott Field On 2018/08/28, 01:34, "hello@flicktype.groups.io on behalf of FlickType" <hello@flicktype.groups.io on behalf of hello@flicktype.com> wrote: As for your second issue, we agree that the dictionary is not as extensive as we'd like. Due to the nature of our autocorrect engine and ranking system it is quite a large undertaking to update the existing dictionary, though this is high on our list of goals it will take us a little bit of time to get there. We hope the convenience of adding words to the dictionary helps a little bit in counteracting this shortcoming. ******************** Nedbank disclaimer and confidentiality notice: This email may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this email or all or some of the information contained therein, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this email is neither an offer or a solicitation to buy or sell any securities, investment products or other financial product or service, nor is it an official confirmation of any transaction or an official statement of Nedbank. Any views or opinions presented are solely those of the author and do not necessarily represent those of Nedbank. Nedbank Ltd Reg No 1951/000009/06. The following link displays the names of the Nedbank Board of Directors and Company Secretary. [http://www.nedbank.co.za/terms/DirectorsNedbank.htm] If you do not want to click on a link, please type the relevant address in your browser ********************
|
|
|
|
Field, S. (Scott)
Hi Chuck Thanks so much for the info on slow pressing to add words, I got into the habit of switching to another keyboard when words weren’t being recognised, should have done some more reading before speaking up ☺ Fleksy is far from perfect for low vision users. I am just used to it as I have used it for a long time. Flicktype is far better than Fleksy for our community of users. Regards Scott Field
From: <hello@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Also, if you are using the minimal keyboard, how do you insert a new line, and how do you change to the iOS keyboard. These were the main problems I had with fleksy besides the prediction engine didn't seem as accurate.
Nedbank
disclaimer and confidentiality notice: ********************
|
|
|