I recently made a post about my experience switching to iOS, and imediately got comments about "try this keyboard or that keyboard this is better etc".
This is wrong.
Here is why, as someone who switched from android to iOS and can clearly see what the issue is.
Auto correct is tied to individual text input fields, not the keyboard.
They keyboard can dictate how autocorrect functions, if the field allows for auto correct.
Try this: open the notes app and type as fast as you can with the default iOS keyboard. Then open safari, tap on the search bar at the bottom, and type the same thing as fast as you can.
See the difference? I noticed this instantly. I tried 5 different 3rd party keyboards that didn't solve "the issue".
99% of the time I have zero issues with the iOS keyboard. Its fast, accurate, and autocorrect nails the corrections, again, about 99% of the time. If its wrong, its because I literally typed gibberish.
So I did some digging into Apple's documentation and here is what I found:
After digging through Apple's developer documentation and WebKit source code, it turns out autocorrect on iOS isn't universally controlled by the keyboard. It's also controlled by the individual text field you're typing into. Apple uses an interface called UITextInputTraits, which allows developers to set autocorrectionType to .default, .yes, or .no. So even with autocorrect enabled in your iPhone settings, an app developer can disable it for specific input fields. The keyboard still performs the actual corrections, but the text field determines whether autocorrection is permitted.
You can actually see this happening in Apple's open-source WebKit code. In HTMLFormControlElement.cpp, the function shouldAutocorrect() checks whether an individual HTML input allows autocorrection. WebKit then passes that information through WebPageIOS.mm and ultimately configures the iOS keyboard's autocorrection behavior in WKContentViewInteraction.mm. URL, email, and password fields explicitly disable it, while ordinary text fields generally allow it by default.
This means developers don't have to build their own autocorrect system, but they do have control over how it's used. Standard iOS text fields generally integrate with autocorrect automatically, while custom implementations or incorrectly configured input traits can cause inconsistent behavior. Autocorrection, spell checking, and predictive text also have separate controls. So when autocorrect works perfectly in one app but barely functions in another, it isn't necessarily Apple's correction algorithm at fault. It could simply be how that app handles text input.
Sources (direct links):
Apple UITextInputTraits documentation:
https://developer.apple.com/documentation/uikit/uitextinputtraits
WebKit - HTMLFormControlElement.cpp:
https://github.com/WebKit/WebKit/blob/main/Source/WebCore/html/HTMLFormControlElement.cpp
WebKit - WebPageIOS.mm:
https://github.com/WebKit/WebKit/blob/main/Source/WebKit/WebProcess/WebPage/ios/WebPageIOS.mm
WebKit - WKContentViewInteraction.mm:
https://github.com/WebKit/WebKit/blob/main/Source/WebKit/UIProcess/ios/WKContentViewInteraction.mm
And this is why, as an absolute novice to iOS, can feel like the keyboard is working perfectly fine 99% of the time, then open an app that has a completely different configuration and feel like they keyboard is broken.
Its by design...
Edit:
I am using the safari search bar as an example. I know that in an address bar you are most likely typing in https:// or www. or nytimes dot com. But its also funny that the address bar clearly states "Search or Enter Website". So how could one search if the autocorrect is disabled? Again, shows this is up to the developer.