Welcome to SwiftKey VIP Community

This community has now become "SwiftKey Insiders" - where the community is built around SwiftKey users who want to help shape the future of SwiftKey.

If you're interested in:

  • Seeing early designs
  • Prototypes
  • Taking surveys 
  • Giving thoughtful honest feedback

About SwiftKey products, sign up and we'll be in touch. 

If you're looking for general support, feedback and feature requests, visit our support site here


jfmcbrayer

Members
  • Content count

    117
  • Joined

  • Last visited

  • Days Won

    3

jfmcbrayer last won the day on May 15

jfmcbrayer had the most liked content!

Community Reputation

61 Excellent

About jfmcbrayer

  • Rank
    Awesome VIP

Profile Information

  • primary_lang
    English-US
  • Gender
    Not Telling

Recent Profile Visitors

500 profile views
  1. I like the new experience, for a couple of reasons. 1. SwiftKey's Flow recognition is bad enough that correction is something you have to do often. So this simplifies the common use case. 2. It is more consistent with other keyboards (notably Google Keyboard, which I deleted when it became GBoard and started to try to do too many non-keyboard things). Just to balance out the negative comments.
  2. Apparently my signature emoji is "poop". I guess because I use it in lieu of a "dislike" button on Facebook.
  3. Hopefully this will mean the onscreen keyboard on Windows tablets will start to suck less. I have a Venue Pro at work, and you really can't use it without the hardware keyboard.
  4. I'm really digging Neural, too. Hopefully, it will be merged and become the mainline SwiftKey.
  5. I'm frequently disappointed that the communism emoji (☭) is not accessible from SwiftKey.
  6. That wouldn't explain it, unfortunately. The "read sensitive log data" is used to read logcat, which includes debug and error output from any application that chooses to use it. Neural is able to look at errors, warnings, debug messages, etc., logged by any apps. It doesn't have anything to do with text that you've typed. My guess is that they want this permission to see what else is running on your device (and therefore what might be impacting Neural's performance), or perhaps to see if Neural is triggering errors/warnings/degug-messages in other apps. Ultimately, only the developers can answer this question.
  7. I'm trying out SwiftKey Neural Alpha, and so far, I'm impressed. On my quite old device (2012 Nexus 7, running an AOSP Lollipop ROM), it is much faster than SwiftKey Beta, and prediction quality is at least as good in general. One thing I note is that there are not currently any options for feeding training data to the keyboard, as there are in standard SwiftKey (ie Facebook, RSS, Gmail). Hope this is likely to change, because I'd like to see how it learns right away rather than waiting for it to accumulate a corpus from my usage.
  8. I'd expect the opposite. Neural is clearly built with the main SwiftKey front-end, and a different backend. Clarity is a completely different keyboard, as far as I can tell (maybe uses n-gram engine in the backend?).
  9. Doesn't seem to work at all in contexts where there is no prediction (e.g., terminals, certain text editors -- wouldn't be suprised if that also included password fields). In contexts where completion works, I do like the feeling of "I'm going to type complete garbage and have it come out correct."
  10. I've tried it. It works surprisingly well, but it's not really a terribly fast entry method. It does work where SK Flow doesn't, though, so that's something.
  11. I expect that learning a new layout for gesture typing would be less effort than learning MessageEase was, and I feel like that has paid for itself over a few months. So I wouldn't overestimate the burden of learning a new layout.
  12. The article and the paper are a nice find that I plan to share on the Colemak forum. One thing I've found is that a layout that is highly optimized for touch typing is terrible for swiping. I touch-type Colemak on hardware keyboards; for those who don't know, it's a layout optimized for fast and ergonomic typing in English (there are variants for some other languages), without being as different from QWERTY as Dvorak is. SwiftKey supports Colemak out of the box for English, so I tried it. I normally use SwiftKey Flow for writing long bits of text on my tablet. My experience with Flow and Colemak was that the rate of errors was much higher -- there were far more ambiguities, mainly because many of the most common letters are on the home row (arst neio), and so you're often just swiping back and forth across the home row, which could mean anything. You also end up having to swipe farther, because of more lateral movement from one end of the keyboard to the other, and less top-to-bottom movement. I'd be interested in hearing the experiences of anyone who's tried swiping on a Dvorak layout. One final note, if anyone hasn't seen MessageEase, they should check it out. It's a compelely different model for typing that involves a very compact and optimized layout to minimize finger movement, as well as a mixture of tapping and swiping. If it had the benefit of SwiftKey's language model, I'd use it for everything, but as it stands, I use it mainly where completion is not available (e.g. in terminal sessions). ETA: if it's not patented, I'd like to see the "dghpa" layout they generated included in a future SwiftKey.
  13. While Google Play is highly prominent, it's not the only repository for Android software. There's Amazon, of course, and for FLOSS software, there's F-Droid. In fact, if you're extremely concerned about malicious apps, F-Droid is probably your safest repository choice (though the amount of software on it is rather limited).
  14. Not that I know of. But it's not a whole lot of information to put in, usually just the base URL of your blog.
  15. Under the SwiftKey Cloud menu, go to Personalization, and select RSS Feed. Put the URL of your blog in the search box and press search. Then select the feed for your blog posts (ie, not comments).