Welcome to SwiftKey VIP Community

Welcome to SwiftKey VIP Community. Like most online communities you must register to view or post in our community, but don't worry this is a simple, free process that requires minimal information for you to signup. Be a part of SwiftKey VIP Community by signing in or creating an account.

  • Start new topics and reply to others
  • Subscribe to topics and forums to get email updates
  • Get your own profile page and make new friends
  • Send personal messages to other members

  • 0
Jshwam

[FR] Turn off all gestures

Question

How the heck do you turn both of these settings off? I hate flow so that immediately is gone. So it gives me an option to choose between gestures or flow writing. Both of which I don't want or use. I put it on gestures as its the lesser of two evils. Problem I find though, when trying to use the swipe ? or ! or , I am actually closing the keyboard  because I'm apparently swiping downwards just a little to much. Please help! 

0

Share this post


Link to post
Share on other sites

54 answers to this question

  • 0
On 7/26/2016 at 1:32 PM, Alpert said:

Of course I can't see till I got your reply. Be calm. I just want you to explain so that can make it as a part of request.

Besides your phone model, I am gonna need your SwiftKey version, ROM version and Android version as well. We need to know if it's particular issue.

I will raise it to the mods team.

 

 

Plenty calm.. :)

 

 

1 hour ago, Prad said:

 Oddly enough I got an email from one of our devs this morning saying they believe they have a fix for this "ghost flow"

 

If anyone who has this issue wants to chime in with what device and OS this happens on I'll pass this feedback on for further testing.

 

That's great and all, but.. I'm not sure why you guys won't just simply allow us to turn it off.  You guys drag your heels at the thought of doing so, and basically take the stance that "we're using it incorrectly".  The only thing keeping me around is the correction and prediction.  Just let me type fast.

0

Share this post


Link to post
Share on other sites
  • 0

Signed up so I could also say this is really annoying. The feature is probably working just as designed when it deletes a word, but it really is annoying that we can't just disable Gesture input altogether. As a developer myself, I just am not understanding why an option to disable both is not available. There must be a development requirement for some gesture to be captured??

 

It only happens when I'm typing fast, which is most of the time. :) 

 

Overall, very happy with SwiftKey.

 

If there is a development reason why one must choose either or rather than disable both, that would be great to have high level explained for users. Save the condescending "You can not turn both things off. Because this is what makes SwiftKey awesome." responses please. 

 

 

1

Share this post


Link to post
Share on other sites
  • 0
17 minutes ago, SmoothDoogie said:

Signed up so I could also say this is really annoying. The feature is probably working just as designed when it deletes a word, but it really is annoying that we can't just disable Gesture input altogether. As a developer myself, I just am not understanding why an option to disable both is not available. There must be a development requirement for some gesture to be captured??

 

It only happens when I'm typing fast, which is most of the time. :) 

 

Overall, very happy with SwiftKey.

 

If there is a development reason why one must choose either or rather than disable both, that would be great to have high level explained for users. Save the condescending "You can not turn both things off. Because this is what makes SwiftKey awesome." responses please. 

 

 

 

I haven't experienced the accidental gesture detection yet in SwiftKey, but only been using it for a couple weeks.

I did, however, experience it a lot in Swype+Dragon, which was my previous keyboard of choice. It appears Swiftkey does a lot better job avoiding the accidental gestures. In Swype, it usually would happen to me when 2 fingers were touching the screen simultaneously but somewhat far apart (both my thumbs when fast typing).

 

I personally would like 2 additions to the gesture options:
3) Cursor control (like Samsung keyboard does - swipe left and right to move the cursor left and right)
4) Disable gesture detection completely

0

Share this post


Link to post
Share on other sites
  • 0

Please just add a feature to disable it. I've been a SwiftKey user for many years, in fact when I installed it I don't even remember there being a swiping input. Up til recently there was an option to disable it, but it's gone now. Please reinstate. 

 

Funny enough, I had a typing error while typing the previous paragraph, because it thought I was flowing. It's extremely irritating. 

0

Share this post


Link to post
Share on other sites
  • 0

I also made an account to petition for this option. It is enraging that you have reps arguing that lack of an option is superior to the option. It wouldn't take your coders ten minutes to fix this just do it! 

0

Share this post


Link to post
Share on other sites
  • 0
On 9/23/2016 at 3:23 PM, Jehnidiah said:

Please just add a feature to disable it. I've been a SwiftKey user for many years, in fact when I installed it I don't even remember there being a swiping input. Up til recently there was an option to disable it, but it's gone now. Please reinstate. 

 

 

 

Exactly. Flow/Gesture isn't what brought me to SwiftKey in the first place. So don't tell us "that's what makes it awesome". I came here because it's a superior KEYBOARD.

0

Share this post


Link to post
Share on other sites
  • 0

Everyones, lets calm down here. Everyone is entitled to their own opinion. Also, English is not everyones first language here, so something things come off as not intended.

 

People also make mistakes. We've all decided to use SwiftKey for different reasons. I've taken note of this feature request.

0

Share this post


Link to post
Share on other sites
  • 0

I just wanted to say that this feature is great, but you must consider the fact that not everyone has a phone with the most responsive touchscreen or their phone is just laggy, and typing fast with gestures does much more harm than it helps. I use SwiftKey on my Idol 3 (not the worst but not the best phone either) and I get frustrated from time to time when I try to type something fast, phone starts to misbehave (lagging) and gestures just delete every word I try to type. Most of the time it works fine (I don't use gestures, but I don't mind them either) but there are days I'd throw my phone out through the window because of the lags that cause gestures to be registered when I had no intention of using them.

0

Share this post


Link to post
Share on other sites
  • 0

Hi All, 

 

I'd like to chime in here in support of bringing back the option to turn off gesture input completely. I used to be a loyal SwiftKey user ever since the early days,  years back,  when it used to be a paid app. It was on all of my devices and I swore by it until the gesture input became a mandatory feature. I've tried to suffer through it a few times, but it's just too annoying to mess up your typing by accidentally using it all the time. So eventually I switched all my devices over to a different keyboard, which I've been using for the past 1-2 year now. Its autocorrect and predictions aren't nearly as great as SwiftKey's, but it lets me turn off the annoying feature completely. What I'm trying to say is that I don't mind worse autocorrect and predictions as long as I don't have to deal with gesture input. It's a shame that I have to sacrifice one for the other now, because I didn't use to have to. 

1

Share this post


Link to post
Share on other sites
  • 0

I also used to use the paid version back in the day and switched to a different keyboard because of two reason: 1) SwiftKey wasn't giving me predictions in all fields, only select ones. That was remedied at some point but I had already moved on to other keyboards. And 2) SwiftKey flow couldn't be disabled and it was causing false readings.

Now, with my S7 Edge, SwiftKey doesn't detect false flows/swipes, so I don't mind the fact that you can't disable the feature. I've been using it over 2 months now, and have had zero (maybe 1?) occurrences of SwiftKey falsely detecting a swipe/flow.

 

Yet it is rather mind-boggling that an Android app dev would take away an option like this. Go ahead and force iOS users to do when you want them to do, they're used to that. Android users on the other hand are used to having options in their apps. We get it, you want to show off gesture controls and streamline the options and stuff, but seriously just give us the option to disable gestures. And really if you want to compete with other keyboards, you should give us the ability that Samsung keyboard does, which is to swipe for cursor control. It makes fixing typos a bit easier. I even had this ability on my jailbroken iPad because there is a Cydia app that specifically enables swiping keyboard left and right to move the cursor.

 

The reason I even searched and found this thread was because my friend, who is admittedly quite picky, was looking for a keyboard to fit his needs. He likes Samsung keyboard except that it would constantly give suggestions of email addresses in his contacts, and he was somehow annoyed by that. I suggested Swype or SwiftKey, but he said he tried those and liked them both except how you can't turn off the swipe/flow detection in either one. He said he despises that feature and refuses to use a keyboard that won't let him disable it. I think he ended up using Google keyboard. I'm sure there are plenty more people like him that aren't using SwiftKey simply because you can't disable gesture/flow/swipe. And for what? It would take the devs 10 minutes tops to add the option, no? Oh well, I'll still use SwiftKey, so I suppose I don't care. Just seems kind of silly.

0

Share this post


Link to post
Share on other sites
  • 0

please provide an option turn both these damn things off.... both flow and gesture are quite irritating. Flow us totally useless and Gesture simply delets my words when i try to type fast and the letters are placed adjacently from right to left... say "gfd". I created na account here just to let you know that both these features are annoying. 

0

Share this post


Link to post
Share on other sites
  • 0

I'm sorry if I come out a bit forward or rude and for my bad English. I made an account just for this request to go more in the interest of the developers, since no change has been made since mid august (4 months, multiple updates). I don't know if it's the developer's inability to make this change (which I doubt heavily) or ego, but the gesture thing is the problem for a lot of users and it's not a bug, it's just how the screen acts when pressed on multiple places at once or in swift succession. And it really isn't hard to make an option to turn off both features, it won't hurt anybody, it may even bring more users to the app.

Sorry again for the rant but changes must be made. This (one button) or a move to a new keyboard app.

 

Thank you in advance, E

0

Share this post


Link to post
Share on other sites
  • 0

Think I've proven my point that it's not just me. I could understand not listening to the customers every demand. Especially if it was a new feature that didn't have a real use. This however, is just making it so we don't have to use a particular feature. You say that using one of the two features is what makes the keyboard great, and that might be for a lot of people. But why not pull in that much more fans, that just appreciate the basic functions of the keyboard, by letting them turn off the more advanced portions of it. The bigger the user base the better? We haven't heard anything from the makers in awhile. Would be nice to hear their input here. 

0

Share this post


Link to post
Share on other sites
  • 0

Hi,

 

I responded on September 27th. We listen to and record all feature requests. We do care about all community input and is taken into account when we work on new features.

The discussion is great, and I continue to watch it and see what people say. I will jump in when I have anything to report on the matter. 

 

Cheers,

 

Ryan

0

Share this post


Link to post
Share on other sites
  • 0
1 hour ago, Prad said:

Hi,

 

I responded on September 27th. We listen to and record all feature requests. We do care about all community input and is taken into account when we work on new features.

The discussion is great, and I continue to watch it and see what people say. I will jump in when I have anything to report on the matter. 

 

Cheers,

 

Ryan

 

Can you just jump in now and answer the question that's been asked over and over again: what is the rationale to NOT have an option for users, when it used to be there? It seems so strange that there is no answer on that point.

0

Share this post


Link to post
Share on other sites
  • 0

I think the same, only half solutions are given, users are not heard, it seems very bad that we are forced to use one of the 2 options and do not let disable the options that we do not want, I would understand if there had always been an application Free but in my case I paid what was worth at the time and was not exactly cheap ... Please take this more seriously and let us choose whether or not to use the options, for pleasure and not for obligation.

0

Share this post


Link to post
Share on other sites
  • 0
6 hours ago, Jehnidiah said:

 

Can you just jump in now and answer the question that's been asked over and over again: what is the rationale to NOT have an option for users, when it used to be there? It seems so strange that there is no answer on that point.

 

1 hour ago, Johan88 said:

I think the same, only half solutions are given, users are not heard, it seems very bad that we are forced to use one of the 2 options and do not let disable the options that we do not want, I would understand if there had always been an application Free but in my case I paid what was worth at the time and was not exactly cheap ... Please take this more seriously and let us choose whether or not to use the options, for pleasure and not for obligation.

There has been an answer, the rationale for not creating more options is simply an ease of use and accessibility. When I jump into an app with 30 different options revolving around the same functionality, I am flustered and overwhelmed. You have to look at SwiftKey on the entire scope before becoming bitter that certain features aren't enabled or enacted immediately. When you have toggle options, you are basically creating two different keyboards. With core functionality changed on both options. Multiply this by the amount of options already available and you have taken the core of SwiftKey's functionality (the prediction engine) and spread it across 45 different keyboards. This affects functionality, lag, usability, and option functions. All of these things affect performance. It has never been my practice here as a SwiftKey specialist to give "half-solutions" or not listen to the users. The group of Specialists in these forums communicate and discuss issues everyday, and everyday we are looking at ways to better serve users in that role. I can honestly say that with the team of people we have providing information in this forum, that we are attentive and take what you guys say about the program very close to heart. This is taken doubly so in when @Prad gets involved as he has direct contact and communication with the development team. With every feature request comes a discussion, you also have to understand the ideas that SwiftKey has for SwiftKey as well as the users that go through, beta test, and comb the app for functionality issues. There is then a prioritized list that comes to the development team, and that is the focus. An option that you may feel is core to the use of SwiftKey, may not have as much weight with other users, this becomes a constantly evolving and changing requests for functionality and features. This leads to things being changed, bugs being created, and focuses shifted. There are no excuses at SwiftKey that I have heard, there is simply progress. Moving forward. Keeping current. There are quite a few of us that paid, some of us multiple times across multiple devices with multiple accounts. I've been using SwiftKey myself on over 30 devices, paid for no less than 5 times across 5 accounts, and every single penny went to creating the most amazing prediction software I've ever seen, with epic customization and personalization. No, it is not perfect, and I do not pretend as such, but I will never say they don't listen or take to heart what their users want to see. I've seen too many developmental shifts through the beta program to ever believe their not listening to their users. They do. Better than most. Just stick around and see what changes are made, very rarely in the software development world is there ever a moment of instant gratification. Happy typing my friends, and believe we are listening, to everyone who uses this app, and every review made about it. =)

 

1

Share this post


Link to post
Share on other sites
  • 0
2 hours ago, Subliminal5oh2 said:

 

There has been an answer, the rationale for not creating more options is simply an ease of use and accessibility. When I jump into an app with 30 different options revolving around the same functionality, I am flustered and overwhelmed. You have to look at SwiftKey on the entire scope before becoming bitter that certain features aren't enabled or enacted immediately. When you have toggle options, you are basically creating two different keyboards. With core functionality changed on both options. Multiply this by the amount of options already available and you have taken the core of SwiftKey's functionality (the prediction engine) and spread it across 45 different keyboards. This affects functionality, lag, usability, and option functions. All of these things affect performance. It has never been my practice here as a SwiftKey specialist to give "half-solutions" or not listen to the users. The group of Specialists in these forums communicate and discuss issues everyday, and everyday we are looking at ways to better serve users in that role. I can honestly say that with the team of people we have providing information in this forum, that we are attentive and take what you guys say about the program very close to heart. This is taken doubly so in when @Prad gets involved as he has direct contact and communication with the development team. With every feature request comes a discussion, you also have to understand the ideas that SwiftKey has for SwiftKey as well as the users that go through, beta test, and comb the app for functionality issues. There is then a prioritized list that comes to the development team, and that is the focus. An option that you may feel is core to the use of SwiftKey, may not have as much weight with other users, this becomes a constantly evolving and changing requests for functionality and features. This leads to things being changed, bugs being created, and focuses shifted. There are no excuses at SwiftKey that I have heard, there is simply progress. Moving forward. Keeping current. There are quite a few of us that paid, some of us multiple times across multiple devices with multiple accounts. I've been using SwiftKey myself on over 30 devices, paid for no less than 5 times across 5 accounts, and every single penny went to creating the most amazing prediction software I've ever seen, with epic customization and personalization. No, it is not perfect, and I do not pretend as such, but I will never say they don't listen or take to heart what their users want to see. I've seen too many developmental shifts through the beta program to ever believe their not listening to their users. They do. Better than most. Just stick around and see what changes are made, very rarely in the software development world is there ever a moment of instant gratification. Happy typing my friends, and believe we are listening, to everyone who uses this app, and every review made about it. =)

 

You're actually incorrect about this. Most of us are saying we bought this app before is had both of these functionalites, AND we were ABLE TO TURN IT OFF AND JUST TYPE. 

 

Not everyone wants a gesture or a flow keyboard. I use it for its way better typing correction and autocorrect. Plain and simple. This is a screen with only two options on it. If you're telling me that disabling bot of these inputs makes the core of the application that much more difficult to support, I'm calling you out. 

0

Share this post


Link to post
Share on other sites
  • 0

You're missing my point.

Firstly, not really sure why you're feeling combative, but we will move on from that. Also, not sure what I'm wrong about.

Secondly, as I stated, I paid for the app too, and while it's not perfect getting hostile in a forum isn't the appropriate way to get changes made, it just tends to kill valuable discussions.

Thirdly, I type very quickly, especially since I have over 5 years using SwiftKey, my predictions are on point. When I can I primarily thumb type. However, Flow is always turned on due to the size of my device and having a less than a year old son makes two hand typing impossible some times. With that being said, rarely, while I'm thumb typing do I enable any kind of gesture typing unless intentional. I have Galaxy Note 5, with my sensitivity turned up and I do not have an issue, that's me as a user.

Fourth, and finally my main point from the last post, understand that this is a huge app with millions of users, sometimes as a company SwiftKey must make decisions that affect all of them, which means depending on the mass majority of users, is where the decision lies. Understand that what I've been getting at this entire time, is that SwiftKey listens to its users. ALL of them. So what seems like a big issue to some, is a non issue for others. I'm not saying that the issue at hand isn't a big deal, because for some posting here it seems to be a validated issue.

After all my time here, and with SwiftKey, I will simply close and say that the developers of SwiftKey are some of the best in the world, and they have yet to let me down. Again, it's not a perfect app with every function I want, but it still beats everything else, hands down.

1

Share this post


Link to post
Share on other sites
  • 0

Wow, that add a shutdown option are hundreds of lines in the code ... That's what you tell a novice or a new user, I've been using and compiling on my android account, I've participated in the compilation and development of Several Android projects, and what you say does not make any sense, add an option to shutdown these systems is not as complicated as you say, share the source code and myself I'm going to compile SwiftKey with a shutdown option or directly without these Damn options. I do not understand how they can force people to use something that at first was not even, and now they force you to swallow with it ... It's hypocritical ... Okay, it seems that apart from not listening to users, The arrogance of developers and their ego cause users to be forced to change application ... I only hope that one day that option will be added before I get tired of that keyboard and change to another, which by the way and I walk Trying other options and very good too, and guess what ... DO NOT OBLIGATE YOU TO USE SOMETHING YOU DO NOT WANT TO USE ... I hope that now you do not respond with a "because you change the keyboard" because you are going to be portrayed as a team ...

0

Share this post


Link to post
Share on other sites
  • 0

Hi again everyone,

 

If it was not known, I do in fact work for the company. So I am your best source of information here. We take every feature request into account. While we do like to be as transparent as possible, we are not allowed to fully discuss upcoming features etc. This is generally pretty standard practice. 

 

There's not really much else I can say. 

 

Please remember to be civil with each other. We're all on the same team here, but may have different views on what makes a keyboard better. 

 

Cheers,

 

Ryan

2

Share this post


Link to post
Share on other sites
  • 0
10 hours ago, Subliminal5oh2 said:

You're missing my point.

 

 

 

Firstly, not really sure why you're feeling combative, but we will move on from that. Also, not sure what I'm wrong about.

 

 

 

Secondly, as I stated, I paid for the app too, and while it's not perfect getting hostile in a forum isn't the appropriate way to get changes made, it just tends to kill valuable discussions.

 

 

 

Thirdly, I type very quickly, especially since I have over 5 years using SwiftKey, my predictions are on point. When I can I primarily thumb type. However, Flow is always turned on due to the size of my device and having a less than a year old son makes two hand typing impossible some times. With that being said, rarely, while I'm thumb typing do I enable any kind of gesture typing unless intentional. I have Galaxy Note 5, with my sensitivity turned up and I do not have an issue, that's me as a user.

 

 

 

Fourth, and finally my main point from the last post, understand that this is a huge app with millions of users, sometimes as a company SwiftKey must make decisions that affect all of them, which means depending on the mass majority of users, is where the decision lies. Understand that what I've been getting at this entire time, is that SwiftKey listens to its users. ALL of them. So what seems like a big issue to some, is a non issue for others. I'm not saying that the issue at hand isn't a big deal, because for some posting here it seems to be a validated issue.

 

 

 

After all my time here, and with SwiftKey, I will simply close and say that the developers of SwiftKey are some of the best in the world, and they have yet to let me down. Again, it's not a perfect app with every function I want, but it still beats everything else, hands down.

 

You should be a spokesperson for SwiftKey.

 

But for real. I was having a problem when I switched to the Galaxy S7 from the S5. I didn't have the problem with the S5 because it was slightly bigger. I was just looking for a way to turn it off.  So I hit the forums and people ran with it. Given just the feedback in this forum alone. That could warrant adding one toggle button to turn off both features imo. Several people said they would switch keyboards or have already because of it. It's not like you would have to rebuild the whole app, or add a bunch of different layers of GUI. Just a "none"  option under flow and gestures.

 

I moved from the Galaxy S7 to the Note 5 because of that reason (and because I hated the curved glass screen) and since, I haven't had much of an issue. It happens from time to time, but nothing to write home about. It is an issue with some phones though apparently. People get heated because this is the keyboard they have likely used forever. They could easily switch, but would rather find a work around because it is a great keyboard (and more). And creating one toggle button. Minor.

2

Share this post


Link to post
Share on other sites
  • 0

Agreed. And it's not like the functionality isn't feasible, it's just not a deal breaker for a lot of users. The feedback in these forums is very important to the development of SwiftKey, and while this is a long running thread, it's comprised of only a handful of users. I'm just trying to explain that there is a bigger picture, and believe that Prad is following this intently. I've been working with Prad in these forums for a couple years now, and he takes everything very close to heart and makes sure to pass that info to the developers. I just want everyone to know they're not being ignored.

Sent from my SM-N920P using Tapatalk

1

Share this post


Link to post
Share on other sites
  • 0

Just going to throw my two cents in, came across this thread when Googling for a solution to this very issue. It is an issue, no matter how much the mods and staff might like to try to say otherwise. I am strongly considering finding an apk for an older version of swiftkey just because of how awful this lack of options is. I didn't update swiftkey on my old S4 because of issues like this, and now with my new pixel I find myself having regular problems with typing that I never had before, solely because I cannot turn off flow and swiping gestures both. It is very frustrating and it's even more frustrating to see the developers have known about this for 6 months and are just short of outright refusing to fix what they themselves broke. I'm probably going to be changing my review from 5 stars to one if they keep ignoring their users and putting them off with false assurances and condescending remarks like this... in the meantime I suppose I will hunt for an apk for the older version on my s4. 

1

Share this post


Link to post
Share on other sites
  • 0

I have an Asus Zenfone 2 and have been frustrated for months with the "auto-closing keyboard", which was caused by sliding gestures. Now I have switched back to flow, which gives me wrong and ghost flow words too often, so I also would like very much to disable gestures completely. I find it very weird and frustrating having to choose between two options I don't want to use... 

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now