Jump to content

Welcome to SwiftKey Insiders Community

This community has now become "SwiftKey Insiders" - built around SwiftKey users who want to help shape the future of SwiftKey products from the ground up. 

 

This is not a support community. If you are looking for general support, feedback and feature requests, please visit our support site here.

 

Note: this community is only available for SwiftKey for Android at this time

But if you would like to join our iOS or Windows lists to be notified when we launch on these platforms, please let us know.

Sign up here if you're interested in:

  • Seeing early designs
  • Playing with prototypes
  • Taking surveys 
  • Giving thoughtful honest feedback

Alpert

Moderators
  • Content count

    1,469
  • Joined

  • Last visited

  • Days Won

    82

Alpert last won the day on May 3

Alpert had the most liked content!

Community Reputation

354 Excellent

About Alpert

  • Rank
    SwiftKey Mod Team

Profile Information

  • What mobile device(s) do you own?
    Android
  • Interests
    Graphic design, badminton, MTB

Recent Profile Visitors

3,584 profile views
  1. Well done! Should be an insider soon. Good luck!
  2. Hi, I suggest you to do it on mobile browser (Chrome, for example), or on a desktop. I doubt Tapatalk supports deep settings like these. Best Alpert
  3. Hi Alpert, 

     

    I realise that the thread I was posting on was about loss of words rather than prediction quality. So thought I'd send you a pm to better describe my issue. 

     

    With my wiped SwiftKey (not beta) install and without logging into my account so that I can start with a clean language model. I noticed that some of my existing words were already in the model (perhaps reading from the beta app?). The issues faced were the same, inconsistent caps of words (even as I type this, I am capturing some inconsistencies). 

     

    Here are the screenshots:

    Screenshot_2017-02-21-11-55-01.png

    Screenshot_2017-02-21-11-56-59.png

    Screenshot_2017-02-21-11-55-49.png

    Screenshot_2017-02-21-11-55-36.png

    1. Jiraffe7

      Jiraffe7

      Do note that I have caps at the start of sentences turned off. 

       

      Additional screenshot with the issue as I was typing this post:

      Screenshot_2017-02-21-12-06-54.png

  4. Have you tried to delete "Hi" and "Park" from the predictions? So next time when you type "h" key and "I" key, there would be "hi", tap on that. Same method for "park". I think this might help you.
  5. Understood. Can you give us some examples (screen shot, videos) of this kind of issue happens? And more details like : does it happen in a specific app or overall experience? During daily use, what percentage would you give for the chance you run into this issue?
  6. First letter of the first word in a sentence to be cap is the grammar rule. In my experience the grammar rule overwrites the word form. Because both prediction of cap and not cap exists in SwiftKey, the rules make the cap one in the front of sentence. And yes, if you want to have non cap word in the beginning of a sentence, you will need to tap on the shift to switch because this is not a normal use or a correct form. It's the same idea that you won't see SwiftKey cap a word automatically in the middle of the sentence. Because it's not the right grammar. SwiftKey aims to fast daily communication typing, regular stuff, so to follow the regular rules is easy and fast, more importantly is most people got used to and understand how they work. If you need something more specific, more professional, more personal use, you'll need a fully customizable keyboard to adjust everything. The plural issue, I just replied in your thread. Please check.
  7. 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
  8. Happy Lunar New Year !

    Chinese-new-year-2015.jpg

  9. I don't use gif, Android support is poor...GIFs are really fuzzy, not clear, and not smooth. Better to introduce it later. And at the same time, it'll depend on the app (facebook, hangouts, wechat...) itself support gif or not. One step further : support 3rd party gif or not. It's not just a keyboard thing.
  10. If I understand correctly, you say that even you type " ALPERT" these keys, there won't be "Alpert" on your prediction bar? That's not normal. SK version number: you can find in SK settings > up-right corner 3-dot menu key > about. I suggest we look at the prediction words for the moment, can you upload a video, recording your typing? I personally suggest this app and strongly recommend to enable the "show touch" option in developer settings in your LG. Keep us updated. Alpert
  11. Merry Christmas everyone !

  12. Please remain calm. Please answer following questions and the one asked by Prad in the first post : Android version, SK version Thanks Alpert
  13. Show your home screen!

    Well, here's mine.
  14. Show your home screen!

    Wow, your phone is the app store... Not the app. lol!
×