Re:Ask HN: Do you still miss your RIM BlackBerry?
by starky on Tuesday September 14, 2021 @11:59AM
(#28526735)
I don't get how Swiftkey went from being almost perfect to being almost perfectly shit at predicting what I want to say. I've switched to GBoard and also hate it (e.g. it won't auto-capitalize "I" for me), but at least the predictions are usable.
Re:Ask HN: Do you still miss your RIM BlackBerry?
by egeozcan on Friday September 17, 2021 @12:05PM
(#28567096)
I was wondering if that's a problem isolated to my first language, but apparently it got worse in English as well. Although, it surely can't be as bad in a language that doesn't have agglutination.
For example "olamayacakmış" ("ol-a-me-cek-miş", meaning something like "we found out that it isn't possible to make that happen in the future") was an easy hit before and I could write "olamyckms" and used to get predicted. For some reason not anymore.
Just wanted to share the bug (?) that reduced my mobile typing speed by 30% in a single hit.
- works with more languages
- can be configured to suggest completions and corrections but not auto-apply them
(If anyone from MS/SwiftKey team wonders: these days if I delete a word and start on a new it shows both the original word and the best predictions for the new word. Thankfully it only inserts the new one - but sadly it inserts two spaces.)
And since this is a startup forum, some advice if anyone else reads this:
1. don't skimp on testers. Good testers are extremely valuable.
2. give us users a way to give you feedback! You get a lot of rubbish (I know, I am a dev who sometimes work on products with easily available feedback channels) but without it feedback like this ends up on open forums like here - or we are just silent and mightily annoyed and ready to forgive quite a lot from the next app/keyboard/service that actually fixes the stupid thing your product didn't fix.