• Avatar
    Permanently Deleted User

    The issue is finally being made public:

    http://www.androidpolice.com/2017/03/21/swiftkeys-new-flow-experience-completely-ruined-keyboard-many-users-microsoft-still-monitoring-situation/

    Including some meaningless response from Microsoft. I wonder if it'll make any difference...

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Another thing about this that keeps bugging me is that they keep saying that it is showing us 3 possible "predictions."  Those are not predictions if they happen after the word is already typed or flowed.  Those are corrections.  By the definition of the word, "predict" means to "say or estimate that (a specified thing) will happen in the future or will be a consequence of something."

    To me, 3 predictions would be 3 words that would come in the future, not fixes for something that happened in the past.

    The main point of differentiation between Swiftkey and other keyboards to me was always their prediction engine.  They seem to have effectively removed that and moved to a correction engine instead.

    I know it's just semantics, but still when they change something like that without notice, and then try to pass it off as a feature using wording that is simply incorrect, it is irksome.

    3
    Acciones de comentarios Permalink
  • 3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Count me in on the dislike party. Not providing instant predictions makes my writing slower. Works well when typing, sadly not when swiping.

    2
    Acciones de comentarios Permalink
  • Avatar
    Ryan P

    Hello everyone,

    We just rolled out a patch to the beta version of SwiftKey Keyboard for Android.

    This patch addresses two bugs that have been reported here:

    1. The double space bug for users who had auto correct turned off
    2. A capitalization bug that made it difficult to make your next word in caps when Flowing

    Please do let us know if these changes help improve your overall experience. 

    Best,

    Ryan, SwiftKey Community Manager

    -5
    Acciones de comentarios Permalink
  • Avatar
    Kenneth Brian Lambert

    Serious question: how do I unsubscribe from emails regarding this thread? I'm getting email after email every time someone posts something. This wouldn't have been a problem if SwiftKey would have stuck to their previous forums which were compatible with Tapatalk...

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    OMG, they're totally tone deaf. Buh bye SwiftKey, hello Gboard. Thanks for the incentive to explore different keyboard apps.

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Kenneth at the top of each page, where the original post is displayed, there's a small link labeled "Unfollow". Click that.

    1
    Acciones de comentarios Permalink
  • Avatar
    Matt Phillips

    OH. MY. GOD. @Ryan P, NOBODY HERE IS ASKING YOU TO FIX THE DOUBLE SPACE AND CAPITALIZATION BUGS, WE'RE ASKING YOU TO PUT BACK AUTO SPACING IN FLOW, THE REMOVAL OF WHICH IS WHAT CAUSED THE "BUGS" TO BEGIN WITH!!! WHAT IS WRONG WITH YOU DEVELOPERS?!? HOW MUCH IS MICROSOFT PAYING YOU TO DESTROY A PRODUCT THAT WE PAID FOR AND HAVE JOYFULLY USED AND ADVOCATED FOR HALF A DECADE?!? Thank God for APKMirror and the old version of SwiftKey! Through the course of all this, you people have proven yourselves to be the most careless developers money ever bought.

    7
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Ryan P - I'm not going to update until you bring back the space after the word. The two things you mention are minor bugs, the issue is you fundamentally changing the product to focus on correcting rather than predictions.

    Could you say if you ever plan to sort it out? Then I can decide if I will find an alternative keyboard or wait for you to listen to your customers.

    4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Ryan P - I look forward to trying the patch. Thanks for creating a patch to address the issues you mentioned.

    0
    Acciones de comentarios Permalink
  • Avatar
    Daniel Weis

    @Ryan P - The update has helped me significantly already, thank you. I really hope the SK team takes our pleads for a toggle switch seriously. The forward looking predictions were THE differentiating factor that made SK so much faster than the competition, and it's sorely missed.

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Add me to the list of people who do not like this new update. I didn't realize until you made this change how much I use the predictive text. Getting really throws me to look up and see the word I just wrote, instead of the probable next word. I imagine some people will like it, and they're not likely to come looking for an answer, so they won't find this post. So this may not be a representative sample of users, but hopefully it's a strong enough response that you will make this an optional feature, rather than forcing not on those of us who don't like it.

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I'm glad we've heard back from the SwiftKey team. This is a step in the right direction.

    The core issue for me is that after flowing, the three words shown in the bar aren't "predictions" anymore, rather they are "corrections". (see http://www.androidpolice.com/2017/03/21/swiftkeys-new-flow-experience-completely-ruined-keyboard-many-users-microsoft-still-monitoring-situation/).

    Because of this unannounced, unsolicited change, the newest SwiftKey version can no longer be marketed as a "predictive" keyboard app if all it is doing is recommending corrections. It has completely lost its competitive edge and Gboard is looking more and more like a worthy replacement for SwiftKey.

    Essentially, if the flow behaviour as it is in v6.5.3.35 is restored, or is made into an option, I'd be a happy camper.

    4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Dear Ryan,

     

    To be precise about the experience I used to have with Swiftkey:

    - I start flowing "This" remove my finger from s and what I get is: "This "
    - Immediately after removing my finger, this and space are typed and I get 3 predictions: "is", "is a" and "evening"
    - I'm going for this is an example so I choose "is"
    - next predictions are "a" "an" and "the"
    - I choose and and flow "example". "Example+space" is immediately there together with 3 predictions...

    You see where I'm going? I flow, I get the word typed with a space and I get 3 predictions. This was the old keyboard.

    With your new changes, I flow "this" and then instead of getting a prediction I get 3 corrections. So I have to do it twice: flow "this" and then choose "this".

    I think it's pretty easy to understand. Thanks for your efforts. Please give us the best feature, the "spirit" of Swiftkey back.

     

    1
    Acciones de comentarios Permalink
  • Avatar
    Ryan P

    Hello everyone,

    Thanks so much for writing in on this thread. We’re sorry so many of you are upset by this change.

    I’m working to provide as much clear feedback direct to the developers as possible and it would be helpful for me to get specific examples of how this change is slowing you down and when you’d expect something different when Flowing than what you’re seeing.

    This would be most useful in context of actual sentences you are typing. Again, we really appreciate your feedback and time spent helping us out.

    Best,

    Ryan, SwiftKey Community Manager

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Ryan: to be fair, the article on Android Police express the problem very nicely - http://www.androidpolice.com/2017/03/21/swiftkeys-new-flow-experience-completely-ruined-keyboard-many-users-microsoft-still-monitoring-situation/

     

    But I'll try expressing my issue here. Right now I feel I need to press-to-confirm each word I'm gliding, in order to see the actual useful part which is the predictions for the rest of my sentence.

     

    For example, previously, if I glide "Hello", I would get the word "World" predicted and I can simply tap it in order to create the sentence "Hello World".

     

    Now, if I glide "Hello", I get the word "Hello" predicted, and I need to tap it in order to confirm that I wanted to type that word, THEN I can see the predictions, and tap the word "World" in order to create the sentence "Hello World".

     

    Or, in other words, before the update, I could type "Hello World" with glide+tap, now I have to do glide+tap+tap. So you've effectively doubled the number of taps I have to do, and slowed me down.

    2
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Ryan,

    I find that almost all of the time for me when flowing, swiftkey gets it correct the first time.  When it does get it wrong, about half the time the "predictions" (which are really just corrections), are all wrong as well, so I have to go back and re flow it anyway.

    As I mentioned in a previous post, what I expect from a prediction bar is that it will give me predictions of what I might type next, not corrections of what I already typed/flowed.  As soon as I hit the spacebar or click on the correct correction, then it gives me the next predictions.  

    The way it worked before, as I was flowing, I could glance up at the predictions and see if the next word or 2 were there.  If not I would continue flowing.  Sometimes I could type most if not all of a sentence just from those predictions.  The way it works now, as I flow, I see the word I just flowed and some other correction options, so I just keep flowing and not using predictions at all anymore, which is where my slowdown is.

    The other reason that the corrections is pointless for me is that many times when I get something wrong, I don't notice it until I go back and read through, which means I have to click on the word to change it anyway, which still works the exact same as I used to.

    Basically what it boils down to is that I have yet to use your "new improved" predictions/corrections to actually correct a word that was mistyped, and instead just lost any speed from future predictions.

    There is now no differentiating factor in my mind between Swiftkey and any other swiping type keyboard.

    0
    Acciones de comentarios Permalink
  • Avatar
    Ryan P

    @Nicholas,

    Thanks for that example, it was helpful. I see how those extra steps impact your typing experience. 

    Not trying to have you alter how you use SwiftKey, but could you also not just flow the word "World" and ultimately it would be the same amount of steps?

    I guess this still requires more effort by having to gesture type the word versus seeing the word "World" sitting waiting to be inserted.

     

     

    -1
    Acciones de comentarios Permalink
  • Avatar
    Ryan P

    @Josh,

    Thanks for your insight as well. It seems to most people in this thread, Flow predictions seemed to work quite well the first time. 

    I've never personally been much of a retro active corrector, I tend to make sure the word is right before I move on. Different strokes for different folks.

    There has also been a lot of chatter around the words corrections and predictions when talking about this new experience. This has also shed some light on how you guys think about SwiftKey and what you get out of it. 

     

    -1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Yes, I could indeed flow "World" as well, but SwiftKey has known me now for so long that I can simply flow a single word, and get 75% of the rest of my sentences as predictions.

     

    I am rating my typing speed like this from faster to slower:

    tapping a prediction

    flowing a word

    spelling the word

    So if I can chose between flowing a word or tapping a prediction, I'd rather tap the prediction. I'm an exact typer type, and this fits my style better. I'm still pretty slow at flowing, because I try to be too exact. OCD and all.

    1
    Acciones de comentarios Permalink
  • Avatar
    Ryan P

    @Nicolas,

    Fair points, thanks for being honest and providing examples. 

    Tapping the prediction does seem like the fastest thing one could do. 

    Cheers,

    Ryan

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I have some common messages that I can get entirely from the predictions.  For example, I go to the gym 3 nights a week.  When I leave, I text my wife to see if she needs anything on my way home.  I flow the word heading, and hit the middle prediction 4x, and end up with "heading home now, need anything?"  That's WAY faster than swiping all of those words.

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I guess I can see the reason for this logically, but it feels like a backspace, feels like it throws off my "flow." When I type the word, and look for predictions for the next word--and have to either confirm the word I just flowed, or flow the next word. If I'm using a common phrase--like "heading home now, need anything?" from the last example--I like to swipe "heading" and then see that it has anticipated the next word. I know I could swipe "heading" then select "heading" then tap the center for "home" "now," but the two steps to make the first word seems like it slows everything down.

    I was hunting through the app settings trying to find where I changed the settings to mess up my flow. I wish I could find a way to change it back.

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I honestly cannot say if I flow or type more, but as others mentioned, the combination of flowing and typing was something SwiftKey really made special. Especially, since you seem to be very proud of your neural prediction (which works great, indeed!). And with this step, you take the prediction aspect away, at least for people flowing a lot.

    0
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Being an app developer myself, I know the urge to find small issues in my apps and try to fix them optimally. However, with 10 years of experience, I've also realized one should usually add a toggle when introducing fundamental changes to the core features of an app.

    Everyone can do mistakes though, so please go ahead and state that "oops, we probably should have added a toggle for this one" and inform us that you're working on the toggle.

    5
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I'd still like the space to automatically appear after I've typed a word, please. Thank you.

    4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    How can I go back to the previous version of swiftkey? I don't like the change at all.

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Out of the 200 comments in this thread, only 5 people (except mods) had an account before this "feature".
    At least you got some more users on the support-site.
    I have already changed to GBoard. Would probably change back if this is fixed, but from the comments of the mods it doesn't look like they are interested in fixing it.

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Please, change this unproductive "feature" going to gboard until you revert.

    1
    Acciones de comentarios Permalink