Well that would make sense as to why I don't hate it.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Well, that would actually make sense as to why I DO hate it!
I've been living with the Samsung keyboard (even though Google Keyboard is my favorite) for the past few days just to see if there are attributes to the Samsung keyboard that make it a great choice to use. I wondered if there were features that closely tie the keyboard into other Samsung apps. So far, I am not seeing that, but I did just discover a huge flaw.
I was an early adopter of Swiftkey, years ago, and really enjoyed the awesome prediction capabilities of that app. But, a couple of years back I noticed that while Swiftkey works great for texts and emails, if you ever try to do work in a document longer than a couples of pages, it grinds to a halt. This is an issue for me across Android phones, versions of Android OS, different word processing apps and is a well-documented bug for Swiftkey - it just doesn't work.
Along with many other hopeful Swiftkey users, we have brought this issue to their attention, and they just don't address it. To make a guess as to the problem, I'd say that their app architecture loads the entire file when it is opened, into the same cache space that the app needs to operate, making the app slower and slower - again, just a guess, but it certainly behaves this way.
So, as of tonight I am back to Google keyboard and Google Handwriting Input. I can say now that I am not missing out on anything by moving back to the Google apps, but I am gaining the ability to work in longer docs. Plus, both Google apps are faster, more accurate and easier to use than the Samsung apps.