• Avatar
    Permanently Deleted User

    I do not like this new feature. It has significantly slowed down my flow speed. I only downloaded this keyboard about a year and a half ago because I moved to LG and this was the closest thing I could come to the keyboard on my HTC One M8. Please allow us the option to turn this new feature off. I'm struggling to even type this message

    11
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Guys obviously this page isn't being monitored.
    For the old flow, or an option for autospace, let's rate and review on play store. That might make things happen.

    2
    Acciones de comentarios Permalink
  • Avatar
    Kenneth Brian Lambert

    Gaurav Tulsiani
    Quit being so overdramatic...
    1) Of course this thread is being monitored. Members of the team have posted in this very thread!
    2) This is the beta keyboard. Where they test new things out. If you don't want to take part in the beta process, then use the regular keyboard, not the beta version.

    We all have our opinions and input on the new feature. I hear you guys loud and clear. My take on it is this: I need corrections when flowing, not predictions. Flowing has such hit or miss accuracy, it's much more convenient to have corrections instead of predictions. When tap typing, I'll take predictions over corrections, as my tap typing is pretty accurate, corrections are needed less.

    -4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I'm not on the beta version and I have this feature.

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Kenneth Lambert,
    As others have pointed out, this feature is being rolled out to non-beta SwiftKey and some non-beta users have already reported this feature.

    My question for SwiftKey then is why even have this forum or the beta version if they are not going to listen to the feedback of their users?

    I've tried to give the new Flow a chance, I really have. But I still hate it. I miss my predictions. I find myself tap typing rather than flowing and it makes me a lot slower. The majority of the feedback here has been negative, though some have expressed that they like the update. Personally I would rather have predictions back. It seems to me like this is a feature that would best be made optional so those who want predictions rather than corrections can have them.

    Please SwiftKey, listen to your beta testers.

    7
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Kenneth, this is happening even with the regular version of SwiftKey.

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Thanks Corey, Rainyday and Raphael, I was actually gonna check the non beta version, but no need now.

    @Kenneth Lambert, bro one long old post does not mean this is being monitored. 

    And exactly, the purpose of beta testing is checking whether a feature is welcome or not. As you can see the majority of users (those who have synced with swiftkey so well that it has almost learned their own mind), get their first time flows perfect. Unlike the new users who have to correct often.
    And your flow is not showing you correct words often clearly indicates that swiftkey is still learning your typing pattern.
    With all due respect, if anyone wants practical results, play store review is the way devs would pay some heed.
    Further since many of the newer users like the new flow(which I'm sure you'll find useless once swiftkey always flows correctly your first word), why not suggest them keeping an option like, "Autospace after flow".
    That way everyone can have what they want.

    6
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I dislike the new changes. I prefer the space happening after the current word because it allowed me to see my predictions. Now the 'prediction' bar just shows options for what I just typed. Frustrating!! Is there a way to use the old version?

    3
    Acciones de comentarios Permalink
  • Avatar
    Daniel Weis

    Please upvote if you agree!

    1. Space-bar should select the middle prediction and add a space. Not two spaces.

    2. Tap typing should edit the current word instead of starting a new word. At the very least make it an option.

    3. Make this [Improved Flow] behavior optional altogether. Give us back the option to have look-ahead predictions.

    9
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    NOT an improvement. I've been using SwiftKey for years, and this is a fundamental change that completely breaks everything I've learned over those years. Capitalization of words is completely broken, everything needs to be done backwards now, and my typing speed has plummeted. Not to mention that the lag on the keyboard is HUGE now!!! Words take an eternity to show up on my HTC 10 after I've swiped them.

    Please either make this change OPTIONAL or get rid of it immediately. This is absolutely awful. I cannot stand to continue using this keyboard on my phone the way it is now.

    8
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Unfortunately I have to agree with most on this post that this new feature is junk. I don't understand what the intent of the change was. It forces me to stop after every word to make sure it was correct, and the conflict with instinct to make sure there is a space after each word in intense. SwiftKey should realize that likely 100% of users also type on a real keyboard (laptop, whatever) and of course we ALWAYS have to make sure there's a space after each word. Now, since there are no longer spaces after flowing a word, it is raging aggravation to keep flowing when we don't see a space. The only logic I can possibly imagine is that you are about to charge for using SwiftKey, so you took away one of the most useful features from the free version, and will come out with "well, if you want that functionality, you'll have to buy SwiftKey now". Otherwise I just don't get it.
    The irony is not lost on me (and hopefully also not lost on SwiftKey developers) when i say that now SwiftKey is worth every penny I paid for it.
    It was working fine, and you broke it.

    7
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    @Ryan P is probably paying attention, if you look at his comments you can see he is pointing people to this thread. Whether or not he or SwiftKey cares is a different story. They probably pumped a lot of money into it and hopefully regret not making it optional and off by default.

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    this new feature is horrible. SwiftKey was unique until the last update. now you killed that unique feature.. I used make corrections very rarely. but I use predictions very often intact these auto space after predictions make my typing faster. now there is no point of using SwiftKey even my default android keypad can flow words like this new updated SwiftKey.
    please make it as it was before.

    7
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Marty C said:
    "The only logic I can possibly imagine is that you are about to charge for using SwiftKey, so you took away one of the most useful features from the free version, and will come out with "well, if you want that functionality, you'll have to buy SwiftKey now". Otherwise I just don't get it.
    The irony is not lost on me (and hopefully also not lost on SwiftKey developers) when i say that now SwiftKey is worth every penny I paid for it."

    LOL! SwiftKey used to be a PAID app, and they had separate phone and tablet editions that had to be purchased separately. All those years ago, I bought both of them. If it weren't free now, I'd be demanding a refund.

    5
    Acciones de comentarios Permalink
  • Avatar
    Daniel Weis

    I paid for it back in the day and I'm starting to want a refund.

     

    6
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Wow. I bought SwiftKey back in December 2010 and have been using it since then, flowtyping since it was first available. And not until this day have I hade reason to come here and register an account just to say how horribly the new flow typing functionality has destroyed my SwiftKey experience. 

    If you still see any reason to keep the new functionality, for goodness' sake make it optional.

     

    7
    Acciones de comentarios Permalink
  • Avatar
    Ryan P

    Hello everyone,

    This page is being monitored. I was sick and on vacation last week. So sorry for my lack of activity. 

    All feedback is heard loud and clear. 

    • This feature is now beyond beta and is rolling out to SwiftKey market. 
    • There is not currently an option to toggle this on/off
    • There are a few known bugs, mostly the capitalization one. It's being worked on
    • For users who are having this double space bug, please submit a ticket via the support site so we can look into it. This is the first time I'm hearing about it.

    Best,

    Ryan

     

    -10
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I should take a page from the suggestion box that my wife keeps giving me and say that I apologize, as I shouldn’t be posting purely negative comments like I did.

    I expect that with time I may get used to the new functionality and be OK with it. Ryan P, the Swiftkey (SK) Team dude above said it himself, that the three words that appear are no longer predictions for the next word, now they are possible words for what you just typed. I won’t say Swyped, because Swype is SK’s competitor, and they recently did just that. They started out free, but changed to being a paid app, and that’s how and when I landed on SK.

    I can see the benefit of now listing possible words for what you just typed, if SK or the user has trouble with text entry. The old way of listing three word predictions for your next word isn’t of much use if the previous word was incorrect. I guess my frustration (from a free app on my smartphone, admittedly a first world problem and “I should be ashamed”, ahem) stems from the fact that old way seemed to work perfectly fine for me. More often than I could possibly explain, the word predictions were accurate, almost wizard-like. It wasn’t broken, so why mess with it? The new functionality really does feel like a step backwards, like saying “well, we are no longer smart enough to predict your next word so we’ll just list variations of what you just typed”. It feels like SK’s baby sibling now.

    And so far I am finding that the 3 word options of what I just flowed is somehow less accurate than it used to be (didn’t used to be 3 options, it just used to be SK’s understanding of what you flowed), and certainly less accurate than the old word predictions, which shouldn’t be a surprise since SK has less info to work with at that point.

    Currently I don’t like either change (the new lack of the auto-space, and the loss of predictions), and it feels like strike 3 when you realize that you get the word predictions back when you manually enter a space. Huh? Wait what? I don’t get it.

    I am trying to be positive. I am positive I don’t like the changes yet. Does that count?

    How about this: Patience, patience, grasshopper.

    2
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    What about the other issues, such as no auto space after a word is typed thus resulting in the need to hit the discerned before seeing your predictions? This makes me want to change back to the swype keyboard.

    1
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I'm sorry, Ryan. I think it's not an answer for all your customers who bought it and had an experience for years.

    You can't just ignore our request and expect us to deal with it.

    Reconsider your answer and let us know when we will get an on/off button for this.

    8
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    And these changes resulted in my use of an incorrect word in my above post... 😡 I was trying to say "resulting in the need to hit the spacebar before seeing your predictions."

    2
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Why would you roll out a feature without making it optional? Then when we give you the feedback about hating it, you push forward and roll it out to the masses? Makes no sense. Take the Pokémon Go route, ignore your customers wants and feedback. Just roll out new non optional features to the world and enjoy the rating drop.

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Hey Ryan,
    I'm a long time SK user and fan. I recommend it to anybody I see with a stock keyboard, and have only had positive feelings towards its improvements over the years. You really have developed the perfect keyboard in my opinion.
    I, like many of your users, have spent the years getting better and better at gesture typing, right alongside your improving prediction algorithms.
    Please, actually consider this. This new feature is a big leap backwards for those of us who have come to trust Flow and its ability to 'magically' know what we are typing.
    Switching back and forth between Flowing and tapping the generated predicted next word is by far the fastest input method available on phones today, and this newly required additional tap between that transition throws a large wrench into that.
    This new feature drove me to search for SwiftKey Support, hoping it was a bug, and has now driven me to comment on a forum, something I've never done.
    I have much love for your work and your app, and at the very least I'm hoping you read this and consider making this feature optional, meant for those who haven't quite nailed down Flow typing yet.

    Thanks for reading and thank you for this keyboard! I truly don't want to have to search for another.

    9
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Based on what I'm hearing from the SwiftKey reps in this thread, there's no plan to either revert this functionality or make it optional. Therefore I am uninstalling SwiftKey and using something else. I can't believe this half-baked feature got pushed out to the regular app before being fully vetted in beta. You've fundamentally destroyed the way I use an on-screen keyboard. My 1-star review in the Play Store will remain. You just lost a 4+ year customer who gave you money multiple times (for both the paid apps and a bunch of themes).

    Does this seem drastic? Maybe, but other than the touch interface, the keyboard is the main way I interact with my phone. Forcing these changes on us UNANNOUNCED is insulting.

    6
    Acciones de comentarios Permalink
  • Avatar
    Ryan P

    I understand everyones frustration and like I said, I'm sending this feedback to the product team. 

    I cannot speak on what is to come or to be. 

    @Dawn, given the current new feature, you have two options, adjust your settings so that spacebar inserts the middle prediction, or tap on the word of your choice to see next word predictions. 

     

    -7
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    echoing everyone else's sentiments here - I'm absolutely not a fan of this new Flow behavior. it's extremely awkward and capitalizing things is nearly impossible.

    it would be best if this change were just reverted - otherwise I'm probably considering switching to another keyboard app, which is a shame because I've been using SwiftKey for nearly two years.

    3
    Acciones de comentarios Permalink
  • Avatar
    Greg Aloe

    I fully agree with Ryan Pool.  I am a paid user and I've recommended it to many other paid users over the years.  And honestly, the keyboard has been so valuable to my productivity that I would pay you even more to revert the feature or make it optional.  I was lucky enough to stumble over it in the beta version, so in the meantime, I'm using the non-beta version and I am simply not upgrading until I know you've provided the old behavior.

    I also agree with Boaty McBoatface (Airplane).  If this thread is the forum for beta feedback, and if the beta feedback has been predominantly negative (with many users thinking the change in behavior was actually a bug that they wanted to report), then what sense does it make to roll it out into production?  Especially when you've now admitted there are known bugs.  Why is there a beta in the first place?  I work in software, and from anyone's experience in software, we know that this is a recipe for disaster.  The best advertisement for any product is personal recommendations.  So you don't want to grow a fan base and then make a backward incompatible change.  That will only proliferate the opposite of positive personal recommendations.

    When I first came to this thread with the intention to report this "bug", I learned that it was a new feature.  So I tried it out for five days.  Having given it a chance, I decided that it was really not good for me and I wanted to write up a very clear response explaining why.  I honestly thought that I'd be doing the WORLD a favor by helping block this feature from becoming the new default and the only Flow behavior.  That is how sincerely valuable I consider this keyboard.

    I hate to do this, but I'm going to have to downgrade you to 1-star simply because I don't know what else to do to make a difference.

    In the meantime, has anyone posted the previous version in case others want to revert to it?  It would be great to post a link to it from this thread if SwiftKey will allow that.  I no longer maintain a rooted phone and I don't have the time to figure out how to serve that .apk-file.

    3
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    I thought my app was messed up. I was frantically checking settings to see what I accidentally messed up. I hate this update so much. This is so bad that I will be looking for a new swiping keyboard. Make it a choice in settings instead of forcing it on everyone. I've used this app for years. I can't use it anymore. 

    4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    This new change has killed the auto prediction. That was one of the best features... I'll be finding something different to use until I find out this goes away

    4
    Acciones de comentarios Permalink
  • Avatar
    Permanently Deleted User

    Bring back auto space with predictions!

    2
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.