First thing I do when setting up a new phone is turning off auto correct and auto capitalization. Yes, I still make mistakes, but I prefer becoming quite handy at using my backspace button than having to fight the auto correct all damn time.

I have also noticed that touch sensitivity has increased and decreased based on which app I am using. I used to never click on ads on Twitter, but now mistake clicks happen frequently (as an example).

I miss the BlackBerry days a lot, security and trustworthiness with the company was paramount as well and now that's all a fond memory... People laughed at the demise of the company's dominance, but I knew way back then that it was a key aspect of reliability that died with the company... sniff

I still have my old 3g Blackberry touch screen model, if things keep going bad I may try to get it reactivated (if that's even possible) and then grow a beard and move up to a log cabin in the mountains. :P

...no way, really?! Could any iOS developers chime in on whether their are actually ways for apps to control this?

- 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.

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.

My previous guess was the original version had spaghetti code (ex: lots of hard coding edge cases), and they tried to move it to a more standardized / maintainable code block that hasn't been fully brought up to speed.

The guess was based on a interview video I saw discussing the various prototypes for the original iphone keyboard.

I can learn to use a consistent kb, but I can't learn a moving target