Join the early bird Black Friday list

Black Friday is just around the corner, and we’re excited to offer early access to our best deals of the year at shop.learningloop.io. If you’re looking to elevate your brainstorming sessions and streamline your team’s workflow, our printed card decks are here to help.

Want to get in before everyone else?
Join our Black Friday Early Bird list to be the first to know when discounts go live! We’re launching the sale early this year, so you can grab your deck and start putting it to use before 2025 even begins.

Join the list

Problem summary

The user needs to quickly enter data into the system, which then in turn interprets the user's input.

Example

Usage

  • Use when the more explicit select boxes, radio buttons, and checkboxes make entering data a too complicated process for the user to engage with the system.
  • Use when the time it takes to complete a task proportional exceeds the importance of the goal the user wants to accomplish.
  • Use when the input you want to collect is relates to one topic. For instance a physical location or an event with a given start time.
  • Use when the expected user input can be somewhat easily interpreted by a computer program.
  • Do not use when the user can possibly ask or input anything. Only use for a narrowly defined purpose.

This card is part of the UI Patterns printed card deck

A collection of 60 User Interface design patterns, presented in a manner easily referenced and used as a brainstorming tool.

Get your deck!

More examples

Solution

Allow users to enter text in their own format and syntax, and let the system interpret it intelligently

Let users focus on getting things done rather than typing in things correctly. Lower the barrier for users to interact by allowing a broad spectrum of formats and syntaxes to be inputted. Consider nudging users to provide more easily interpreted information by paying attention to how you ask for input.

Transfer the problem inputting data from a user interface problem to a programming problem. Behind the scenes, an interpreter checks for different word patterns, and converts them into a formatted value.

Rationale

Using the forgiving format pattern saves space and decreases the barrier for the user to interact with the system.

Depending on how widely defined the input topic is, it can be increasingly hard for the backend program to interpret the input field. The success of this pattern has much to do with how information requested – how the user is prompted.

This article has been commented 2 times.

More examples of the Forgiving Format pattern See all 6 example screenshots

User Interface Design Patterns

2 comments

  • Chris M. on Mar 18, 2010

    Nice explanation of forgiving format, which seems to be a practice that is lacking in many websites, unfortunately (click on the link provided to see other examples of the same problem).

  • ecommerce blog on Jul 12, 2010

    Nice. I hate having to get it right in ecommerce websites. I like the site to correct me.

Comments have been closed