zlacker

>>walter+(OP)
Switched from pixels to iphone in the last year or two and the keyboard is the biggest pain point by far. I tend to use swipe, so this particular issue isn't something I've come across. What I do run into is weird censorship issues where I'm trying to type "kill myself" or something similar and the phone will do anything to not provide that as an option. Then, when I try to manually change it, editing is a nightmare. Inevitably trying to change the ending of a word results in the entire word being deleted. It inserts spaces where I don't want them.

Is this some sort of psyop to get me to use siri to send texts?

>>baseba+Rc
Similar switching story. I'm very happy with an iPhone overall, but god damn they keyboard took some adjusting. The default keyboard on Pixels (GBoard?) is excellent. The autocorrect is also unimaginably better on the Pixel. It's embarrassing how bad the iPhone's autocorrect is. Not just missing obvious cases, but actively sabotaging correct cases.

>>jjice+fe
> The default keyboard on Pixels (GBoard?) is excellent.

Not my experience at all. Do you only write English?

>>tasuki+nr
I personally haven't found any keyboard that works better than gboard. And exactly because it's the only keyboard that just lets me type in two languages without having to "switch", and it does that well. Right now my spacebar just says "NL - EN" and it lets me combine Dutch and English just fine.

>>mavama+Ey
From my experience it is much worse than it used to be 5 years ago. I have been writing English, French, and to a lesser extent German on an iPhone since ~2008. Initially, the dumb autocorrect would just correct to the closer word in the dictionary corresponding to the current keyboard, but over time it would pick up more and more words I used regularly. At some point around 2018 or so, it was nearly flawless. I think it changed the dictionary depending on the language or the sentence, because I had different suggestions for the same mistyped word in the same document. Also, I assume that by then my personal dictionary was quite extensive.

And then they bragged about a new machine-learning improved keyboard and it went downhill. First, all keyboards became monolingual, which was a 10-years regression. And even in that language, it was very flakey. They added multi-language keyboards somewhat recently and it got slightly better, except that for some reason it changes the keyboard back to the English-only one regularly for no reason I can see.

It is maddening. For a couple of years it was fantastic.

>>kergon+1R
And that’s not the worst. On the Apple Watch not only is the multilingual keyboard completely broken, but worse than that: if you change the language of the keyboard by long pressing the space button it shows the new language, but the autocorrect proceeds to just ignore it completely and autocorrects everything as if I were typing in the system language rather than the one I selected.

And contrary to the iPhone you can’t even disable autocorrect! This + the super-aggressive autocorrect of watchOS (the screen is small after all so you are likely to make a mistake and we better fix it automatically!) makes it an absolute NIGHTMARE to type on an Apple Watch in multiple languages. Your only option is to use speech to type because that one for some reason works when you change the language whereas the keyboard doesn’t care.

Edit: the language switch bug on watchOS seems to have finally been fixed on watchOS 26.1. The bug was already long present on watchOS 11, so not something that watchOS 26 introduced.