# Best Practices for UX/UI Well‑designed UX/UI plays a critical role in ensuring **performance, maintainability, and long‑term usability** of applications built on ONEWEB.\ Thoughtful design decisions made early help reduce rework, simplify reviews, and prevent common usability issues later in the development lifecycle. This section focuses on **platform‑level UX/UI best practices**—how to design pages, forms, and interactions effectively using ONEWEB UI and Page Designer tools.\ It does **not** cover business logic, functional requirements, or project scope. Instead, it concentrates purely on creating a **clean, consistent, and user‑friendly interface**. By following these best practices, designers and developers can: * Deliver a smoother user experience * Minimize confusion and user frustration * Improve performance and maintainability * Ensure consistency across pages and applications The following guidelines outline key **do’s and don’ts** to help users achieve an effective UX/UI setup while working with ONEWEB. --- # 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/oneweb-platform-th/building-apps/ui-page-designer/best-practices-for-ux-ui.md?ask= ``` 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.