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


  • Content count

  • Joined

  • Last visited

  • Days Won


Briankbl last won the day on November 27 2016

Briankbl had the most liked content!

Community Reputation

73 Excellent

About Briankbl

  • Rank
    Uber VIP
  • Birthday 11/07/1985

Profile Information

  • Gender


  • Model
    Droid DNA
  • Country
    United States
  • primary_lang

Recent Profile Visitors

1,096 profile views
  1. "Swiping" was a specific feature of Swype, but you copied it no problem, as did almost every other keyboard out there...I'm sure you could find a way to add gesture shortcuts to SwiftKey. Add a "SwiftKey" button that you can swipe from, like in Swype.
  2. While those are handy for some cases, they still don't beat actual shortcuts for cut/copy/paste/select all/capitalize, like it's implemented in Swype. Having gesture shortcuts makes these tasks SO MUCH FASTER. When I want to copy and paste something, most of the time it's something new that I stumbled upon, not something that I would already have saved in my text expansion list...
  3. Just bumping this.
  4. 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!
  5. In your example, it's actually faster for you. You flow a word. SwiftKey doesn't get it right. Would you rather press backspace to delete the auto space and then select your correct word? OR Not have to press backspace to correct the word? Just immediately choose the correct word from the bar and move on to either flowing the next word or choosing predictions? It's faster this way because you're skipping the step of having to backspace then choose correction.
  6. Seriously, this is the way it should have been from the start. It makes correcting mistakes so much easier! I no longer have to backspace, then choose a correction. The whole typing flow is so much smoother now. However, my one bone to pick is that colons still auto insert spaces between it and the previous word, resulting in this : It's Supposed to look like this: This is the last spacing issue I want fixed and I'll be a happy camper!
  7. Here is a video showing how much faster copy/paste is with gestures in Swype.
  8. Same here. Swype has these gestures built in. Swype from the Swype key to A for Select All, etc.
  9. Swype allows swiping and gestures at the same time. Not sure why we can't have the same feature.
  10. I bought the year of Dashlane because of it's old integration with SwiftKey. Really pissed off that I wasted my money...
  11. neural

    Can someone please give us specifics on what features of Neural have been included into SwiftKey and SwiftKey Beta?
  12. The store page didn't have a changelog present. Seeing as it's been several months, one would think this would be a substantial update. Anyone from the team care to fill us in? Thanks!
  13. No, this is a SwiftKey issue, not specific to Neural. It's a fundamental issue with how SwiftKey works. Please move back to previous forum. Thanks.
  14. When I'm flowing a long text - and I'm sure I'm not alone on this - I like to go fast. Meaning, I flow from one word directly to the next, and the next, and the next. I never stop between words to choose a prediction. ---------------- What would be more handy for the user, in my opinion, would be to have corrections show up after a flowed word instead of predictions. Let me demonstrate my point. ---------------- "I have to work five to sox today." ---------------- There's our example sentence. It should be obvious to most that sox is SUPPOSED to be six. However, SwiftKey's Neural algorithm still doesn't pick up on the context of what's being typed. Neural only works for predictions...not corrections. ----------------- So, while I do like to flow fast from word to word, I'm still able to check the accuracy of my words as I flow. ----------------- Here's how correcting is now: After I flow 'sox' and realize that's not what I was trying to type, predictions are shown up top, being of absolutely no help to me. I have to hit 'backspace', then choose a correction. ----------------- Here's how correcting should be: After I flow 'sox', corrections show at the top instead of predictions. This saves me time as I can easily and QUICKLY just choose a correction. ----------------- Again, I see no need to have predictions show up after flowing a word. I don't figure many people are typing a sentence by flowing, flowing, flowing, choose prediction, flowing, choose prediction, choose prediction, flowing. ----------------- Makes sense to me. P.S. For some reason, I can't break up my paragraphs with spaces? On Tapatalk if that matters.
  15. I like it, although swiping accuracy is STILL better in Swype...but that's a general critique regarding all SwiftKey keyboards. As far as 'Neural' goes, it's cool, but it ONLY works for predictions, NOT corrections. I'd like to see Neural recognize that the word you just swiped/flowed matched, or came close to matching, a word that contextually matches with another word, or your previous string of five to six words. For example, that last sentence, Neural kept changing my flowed word from six to sox... Contextually, it should have known I was trying to flow six, not sox lol, considering 'five to sox' makes no sense.