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


Popular Content

Showing content with the highest reputation since 02/23/2017 in Posts

  1. 3 points
    Hey Brian, We had about ~30 people use Tapatalk on our forums on a monthly basis. Thats not much. And Tapatalk may have been the market leader in reading multiple forums, but their product still left a lot to be desired in my opinion. You couldn't tell if you were talking to a Moderator/Staff member or a regular person, because no badges were shown. Trying to Moderate content on Tapatalk was also a poor experience. I'm not here trying to bash their service. Ultimately, this is what we felt made the most sense. I'm sorry that this is not the best experience for you. This is not to say Tapatalk may not come to this service at some later point. I can't speak for what Zendesk is going to do. But we will continue to try and provide a good experience for users coming to the Forums.
  2. 2 points
    Hey there, - Nexus 5X - Android 6.0.1 (Okt 15) - Version - german and english After flowing a word it is displayed like this: "test¦" (where ¦ is yhe text cursor). It should be: "test ¦" After i press space I got: "test ¦" (two spaces) So my guess is that the first space is written but not displayed somehow. When I choose the word from the three choices above it works. Please fix this as it is very confusing Thanks, Clem
  3. 2 points
    I second that, I've been pulling my hair off trying to figure out a way, thought it was a bug or something, and found this thread saying it's not. This way makes prediction kinda useless, maybe that's not the best word, but, well, it's not automatic anymore. Having an option to disable/enable would be the way to go, everyone happy, company happy, maybe mad devs trying to figure out a way.
  4. 2 points
    I desperately want it to go back to automatically adding a space after flowing. When I type a message now, I have to touch the screen twice as often because I have to put in a space after the word I just typed in order to see the predictions. I rarely had trouble with it misunderstanding the word that I was flowing, but now it "suggests" the word that I've already typed. I absolutely despise this new feature and I don't understand why there isn't an option to have the space automatically dropped in.
  5. 2 points
    Please give an option to go back to an autospace after flowing a word. I have loved my Swiftkey keyboard for years now and I rarely make mistakes. Now there is an extra tap every time I flow a word. It makes me insanely frustrated to see it "correcting" my word to the exact word I already typed. Bring back the autospace after flowing, please. I beg of you.
  6. 2 points
    I'm with AdamBanzi on this - there at least needs to be an option. I feel several times slower using the no-space version,and it's made SwiftKey feel anything but swift. Oddly, some of the predictions were less accurate with the first version to introduce the no-space, too, but that seems to be mostly fixed by the latest version I just installed. The update does seem to help, so I might need the option less than I did, but I still prefer having an option from a UX perspective.
  7. 2 points
    Hi Khaled, Thanks for the detailed suggestions. Hope your contribution could make a difference of Arabic typing. Alpert
  8. 2 points
    Thanks Ryan. As I always use Chrome to browse the forum, there won't be difficulties for me to switch. But I do see some webpage compatibility issues of the new community. Hope it could be better. Glad that I can help this great app and service! Applause for all MOD members! And thanks for the great support from all VIPs ! Alpert
  9. 2 points
    I absolutely love it. It makes correcting spelling errors so much faster! No more having to backspace! However, there is one thing that's been infuriating. Capitalizing words. For example. I swipe "Happy new year". Crap, I wanted all three words capitalized... "happy new Year". Nope. If you swipe a word, hit shift, then swipe the next word, it undoes your previous word's capitalization and works correctly on the next word. It happens because of the missing autospacing. Because the cursor is at the end of the previous word, hitting shift is telling the keyboard to change shifts on the previous word. I hope I'm explaining this well lol. Type Happy. Happy Type shift, swipe New. happy New Type shift, swipe Year. happy new Year See? That seriously needs fixing, but I'm so glad you guys have finally went with no space!
  10. 1 point
    Hi Devs and Userbase! I am ZAP XAV and ready to roll. ♖
  11. 1 point
    If I might just say: It makes sense to hit backspace to correct an error. In fact, at this point, it's hardwired into my reflexes to hit backspace when correcting an error. Similarly, it's hardwired into me to tap the predicted word that I know will be there, and now that just...adds a space. Totally unnecessary change that makes things feel clunkier.
  12. 1 point
    Great job with text expansion capability. Works great !
  13. 1 point
    I think the only problem here is that beta is not auto inserting a space after user is done swiping. Non-beta app does that. Since the beta app is not auto inserting a space, prediction engine thinks that user is not done typing word yet and does not make accurate predictions (that is my guess), cause predictions show up correctly as soon as I manually insert a space (which then actually inserts 2 spaces as OP reported) Switching to non-beta until this is fixed and hoping this buggy behavior does not end up in non-beta app.
  14. 1 point
    Apps are a much faster and smoother experience than mobile sites in web browsers. That's just how it is. Visit your forums in Tapatalk then visit your new forums... It's night and day from a performance standpoint. Then, of course, you have all the extra features an app can bring you, particularly notifications. Instead of sending me junk emails letting me know that somebody responded to my question (new forums), I could instead be receiving notifications that are easily dismissable and actually result in fewer steps to get to my post. Tapatalk is the number one forum app for a reason and now you're abandoning it for a less convenient, less feature-rich option.
  15. 1 point
    No auto space when using flow has really killed my efficiency and speed. I, quite honestly, can't stand it. As others have mentioned I get tripped up when trying to capitalize the next word, but most frustrating is I no longer get predictions when I use flow because the cursor is stuck on the last word. I only get suggestions for the last word flowed and no predictions for the next word or words. It's a good idea in theory but if you're going to make a feature like this at the very least make it optional so we can turn it off if we hate it. I only just got the update today and I'm already extremely frustrated by it.
  16. 1 point
    I really dislike everything about this announcement. No more Tapatalk, which is infinitely easier to use than your mobile support site. I just posted a question over there, so I know lol. Also, combining discussion of beta and market apps into one area? That's the opposite of simplifying things. How is it more simple to wade through a mess of posts from two products? No, simple is keeping the two separate as to eliminate confusion and allowing your users to find topics quicker. Just my two cents...
  17. 1 point
    Something that always bugs me is that you wind up with an extra space at the end of whatever it is you type (especially relevant for fixed length text like SMS and Tweets). This is because SwiftKey adds a space immediately after punctuation. My suggestion is to not auto space after punctuation until you start to type the next word. This would also fix the problem whereby I want to insert some additional text between parentheses and an extra space is added after the closing parenthesis, even though a period follows immediately after it. For example, if I was to move the cursor to right before the period of a sentence and type an open and closing parenthesis. Similarly, if I move the cursor back to the end of a word and add a comma, now I wind up with a double space. This definitely feels like a bug.
  18. 1 point
    So how do we get some attention from someone who has some control over this?
  19. 1 point
    I think it might be a good ideia **if** (and only if) this would be optional, as a setting users can toggle on/off. By doing this, you can satisfy both group of people. Most of users are used to auto spacing after flowing words. Changing this with no option of turning back seems pretty bad. Also, as more languages get neural net support, SK predictions tend to get better over time, diminishing, thus, the need to correct bad predictions. I perceive that, after using SK Neural for quite some time, the predictions improved a lot, and, in this case, the auto spacing helps (at least me) flowing even faster. Regards.
  20. 1 point
    Hi there. I may have asked this already, but I'm still wondering what are you guys up to. I'm pretty amazed at the latest beta update (6.0) which came with a bunch of new features. I see that you've been working hard on the Neural app as well. But I'm still wondering if you plan to add the feature to implement to sync the user defined settings to the cloud feature... Are you working on something else with higher priority or will you consider this to near future updates? It's such a pain to reconfigure everything once again after a new install... So please, consider this as a near future idea. Thanks.
  21. 1 point
    Heslo can i somehow turn of diacritics for Czech language? It is pretty. Expensive when i forget to delete 1kind of this á od č od etc. when i am writing sms Please reply on my email : cpatrin@seznam.cz