Coded App projects in Studio Web

Coded app project lifecycle in Studio Web, how Studio Web and the UiPath CLI work together to initialize, develop, push, and publish a coded app inside a solution.

Coded Apps can also be initialized directly inside a Studio Web Solution, alongside RPA workflows, agents, and other project types. Studio Web owns the project's identity, versioning, and publish lifecycle, while the app's source code is written in your local IDE and pushed to Studio Web using the UiPath CLI.

The lifecycle has four stages:

• Initialize — The coded app project is created inside a Studio Web Solution. Studio Web scaffolds the project with a webAppManifest.json file; no source code, template, or dependencies are added at this stage.
• Develop locally — Source is authored in your local project folder using the framework of your choice. There is no pull step: the local source is yours to bring. If the app needs UiPath resources at runtime, a bindings_v2.json file declares them.
• Push — The uip codedapp push command uploads the built files (and, if present, bindings_v2.json) into the Studio Web project. Studio Web registers the resources from bindings_v2.json as part of this step, and the pushed source is available in read-only mode under the project's Source section.
• Publish and deploy — The coded app is published and deployed together with the rest of the Solution.

Remarque :

Once code is pushed to Studio Web, it is displayed in read-only mode inside the browser. Studio Web does not offer a pre-wired template, an in-browser code editor, or a live preview for coded app projects — all authoring happens in your local IDE.

For the full walkthrough — initializing a project, developing locally, declaring bindings, and publishing — refer to the Coded app projects section of the Studio Web user guide.