Use DomUI to create large web-based applications where there are lots of input and data screens. Using the (optional) metadata layer you can very quickly create all kinds of CRUD screens. The rich, generic and extensible metadata layer helps you by retrieving information in your (data) model classes, database etc. so that you do not have to define the same thing over and over again. One definition of "This string field is 30 characters long", for instance as a JPA/Hibernate annotation on a property, is all it takes to have all edit components reuse that value automatically. The stateful page handling makes handling data easy, and prevents serialization headaches. And data binding between business models and UI components allows for separation of business logic and UI without lots of work.
DomUI can be used for most applications, but is less suited for the following:
The design criteria for DomUI value developer productivity over hardware costs.
This site contains the documentation for the code, tutorials to help you with learning and a FAQ for those questions that are frequently asked.
Next page: a developer list of facts about DomUI