Need help with Android-Validator?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

457 Stars 117 Forks 181 Commits 6 Opened issues


Form Validator Library for Android

Services available


Need anything else?

Contributors list


Form Validator Library for Android

Flattr this git repo


Form Validator Library for Android is based on Zend_Validator coded in PHP. This library is intended to simplify and streamline the code to validate a form Android. For the moment, the form can just handle the EditText. Other elements will emerge in future versions.



  • Android 2.2+


  • demo application demo folder (coming soon)
  • library library project directory
  • others Others Resources directory (icon, sreenshots, ...)
  • library/tests Unit Test Directory (coming soon)

Import in your Project

Graddle Project

Comming Soon

Maven Project

Comming Soon


In order to execute tests:

gradle localTest
Results are available in app/build/reports/tests/index.html


Form Validator Library is composed of 3 members : - Form : Contains all beings validates to treat. This is the Form that manages the display of error messages in the various elements. - Validate : Contains all the validators to be treated for a given element. - Validator : Can define a validation rule.


The validator is basic class for this library. It contains specific validation rules. To instanciate validator, you just have to do this (EmailValidator for example):

new EmailValidator(context);

For some validators, functions can change the validation rules. The validator currently contains three basic validation rules: + EmailValidator : Ensures that the field does contain a email address. You can also define a regex to check for a particular domain name with the function

. Example for domain :
. + NotEmptyValidator : Ensures that the field is not empty. + UrlValidator : Ensures that the field is a valid url. + AlnumValidator : Ensure that the feld has Alnum characters. + HexValidator : Ensure that the field has Hex characters. + RegExpPattern : Ensure that the field does match setted Pattern. + PhoneValidator : Ensure that the field is a valid phone number. + RangeValidator : Validates whether the given value is bettween a range of values + NumericValidator : Checks whether the field contains only numeric digits + IPAddressValidator : Checks whether the field contains a valid IP Address + MockValidator : Used by dev as a placeholder while testing validation + Custom Validator : You can create your own Validator. To do this, you can just create class extends AbstractValidator :
public class CustomValidator extends AbstractValidator
    private int mErrorMessage = R.string.validator_custom; // Your custom error message

public CustomValidator(Context c) {

public boolean isValid(Object value) {
    // Your validation Test is here.
    // Retour true if it's correct, false if it's incorrect
    return true;

public String getMessage() {
    return mContext.getString(mErrorMessage);



The pure Validate class is a FIFO validator. It's test a list of AbstractValidator for specific EditText. For some special cases, Validate is not enough. This is why there are specific validates. This is why there are two individuals with a Validate operation different from that base : + ConfirmValidate : Can check whether a value is identical between the two fields. Can be used to confirm the entry of a password. + OrTwoRequiredValidate : If one of the two target fields has a value, then it is valid. Can be used if a user must give his phone or fax. + Validate : The base Validate. It creates his validators stack.

Basicly, Validate can only handle a single EditText. If you want to manage several at the same time, see if *ConfirmValidate * or *OrTwoRequiredValidate * match your problem. If this is not the case, you may need to create your own Validate. To instantiate a Validate, you just have to do this:

Validate emailField = new Validate(email);

And to add Validator stack, for example to add a required Email field, you have to do this:

emailField.addValidator(new NotEmptyValidator(mContext));
emailField.addValidator(new EmailValidator(mContext));


The Form class is the class teacher of the whole Library. It is this which manages the processing of each Validate, Validator and displays the error on the EditText automatically. The Form class stores a Validate stack and then you just have to run the validation with the

function. To instanciate Form and add Validates, you have to do this : ``` java Form mForm = new Form(); mForm.addValidates(emailField); mForm.addValidates(confirmFields); mForm.addValidates(urlField);

// ...

// Launch Validation if(mForm.validate()){ // success statement }else{ // error statement like toast, crouton, ... } ```

You can close the error using the form. Can close all errors or just one :

// close one error
// close all errors


  • Fork the repo
  • create a branch
    git checkout -b my_branch
  • Add your changes
  • Commit your changes:
    git commit -am "Added some awesome stuff"
  • Push your branch:
    git push origin my_branch
  • Make a pull request to


  • 0.1 : Create library
  • 0.2 : Add ConfirmValidate and OrTwoRequiredValidate
  • 0.3 : Extends EmailValidator with
  • 0.4 : Replace Validator by AbstractValidator
  • 0.5 : Fix bug in UrlValidator
  • 1.0 : Add AlnumValidator, HexValidator, RegExpValidator, ValidatorException. Fix Validate class.
  • 1.1 : Go to Android 2.2 for android.util.Patterns. Add PhoneValidator. Edit UrlValidator.
  • 1.5 : Project reorganization, graddle and maven support
  • 1.6.0 : Fix bugs, optimize code, add contributions
  • 1.7.0 : Refactoring/Cleaning, add UnitTest
  • 1.8.0: Optimize code, add new validators
  • 1.9.0 : Add validators, add closeError, closeAllErrors, translate into Korean, set the error message by resId or by specifying a string.
  • 1.10.0 : enable gradle builds of the .aar file, allow use of a custom error drawable, define custom error behavior.


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.