5.1 Canvas Apps: Use Cases & Capabilities

Canvas Apps: Use Cases & Capabilities

Quick Answer: A canvas app is built from a blank canvas rather than from an existing data model, giving the maker full, pixel-level control over layout and design. Canvas apps connect to 1,000+ data sources through connectors and use Power Fx, a low-code formula language similar to Excel, to add logic. They're the right tool when the UI needs to be highly customized or the app needs to pull data from several unrelated sources.

Power Apps offers two primary app types on the PL-900 exam: canvas apps and model-driven apps. This section focuses on canvas apps — what they are, how they're built, and when a maker should choose them over the alternative.

What Is a Canvas App?

A canvas app begins as an empty design surface, much like a blank slide in PowerPoint. The maker drags and drops controls onto screens, arranges them exactly where they want, and wires up behavior using formulas. There's no requirement to start from a predefined data model — the maker decides the look and feel first, then connects the data.

This blank-canvas approach is what distinguishes canvas apps from model-driven apps (covered in the next section), which are automatically generated from a Dataverse data model. Canvas apps trade some of that automatic structure for freedom of design.

Building Blocks of a Canvas App

Every canvas app is assembled from a small set of core elements:

• Screens — individual pages the user navigates between, similar to slides or app views
• Controls — buttons, labels, text inputs, forms, galleries, images, icons, and media players placed on a screen
• Data sources — connections to external systems (Dataverse tables, SharePoint lists, SQL databases, and more) that supply the app with records
• Power Fx formulas — the logic layer that responds to user actions, validates input, and manipulates data

Makers build and edit all of this inside Power Apps Studio, the maker environment where screens are designed, controls are configured through a properties pane, and formulas are written in a formula bar.

Connecting to Data: 1,000+ Connectors

One of the biggest strengths of a canvas app is how broadly it can connect to data. Power Apps ships with more than 1,000 connectors, which fall into a few broad categories:

A single canvas app can combine several of these connectors at once — for example, reading customer records from Dataverse, pulling inventory numbers from SQL Server, and sending a confirmation through Outlook, all inside the same app and the same screen.

Power Fx: The Formula Language

Canvas apps use Power Fx, a declarative, low-code language that deliberately borrows its syntax from Excel formulas. If a maker already knows how to write a SUM() or IF() formula in Excel, Power Fx will feel familiar. Common uses of Power Fx in a canvas app include:

• Filtering and sorting records displayed in a gallery (Filter, Sort, Search)
• Creating, updating, or removing records (Patch, Collect, Remove)
• Controlling what a user sees based on conditions (If, Switch, Visible property)
• Navigating between screens (Navigate)

Because Power Fx is a formula language rather than a full programming language, it's accessible to citizen developers and business users without a traditional coding background — while still being powerful enough to express real business logic.

Screens, Galleries & Layout Options

Canvas apps typically start from a blank screen, a layout template, or an existing image/Figma design that Power Apps can convert into a starting layout. Within a screen, galleries are one of the most heavily used controls — they repeat a layout (a card, a row, an image-and-text pair) once for every record in a data source, so a maker can display a scrollable list of customers, inventory items, or tasks without building each row by hand. Common gallery layouts include blank, title-only, and title-and-subtitle formats, all of which can be customized further with additional controls.

Canvas apps can also target different form factors and hosting contexts: a phone layout app optimized for a single-handed mobile experience, a tablet layout app designed for a wider screen, and apps embedded directly inside Microsoft Teams so users never have to leave their collaboration tool to complete a task.

Best Use Cases for Canvas Apps

Canvas apps shine when:

1. The user interface must be highly customized or branded — a specific look and feel matters more than automatic structure.
2. The app is task-specific and mobile-first — for example, a field inspection app used on a phone with a camera control.
3. Data comes from multiple, disparate sources — combining SharePoint, SQL, and a third-party API in one experience.
4. Rapid prototyping is the goal — a small team wants to stand up a working app quickly without first designing a full Dataverse data model.
5. The app needs to live inside Teams — surfacing a lightweight tool directly where users already collaborate.

Exam Tip

PL-900 questions frequently describe a scenario and ask which app type fits best. If the scenario emphasizes a custom, pixel-perfect design or connecting to many different data sources, the answer is a canvas app. If it emphasizes a structured, table-driven business process, that points toward a model-driven app instead — the subject of the next section.