← Graph

Does per-field validation blow up UI complexity?

question 2 connections

Audience worries that validating each field via events (label, description, etc.) would require many new forms and UI screens, inflating complexity. Garofolo: you're not forced to go this way, but a task-driven UI keeps each form small (you rarely submit a giant multi-field form), so more screens but each less complex. He finds the overall model less complex than MVC-CRUD — 'more things of less complexity' — comparing events to coins rolling into their slots in a piggy bank, versus MVC-CRUD's tangled validation code.

answer_summary
You aren't forced to validate every field this way, but pairing the approach with task-driven UIs yields many small forms that are each simpler than big MVC-CRUD forms.
question Does per-field validation blow up UI complexity?
about
Task-Driven UI concept
Garofolo answers by appealing to task-driven UIs as the complexity mitigation.
question Does per-field validation blow up UI complexity?
asked_at
Asked in Q&A after the talk.

Provenance

Read by
2 extractions