Model-driven, canvas or code app? The Power Apps app types with examples
Power Apps offers three kinds of apps. A model-driven app is built from Dataverse tables and has the same interface as Dynamics 365 Sales or Customer Service. A canvas app has freely designed screens and works with many data sources. A code app is a web app written in code by a developer (for example React and TypeScript) that Power Platform hosts and authenticates. This article compares them in a table, shows with examples which fits what, and explains the licensing.
In short
- Model-driven: data-dense, process-driven app on Dataverse, assembled without code; the Dynamics 365 CRM apps are model-driven too.
- Canvas: a free-form UI for a well-defined task, from many data sources, typically on mobile.
- Code app: a web app written in code (React, Vue, etc.) with Power Platform authentication, connectors and governance.
- Middle way: a PCF component, a control written in code inside a model-driven or canvas app.
- Licensing: a Dynamics 365 licence covers extending the licensed app; a code app always requires a premium licence.
Author: Norbert Madarász
, Managing Director and Partner · Updated: 15 November 2026
What are model-driven, canvas and code apps?
Comparison table
| Criterion | Model-driven | Canvas | Code app |
|---|---|---|---|
| Data | Dataverse only | Dataverse, SharePoint, SQL and 1,500+ connectors | the same connectors, called from JavaScript |
| User interface | forms, views and dashboards generated from tables; consistent and responsive | freely designed screens, Power Fx formulas | any web UI (React, Vue, etc.), full control |
| Who builds it? | consultant or key user, with no-code designers | app maker with Power Fx skills | web developer: TypeScript, Node.js, Power Apps CLI |
| Lifecycle (ALM) | solutions, pipelines, Git integration | solutions, pipelines, Git integration | solutions and CI/CD with the CLI; Power Platform Git integration is not supported |
| Mobile | Power Apps mobile app, with offline options | Power Apps mobile app, with offline options | runs in the browser; not supported in Power Apps for Windows |
| Licensing | Dynamics 365 licence to extend the licensed app, otherwise premium | Microsoft 365 with standard connectors, Power Apps Premium with premium ones | always premium (Premium, pay-as-you-go, App Pass) |
Our rule of thumb: if the task is about records, processes and permissions, a model-driven app; if it is one well-defined workflow, often on a phone, a canvas app; if you need a custom UI or existing web code and have a developer for it, a code app.
Examples: which type for which task?
| Task | Recommended type |
|---|---|
| Tracking contracts, assets and warranty cases alongside the CRM | model-driven: new tables in the Dynamics 365 Dataverse, with their own forms and views |
| Employee onboarding with steps and approval | model-driven, with a business process flow |
| Site survey on a phone, with photos and signature | canvas mobile app, saved to a Dataverse table |
| Warehouse issue with barcode scanning, on a kiosk | canvas app |
| Custom-branded internal calculator or configurator | code app with React, when a canvas UI is no longer enough |
| An existing React app that should run with Power Platform authentication and connectors | code app |
The types can be combined in one solution: a Dynamics 365 model-driven app can be paired with a canvas field app on the same Dataverse tables. Power Automate adds the automation to all three: Power Apps or Power Automate?
The middle way: PCF components
The Power Apps component framework (PCF) is a control written in code (TypeScript, HTML, CSS) that works in both model-driven and canvas apps: for example a slider, a map or a custom grid in place of a form field. It is a good choice when most of the app works fine without code and only a few places need a custom UI. According to Microsoft, a component that calls an external service directly from the browser makes the app premium, and PCF components in model-driven apps on Dataverse require Power Apps licences.
Code apps: what to know in 2026
- Status: Microsoft’s documentation no longer marks them as preview, and the official GitHub repository states they are generally available (GA).
- Enablement: an admin turns them on per environment (Power Platform admin center → environment → Settings → Features → Power Apps code apps).
- Licensing: users who run them need Power Apps Premium, pay-as-you-go, an App Pass, or an auto-claimed premium licence.
- Lifecycle: the pa app push command places the app in a solution, so the usual export/import and CI/CD work; Power Platform’s built-in Git integration does not support them. The source code lives in your own Git repository.
- Security: compiled assets are served from a public endpoint without IP-based restriction; access can be limited with Microsoft Entra Conditional Access (block by location).
- Limitations: not supported in Power Apps for Windows, no SharePoint forms integration and no Power Platform Git integration.
- Embedding: can be embedded in a model-driven app or Dynamics 365 via an iframe once an admin allows the host in the Content Security Policy (frame-ancestors).
Which licence does Power Apps need?
What does an implementation partner do?
The first question is not which app type, but where the data lives. If the company uses Dynamics 365, the data is in Dataverse, and most extensions are fastest as a model-driven app or as an extension of the existing app. We suggest a canvas app where people work in the field on phones, and a code app where a custom UI is needed and a developer will maintain it. Then come the licence plan, solutions, test and production environments, pipelines and governance (DLP, owner, service account). That is what we do: Power Apps and Power Automate development, Dynamics 365 consulting, support.
Frequently asked questions
What is the difference between model-driven and canvas apps?
A model-driven app is built from Dataverse tables, most of its UI is determined for you, and it is consistent on every device. A canvas app has freely designed screens and can work with many data sources.
What is a Power Apps code app?
A web app written in code (for example React and TypeScript) and published to Power Platform with the Power Apps CLI. Power Platform handles authentication and hosting, and the app reaches data through 1,500+ connectors.
Are code apps generally available?
Yes. Microsoft’s documentation no longer marks them as preview, and the official GitHub repository states they are generally available. An admin must enable them in the environment.
Which licence does a code app need?
According to Microsoft Learn, users need a Power Apps Premium licence, pay-as-you-go, an App Pass, or an auto-claimed premium licence.
Is Dynamics 365 a model-driven app?
Yes. Dynamics 365 Sales, Customer Service and the other CRM apps are model-driven apps on Dataverse, so they are extended with the same tools.
What is a PCF component?
A control written in code with the Power Apps component framework, usable in both model-driven and canvas apps, for example as a custom UI in place of a form field.
Do code apps run on phones?
They run in the browser. Power Apps for Windows does not support them; Microsoft’s documentation does not cover the mobile app separately, so test before relying on mobile use.
Let’s talk about your project.
Tell us what you are planning and we will get back to you within a few days.
Get in touch