• Avatar
    Permanently Deleted User

    Guys, I've been a software developer for almost 20 years.  And one thing I have learned during my time writing software - do not suddenly change the fundamental way your software functions if you don't want your users to get upset.  At the very least you should have introduced this feature in Swiftkey Beta, and you should have made it optional.  Give people the option, see if they try it, see if they like it!  Don't force it down their throats.

    0
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    My favourite app has become useless. Spent a week at it. What are people switching to?

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    This update has stopped my flow completely. I hope you go back to predicting the next word without having to accept each word one by one. The flow used to be fairly accurate. Now I've lost all predictive powers unless I accept each word I enter one by one. Very frustrating.

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    @Ryan P : can you simply tell us if Swiftkey is planning to come back or not about this new feature which a lot of people obviously don't like ?

    If not then I will install another keyboard. At the moment, like many others I'm using an old APK and I would like to know if I should wait for a future update solving this problem or if I should change my keyboard.

    Thank you for your answer which I'm sure can help a lot unhappy customers on this thread !

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    Wow this was an awful change. It keeps changing my words even when I try to just "flow" /type my next word WITHOUT tapping the suggested word. This has immensely slowed down my efficiency and would much prefer the old version.

    3
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    Ryan, we're not asking for a fix for your bad update, we are asking for its removal entirely! Get rid of the changes you've made, there are very few people, maybe no one who likes anything about the update. With terrible bugs like automatically changing words without command, this update is a complete failure even if the bugs are fixed. Listen to the consumers or you'll be losing a lot more. I'll temporarily be installing a new keyboard until you fix this one.

    4
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    Had to Google just to see what was going on with what is typically my favorite keyboard. I also find that this has slowed down my typing as I often capitalize words for emphasis, etc. Now when I want to capitalize the NEXT word (see, I'm doing it just there!) it ends up capitalizing the PREVIOUS word that I just completed. When I hit space to get away from that word, it adds TWO SPACES. What in the world? Why mess with this? I feel like I've trained myself to type in the way that aligns with your app, and then you change it randomly and I can't break the habit. It feels abusive to your long time users. At least provide the option to "flow" as we used to. Thank you for reading.

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Daniel Weis

    @JQ
    The capitalization and double spacing bugs have been patched in the beta version, we'll likely see an update to the regular app within the next few days.

    1
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    @Daniel: can you confirm whether or not the three "predictions" in the top bar after flowing a word are actually predictions (for the next word) and not corrections for the flowed word in the beta? Sorry, I would test but I'm currently happy on the last good SwiftKey version.

    1
    Aktionen für Kommentare Permalink
  • Avatar
    Daniel Weis

    @Jackie
    No such luck. There is still no option in the current beta app to auto-space and show next word predictions.

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Greg Aloe

    @Jacki Chun, the beta is a separate keyboard app.  You can have both installed at the same time and swap between them to test out the beta without losing your good old version of SwiftKey.

    0
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    I paid for this keyboard years ago and have been using it ever since, but the new flow "predictions" suck. They are corrections rather than predictions and have slowed down my typing. The predictions were quite good for me before.

    I will also be changing to Gboard until this is fixed.

    3
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    Just for a change: I actually do prefer the new flowing experience. There is a reason why other successful swipe keyboards do it exactly the same way.

    -6
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    This new feature has been irritating and slowed my typing, I prefer when a space is inserted and the next word is predicted

    4
    Aktionen für Kommentare Permalink
  • Avatar
    Gauravmtulsiani

    Another pointless update.
    Even those(including me) who are using the earlier better version are a part of swiftkey user base.
    I'm Uninstalling sk today, let's take a break from sk,
    If the fall in user base is also not waking these people up, then sk is not worth staying with anymore. 

    3
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    Hey guys,

    First of all, thank you for all you do to make this amazing app.

    Second, I definitely have to thumbs-down this change. It has drastically decreased my typing productivity, probably cutting my words per minute almost in half. It also messes up typing posts or comments on the Facebook app, trying to tag several friends when you don't intend it to. Please change it back to having an auto-space after each word typed via flow. I want to see the next word prediction, rather than options on the previous word.

    I've been a loyal user for years, but this change is making me look for other options, which I definitely don't want to do!

    Thanks for all your hard work. I really appreciate it.

    3
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    My two cents.

    1. I really feel that this goes against the essence of Flow. After all, you'd want to keep flowing without stopping, and when you have to tap an option, it breaks the flow.

    2. I rely heavily on predictions for the next word. Helps make my typing faster. So now that that option has been taken away, it has COMPLETELY killed my typing speed. So much so that I considered Google keyboard, but then decided to try and stay loyal to the SK I love.

    3. I am one of the most inaccurate when it comes to Flow. Over time, SK had learned to deal with my madness, and improved my efficiency by 16%. Now, I'm slower, but mostly because I've been forced into a change I didn't want or need.

    4. After years of using SK's Flow, most users like me have gotten used to how it works. Suddenly, this new method had been thrust on us, without any alternative. I, at least, feel utterly, utterly cheated and betrayed.

    And 5. Consumers today want options. It's said that Android was born because everyone had gotten tired of the fixed, unchangeable iPhone, and wanted something that could be customised to their needs. I'm not against this update, since there are so many people who prefer this way of flowing. But there are equally many others who don't. If this update were an option that could be toggled on or off, everyone would've been happy. Instead, SK is alienating so many of us.

    Bottom line: Please make this optional.

    1
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    More Bugs:

    Whilst I still think the new flow is clearly a step backwards, I have found yet more bugs in it.

    This is SwiftKey 6.5.5.30 on a Samsung S7 running Android 7.0.

    1. If you just straight up flow a url, you get this:

    http://google .com   (extra space inserted before the period)

    2. Now I want to go back and prepend "drive" to "http://google.com."  I put the cursor in the correct position and flow "drive."  Now you get one of two options, seemingly arbitrarily:

    http://drive .google.com   (extra space before the period)

    or

    http:// drive. google.com   (extra space before "drive" and after period)

    I have no idea why one happens or the other.

    At no point do you ever go near the spacebar, but there's spaces everywhere.

    1
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    Another question on the new flow.  (Swiftkey 6.5.5.30, Samsung S7, Android 7.0)

    I flow:

    "My dog is a blood"

    My finger lifts. But now I want to append "hound" to the end.  If I just flow "hound", I get:

    "My dog is a blood hound"

    which is very different from "bloodhound."  How do I append to the last word I flowed?  In the old flow, I just hit backspace.  In the new flow, it would appear that I need to confirm the word is correct, which it isn't, and then hit backspace.  Am I missing something?

    1
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    After trying this new feature out for some time, I've realized I like both options, and thought a combination might be the sweet spot - when SwiftKey is unsure enough on what you are trying to "swype", (ideas on how to do this: check if one of the suggestions to the previous word is also the one SwiftKey thinks you just "swyped". Or if SwiftKey has more than X guesses on what you just swyped) it should act like the new behavior.

    Otherwise if it's very certain it got the swype right, it should do the old behavior.

    This would prevent the many cases with the new behavior, where you have to click on the primary guess SwiftKey, just to get the new suggestions for the next, aka the extra click many people here are complaining about.

    -1
    Aktionen für Kommentare Permalink
  • Avatar
    Jordan Thompson

    Please include an option in the next release that allows for users to turn on the auto-space feature again. The new non-autospace release is not very convenient and somewhat wonky. The new feature does not really make it faster to flow because often the auto-correction options that are displayed are not what I was trying to say. Also, if you need to capitalize the next word, the only way to do it is to hit the space bar, which jumps the text 2 spaces, then backspace one space and then capitalize. If those steps are not followed, the word that the cursor was previously on (that you don't want in capitalized) will also be capitalized. If you want to insert an emoji, you basically have to do the same thing too or the emoji we be attached to the previous word.

    In short, the new release has major bugs with simple and common situations. The previous release did not have any of these problems and none of the issues you were attempting to address really caused much of a problem.

    1
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    So glad I found this thread at last - like others I was baffled as to what had happened when this behaviour changed and messed up my typing with no explanation! I don't have beta enabled yet I have this and it wasn't mentioned in the update info - ridiculous for such a major change. It's riddled with bugs - like the pre-punctuation space and previous-word capitalisation others have mentioned - and generally makes my typing slower and harder than it used to be. At an absolute minimum you need to fix all the resultant bugs urgently; you should also really make this behaviour an option to be selected in the settings; or just abandon this experiment altogether. I bought SwiftKey back in the early days when you still had to and this is the first time I've ever considered jumping ship from it - it's just so frustrating! But having seen this thread I do at least now understand how I'm *meant* to be trying to use it. I think the most important lessons here for SwiftKey are:
    1. Don't put a major change into the main product without giving it time to be thoroughly tested, fed back on and fixed in beta first (surely that's what beta is for?!);
    2. Don't make a change that affects literally every single user who Flows without properly announcing and explaining it so they have an idea why their typing is suddenly going weird and what they should be doing differently!

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    @Paul S - just want to make testimony that I did provide feedback in December when this was rolled out to me in Beta. A couple of others did. Was never contacted nor responded to in the VIP forum.

    Also in fairness to the devs, some of the issues being raised by posters here refer to longstanding functionality that hasn't changed with the recent changes.

    But I still don't like the new functionality and am using an old version. To me this is significant because I'm typically willing and able to adapt and adopt new practices if they're better. But this isn't working for me.

    Meh - maybe I'm just another aging Gen Xer.

    0
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    This is not an I proxenetas. This is not an improvement. This keyboard is currentlyso poorly designed, I've lost the will to autocorrect. Carruaje it back. Change. It. Back.

    See want autopsies. We want autoestopista. We want autoclave. Autospace. Bring back the Autospace feature, This sucks so much .

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    I'm really surprised by the reactions here. SwiftKey has never been a keyboard used by hardcore swipers. If you really don't need to correct your flowed words because of flowing that precisely I'd guess you would be better off typing. It's much faster.

    -5
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    @Po8: I'm not quite sure what constitutes being a "hardcore swiper" or if you have numbers/facts to support your statement that "SwiftKey has never been a keyboard used by hardcore swipers", but if we don't need to correct our flowed words because we flow that precisely, I'm sure we're better off NOT changing our input method.

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    Could anybody from the Swiftkey-team shed some light on the changed capitalization behavior? I'd say if you priories the correction of the flowed word, it should also be possible to change capitalization. No?

    0
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    Simply put, this new flow feature sucks. Looks like I'm using a different keyboard until it's fixed or made an optional setting.

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    Gave this a fair chance, Tried it for a month, hate it. This change completely broke my writing "flow". Now I perform better using my phone's default keyboard.

    Please make this an option that is off by default. I'm going to Google Play to rate SwiftKey down by a couple of stars until that happens.

    2
    Aktionen für Kommentare Permalink
  • Avatar
    Permanently Deleted User

    To be honest, it doesn't matter if this is an improvement or a regression. It's a massive change from the old method, and therefore should be OPTIONAL!!! In the options, there should be a setting where you can choose:

    - Prioritize Corrections (new method): for new users or for those who need assistance with swiping

    - Prioritize Predictions (old method): for advanced users who have trained SwiftKey and wish to take advantage of predictions based on the user's writing habits

    Feel free to default to the first one if you're SO INCREDIBLY INTENT on pushing it, but for Pete's sake give us back the old SwiftKey behavior that we've been using for YEARS and YEARS!!!

    My wife's phone just updated SwiftKey yesterday. I got an earful for not warning her not to let it upgrade. She hates the new behavior so much, she removed SwiftKey and installed Gboard.

    3
    Aktionen für Kommentare Permalink