> For the complete documentation index, see [llms.txt](https://docs.amltd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amltd.com/dc-works/core-concepts/understanding-suites.md).

# Understanding Suites

A **Suite** organizes one or more Applets into a launcher that users can run on an enrolled device or as a Web App.

Applets are created first and then added to a Suite.

```mermaid
flowchart TD
    A1["Applet 1"] --> S["Suite"]
    A2["Applet 2"] --> S
    A3["Applet 3"] --> S
    S --> D["Enrolled Device"]
    S --> W["Web App"]
```

### What a Suite contains

A Suite can contain a single Applet or several related Applets.

Its launcher may include:

* Buttons that open Applets
* A company or solution logo
* Text or other fields
* A background color or image
* Actions that run when the Suite launches

The Suite provides a starting point from which users access the Applets required for their work.

### Applets and Suites

An Applet performs a particular task or workflow. A Suite brings Applets together for a particular solution, user, or operational purpose.

For example, an inventory Suite might contain Applets for:

* Receiving inventory
* Moving inventory
* Cycle counting
* Looking up an item
* Shipping an order

```mermaid
flowchart TD
    S["Inventory Suite"] --> R["Receiving Applet"]
    S --> M["Inventory Movement Applet"]
    S --> C["Cycle Count Applet"]
    S --> L["Item Lookup Applet"]
```

{% hint style="info" %}
An Applet exists independently of a Suite and may be reused in more than one Suite.
{% endhint %}

### Running a Suite

A Suite can be made available in two ways:

* **On a device** — The DC Works mobile application is installed, and the device is enrolled in the Suite.
* **As a Web App** — The Suite is made available to an authorized Web User and accessed through a supported browser.

The Applets within the Suite provide the same underlying workflows, although their presentation and available device features may differ depending on how the Suite is accessed.

### Suites are more than folders

A Suite does more than simply group Applets. It provides the user-facing launcher and can help tailor how a solution is presented.

For example, two Suites could include some of the same Applets while providing different launchers for:

* Warehouse employees
* Supervisors
* Service technicians
* Retail employees

This allows Applets to be reused without requiring every user or device to receive the same collection of tools.

### Plan Suites around users and workflows

When planning a Suite, consider:

* Which Applets should be available together?
* Who will use the Suite?
* Will it run on mobile devices, as a Web App, or both?
* Which Applets should be easiest to access?
* Does the launcher need instructions, branding, or launch actions?
* Could an existing Applet be reused instead of duplicated?

Keep the launcher clear and focused. Users should be able to quickly identify the Applet needed for their next task.

### The Getting Started example

In the Getting Started tutorial, you created the **Getting Started** Suite and added the **Asset Check-In** Applet to it.

```mermaid
flowchart LR
    A["Asset Check-In Applet"] --> S["Getting Started Suite"]
    S --> D["Enrolled Device"]
```

The Suite provides the launcher, while the Applet contains the pages, fields, records, actions, and conditions used to perform the asset check-in workflow.

### Key distinction

| Component       | Primary purpose                                        |
| --------------- | ------------------------------------------------------ |
| Applet          | Performs a task or workflow                            |
| Suite           | Organizes Applets and provides their launcher          |
| Enrolled device | Runs the Suite through the DC Works mobile application |
| Web App         | Provides browser-based access to the Suite             |

### Next

Continue to **Records and Data Binding** to learn how Applet fields connect to working data and information retrieved from tables.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.amltd.com/dc-works/core-concepts/understanding-suites.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.