The design decision
Both approaches belong to Power Apps. A canvas app gives the maker control over layout and control properties, with Power Fx formulas defining behavior. It can use Dataverse or other supported data sources. A model-driven app requires Dataverse and assembles components such as forms and views around its tables and relationships.
| Question | Canvas app | Model-driven app |
|---|---|---|
| What leads the design? | A task-specific interface | The Dataverse data model and components |
| How is record navigation arranged? | The maker designs it | Defined relationships support navigation |
| Who controls the layout? | The maker builds the screen | Components determine much of the layout |
Dataverse is available to canvas apps too. Using it does not make the app model-driven.
A maintenance case
The fictional Rowan Shuttle workshop needs two ways to handle repairs. A technician records a quick estimate on a small screen. A coordinator reviews repairs alongside sites, equipment and prior visits.
For the technician, consider a canvas screen containing the few controls needed for that task. The maker still has to design a usable narrow layout, focus order and accessible labels. A small screen alone does not make the app easy to use. Custom canvas design also costs maintenance time: a field change can require reviewing dependent formulas and controls across screens.
For the coordinator, consider a model-driven app if the records live in Dataverse and standard forms, related-record navigation and review views fit the job. Begin by defining the Site and Repair relationship.
A similar site name is not a relationship key.
This is a design proposal for a fictional case, not a rule that every intake must be canvas or every review must be model-driven. A real choice also depends on the existing data, required interactions, access model and licensing.
Checks before adoption
Try a repair whose site is missing and another whose site has a similar name. Confirm which fields the reviewer can edit and how a failed save appears. For canvas work, also test the query population and connector-specific delegation limits; a gallery can look correct while omitting a record.
Model-driven components supply established responsive and accessibility behavior, but the finished app and its customizations still need testing. A shared form does not establish that every user has the same data privileges.
Practice scope
The Power Apps course models selected views, relationships and required-field rules locally. It does not create a Dataverse environment or reproduce the full model-driven designer. Its canvas workspace uses the official Power Fx interpreter with a disclosed local behavior layer.
Continue with data sources or gallery queries. Power Apps versus Power Automate covers the separate choice between an interactive app and a workflow.