I also tried editing a word, which worked perfectly, and when I went back to review word by word FlickType pronounced the word instead of each letter. I know this was buging some people. Personally, I expect some trade offs when dealing with accessibility.
 
 Chuck

> On Jun 11, 2018, at 11:52 AM, Chuck Dean <cadean329@...> wrote:
>
>
> Hello Kosta and Ashley,
>
> More great features!
> The dictionary entry works flawlessly and the visual border is very helpful without being too intrusive.👍
>
>> On Jun 11, 2018, at 11:30 AM, FlickType <hello@...> wrote:
>>
>> - Automatically learn new words at end of the typing session. You can always review and remove learned words from your dictionary at any time.
>> - Touch-typed words will stop being editable by character as soon as you start typing the next word. This still gives you the chance to make character edits right after spacing and hearing the word back, and beyond that any cursor move or deletion will affect the entire word.
>> - Introducing corrections for touch-typed words. After spacing and hearing your word, you can now flick down to change it, just like you would if you had tap-typed it instead. This can be useful to add an apostrophe after typing words like "its" or "were", or to properly capitalize a word like "iPhone". It's also a fun way to test the limits of the FlickType correction algorithm by purposefully choosing nearby letters instead of the correct ones, and then checking if your intended word was in the suggestion list.
>> - When editing existing text, such as if you switched to the iOS keyboard and back to FlickType, attempting to change an pre-existing word or punctuation mark will now work as expected.
>> - Low-vision users: added a visual border to help identify the edges of the keyboard more easily. Tell us if this helps your accuracy!
>>
>> Thank you for testing FlickType!
>>
>> Kosta & Ashley
>>
>>
>>
>
>
>