Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 38 ยท Concepts and Canvas Apps

Canvas Apps Versus Model-Driven Apps

Compare canvas and model-driven Power Apps in layout control, data requirements, speed of building, mobile use and governance, with a practical decision guide.

The most important early decision in Power Apps is the app type. The two main choices, canvas and model-driven, solve different problems and are built in different ways. Choosing wrongly can mean rebuilding later, so this lesson gives you a clear way to decide.

Canvas apps: you design the screen

In a canvas app you start with an empty screen and place each control exactly where you want it. You connect to one or many data sources and write formulas for behavior. You decide everything: layout, colors, navigation and logic.

Strengths:

  • Full control of the user experience, including phone-first layouts and kiosk screens.
  • Works with 1,000+ data sources and mixes several in one app.
  • Fast for small, focused tools and prototypes.
  • Camera, location, barcode and offline scenarios.

Costs:

  • You build and maintain the UI yourself.
  • Large apps need careful design to stay fast and consistent.

Model-driven apps: the data model drives the UI

A model-driven app is generated from Dataverse design: tables, columns, relationships, forms, views, charts, dashboards and business process flows. You choose which components appear in a site map (the navigation), and the platform renders a consistent, responsive interface.

Strengths:

  • Very fast for data-heavy, process-driven work such as case management or CRM.
  • Consistent look, built-in search, filters, grids, charts and Excel export.
  • Security roles and business rules apply automatically.
  • Works on web and mobile with the same definition.

Costs:

  • Requires Dataverse.
  • Limited layout freedom; you configure rather than design.

Side by side

Question Canvas Model-driven
Start from A screen A data model
Layout Free-form Generated from forms and views
Data Any connector Dataverse
Logic Power Fx in controls Business rules, process flows, plug-ins, Power Fx commands
Best for Task apps, field tools, custom UX CRM-like and case-management apps
Typical build time for a data app Medium Short

Many organizations use both against the same Dataverse tables: a model-driven app for back-office staff and a canvas app for field workers.

flowchart TD
  Q1{"Need Dataverse relationships and lots of forms?"} -->|Yes| Q2{"Need a very custom layout?"}
  Q1 -->|No| C["Canvas app"]
  Q2 -->|Yes| C
  Q2 -->|No| M["Model-driven app"]

A first-pass decision path; exceptions are common.

A decision helper

The stand-in below scores a requirement list. It is only a classroom model of the reasoning, not an official rule.

JS Stand-in: suggest an app type

Press Run (or Ctrl + Enter) to see the console output here.

No output.

How each is built

Canvas: maker portal, Create, Blank canvas app, opens Power Apps Studio. You insert controls and set properties.

Model-driven: maker portal, Create, Start with a Dataverse table or Blank app, Model-driven, which opens the app designer. You add pages (tables, dashboards, custom pages), arrange navigation and save. Forms and views are edited in separate designers. A custom page is a canvas-style page embedded inside a model-driven app, giving you the best of both.

The stand-in below shows the "inventory" idea: an app composed of components, as the model-driven designer presents it.

JS Stand-in: a model-driven app is a list of components

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Rules of thumb

  • Need pixel-perfect UI, camera, or several data sources? Canvas.
  • Need a full CRM-like workflow on Dataverse? Model-driven.
  • Need both? Share one data model and build two apps, or use custom pages.
  • Not sure? Prototype the main screen in each; the ten-minute test usually decides.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which app type always requires Dataverse?

    Model-driven apps are generated from Dataverse tables, forms and views.
  2. 2. You need a phone-first inspection tool with a camera and free-form layout. Which fits best?

    Canvas apps give full layout control and device features.
  3. 3. What is a custom page?

    Custom pages let you add free-form canvas screens to a model-driven app.
  4. 4. Which components make up a model-driven app's interface?

    The platform renders these configured components.

Summary

  • Canvas apps: free-form design, any data source, Power Fx logic.
  • Model-driven apps: generated from a Dataverse model with forms, views and process flows.
  • Both can share one data model; custom pages blend the two.
  • Decide by layout needs, data needs and how much standard CRM-style UI you want.

Next: Anatomy of a canvas app