> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getvirtualbrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Building Apps

> Translate your firm's methodologies into repeatable workflows with the no-code App builder

The real power of the Use Case Factory is that you're not limited to the catalog. With the no-code builder, anyone who knows the business logic can build an App, translating the firm's methodologies, processes, and frameworks into instructions, no coding required.

If you can write down how the work gets done, you can build the App that does it. Start from **New App** or adapt an existing template, then work across two tabs.

<Frame>
  <iframe style={{ width: '100%', aspectRatio: '16/9' }} src="https://www.youtube.com/embed/B75iPHSkyK0" title="How to build an application in the no-code interface" frameBorder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen />
</Frame>

<Steps>
  <Step title="Set the general settings and user inputs">
    Give the App a name, a description, and an estimated time saved. Then define the user inputs, the questions a colleague answers when they run it: a description, the Brains to use, a document upload, the language, and so on. Mark each input optional or mandatory.

    <Frame caption="General settings: name the App and define the inputs it collects at run time.">
      <img src="https://mintcdn.com/virtualbrain/VZdLXSl7brhQEIEq/images/apps/app-builder-settings.png?fit=max&auto=format&n=VZdLXSl7brhQEIEq&q=85&s=56e834f6adf5ae199e161be77d9f2498" alt="The App builder settings tab with name, description, estimated time saved, and configurable user inputs marked optional or mandatory" width="3024" height="1714" data-path="images/apps/app-builder-settings.png" />
    </Frame>
  </Step>

  <Step title="Define the application blocks">
    An App is a sequence of blocks that run in order. For each block, choose its **Knowledge Source(s)**, which can be user inputs, Brains (or specific files within a Brain), a web search, or the output of earlier blocks, and write its instructions: the prompt. Type `/` to insert a variable.

    <Frame caption="Each block pairs its knowledge sources with the instructions it executes.">
      <img src="https://mintcdn.com/virtualbrain/VZdLXSl7brhQEIEq/images/apps/app-builder-blocks.png?fit=max&auto=format&n=VZdLXSl7brhQEIEq&q=85&s=cf91ab741a6ed881d3cad594ac817fcc" alt="The App builder blocks tab showing a block's knowledge sources, instructions field, and block options" width="3024" height="1714" data-path="images/apps/app-builder-blocks.png" />
    </Frame>
  </Step>

  <Step title="Add review steps where judgment matters">
    Block options let you show the block in the session and add a review step. In **Set up a review step**, write what the reviewer should check. The App then pauses at that block on every run, waiting for a person to confirm the output before the blocks downstream begin.

    <Frame caption="Set up a review step: write what the reviewer should check on every run.">
      <img src="https://mintcdn.com/virtualbrain/VZdLXSl7brhQEIEq/images/apps/app-review-setup.png?fit=max&auto=format&n=VZdLXSl7brhQEIEq&q=85&s=d118fab9e64a3e1cb9440fa4623d6489" alt="The Set up a review step panel where the author writes reviewer instructions for a block" width="2986" height="1700" data-path="images/apps/app-review-setup.png" />
    </Frame>
  </Step>
</Steps>

Add as many blocks as the workflow needs. See [App Blocks](/features/apps/app-blocks) for how a block draws on its sources and what stays fixed between runs.

<Note>
  An App carries its own standards. Whoever runs it brings your firm's [Company Context](/features/personalization/custom-instructions), but not their personal My Instructions, so write anything the workflow must always do into the block's instructions.
</Note>

## Start with the App Creation Assistant

Don't want to design the workflow from a blank page? The **App Creation Assistant** takes you from idea to a buildable blueprint in minutes: describe your goal in a few sentences (the more specific, the better), pick an output language, and optionally attach supporting documents such as an output example or a template.

The assistant then shows how it interpreted your brief so you can correct any ambiguity, proposes the App's name, description, and user inputs, designs the block architecture (viewable as a flowchart of blocks, Brains, and inputs), and writes a prompt for each block. Everything is packaged into an implementation guide: the inputs to define, the Brains to connect, and the title, knowledge sources, and prompt for every block, ready to copy into the builder.

<Frame>
  <iframe style={{ width: '100%', aspectRatio: '16/9' }} src="https://www.youtube.com/embed/C_QE6M_B3MQ" title="The VirtualBrain App Creation Assistant" frameBorder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowFullScreen />
</Frame>

## Related

<CardGroup cols={2}>
  <Card title="Sharing Apps" icon="share-nodes" href="/features/apps/sharing-apps">
    Make your App a capability the whole team runs.
  </Card>

  <Card title="Using Templates" icon="play" href="/features/apps/using-templates">
    Start from one of the 50+ ready-made templates instead.
  </Card>
</CardGroup>
