> - Keyboard sometimes doesn't get out the way any more when it should.
Depends on where you were seeing this of course, but this could very well be an app problem instead of a system problem.
Native UIKit/SwiftUI do a little bit of keyboard management for “free”, but there are many circumstances where it falls on the developer’s shoulders to do this. For cross platform frameworks, some do keyboard management others don’t even try. For web apps it’s a coin toss and depends on which of the gazillion ways the dev built their app.
It’s not actually that hard, usually just a matter of making sure that your scrolling content either resizes to match the keyboard-shrunken viewport or adding bottom padding equivalent to the height of the keyboard and then and adjusting scroll position accordingly, but it’s not unusual to see this partially or fully absent, especially on poorly built cheapest-bidder-contracted apps.
In modern UIKit it's as simple as constraining to the keyboard layout guide. That gives you full animation support for free as well, no more need to listen for the notification and manually set up animations with the same timing and curve. On iPads the keyboard guide can even help you avoid the split keyboard, it's really nice.
Of course SwiftUI gives you almost none of this control, forcing you to hope the magic automatic support works how you expect.
But then neither help you with any of the other interactions, like any background dimming you may want, or tapping away from the keyboard to dismiss. That has to be done manually.
Depends on where you were seeing this of course, but this could very well be an app problem instead of a system problem.
Native UIKit/SwiftUI do a little bit of keyboard management for “free”, but there are many circumstances where it falls on the developer’s shoulders to do this. For cross platform frameworks, some do keyboard management others don’t even try. For web apps it’s a coin toss and depends on which of the gazillion ways the dev built their app.
It’s not actually that hard, usually just a matter of making sure that your scrolling content either resizes to match the keyboard-shrunken viewport or adding bottom padding equivalent to the height of the keyboard and then and adjusting scroll position accordingly, but it’s not unusual to see this partially or fully absent, especially on poorly built cheapest-bidder-contracted apps.