Develop an app in code

Use the Code Editor when your app needs custom source, components, and routing. The hosted developer workspace combines editing, preview, build output, and source control where configured.

Start the workspace#

Open Web Apps → Go to Code Editor, select the app, and start its Build environment. Check the current app, developer, branch, and preview target before changing files.

Apps connected to Git provide a persistent workspace per linked developer. Workflows, sandbox data, and app settings remain shared. Apps without Git use a shared workspace with explicit handover.

Work with source control#

1. Open Source control and inspect the current branch and commit.
2. Create a feature branch if needed; a new workspace does not automatically invent one.
3. Edit and preview your changes.
4. Review changed files, select the intended files, and Save and commit.
5. Fetch, push, or update from origin through the explicit controls.

Switching a dirty branch requires saving its draft or committing first. Branch operations can stop preview/editor compute; restart the environment afterward. Updates from origin require a clean branch and fast-forward safely. Resolve merges through your repository workflow.

Create a release from a commit#

For connected Git apps, Changes → Create release from commit uses a clean committed app tree. Production candidates must come from the configured production release branch. The candidate records an exact source snapshot; later edits do not alter it.

A local commit and a successful push are different events. Review origin status and your team's repository process, but do not assume pushing alone publishes the app.

Handle conflicts#

If a release or source update reports that the reviewed revision changed, refresh the state and inspect the new differences. Preserve your draft and resolve the conflict explicitly rather than retrying an outdated write.

Continue with SDK integration and release review.