Improved Flow (swipe) feature in SwiftKey for Android
Hello everyone,
We are rolling out a new Flow experience for SwiftKey for Android. The idea of this change is that when Flowing (aka "swipe" gesture typing), we want to provide you with more choices to insert the word you wanted.
How this new Flow feature will work:
You Flow a word. Instead of the prediction getting automatically inserted you will be shown three possible candidates. You can then take one of the following 3 actions:
- Select one of the three predictions by selecting the word. This will insert the word and give you a space
- Continue Flowing your next word - this will insert the middle prediction and auto add a space for you
- Start tap typing. This will also insert the middle prediction and also auto add a space for you.
Basically this is ensure that if the wrong word is predicted, you can easily change it by tapping one of the three predictions. But if it is correct, you can keep on Flowing or tapping just as before and it will use that middle prediction.
Let us know your thoughts on this new change in the comments below.
Cheers,
Ryan, SwiftKey Community Manager
In case you missed it, you can submit a feature request. Many of us have already asked for a toggle switch that would allow us to revert back to the old style flow, but another drop in the pond can't hurt.
https://support.swiftkey.com/hc/en-us/requests/new?ticket_form_id=27342
Please make this an optional feature. It is very annoying having to to change my typing habits. Bring back next word prediction after flow, please!
The comment by @Paul S expresses the problems with functionality of the new flow keyboard perfectly. I hope the SwiftKey team will take a close look at the use cases he describes there.
I think there are more of us who use SwiftKey for tasks requiring us to type grammatically correct prose
Edited to say that I stand corrected. The beta does have the option. Thank you SwiftKey for giving us this option back. All is right with typing again.
I just got duped again. Another update that says i the space issue was fixed. I figured there was no way the "typo" wouldn't have been fixed. Yet, still no space after flowing the word....
"Fixed:
- SwiftKey will now auto space after Flowing and adding an emoji "
Congrats guys :-). We finally have the autospace (as a toggle in typing) :-)
Let's rate it to 5 stars again as a thanking gesture :-)
I can confirm that in SwiftKey Beta there is now a "Show predictions after Flow" option (disabled by default). Description: "Add a space and show predictions after gesture input".
Once enabled it seems to work well. Thank you Ryan and devs for taking our feedback into serious consideration.
I'm hesitant to move from the neutered v6.5.3.35 back to the official app due to the worry of future potential updates as disruptive as the "new flow experience" change was, but this is a welcome solution for this particular episode.
SwiftKey Beta - Apri 24, 2017:
"- Added a setting that inserts a space and shows predictions after Flowing
- The Hub now has its own dedicated button
- Type in 3 new languages: Gallo, Jèrriais, Cantonese LM ✏️
Fixed
- Fixed an issue that prevented longpress to delete in WeChat
- Bracket formatting for Samsung devices using RTL languages"
I second Jackie's statement. Auto space is NOT back in standard SwiftKey, but it's finally optional in beta. I'll be keeping my neutered apk as well, though. Thanks for finally kinda listening. Sort of.
I want to thank the SwiftKey team for keeping us up to date on the situation!
...oh wait
I just installed the update and was pleased to find the toggle at the bottom of typing and autocorrect. Thank you SwiftKey for finally doing something, it's been a frustrating 53 days. I'm amazed that something so simple could take so long to implement.
@Ryan_P
Thank you so much for taking all of our comments into consideration. I really appreciate it and see that the feature indeed works.
Thank you for the patience.
The function is now optional in beta as @Ryan said. Don't forget to tell what do you think.
Just downloaded the beta and the toggle works great - it is now back to its normal behaviour. Thank you for fixing it! Much appreciated.
I've been using the beta for a couple of days now since this came out, and my flowing is now fully back to what it was before. Thank you, much appreciated.
If the current beta makes it to the standard app as it is right now, then I'll change my rating from 1 star back to 5.
As with many others after reading this thread, I would like either the return of the auto space after flowing a word or at the very least and option. My typing and efficiency has taken a major hit with this update.
Long time user and lover of your keyboard but with this I am not impressed whatsoever. It is a downgrade.
@Ryan P...Awesome, awesome!! Thanks very much for this...just downloaded the beta version and it's lovely to have my normal typing back. The impressive feedback I have here is that despite becoming increasingly irritated with the keyboard not adding a space after my words I am still using SwiftKey as it's still better than anything else out there, even when it's not behaving quite as I prefer :)
I hope I remember to keep an eye out for the beta changes going forward and provide feedback - it's fabulous to know that it's taken into consideration and that you engage so well with your users. Many thanks
@Rick,
If you read a few posts back, we added an option so you can adjust your Flow spacing behavior. It is currently being tested in beta at this exact moment.
I will update this thread when it has gone live to the market version of SwiftKey.
We just wanted to let everyone know that the settings option was live in SwiftKey beta.
Cheers,
Ryan
@Rick Springer
Download the beta link Ryan P sent out. You can toggle it on in the settings. It's great and will work just like before.
@Ryan P - you might wants to look at the "What's New" bit of your play store listing for the NON-beta version, which states "SwiftKey will now auto space after Flowing"!
@Chris,
I just had a look at this and did not see that text. You or I may be seeing an older version. But I will look into it further.
Thank you thank you thank you for listening to us and making this "feature" optional. Once this goes live in the version of SwiftKey that I paid for, I will set my rating back to 5 stars.
Ryan,
For the past few days, I have been going bonkers to get it back to where it was. I deleted (and in the process deleted all my saved words) and re-installed but to no avail. The earlier system would put the word there and then new word prediction was already there for me. e.g. I only need to write Happy and then birthday and buddy was already there and I had to just tap the center prediction, and I was able to wish so many people with minimal of fuss.... Can you please revise it to the original way or tell me how I can go back.
If you haven't felt it... let me say it loud.... I hate it, I HATE IT. Please fix it back
Downloaded the beta keyboard and all is well with the world again. Why is this not available in the standard one though? Is it a conspiracy to get more users to use beta version?
@Jasmit
All modifications goes alive on beta version first, if they're well tested and passed public test, we will move it to market version. This is how software improves and be tested, I believe.
Hello everyone,
Today we rolled out SwiftKey 6.5.8. With this new release we have added a setting that allows you to alter how auto-space after flow works.
You can have it auto space or not - depending on your preference.
Here's how to adjust your setting:
Best,
Ryan
Thank you for giving me the option to "revert" back to the original way. I don't have to search for a new keyboard anymore (yes I did start)
@Daniel,
The update we rolled out yesterday does have an option to change the Flow behavior, it should even be listed in the release notes.
See my post with instructions on how to find it:
"Hello everyone,
Today we rolled out SwiftKey 6.5.8. With this new release we have added a setting that allows you to alter how auto-space after flow works.
You can have it auto space or not - depending on your preference.
Here's how to adjust your setting: