If we take a quick look at designing an actual Model-driven application, you'll notice there's no way of dragging and dropping controls or customizing how it will look. Basically, you can only change a few aspects of the app. For example, if I wanted to add the account data table to the app, all I have to do is select it and now it will show up in the app. From here, I can add different forms, views, charts, dashboards, and business process flows or even add another data table to my application.

Now let's take a look at what a Model-driven application looks like when I actually play one. You can see that everything is very clean and neat, which is of course good. Right now I'm creating a new contact in a default form that was provided, without me even setting anything up. You can see how quick, clean, and easy it is to enter the data in. We'll look more into these Model-driven applications later on in the course, but I hope you can see how when needing to do simple data entry, run a business process or visualize data, Model-driven applications really do make it easy to set up and create. 

Something important to remember as we continue to talk about Model-driven applications is that Model-driven apps can be used for mobile users as well. So, if you know you're going to be building an app for mobile users, don't be so quick to throw out Model-driven applications as an option. Let's now talk about some of the common use cases for Model-driven applications. Some great use cases are when you have a complex business process that you want to enhance and visualize. So, examples of common complex processes that you may consider using a Model-driven app for might be, onboarding a new employee, tracking a new lead or potential customer, or checking out company assets.

In the next lecture, we'll go over the differences between Canvas and Model-driven applications.