# Complex Apps: Combining UX/UI, Business Processes, and Integrations **Complex Apps** are enterprise‑grade applications that combine **user experience (UX/UI)**, **business process automation**, and **system integration** into a single solution. This design pattern represents the most comprehensive use of the ONEWEB platform.\ Complex Apps are typically built when applications must support **end‑to‑end business scenarios**, from user interaction through process execution to integration with external systems. *** #### Characteristics of Complex Apps Complex Apps commonly include: * **Web and mobile user interfaces** for end users * **Web forms and dashboards** for data entry and monitoring * **Business processes** for workflow, approvals, and orchestration * **Integration services** to connect internal and external systems Rather than focusing on a single capability, Complex Apps integrate multiple application layers to deliver complete business functionality. *** #### 🛠ONEWEB Capabilities Used in Complex Apps ONEWEB provides specialized designers to support each aspect of a Complex App: * **App Designer / Page Designer**\ Used to design web and mobile user interfaces, forms, and navigation * **Process Designer**\ Used to model and manage business workflows and task routing * **Microflow Designer**\ Used to implement integration logic, service orchestration, and backend processing These components are **orchestrated together using ONEWEB Microflows**, allowing data and control to flow seamlessly across UI, processes, and integrations. *** #### When to Use the Complex App Pattern Choose the Complex App pattern when: * Applications must support **user interaction, automation, and integration** * Business logic spans multiple systems or departments * End‑to‑end visibility and control are required * The application is expected to evolve and grow over time Most real‑world enterprise applications—such as case management systems, digital service platforms, and operational portals—fall into this category. *** #### Design Guidance for Complex Apps As part of **App Design Fundamentals**, consider the following best practices when designing Complex Apps: * Start with a **clear separation of concerns** (UI, process, integration) * Avoid building everything at once—design incrementally * Keep Microflows modular to simplify maintenance * Ensure UI design aligns with underlying process logic * Design integrations to be reusable and loosely coupled Complex Apps often begin as simpler patterns (UI‑only or Process‑only) and gradually evolve into full enterprise solutions. --- # 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/app-design-fundamentals/choose-your-oneweb-design-patterns/complex-apps-combining-ux-ui-business-processes-and-integrations.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.