android2014.06.26 10:45
21 November


By Roman Nurik

Entering data and filling out forms on mobile devices kind of sucks. Because of this, you generally want to put as much of the burden of data entry on yourself—the developer—as you can, and as little on the end user as possible. For example, registration forms with 10 input fields are likely to annoy users far more than those with only 2 input fields… or one… or even none (auto-fill the email and auto-generate a password!).

Having said that, there are a number of very fair use cases that require a lot of user input, or complex user input, and have potentially nontrivial consequences. For example, customizing and ordering physical goods, scheduling bank transactions, or setting up a complex app (or operating system!) for the first time.

Key features

  • Branching, or the ability for wizard steps to influence the availability of later steps
  • Allowing the user to review before committing
  • Allowing the user freeform navigation between wizard steps
  • Support for required and optional steps
  • Support for step classes (technically, each step is an instance of a Java class, so you can have multiple instances within the wizard)

Posted by 레드오이