Terrorizing Apple with a countdown threat is probably not going to accomplish much.

You could try installing Gboard (https://apps.apple.com/ca/app/gboard-the-google-keyboard/id1...), or SwiftKey (https://apps.apple.com/ca/app/microsoft-swiftkey-ai-keyboard...)...and there are probably other options.

It may be even more obvious, but there are settings in general/keyboard that you can toggle.

I noticed a bit of a shift in the stock typing experience, but I adapted and it's fine.

▲

Kovah 8 hours ago | parent | next [-]

I recently tested Swiftkey after Typewise is sadly abandoned. It's sooooo much better than the stock keyboard. Not only is the auto-correct working incredibly well (garbage like witjoit is correctly transformed to without, which Apple Keyboard can't), Swiftkey also manages multi-language typing astonishingly well. Last but not least, I can customize it. I am also not signed in to my account, so no settings or whatever is stored on Microsoft servers.

▲

eptcyka 8 hours ago | parent | prev | next [-]

Of course, the first party keyboard doesn't work, you should use the ones that definitely do not phone home to either Google or Microsoft.

Of course regular window management doesn't just work out of the box, you should install one of the many different window managers on macOS.

I was under the impression that to get a product that just works, I can buy Apple hardware, right?

▲

speak_plainly 5 hours ago | parent | next [-]

Is this an actual bug or is this just a corrupt database or corrupt setting? What steps were taken to try to alleviate the issue, basics like resetting the keyboard dictionary? DFU restore of the phone? If you're not willing to troubleshoot an issue on your phone, rather than just throw it away and buy an Android, trying a 3rd party keyboard seems sensible to me.

Ultimately, Apple is responsible here but I don't think this is an intractable issue baked into the software. And yeah, maintenance is required despite what the perception might be. Apple even offers great support services for people who are not able to do it themselves.

	▲	eptcyka 4 hours ago \| parent [-]
		What are you even talking about? DFU mode? For a keyboard ussue? My brither in christ, it is a keyboard, it is the one thing that must just work. Oh yeah, let me just dump a sysdiagnose for the 50th time today because the keyboard chose to autocorrect my spelling into nonesense. I submit enough bugs as is, I receive radio silence enough, I ain’t got time to do unpaid qa or pr for a billion dollar company. What is so dofficult about observing that the touch inputs and the touch feedback does not match the characters that end up produced into the text input field. Does it even matter if it is a corrupt setting or not? Why would it matter? As far as I am concerned, I am seeing every iOS user around me suffering from this. The root cause does not matter here.

▲

Kovah 8 hours ago | parent | prev [-]

The sad part is, that Apple used to make somewhat stable, functional software. I started with the iPhone 3 and a bit later with Mac OS Snow Leopard. It all started when Mr Cook decided to serve the shareholders, instead of focusing on Apple's core values. The software went downhill in such a speed in just a few years. And moving out of the ecosystem is a painful, if not unbearable, task that barely anyone loves to do. At least I can't even think about moving back to Android.

▲

avazhi 8 hours ago | parent | prev [-]

Telling anybody to install third party shit to fix first party shit should have been a hint to you that what you're saying is laughable.

Throwing random nonsense about 'general/keyboard' settings (that don't exist, btw) because you yourself can't think of anything specific should have been another.

The keyboard, specifically the Autocorrect, is fucked and has progressively worsened over the past 5 years. It's atrocious today. This is a first party problem that shouldn't need 3rd party solutions, end of story.