Re: Build 85


Ed Worrell <ed.worrell@...>
 

Hello all,

I am in love with the new add to dictionary option. Great job!👍🏻

I personally do not use the visual markers on the keyboard so I have several people playing with the keyboard. They are a little less tech savvy to put it nicely.

They like the border, but they still would like to see high contrast modes. They like the progress, but would like to see more detail put into bore low vision features. They do understand that this is very much a project in its early stages, and would like to see a full keyboard on screen at some point in the future.
Thanks,

Ed Worrell

On Jun 11, 2018, at 4:11 PM, Dan Lococo <dan.lococo@live.com> wrote:

Kosta & Ashley,

Thank you for all you are doing to make IOS more accessible.

I noticed with the most recent builds that when I go to the share sheet, focus falls to the end of my list. I've organized the list so my most commonly used come first. I find this very handy.

Thanks again.

Dan


-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf Of FlickType
Sent: Monday, June 11, 2018 1:31 PM
To: alpha@flicktype.groups.io
Subject: [FlickType-alpha] Build 85

- 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






Join alpha@flicktype.groups.io to automatically receive all group messages.