• Avatar
    Permanently Deleted User

    Yeah this is a pretty terrible update, especially with the lack of patch notes about it and no option to turn it off. I was with the majority of the other users here in thinking that it was a bug. This update is essentially admitting that flow is so inaccurate that the default behavior expects the user to correct it. Having to press space or the middle button after each word to get a prediction drastically increases the number of actions needed in order to write the next word.

    2
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    So, I got a response from SwiftKey support about this. All they did was explain how it's supposed to work, make my life much more enjoyable, and save kittens and the world all at the same time. And that I should just keep using it to see how much I'll love it. 

    So, I explained that they were wrong, that I and many other hate it, and that I was downgrading. Which I did. Life is much better now that I've gone back to a working version and turned off auto-updates for it. Thanks so much @Jackie for the info.

    5
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Just adding to the chorus. This new system is not working for me. Please give us an option to return to the old system. Or, I guess, failing that, some proof that once we relearn the new system it'll be faster for us?

    6
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I have been really frustrated with the recent update but I'm hoping now that I understand the thinking behind it I will get accustomed and appreciate it. My main complaint is that when all three options aren't what I want I have a hard time getting to what I actually want. It seems more difficult for some reason. Also, the capitalization issue that people have mentioned is very frustrating and a time suck to try to overcome. Could SwiftKey offer the option to go back to the old way if people want?

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Whoever. Signed. This. Annoying. New. Feature. Should. Be. Fired!
    Please give us the option to turn this off. I too thought this was a bug. How annoying is this now? I want my predictions back. This is so slow now. Swiftkey was the reason I moved from iOS in 2013. But this is horrible now. Uninstalling for now. Gonna Try Gboard.

    6
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I'm glad that I came here before submitting a bug report, because I thought this was a bug from the last update. I agree with the complaints here, because my experiences are exactly the same. Please let us choose to switch back, because this is really killing my efficiency, and I shouldn't have to retrain myself after using SwiftKey the same way for years. I only skimmed past the first page, but I wasn't sure if anyone else also had the problem where it will change the previous word to "I" when they start flowing the next word? It's happened a few times to me, but I can never replicate it when I try. Otherwise, the missing/doubling space bar is absolutely killing me.

    7
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I objected to the capitalization issue on the VIP forum way back in December when it was first rolled out to my phone (but not my tablet, which made it especially crazy-making - I spent 15 minutes of my precious time comparing settings to figure out the problem). The developers made no response, and now I find the non-optional correction over prediction feature rolled out to the stable build on my phone. So I'm gathering they have a long game, with some far more efficient system or use we haven't thought of (perhaps related to voice to text?) or have done market research showing that (as I've mused in the past regarding the weird colon spacing) the majority of target users don't care about correct spacing and capitalization.

    Or perhaps there was some method in the madness of SwiftKey 's insistence on permanently learning to capitalize some words - the devs may fancy they can predict all possible cases in which users may wish to capitalize or USE ALL caps and gamble the exceptions will be few enough not to allow the average user down.

    I think they may not have a firm a grasp of who their average user is, if that's the case.

    I'm Using Swype again on my tablet, And Gboard on my smartphone, but I'd *love * to be able to come back to SwiftKey when this gets made into an option.

    5
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I agree with some others, noticed the change. Thought it was a bug, restarted my phone and it didn't fix it. Bummed, not a big fan of "update". Just my $0.02

    2
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Well, add me to the list of people that hates this new feature. I thought I was doing something wrong or that it was a bug. My wife ran into it and asked me to fix her phone. I start searching for a solution and I end up here. Bummer that this is being forced on us rather than being made optional. I rely on predictions a lot and this has seriously killed my typing speed. Way to render your single most usable feature completely useless.

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I just realized installed os on two phones and thought my phone was broken. My productivity has slowed a lot due to changing the way I have been typing for the last 4 or 5 years. Please give us the option to use either way.

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    We're preparing a story about the outrage, but none of us are seeing this feature live yet ourselves. Could someone please post a few screenshots?

    -1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Artem - You've already published an article about the new "feature" - http://www.androidpolice.com/2017/03/16/swiftkey-beta-improves-flow-experience-3-possible-predictions/

    This is what all the complaints are about, no other live feature to post screenshots of.

    2
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Chris I realize we did, but it has no screenshots. I'm asking for screenshots of the feature so we can compare to how it used to work (and still does for us) and understand what has changed better.

    -2
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Artem - I can't, sorry. I rolled back to the old version using an awesome website called APKMirror that some super helpful people made!

    The new versions are on there too though.

    2
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Chris The feature is server-controlled even on the new builds, so we're not seeing it. I imagine if the full SwiftKey user base suddenly got them, we'd be seeing a lot more concerned comments here. I'm curious what percentage of users have it enabled now.

    -4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I just updated Swiftkey 2 days ago and I have to agree with everyone else here, the latest update stinks and I spend more time correcting errors and stuff then I do actually typing (flowing) now. No more automatic space with next word prediction, if I tyr to capitalize the next word, it will capitalize the current word, I get double spaces all the time... I have been using this SO LONG (back when I actually paid for it before it became 100% free) and until this issue gets fixed, I think I am going to either roll back one or two versions or look for another option. I wouldnt mind if this "new" feature was in the app but make it an option so I can turn it off! This is the first time I have ever really had a big dislike for this app in years.

    5
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Chris, what version dod you go back too? I cant take this nonsense any longer with this latest update. Looks like there were a few minor updates over the last few days and dont want one with this new feature junk. Thanks

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Thanks to the message of Jackie Chun I could downgrade to version 6.5.3.35, Swiftkey is working again as expected.

    @SK team : Guys I don't know how you make business, but in my company when we receive such an amount of complains we try to correct the problem quickly or at least answer to the angry customers... 

    6
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Dear Ryan P, this is a feature only when I have a choice to turn it on. Otherwise it's a bug.

    This is seriously impacting my typing speed and my productivity.

    Switching to old version right now.

    Please bring back the autospace feature. Let us decide for ourselves if we want it or not. Thanks

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I would like to echo the complaints of the other users in this thread. I've been using SwiftKey for three years and find it unusable with the most recent update. I have downgraded to version 6.5.3.35 using the APK provided at APKmirror.com and disabled automatic updates from the Google Play Store.

    4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    This new "feature" has slowed down my typing by a huge margin. I know I am just adding to the chorus but hopefully the more complaints you get, the faster you will fix this and bring the old system back.

    4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    To echo everyone else here : I hate this feature, it slows down typing efficiency, and I thought it was a bug until I came here. Please get rid of it.

    4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    So the last "good" version is 6.5.3.35 I just switched back and it feels as good as before they introduced this bug ;)

    3
    Acciones de comentarios Permalink
  • Avatar
    Greg Aloe

    @Artem,

    Here's a tip if you want to compare the new and old features.  Install SwiftKey 6.5.3.35 using the advice offered by others.  Then install the latest SwiftKey Beta.  Now you can swap between keyboards without having to reinstall.

     FYI, I don't know if my posts are too long or what, but it seems when I post, it's set as "pending approval" first.  Sorry if my help comes late.

    Since I'm writing again, I want to add more details about one of my negative experiences with this new bug, ahem, I mean feature.  As veterans know, pre-feature, when you need a correction after a flow, you simply hit backspace to see two additional options.  For me (and probably for all veterans), I use this backspace less often than not because my Flow is fairy accurate.  But when I do backspace, I usually end up having to delete the whole word anyway since the two additional options are usually not the word I was looking for.  Therefore, when I try the new feature, even if I Flow the wrong word, I rarely see the word I want in my three options.  So yes, maybe the new feature allows me to make the decision to delete the whole word without having to first hit backspace, but as a whole, that simplification does not outweigh the fact that we need to tap the middle correction for the strong majority of the words, which we already Flowed correctly.  As suggested before, to improve the keyboard's productivity for veterans like me, they should provide a feature that makes it easier to delete the whole word (like the backswipe does when Flow isn't enabled).

    I appreciate the positivity offered by some people in this forum, such as Marty and Krissa, but my suspicion is that this has more to do with gaining popularity with new users.  Newer users are more focused on the correction as they learn to Flow.  But veteran users are more experienced at Flow, allowing them to leverage the power of the predictions.  The problem with their decision is that newer users will eventually become veterans and they'll quickly lose the long-term benefits of the previous behavior.  As I wrote before, it's a shame that Microsoft/SwiftKey would close the door on the veterans who have been using and promoting this keyboard to their friends and colleagues for 5 years.

    I continue to be infuriated by the lack of response from Microsoft/SwiftKey.  We want explanation or at least some comment to give us expectations about whether they plan to react to our feedback.  So far, the responses from SwiftKey in this thread are one direction.  They are passing along our feedback, but they're not standing up to their development or marketing teams to demand a response for their angry users.

    2
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Artem Here are some screenshots of the old Flow behavior compared to the new one.

    I swiped this with the old Flow behavior. Note the list of words on top of the keyboard is a series of suggestions for the next word, predicted based on my usual typing pattern. And there's a space immediately after the word I just swiped, that SwiftKey inserted:

     

    This is me manually capitalizing the letter "i" by tapping the shift key before tapping "i":

     

    This is me tapping the shift key twice before swiping the words "all caps":

     

    And the following screen shots are the new Flow behavior. Here you can see no space has been added after the word I just swiped. Note the list of words above the keyboard is now a series of suggestions for the word I just swiped. One of them is the word that just got inserted (I'm expected to tap it or the spacebar or some punctuation to confirm it). One of them MIGHT be considered a pseudo prediction:

    Here, once again, I tapped the shift key before tapping the i. Notice how the previous word got capitalized too:

    And again, same example as I showed above, I double-tapped the shift key before swiping the words "all caps", and the word immediately before got all-capped too:

    And once again, in all the examples of the new Flow behavior, the words that showed up above the keyboard are completely different. Possible corrections instead of predictions.

    With the old way, I almost never interact with the spacebar at all. I just swipe from word to word or tap from prediction to prediction. If a swiped word gets inserted wrong, I just tap the backspace key to get a series of suggestions for correction, or fix the word manually if none of the suggestions are helpful. I need to do this relatively rarely (some days more than most).

    With the new way, it's as if I've hit backspace after every word. I don't get predictions unless I hit the spacebar, some punctuation, or a word above the keyboard. I now have to interact with a bunch more keys before I can get the predictions I've grown accustomed to.

    edit: feel free to use these on AP or wherever to illustrate the differences in behavior. I want no attribution, just consider these "public domain".

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I just posted a 1 star review, and will be going back to the last good version until this is fixed.  

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Yes, 6.5.3.35 is the last good version before they snuk in this horrible forced so called feature. I call it a major bug myself. 6.5.4.25 doesnt mention it in the change log, but it's in there so make sure to go to 6.5.3.35 if you would like to live without it.

     

    Feels so good to be back on 6.5.3.35. I wont be updating until this it fixed either.

    4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Artem I wrote an entire post earlier including 6 screenshots of the old vs new behavior, but it's "pending approval" (likely due to the inclusion of images) and will likely never be published, so I sent the same info via the AP "Tip Us" page instead.

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @frank gore, I seen it but now it seems to be gone. Maybe it was the size of the images or something but it was there for a while.

     

    I wonder if they are even taking all these comments for the huge dislike of this so called feature into consideration and fixing it. What shocks me is it wasnt even rolled out into the beta that I know of. They just snuk it right in there and didnt tell anyone. So glad I paid for this app before it was 100% free. haha

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Kevin I had resized the images in a subsequent edit so they didn't look so huge. Maybe the multiple edits got it flagged for "Pending approval", or maybe the SwiftKey team doesn't want these details to be made public. Who knows? Either way, I hope the info gets published.

    1
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.