On (Form) Validation

It's beyond frustrating to see software developers still handling "validation" in applications the same old way, especially when it comes to user input systems like contact forms. The typical forms and submission processes, with labels above or to the side and asterisks for "required" fields, are submitted either directly or asynchronously, only to generate impersonal validation or confirmation messages.

Users are bombarded with inorganic and harsh responses, including intimidating red boxes listing validation errors. We can, and should, improve our apps by incorporating more respectful and user-friendly responses. Sometimes, a submission might lack certain fields because the visitor isn't ready to provide that information. By respecting our visitors' intelligence, we can build brand credibility.

It's maddening to see so many touch-points for strengthening brand-client relationships neglected, leading to public-facing marketing assets that drive potential customers away due to poor user experience. Even though users might be used to computer-generated responses, our goal should be to create enjoyable, valuable interactions.

One much-needed change is rethinking the use of "required" fields. While not always applicable, such as in registrations, we should assume that users provide input intentionally. Instead of demanding specific formats or quantities of information, we need to focus on demonstrating the value of our offer and being available for further inquiries or transactions.

For instance, if a request for information form has phone and email fields, getting either one should be considered successful. But users often face validation errors like:

• E-mail invalid or missing
• Username already used
• Phone number required

These impersonal messages penalize potential customers trying to engage with the brand, showing a complete lack of tact in user interactions. We could write additional business logic around form submissions to handle interactions more appropriately and tone down the machine's abruptness.

One possible approach is to display a summary of the submitted information, like a receipt, regardless of its completeness, respecting users' choices without judgment. Another option is to subtly accept the information provided and gently prompt the user for more details during their session. By using cues from the visitor, we can assess when it's appropriate to request additional information. Emulating a face-to-face interaction style can enhance our marketing tools and create a more enjoyable user experience.