When you first started learning about Power Apps, you might have heard of, and maybe even seen examples of Canvas applications and/or model-driven applications. They may seem very similar, but how are they different? Let's compare the two different applications.

Canvas applications can connect to multiple data sources, allow for more complete user interface customization, require a little bit more coding and in my opinion, are focused more on solving the unique processes of a business that need to be more customizable. Model-driven applications have limited layout and user interface customization and can only be connected to Dataverse. But they do provide a fast and easy way of automating, enhancing and viewing business processes and data that requires much less code than Canvas apps.

Model-driven applications don't have a drag and drop way of customizing the app but rather offer more of a dashboard where you can select what data you want to show, how you want to show it and of course, more. Truthfully, for both applications, the focus is very similar, but Canvas applications are going to give you more customization while model-driven apps could potentially be built slightly faster and can be a lot less confusing.

As you build both types of applications, you will see perhaps more differences in them. But the basic idea is that Canvas apps are great when you want a really custom experience while model-driven apps are great for visualizing business processes. Both can improve and automate business processes, increase productivity, reduce cost and be used on desktops, tablets and mobile phones. In the next lecture, we'll discuss Power Apps portals.