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

# Write code in the browser IDE

## Overview

Application can be built in Condense is a custom, code‑based unit developed in the built‑in IDE and version‑controlled through Git. Once built and published, an application becomes deployable as a Custom Transform or a Custom Connector (Input or Output) within a workspace pipeline.

Applications help:

* Implement domain‑specific processing or integrations when prebuilt options are insufficient.
* Keep logic close to the data path and governed by workspace roles.
* Maintain traceability through Git commits, image tags, and published versions.
* Standardize development‑to‑deployment through a single, auditable workflow.

## What You Can Do in Applications

### Create, Develop, and Test

* Create an Application from a connected Git repository or start from a template.
* Edit code in the IDE (file explorer + code editor) and commit to Git.
* Configure ENVs (environment variables) for build/runtime.
* Optionally expose HTTP(s)/TCP servers for service testing.
* Use Publish/Subscribe testers to validate I/O against workspace topics.

### Build and Publish

* Build the Application into a container image (image name + tag) with live build logs.
* Publish the Application as:
* Custom Transform (processing component in pipeline), or
* Custom Connector: Input or Output (integration component listed with connectors).

### Operate and Maintain

* View versions (draft and published) with immutable release history.
* Roll back by selecting an earlier published version at deployment time.
* Delete drafts or published Applications (role‑gated; irreversible in Condense).

## Applications Lifecycle

Every Application follows a clear lifecycle, from creation and development to build, publish, deployment, iteration, and eventual deletion. This section outlines each stage and who can perform it.

### 1) Creating an Application

<Info>
  **Who can create**: Workspace Admins, Maintainers, Developers
</Info>

Steps to follow while creating an application:

1. Go to Applications → Create Application.

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications1.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=c46a2174fdbc2c43b3c2447c5ec9e816" alt="Applications1" width="2304" height="1366" data-path="images/Applications1.png" />

2. Version Control: Connect a provider (GitHub/GitLab/Bitbucket), then select Repository and Branch.
3. Application Info:
4. Icon (optional)
5. Application Name (unique within workspace)
6. Publish as a custom: Transform, Input Connector, or Output Connector

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications2.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=a9af2e88e5142ee18444350ef3b3cf1e" alt="Applications2" width="2304" height="1304" data-path="images/Applications2.png" />

7. Expiry (draft retention period)
8. Version (e.g., v1, v1.1.0)
9. About (optional description)
10. Click Develop Application to open the IDE.

For field‑by‑field info: see Configuration Parameters → A. Creation (Step 1).

### 2) Develop in the IDE

<Info>
  **Who can edit (drafts)**: Admins, Maintainers, Developers
</Info>

* Navigate/edit code via File Explorer and Code Editor.
* Configure ENVs (build/runtime).
* (Optional) Enable Expose HTTP(s) Server / Expose TCP Server for local testing.
* Validate topic flow with Publish and Subscribe testers.
* Commit and push to the connected repository.

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications3.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=fb1ef767607608d3d64e69396a305346" alt="Applications3" width="2304" height="1373" data-path="images/Applications3.png" />

Capabilities and limits: see Editing an Application and IDE Structure.

### 3) Build the Application

**Who can build:** Admins, Maintainers, Developers

Steps to build an application:

1. Click Build Application.
2. Enter Docker Image Name (registry path) and Tag.
3. Start building and monitor Build Logs; fix errors and rebuild if needed.

<Frame>
  <img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications4-1.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=2c1c8b587b3c288e798f6987665ff33d" alt="Applications4 1" width="2304" height="1315" data-path="images/Applications4-1.png" />
</Frame>

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications5-1.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=74a8f2480dec2bbb5a1223cc5c7c3ac8" alt="Applications5 1" width="2304" height="1291" data-path="images/Applications5-1.png" />

Guidance on naming/registries: Read [Building an Application. ](#building-an-application)

### 4) Publish the Application

Who can publish: Admins, Maintainers

Publish targets:

* Custom Transform → appears in Transforms → Custom.
* Custom Connector (Input/Output) → appears in Connectors → Custom under the respective role.

Steps to publish the application:

1. Click Publish Application.
2. Confirm Publish as a custom type (Transform / Input Connector / Output Connector).
3. Confirm Version and optional release notes.
4. Click Publish.

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications6.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=88f1e9a77b6aebb9a5d490f5a2b8fabd" alt="Applications6" width="2048" height="1214" data-path="images/Applications6.png" />

Versioning is immutable: see [Publishing an Application. ](#publishing-an-application)

### 5) Deploy the Published Artefact (reference)

Deployment happens outside Applications:

* **Transforms**: pipeline editor → Add Transform → Custom → choose app/version → configure ENVs/parameters → Deploy.
* **Connectors**: Connectors → Custom → choose app → select role (Input/Output) → configure ENVs/parameters → Deploy.

Deployment behaviour is covered in the Transforms and Connectors docs.

### 6) Update / Roll Back a Version

To change logic, update code in Applications, rebuild, and publish a new version. In the deployed transform/connector, switch the Version to the new release (or choose an older one to roll back).

Editing deployed parameters happens in the pipeline/connector UI. Editing logic requires a new publish from Applications.

#### Edit application

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications7.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=7b7b9c5deab850b1b09d3f0664c979d7" alt="Applications7" width="2304" height="1292" data-path="images/Applications7.png" />

#### Adding the new version

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications8.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=7d2721aaa5b41bf4d2bbd106dce69cbf" alt="Applications8" width="2304" height="1302" data-path="images/Applications8.png" />

Starting the development of an application involves completing all required steps to build and publish it. After publication, the application appears in the **Transforms** or **Connectors** section, and when deploying a transform or connector in a pipeline, you will be prompted to select the desired version to deploy.

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications9.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=1957e1a1b4a2241da0a48b716a79dd8b" alt="Applications9" width="2304" height="1380" data-path="images/Applications9.png" />

### 7) Deleting an Application

Who can delete: Admins (and Maintainers if policy allows) <br />Warning: Deletion is irreversible. If a published Application is referenced by a transform/connector in a pipeline, update or remove that deployment first to avoid runtime errors.

### Naming Rules

* Allowed: only letters in lowercase
* Length: 3–63 characters.
* Must be unique within the workspace.

### Editing an Application

Who can edit: Admins, Maintainers, Developers

Editable (drafts):

* Source code in the IDE
* ENVs (environment variables)
* Expose HTTP(s)/TCP server toggles
* Description, icon, and version (for drafts)
* Repository/branch (until the first build against a commit)

Non‑editable:

* Application ID
* Creation timestamp

Note: After publishing, logic changes require a new version (edit → build → publish). Deployed components can switch versions without a rebuild.

## IDE Structure

* File Explorer (left): navigate and manage files
* Code Editor (center): code, linting, errors
* ENVs panel (side): runtime configuration, secrets masked
* Test Your Application: Publish and Subscribe testers
* Build Application: opens image name/tag dialogue

## Building an Application

Who can build: Admins, Maintainers, Developers

Steps to build an application:

1. Build Application → enter Docker Image Name and Tag.
2. Monitor Build Logs; on failure, review errors, fix code/ENVs/Dockerfile, and rebuild.

<Info>
  Notes

  * Use a fully qualified image name for external registries.
  * Some registries enforce lowercase tags; prefer lowercase alphanumerics, dots, and dashes.
  * Pass secrets via ENVs; do not bake them into the image.
</Info>

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications10.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=52a45416d8602d5fab519db6f5fb39e0" alt="Applications10" width="2304" height="1302" data-path="images/Applications10.png" />

## Publishing an Application

Who can publish: Admins, Maintainers

Publish Targets

* Custom Transform: listed under Transforms → Custom for pipeline use.
* Custom Connector (Input/Output): listed under Connectors → Custom according to your implementation.

Post‑publish

* Published versions are immutable.
* To change logic, edit → build → publish a new version.
* Deployed components can be switched to a new version from their configuration.

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications11.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=60d4bfda8db767920432a32a8fb86df6" alt="Applications11" width="2304" height="1299" data-path="images/Applications11.png" />

## Deleting an Application

Who can delete: Admins (Maintainers if your policy allows)

Warning

* Irreversible in Condense.
* If referenced by any deployment, update/remove those deployments first.

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications12.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=4e2966cf3bec97babcb21e96f698068c" alt="Applications12" width="2304" height="1297" data-path="images/Applications12.png" />

## Configuration Parameters

A. Creation

| **Field**           | Description                         | Required | **Notes**                                      |
| ------------------- | ----------------------------------- | -------- | ---------------------------------------------- |
| Application Name    | Unique identifier in workspace      | Yes      | 3–63 chars; letters, numbers, -, \_            |
| Publish as a custom | Publish target at release           | Yes      | Transform / Input Connector / Output Connector |
| Version <br />      | Human‑readable version label <br /> | Yes      | e.g., v1, v1.1.2                               |
| Expiry              | Draft retention period              | Yes      | Draft artifacts auto‑cleaned after expiry      |
| About               | Description for operators           | No       | Shown in details and summaries                 |
| Git Provider        | Git Provider                        | Yes      | GitHub / GitLab / Bitbucket                    |
| Repository          | Repository path                     | Yes      | Selected from provider after auth              |
| Branch              | Source branch                       | Yes      | Changeable until first build                   |

<table><thead><tr><th width="137.2265625" align="center">Field</th><th width="162.7109375" align="center">Description</th><th width="126.375" align="center">Required</th><th align="center">Notes</th></tr></thead><tbody><tr><td align="center">Application Name </td><td align="center">Unique identifier in workspace </td><td align="center">Yes </td><td align="center">3–63 chars; letters, numbers, -, \_ </td></tr><tr><td align="center">Publish as a custom </td><td align="center">Publish target at release </td><td align="center">Yes </td><td align="center">Transform / Input Connector / Output Connector </td></tr><tr><td align="center">Version </td><td align="center">Human‑readable version label </td><td align="center">Yes </td><td align="center">e.g., v1, v1.1.2 </td></tr><tr><td align="center">Expiry </td><td align="center">Draft retention period </td><td align="center">Yes </td><td align="center">Draft artifacts auto‑cleaned after expiry </td></tr><tr><td align="center">About </td><td align="center">Description for operators </td><td align="center">No </td><td align="center">Shown in details and summaries </td></tr><tr><td align="center">Git Provider </td><td align="center">Authenticated provider </td><td align="center">Yes </td><td align="center">GitHub / GitLab / Bitbucket </td></tr><tr><td align="center">Repository </td><td align="center">Repository path </td><td align="center">Yes </td><td align="center">Selected from provider after auth </td></tr><tr><td align="center">Branch </td><td align="center">Source branch </td><td align="center">Yes </td><td align="center">Changeable until first build </td></tr></tbody></table>

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications13.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=cbc009f466368e433a73d59d66b27210" alt="Applications13" width="2304" height="1304" data-path="images/Applications13.png" />

## B. Development (Step 2: IDE)

| **Element**           | **Description**                                                               | **Notes**                                                             |
| --------------------- | ----------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| **File Explorer**     | Navigate and edit project files.                                              | Supports multi-file editing.                                          |
| **Code Editor**       | Write and modify application code with inline linting and error highlighting. | Supports committing changes directly to the connected Git repository. |
| **ENVs**              | Configure runtime environment variables.                                      | Supports secrets with masked values.                                  |
| **Expose HTTP(s)**    | Enable an HTTP(S) endpoint for the application.                               | The application must listen on the configured port.                   |
| **Expose TCP**        | Enable a TCP endpoint for the application.                                    | Useful for stream and socket-based applications.                      |
| **Publish**           | Send test messages to a topic.                                                | Configure topic, key/value, message format, and partition.            |
| **Subscribe**         | Consume messages from a topic.                                                | Supports topic, partition, offset, and fetch-size presets.            |
| **Build Application** | Build the application into a container image.                                 | Opens the build dialog to specify the image name and tag.             |

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications14.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=8311e345ae6c03c2d9a8d311e423276e" alt="Applications14" width="2304" height="1373" data-path="images/Applications14.png" />

## C. Build (Step 3)

|     **Field**     |   **Description**   | **Required** |              **Notes**              |
| :---------------: | :-----------------: | :----------: | :---------------------------------: |
| Docker Image Name |  Registry/repo path |      Yes     |   e.g., registry/acme/vehicle-app   |
|        Tag        |      Image tag      |      Yes     |  Align with Version (e.g., v1.0.0)  |
|        Logs       | Build output stream |       —      | Downloadable; success/failure pills |

Summary Pane (left): provider, repo, branch; detected language/runtime; app name/type (Transform/Connector); version; About; configured ENVs (masked); flags for exposed servers.

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications15.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=bd9b082f4df5412d3bd55c2fbe3e19d8" alt="Applications15" width="2304" height="1315" data-path="images/Applications15.png" />

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications16.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=41bf2a000ed394afbff237948dbbc2a1" alt="Applications16" width="2304" height="1291" data-path="images/Applications16.png" />

## D. Publish

|      **Field**      |       **Description**      | **Required** |            **Notes**           |
| :-----------------: | :------------------------: | :----------: | :----------------------------: |
| Publish as a custom | Transform / Connector type |      Yes     | Determines catalog destination |
|       Version       |       Release version      |      Yes     |     Immutable after publish    |
|        Notes        |        Release notes       |      No      |     For operators/reviewers    |

<img src="https://mintcdn.com/zeliot/P380yXoMhFOwPfgF/images/Applications17.png?fit=max&auto=format&n=P380yXoMhFOwPfgF&q=85&s=3552c2f632d177deff62f8522755d1ba" alt="Applications17" width="2304" height="1292" data-path="images/Applications17.png" />

## Roles and Permissions (Applications)

|         Operation        | Admin | Maintainer | Developer | Viewer |
| :----------------------: | :---: | :--------: | :-------: | :----: |
|    Create application    | **✓** |    **✓**   |   **✓**   |  **✕** |
|     Edit code / ENVs     | **✓** |    **✓**   |   **✓**   |  **✕** |
|   Use Publish/Subscribe  | **✓** |    **✓**   |   **✓**   |  **✕** |
|     Build application    | **✓** |    **✓**   |   **✓**   |  **✕** |
|    Publish application   | **✓** |    **✓**   |   **✕**   |  **✕** |
|    Delete application    | **✓** |   **✓\***  |   **✕**   |  **✕** |
|  View applications list  | **✓** |    **✓**   |   **✓**   |  **✓** |
| View application details | **✓** |    **✓**   |   **✓**   |  **✓** |

\* Maintainer deletion depends on your organization’s policy.

### Role descriptions

* Admin: Full lifecycle control and governance.
* Maintainer: Operates lifecycle (develop/build/publish) but not workspace settings.
* Developer: Develops and builds; cannot publish or delete.
* Viewer: Read‑only.

## Monitoring and Audit

* Build Logs: full build output with success/failure indicators.
* Runtime Logs (when deployed): stdout/stderr available via Logger/observability stack.
* Version History: immutable publish records (version, author, timestamp).
* Activity Log: who created, edited, built, published, or deleted the Application.

## Best Practices

* Single responsibility: keep each Application focused for simpler testing and review.
* ENVs over hardcoding: configure ports, credentials, and endpoints via environment variables.
* Stable branches: map branches to stages (dev, staging, main).
* Tag discipline: align Version, image tag, and Git tag/commit for traceability.
* Test early: use Publish/Subscribe testers before builds to catch schema/mapping issues.
* Minimize image size: prefer slim base images for faster builds and deploys.

## Common Pitfalls and How to Avoid Them

* Published artefact not visible for deployment <br />**Cause**: Wrong publication as a custom choice. <br />**Avoidance**: Confirm the Transform vs Input/Output Connector before publishing.
* Unreachable HTTP/TCP during testing <br />**Cause**: Server not exposed or wrong port binding. <br />**Avoidance**: Enable the correct toggle and match the port ENV in code.
* “No messages yet” in Subscribe <br />**Cause**: Topic/partition/offset mismatch or too small a fetch window. <br />**Avoidance**: Use First/Last/Size presets and verify topic + partition.
* Build failures due to missing dependencies <br />**Cause**: Dependencies not in project config. <br />**Avoidance**: Add to dependency file (e.g., requirements.txt) and rebuild.
* Deleting an Application still referenced by deployments <br />**Cause**: Active transform/connector points to this Application. <br />**Avoidance**: Update or remove dependent deployments first.

## Related Links

* [Workspaces](/condense/v2.4.0/condense-guide/condense-core/create-your-workspace.md)
* [Transforms](/condense/v2.4.0/deep-dive/transforms.md)
* [Connectors](/condense/v2.4.0/condense-guide/condense-core/deploy-an-input-connector.md)
* [RBAC](/condense/v2.4.0/condense-guide/condense-console/roles-and-permissions.md)