UX in the context of user interfaces (UI) refers to the degree of quality in the interaction between the user and the UI. An application designed with UX in mind enhances the user satisfaction by improving its usability. Simplicity is key in the process of UX design, but avoid falling into a minimalistic design, which may otherwise spoil usability.

UX design may include several disciplines, including wireframing, prototyping, testing, and validating designs. In this section, we'll explore variations of typical CRUD views. Examples of this kind of views are the admin views for managing registered users, views for internal application configuration, or views used by DevOps members.

We'll avoid the term CRUD for more sophisticated views that might include all of the CRUD operations. In general, these views are business-specific, and developers should design them according to the particularities of each case.

CRUD views are about record editing. Records are items that are usually understood as a whole. Some are suitable for tabular presentation, while others are not; for example, events on a calendar. When designing a CRUD view, think about the following factors:

• Record complexity: How many fields does the record contain? Do the fields change depending on the state of other fields? Are there any complex fields such as maps or calendars? How complex are the validation rules?
• Editing frequency: How often do users need to edit the record? Do they need a quick way to edit certain fields?
• Context awareness: Do users need extra data when editing a record? Do they need, or would they benefit from, seeing other records when editing one?

Let's analyze three CRUD user interface designs: in-place fields, modal pop-up windows, and hierarchical menus.