It's important to note though that the _actual_ touch targets for keys are influenced by what you've already written. You can miss the key from a visual perspective but still end up with the right letter as a result.
I'm guessing that's the reason why I've gotten worse at typing on mobile some years ago, and can't seem to improve it, despite being able to quickly master any similar skill through repetition.
Desktop isn't much better. I actually somewhat like having the text inputs in some programs as I do writing in nontraditional programs (like arbitrary chat programs that don't implement spell check, because why would they?) but it feels incredibly unintuitive, especially when using RDP from my tablet [4], but also when using it locally. Windows is a keyboard-first OS for me, I shouldn't need to use the mouse for any first-party functionality.
1: including autocomplete suggestions, predictive text, and swipe input. I call all of these autocorrect since they mostly seen to share the same dictionary and rules. 2: they're not in my custom dictionary, and dragging the suggestion to the middle of the screen doesn't prevent it from happening again) 3: easy fix, but it needs to be implemented: a single dash is part of a word, a double dash is not. 4: this is an area Microsoft could improve tbh. They know what kind of input you're using when you're in edge or command line. In these software the mobile RDP client should provide keyboard hints to the local soft keyboard to switch input modes based on form input types, and should reset the local keyboard when the active remote keyboard context changes. It should certainly not be deleting entire command lines when I hit backspace in RDP (this is especially annoying in CMD and notepad) as the local software keyboard doesn't know that the my long string was 7 inputs to 4 different programs, not one long input.
How do people survive with their ducking auto-correct on, I don't know. I guess they don't type that much.