In February 2026, Microsoft announced general availability for Power Apps Code Apps. The silence in the Polish Power Platform community was telling — no article, no official discussion. And yet this feature changes the rules of the game more than anything in Power Apps in years.
The title question is not rhetorical. As reported from the Power Platform Community Conference in October 2025, Charles Lamanna declared — according to MVPs and attendees — that “low code, as we know it, is dead.” MVP Keith Atherton cited this statement as a bold declaration, not a careless remark. MVP Dian Taylor called it a “cold shower” for the community, forcing a shift from “how do I build this?” to “what do I actually want to achieve?”
And here is where the problem starts. Code Apps is not just another update to Power Apps Studio. The question “are you a maker or a developer?” is no longer academic.
What You Actually Get with Code Apps
Technically: Code Apps is a standalone SPA (Single Page Application) that you write locally in VS Code, compile, and push to your Power Platform environment using pac code push. The application is then hosted and served by Power Platform — you do not need Azure App Service, Storage, or a CDN.
The tech stack: React + TypeScript (default), Vite as bundler, Tailwind CSS, TanStack Query for async state management, React Router, Fluent UI v9. Vue and other SPA frameworks are also supported. This is not “Power Apps with a pro-code label.” This is a fully-fledged web application.
The killer feature — and this is the heart of the matter: through the @microsoft/power-apps npm package, you have direct access to over 1500 Power Platform connectors from JavaScript. No writing auth, no token management, no building your own API proxy. Microsoft Entra (Azure AD) is handled by the Power Apps host — you do not write that code.
This is exactly what you do not have in a pure Azure Static Web Apps application. There, every connector, every authentication, every external service connection is manual work. Here you get it out of the box.
On top of that: governance. DLP policies, Conditional Access, App Quarantine, sharing limits — everything works exactly as in Canvas Apps. If your organization has Managed Environments configured, Code Apps uses them automatically.
One honest downside — ALM. Code Apps does not support Power Platform Git integration based on solutions. The normal workflow is a separate pac code push from the CLI. For someone used to full CI/CD in Azure DevOps, this is not a problem — you know how to handle it. For someone who lives in Power Platform solutions and Managed Environments pipelines — this is a real gap in the ecosystem. Microsoft knows this and did not fix it before GA. Worth accepting without illusions.
Licensing: Power Apps Premium for end users. There is no separate Code Apps license — it rides on the same tier as Canvas Apps Premium. Managed Environments costs are additional if you do not already have them in your organization.
When Code Apps Wins, When It Loses
Code Apps vs Canvas Apps
Canvas Apps win when: you have citizen developers or makers without TypeScript, you are building a quick prototype, you want business users to independently modify the app without involving a developer. Power Fx is accessible to business analysts. Time to MVP can be radically shorter.
Code Apps wins when: you need advanced UI state management, you have complex front-end logic that cannot be expressed elegantly through Power Fx, you work with a TypeScript/React team, you have WCAG 2.1 AA accessibility requirements, or your application grows to a scale where “spaghetti formulas” in Canvas become a maintenance problem. Wyatt MVP wrote it plainly: “Nothing of scale has ever been made vibe coding.”
Code Apps vs Azure Static Web Apps / App Service
Azure-native wins when: you do not have budget for Power Apps Premium licenses for end users, your stack is multi-cloud or non-Microsoft, you need full infrastructure control (custom domain, WAF, CDN layer, geo-distribution), or your organization is not in the Power Platform ecosystem at all.
Code Apps wins when: you are already in Power Platform, you have Premium licenses, your team knows Power Platform connectors, and you want to avoid manually building auth + integrations with each service separately. 1500+ connectors ready to use is a significant time saving in enterprise scenarios, where integrations with SAP, ServiceNow, Salesforce, and dozens of other systems would otherwise be tedious, manual work.
PCF vs Code Apps — An Open Question
Power Apps Component Framework has existed since 2019 and is used to build reusable components embedded in Canvas Apps or Model-driven Apps. Code Apps is a standalone SPA — full ownership of the application, not a component contribution. That is the key architectural boundary.
But Microsoft has not published a clear document defining where PCF ends and Code Apps begins. GitHub Discussion #679 in the powerplatform-build-tools repository, with over 21 upvotes on the critique, shows that PCF developers feel left without answers. Microsoft’s response was evasive. If you have PCF investments — treat this area as an open problem to monitor, not a resolved question.
Community Tension — and Why It Matters
You cannot write about Code Apps without addressing what is happening in the Power Platform community. Because there is no consensus there.
Thomas Sandsør on CRMKeeper wrote without pulling punches that Canvas Apps are becoming “the VHS tapes of Power Platform — nostalgic, clunky, doomed to fade” and that “we are all pro-developers now.” A strong, deliberately provocative thesis. Charles Sexton of charlessexton.com went a similar route — arguing that the barriers to writing code have collapsed with AI, so a maker should simply start writing TypeScript.
But David Wyatt, an MVP with real-world experience, frames it differently. He writes about two paths — happy path and unhappy path — and openly acknowledges that current skilled makers may feel marginalized. Wyatt also points to something that rarely appears in the pro-code enthusiasm: “Nothing of scale has ever been made vibe coding.” In other words — dropping TypeScript into Power Platform does not automatically turn an organization into a shop with mature software development practices.
If you are a maker who has spent the last few years building Canvas Apps for the business and solving real problems — this is not a moment to panic. It is a moment to evaluate: what applications do I build, does their complexity justify a pro-code stack, and does my organization have appetite for that shift.
Worth noting: April Dunnam — Principal Cloud Advocate at Microsoft and the voice of Power Platform Developer Advocacy — has not yet published any material on Code Apps. Her work focuses on AI and low-code for practical use. This absence in a topic Microsoft is promoting as a breakthrough is itself a signal. Either Code Apps is not addressed to her maker audience, or Microsoft is consciously not pushing too hard on this topic toward the low-code community.
What This Means for You — Specifically
Solution Architect: Code Apps is a new card in your hand at design time. If a project requires a custom UI with access to the Power Platform ecosystem and you have TypeScript/React on the team — this is a better answer than a Canvas App extended with custom PCF. But the ALM gap is a real blocker in environments with rigorous release management — price this into your project scope.
Power Platform Consultant: Your clients will start asking about Code Apps in 6-12 months. Better to have your own view before they ask. The scenarios where it wins are not edge cases — they represent a significant portion of enterprise deployments.
Maker / Low-Code Developer: You do not need to drop everything today and learn React. Canvas Apps are not disappearing. But if you are building increasingly complex applications and regularly hitting Canvas limits — Code Apps is a natural evolution path, not a leap into the unknown.
Pro-Code Developer (.NET, TypeScript, React): Power Platform is no longer what you thought it was — an environment for “non-programmers.” Code Apps gives you familiar tools, access to a massive connector library, and governance managed by the platform. Premium licensing is the only threshold. Worth calculating whether this is cheaper than manually building integrations in Azure-native for a typical enterprise scenario.
Wondering whether Code Apps fits your scenario? Let’s talk.