Welcome to the channel dedicated to #PowerBIDesign and #DAX tutorials! Join us as we explore the world of data visualization, guiding you through the process of creating stunning dashboards
Power Apps Code Apps let developers build React or Vue applications and run them in Power Apps, using Power Platform connections, sign-in, and governance. They are aimed at developers and makers who want more control over the interface than a canvas app provides. Power BI Professionals demonstrates a Code App workflow using Claude Code to create a team task board, connect it to SharePoint, and publish it.
A Code App is a web application built with a framework such as React or Vue and run as an app in Power Apps. The key difference from building a standalone web app is that the Power Platform supplies connections and platform-level management for the app. Microsoft describes Code Apps as Power Platform assets governed in their environment.
This approach can suit interfaces that are awkward to build with canvas controls, such as a drag-and-drop board or an experience based on an organization’s web component library. It does not remove the need to understand and review code. Instead, a coding agent can help write and revise the app while the maker or developer remains responsible for checking the result.
In the example, the task board has To do, Doing, and Done columns, with cards that include an owner and due date. Claude Code builds the React interface, and the task data comes from a SharePoint list. That example illustrates the workflow; it does not establish that every design or data source is suitable for Code Apps.
Code Apps are for people who want a code-first web development workflow inside Power Apps. The demonstration contrasts them with canvas apps: if you are comfortable with Power Fx and canvas app design, a canvas app may be the better fit. Code Apps may be more relevant when a custom interface or framework-based project is the priority.
The demonstrated setup includes Node.js, a code editor, Claude Code, an environment with Code Apps enabled, and Microsoft’s Power Platform skills marketplace plugin. The transcript says an administrator must enable Code Apps in an environment that does not support them. It does not provide an exact menu path for that environment setting.
The transcript cites community guidance for a Power Apps Premium license for users, but explicitly advises checking licensing with the organization’s licensing owner. The official documentation cited here does not establish licensing terms in the material provided, so confirm the requirements before deployment. The transcript describes desktop-browser use and says mobile support is not available; check current Microsoft documentation for changes.
Claude Code is the coding assistant in this workflow, not the Power Apps runtime or the source of the platform’s governance. Before building, the creator installs Microsoft’s plugin so the agent can follow Code Apps-specific instructions. The plugin repository and architecture documentation are listed in Sources.
The project includes a power.config.json file containing connection and publishing details, according to the architecture documentation cited in the transcript. The transcript also cautions that publishing commands vary across versions: it identifies pac code push as an earlier command and says newer guidance uses an npm-based command. Consult the current documentation for the command that applies to your setup rather than copying an unverified command.
For related coverage of the wider product, see our Power Apps resources.
The demonstrated approach still requires a working development environment and familiarity with ordinary web project issues. The transcript mentions build errors, package versions, command-line tool versions, and environment configuration as potential hurdles. Claude may help interpret errors, but the workflow does not make those issues disappear.
The video says Code Apps run in desktop browsers, are not supported in the Power Apps mobile app, and cannot be embedded inside a canvas app as a component. These constraints matter if users need mobile access or if the desired design is a Code App embedded in an existing canvas experience. The app is presented as its own Power Apps app instead.
Security and review remain the team's responsibility. The demonstration advises keeping passwords and API keys out of React source code and using platform connections for data access. It also recommends that someone on the team be able to read the code, even when Claude writes much of it.
Licensing details, mobile support, and the exact publishing command should be verified against current Microsoft guidance; the transcript's licensing and mobile statements rely on community sources. The material also does not specify regional availability or a complete set of supported frameworks and connectors. The official sources below cover the feature update, architecture, code-app repository, and plugin repository.
The demonstrated setup uses a Code Apps-enabled environment, Node.js, a code editor, Claude Code, and Microsoft’s Power Platform skills plugin. The transcript also says users may need Power Apps Premium; confirm licensing with your organization.
The demonstration describes Code Apps as desktop-browser apps and says mobile support is not available. The material does not confirm whether that limitation has changed, so check current Microsoft documentation.
The demonstration says a Code App cannot be dropped into a canvas app as a component. It is published as its own app.
The transcript says an earlier workflow used pac code push and that newer guidance uses an npm-based command. It notes that commands vary by version, so check the current documentation for your setup.