Power Apps Code Apps - What Pro Developers Actually Need to Know

Power Apps has always had an awkward relationship with professional developers. You could build PCF components, sure - but you were still a guest in a low-code house. That just changed.

Code Apps went GA in February 2026. You can now build a full React or Vue app in VS Code, push it to Power Platform with one command, and it becomes a governed enterprise asset - same DLP, conditional access, and sharing policies as any canvas app.

That’s a big deal. But it’s also not what the marketing makes it sound like. Let me break down what this actually means in practice.

What Code Apps Are (and Aren’t)

A Code App is a custom web application built with any JavaScript framework - React, Vue, Angular, Svelte, whatever - that runs inside Power Platform as a managed app.

Code Apps vs Everything Else in Power Platform

This is where most people get confused. Power Platform now has four ways to build apps:

How It Actually Works

Here’s what the connector API looks like in practice:

import { useConnector } from '@microsoft/power-apps';

// Call a Power Platform connector from your React component
const results = await useConnector('sharepointonline')
  .getItems({ dataset: 'mylist' });

The Real Value Proposition

Let me be direct about who this is for:

It’s for organizations that have pro developers AND Power Platform. If you’re a React developer in an enterprise that runs Power Platform, this gives you a place to deploy internal tools without setting up your own infrastructure. No Azure App Service, no CI/CD pipeline, no SSL certificates - just push and it’s live, governed, and authenticated.

It’s NOT for replacing canvas apps. If a citizen developer can build it with canvas apps, that’s still the right choice. Code Apps exist for the cases where low-code hits its ceiling - complex UIs, custom charting, integration-heavy apps where Power Fx becomes painful.

The governance angle is the real sell to IT. Right now, many organizations have developers building internal React apps deployed on random Azure subscriptions with no oversight. Code Apps bring those apps under the Power Platform umbrella - same admin center, same DLP policies, same audit trail. That’s compelling for enterprise IT.

What They Don’t Tell You

A few things the announcement blog post glosses over:

No mobile means no field workers. If your use case involves frontline workers on phones or tablets - warehouse, retail, field service - Code Apps are off the table. You’re back to canvas apps or a custom mobile solution.

The Per App plan is gone. Microsoft retired the Per App plan in January 2026. So you can’t do the “$10/user/app” thing anymore. It’s Premium ($20/user/month for unlimited apps) or Pay-As-You-Go ($10/active user/app/month). For Code Apps specifically, that Pay-As-You-Go option might make sense for small user bases.

Git integration isn’t there. For a feature aimed at pro developers, the lack of Power Platform Git integration is a head-scratcher. You’ll manage your source code in Git yourself (which you’d do anyway), but the Power Platform deployment side doesn’t connect to your repo.

My Take: Worth Watching, Not Worth Rushing

Code Apps solve a real problem - the gap between “this is too complex for canvas apps” and “let me spin up a whole Azure infrastructure.” That gap is real, and plenty of organizations fall into it.

But the v1 limitations are significant. No mobile, no Git integration, and the licensing math makes it hard to justify for large user bases when alternatives exist.

The feature will get better - mobile support and Git integration are almost certainly coming. For now, it’s a solid v1 for a specific use case, not a universal solution.

---

Building PCF controls instead of Code Apps? Check out Field Audit History - a free open-source PCF control that puts audit data right next to the field. VP365.ai covers Power Platform for practitioners who ship.