# Quick-start ### Overview This **Quick Start** guide provides a high‑level introduction to getting started with **ONEWEB**.\ It is designed to help new users understand the basic flow of using the platform—from accessing the environment to creating a simple application—without going into detailed configuration or advanced concepts. By the end of this section, you will understand: * How ONEWEB is typically accessed and used * The core tools involved in application creation * The basic lifecycle of a ONEWEB application *** ### Prerequisites (At a Glance) Before you begin, ensure that: * You have access to a **ONEWEB environment** (local, on‑premises, or cloud) * You have a valid **user account** with appropriate permissions * The ONEWEB platform has already been installed and configured > Installation and infrastructure setup are covered in detail in the **Getting Started** section. {% embed url="" %} *** ### Step 1: Access ONEWEB AppSpace **AppSpace** is the central workspace of the ONEWEB Platform. After logging in: * You will land in AppSpace * From here, you can create and manage applications * You can access Designer Studios and platform utilities AppSpace acts as the starting point for all application‑related activities. *** ### Step 2: Create a ONEWEB Application In ONEWEB, an application represents the container for all related components such as UI, processes, and integrations. At a high level, creating an application involves: * Defining the application name and purpose * Organizing application components under a single context At this stage, no technical implementation is required—this step establishes the application structure. *** ### Step 3: Design Application Components ONEWEB uses **Designer Studios** to visually design application components. Depending on your use case, you may use: * **App Designer** to create web forms * **Page Designer** to design web or mobile pages * **Process Designer** to model business workflows * **Microflow Designer** to define backend logic and integrations These designers use drag‑and‑drop interfaces, allowing rapid creation without deep coding knowledge. *** ### Step 4: Execute Using Runtimes Once designed, application components are executed by the corresponding **ONEWEB Runtimes**. At a conceptual level: * Designers define *what the application does* * Runtimes execute *how the application behaves* This separation allows applications to be changed and extended without manual redeployment of code. *** ### Step 5: Build and Deploy ONEWEB supports building and deploying applications through a controlled lifecycle. Typical actions include: * Building application artifacts * Deploying applications to the target environment * Making applications available to end users Deployment details vary depending on whether the platform is running in a Standalone, High Availability, or Cloud Architecture. *** ### Quick Application Lifecycle Summary From a quick‑start perspective, the ONEWEB application lifecycle looks like this: 1. Access AppSpace 2. Create an application 3. Design UI, processes, and logic 4. Execute via runtimes 5. Deploy and run This lifecycle remains consistent regardless of deployment model. *** ### What’s Next After Quick Start? This Quick Start provides orientation—not detailed instructions. Next recommended sections: * **Getting Started** – Installation, configuration, and environment setup * **Building Apps** – Step‑by‑step application design and development * **Designer Reference** – Detailed Designer Studio capabilities * **Platform Architecture** – Deployment, scalability, and operations --- # 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/overview/quick-start.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.