I have had issues with app pages that have a text field on the very bottom of the page. If a page has many fields, and a text field is on the very bottom, the keyboard will cover the field so you cannot see what you are inputting. Also wont let you scroll the field to be visible while the keyboard is open. This is on an iPad, and present in either landscape or portrait mode. If a user makes a mistake in the text, they are then unable to edit precisely, as when they click on that text field, the on screen keyboard will cover up the text box preventing placement of the cursor where they want it. The user then has to backspace the whole box and start from scratch blindly again. A fix is to rearrange the page so a field text is never last on the bottom, but would be more user friendly if even if on the bottom, the text field was always visible, or allowed the user to scroll to see the text when the On Screen Keyboard is open. Also noticed if check-boxes, or multiple choice fields are between text fields, when the user hits done on the keyboard, it will skip over the check-boxes, and go to the next text field. Would be more user friendly if it went to any next field, vs, skipping past required check-boxes, multiple choice fields, only to give an error when you try to go to next field, because required stuff was skipped over. Not that these are major issues, would just be a user friendly improvement.
1
Comments
Please sign in to leave a comment.
Hi Dan and Darin,
I'm going to go ahead and submit this to our development team as it's really a usability issue. Dan, you'll get updates on it as a support ticket and I'll update here so everyone has visibility.
Thanks!
This actually is a pretty big issue. Actually a couple of big issues.
The next button in both iOS and Android takes you to the next text field, skipping check boxes, which has made us use drop-down "yes/no" fields, instead. I'm not sure if the following is a fix to that or not, but it would make it somewhat better.
If every app page had a predetermined amount of 'dead space' built in at the bottom of the page to compensate for the on-screen keyboard, and the 'current' field was always no more than 3rd from the top of the screen, then the bottom one or two fields would be visible at all times. Of course, there will be someone with "War and Peace" as their terms and conditions field before a text field for a name and a signature field that will still have a problem, but otherwise, it would make the mobile app much friendlier.