> For the complete documentation index, see [llms.txt](https://kb.theloops.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.theloops.io/agentstudio/resource-library/explainers/digital-crew-application-builder.md).

# Digital Crew:Application Builder

Application Builder is the application layer for Digital Crew in IFS Loops. A Digital Crew coordinates Digital Workers into an end-to-end process. Application Builder turns that process capability into business-facing applications that users can review, launch, and refine.

Applications are built on the worker, entity, process, and ontology context already established in the crew. This gives business users a place to work with the crew’s capability without needing to understand the full orchestration behind it.

## Key Benefits

•       Faster delivery: Reduces the effort needed to move from a process concept to a working application.

•       Low-code experience: Users describe the outcome they want rather than doing detailed UI implementation work.

•       Business alignment: Applications stay tied to the Digital Worker, entity, and process context already established in Digital Crew.

•       Flexibility: Supports structured, ontology-led generation as well as custom application creation from business intent.

•       Controlled publishing: Changes are reviewed before they are published, which helps teams avoid exposing incomplete work.

## How Applications Fit into Digital Crew

Digital Crew focuses on the process: Digital Workers, responsibilities, handoffs, and outcomes. Applications sit on top of that foundation and make the process usable for business teams.

Teams typically define or refine the crew and its Digital Workers first, then move to the crew’s Applications tab. From there, applications can be launched for day-to-day use or opened in Application Builder to be refined, previewed, and published.

## The Applications Workspace

The Applications tab shows the applications built for a crew, alongside the crew’s operating context, including its process description, Digital Worker coverage, live work in progress, items needing attention, and completed outcomes. Keeping applications next to the crew they support makes them easy to find and manage.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Area</strong></td><td valign="top"><strong>What users see</strong></td><td valign="top"><strong>Why it matters</strong></td></tr><tr><td valign="top">Applications tab</td><td valign="top">A crew-specific list of built applications, each shown as a visual card.</td><td valign="top">Keeps application discovery and management close to the crew it supports.</td></tr><tr><td valign="top">Application card</td><td valign="top">A preview image, app name, short description, app type, Digital Worker count, and entity count.</td><td valign="top">Helps business users understand the purpose and scope of an app before opening it.</td></tr><tr><td valign="top">Card actions</td><td valign="top">Options to open the app in Application Builder, launch it in App Hub, or manage it.</td><td valign="top">Lets users move directly from discovering an app to using or refining it.</td></tr></tbody></table>

## Creating an Application

New applications are created from the New Application dialog. Users choose the ontology context the application should be built on, such as a predefined, Digital Worker-specific ontology or a custom schema, and give the application a name and description before opening the builder.

For advanced users, the dialog also offers a view of the ontology JSON. This is the compact ontology brief the builder uses to generate the application. It can be reviewed, copied to share with others, or adjusted for the current builder session. Most business users can continue without editing it, but the option supports technical validation when it is needed.

## The Builder Experience

Application Builder is an interactive workspace for shaping an application. Users describe what they want, review the result, confirm it is grounded in the right business context, and publish when it is ready.

* **Conversational refinement:** Changes are requested in plain language rather than by editing the application directly. Example suggestions help users give useful instructions, such as adding queues, approval paths, or confirmation statuses.
* **Preview mode:** The application can be reviewed as a finished, business-facing experience before it is published.
* **Ontology mode:** The related Digital Worker and entity context can be inspected, so teams can confirm the application is using the right business foundation.
* **Publishing control:** Publishing is a deliberate step after review.
* **Clear controls:** Build, launch, expand, and close controls are kept separate, making it easy to move between designing, validating, and running the application.

## Typical Usage Scenario

A team has a process capability in place and needs a clearer application experience for the business users who rely on it. The team opens the crew’s Applications workspace and reviews the available application cards. When users need to work with an application, they launch it. When the application needs new screens, flows, or supporting context, the team opens it in Application Builder, describes the changes, reviews the result in Preview, checks the ontology, and publishes.

Because the application layer is grounded in the crew, Digital Worker, entity, and ontology context, the same pattern applies across domains.
