4 ms·
That seems like a huge exaggeration of the severity of those issues: > Text Fields are almost unusable for iOS users that don't have predictive keyboard enable
by IshKebab 5y ago
That seems like a huge exaggeration of the severity of those issues:
> Text Fields are almost unusable for iOS users that don't have predictive keyboard enabled.
"Almost unusable" sounds like you can't type, but really it is just missing the autocorrect popups. And if you check the comments, somebody provides an implementation that does show them.
> Emoji rendering is broken on iOS.
This makes it sound like it doesn't show emojis, but really they're just slightly too small.
- onli 5y agoAgreed. I was thinking that we must have completely missed something (working with flutter right now) to not be aware of those bugs, but looking at them they are minor and have a solution in the issue threads. These are in no way blockers for getting apps done that users can like.
- sdflhasjd 5y agoI agree the emoji issue is a little overblown, but I think "almost unusable" could be appropriate. On a phone, the synergy of autocorrect and fat fingers is a delicate one, and even small changes can really upset the typing experience. Samsung once updated the keyboard on my phone, and the different visual cues and behaviour completely threw off my muscle memory and made typing very difficult. Even the autocorrect mode being wrong on an email input can be annoying, so a whole app acting up would be even more unpleasant.
- mort96 5y agoSaying "it is just missing the autocorrect popups" is misleading. The problem with not providing the autocorrect popups is that you _can't cancel an incorrect autocorrect_. That would 100% infuriate me.