After quite a long pause, I’m getting back with a new series of posts. And we’ll start with Android
EditText form validations.
At first let’s define that Android form - it is a set of EditText’s whose data should be processed. There are two main steps to make processing successful: data input and data validation.
Chuck Noris is always valid
In order to make user input easy and comfortable, we need to configure
EditText properly, here is some tips on it:
- put constraints by specifying the type of keyboard you want for your
android:inputTypeattribute. For example, if you want the user to input only digits write
- besides specifying keyboard type using
android:inputTypeattribute you can define other behaviors such as, whether to capitalize all new words or use features like auto-complete and spelling suggestions, e. g.
android:inputType="textCapWords|textNoSuggestions", note that you can put several markers using bitwise operator
- probably you’ll want to disable fullscreen keyboard on landscape mode, you can do this using
- pre-fill form data and provide auto-complete if possible, for example in email registration form you can get user email from
AccountManager, example from Roman Nurik on stackoverflow
- validate and submit the form when user press enter on last EditText field, here code snippet I use:
Here is a code snippet from a layout file with described above attributes:
Question is not how to validate, but how to show validation errors in a user-friendly way?
Android API provide
public void setError(CharSequence error, Drawable icon) method on EditText instance to display errors.
As form validation is quite a common task, there are several third party libraries for that, e.g.:
Both of this libraries use default API to display errors, and personally I don’t like it because when there are a lot of validation rules neglectful user can get screen like this:
Too many errors on one screen
So what is “the right way”? Main idea is to help user solve errors one by one. There are several things to do when validation error happens:
- find the first text view where validation failed
- request focus for it:
- show error message, I prefer using Crouton library:
Crouton.makeText(mActivity, message, Style.ALERT).show()
- open keyboard so user can start typing instantly:
I’ve created the small library with a sample project where you can find all examples from this post. Check it out on GitHub or install Demo app from Google Play. Sample code of creating validation form:
Failed InRange validation
(I’ll update lists every time I find related topics)
Share with: LinkedIn • Twitter • Facebook