PowerApps development can be done using any of the below methodologies
- Canvas Apps
- Model Driven Apps
Let us understand both of these methodologies one by one
Canvas Apps
Designer has complete control over app layout in canvas types of apps. We can develop apps to run on SharePoint, PowerBI, Dynamics 365, Common data service for Apps. PowerApps provides various template and sample data to create apps. We can use these templates for quick understanding of app development, see how the data binding is done, how the UI controls are used and how the application flow is developed. Once we are through with this understanding, we can modify these templates as per business requirements.
PowerApps makes our life easy as we can develop apps automatically from below data sources.
Once the default app is ready, it can be further customized to change the way the data
is displayed, the way it should be sorted , which data to be displayed etc.
Going further we can even develop apps from scratch and implement the way you think / imagine.
These apps can run in various tabs, desktops and phones.
The Apps can be shared with other users and then they can also run these Apps.
Model Driven Apps
Unlike the canvas apps, where designer has complete control over the app layout, Model driven apps layout is completely dependent on the controls you put on the screen.
Model-driven app design provides the following benefits:
- Rich component-focused no-code design environments
- Create complex responsive apps with a similar UI across a variety of devices from desktop to mobile
- Since the UI is based on the Dynamics 365 CE user interface, if you are familiar with Dynamics 365 CE, its very easy for you to develop apps in PowerApps
- Your app can be distributed as a solution to required users/enviornments
At a fundamental level, model driven apps consist of three main components as mentioned below
- Modeling business data
- Defining business processes
- Composing the app
Modeling business data
To model business data you determine what data your app will need and how that data will relate to other data. Model-driven design uses a metadata-driven architecture so that designers can customize the application without writing code.
This means you can can create the entity structure which is closely matching with your organisation business. You can create your entities, add relationships, customize the view and even customize the forms to interact with your data.
Defining business processes
Defining and enforcing consistent business processes is a key aspect of model-driven app design. Consistent processes help make sure your app users focus on their work and not on remembering to perform a set of manual steps. Processes can be simple or complex and often change over time.
This helps the users to follow the standard set of process while they are working on any task. The business process can be defined as per business requirements and can consist of one or more entities. You can define multiple business processes on one entity as well
Composing the model-driven app
After modeling data and defining processes, you build your app by selecting and configuring the components you need using the app designer.
Model-driven apps are based on data, UI, logic and visualizations and consist of below components
| Data | UI | Logic | Visualization |
|
· Forms
· App · Sitemap · View |
|
|
Hope this post helped you to understand two ways to implement PowerApps and you can start creating your apps.
Happy Learning!!
Please click like button if you like my post and mention comments in case you want me to write on something specific or any changes required.
Vrushali's Techno Blog 
There’s definately a lot to know about this topic. I really like all of the points you’ve made.
LikeLike
What are the Advanced use cases of model driven app?
LikeLike