# Don’t: UX/UI Anti‑Patterns

The following practices should be **avoided** when designing pages and forms using ONEWEB UI and Page Designer.\
These anti‑patterns often lead to poor usability, reduced performance, and unnecessary user frustration.

***

#### Don’t Let Visual Design Reduce Readability

The design of a page or form should **never interfere with content readability**.

Avoid:

* Busy or decorative backgrounds behind text
* Poor color contrast between text and background
* Typography choices that make text hard to read

Ensure that:

* Text has sufficient contrast
* Font size, line height, and line length support comfortable reading
* Content remains the primary focus of the screen

Readability is a foundational requirement for good UX.

***

#### Don’t Prevent Users from Scanning the Screen

Users typically **scan** a screen before reading in detail.\
Designs that ignore this behavior make it harder for users to find what they need.

Avoid:

* Lack of clear headings or visual structure
* Dense blocks of text without separation
* UI layouts that do not provide visual cues

Instead, support scanning with:

* Clear section headers
* Logical grouping of content
* Consistent alignment and spacing

***

#### Don’t Fill Screens with Unrelated or Irrelevant Content

Users come to a page with a **specific goal**.\
Unrelated content distracts users and slows task completion.

Avoid:

* Showing unnecessary fields as mandatory
* Mixing unrelated information on the same screen
* Displaying ads, recommendations, or secondary content during critical tasks

Design each page to support **one primary user task** whenever possible.

***

#### Don’t Make Users Wait for Content to Load

Slow‑loading pages quickly frustrate users and reduce trust in the application.

Avoid design choices that negatively impact performance, such as:

* Large unoptimized images
* Excessive animations
* Too many UI elements loading at once
* Heavy reliance on third‑party resources

Optimized UI design helps keep pages responsive and users engaged.

***

#### Don’t Let Multiple Elements Compete for Attention

When too many elements compete for attention, users become confused or overwhelmed.

Avoid:

* Too many call‑to‑action buttons on a single screen
* Flashing or animated elements without clear purpose
* Frequent pop‑ups or modal dialogs

Use **visual hierarchy** to guide users naturally:

* Highlight one primary action per screen
* Reduce visual noise
* Keep interactions predictable and focused

***

#### Why Avoiding These Anti‑Patterns Matters

Avoiding these UX/UI pitfalls:

* Improves usability and clarity
* Reduces user frustration and errors
* Improves performance and maintainability
* Leads to smoother reviews and fewer redesigns

Together with the **Do** guidelines, these anti‑patterns provide a practical foundation for building effective UX/UI using ONEWEB UI and Page Designer.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onewebstack.com/building-apps/ui-page-designer/best-practices-for-ux-ui/dont-ux-ui-anti-patterns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.