1. Support for embedding a logo or other graphic into the survey page. Support for background images, too. 2. An optional progress bar can be added to a survey. The colors used are configurable (as are all colors and styling) and can be programmatically controlled, so your application is not limited to a single stylesheet. 3. The questions can be optionally automatically numbered. Question numbering can be completely disabled as well, which is useful for surveys with conditional questions. 4. Questions, and even entire pages, can be conditional using user-defined rules. Conditional questions appear/disappear live from the page as the survey is answered. 5. Any question, regardless of type, can have comments added. Comments can be disallowed, made conditional, or made required. 6. A respondent can opt-out of a survey at any time. They can also leave a survey and return to exactly where they left off at any time. The ability to opt-out can be disabled; for example, an employee survey might be required. 7. An optional page footer can be added. Any text element in the survey definition can have user-supplied external links (such as the "Privacy Policy" link in this example).

8. An optional page heading and subheading can be added. The page heading and subheading can be part of the page template or different on each page of the survey. 9. A comment or other trigger can be conditionally activated for a question. The trigger happen live in the page as the survey is answered. In this example, checking two or more of the options activates an optional commentary field. 10. Questions can be marked as optional or required. This feature works in conjunction with the conditional logic, allowing a question to be conditional (displayed/not displayed) and still optional (answer required or not required). 11. A powerful analytics mechanism is built into the framework that understands answer weighting, question scoring, and how to construct a statistcally correct answer even when conditional logic is applied. 12. Questions can have single answers, multiple answers or be a matrix of answers. Both questions and answers can be stored in a common library and reused. All question types are plugins, so new question types can be added without changing the Hondai framework. 13. Buttons, text and images can all be branded. Only a single PNG needs to be supplied to change the look of all application buttons. The framework is fully localized and any text can be translated or replaced without changing the code.