Before we start developing an application, it's important to know a set of good practices for developing with Power Apps. The way we organize the code, controls and screens, how we work as a team with other developers, as well as evaluating performance issues and managing errors are very important and make the development process easier.

In particular, adopting the good practices we will see below will be useful to developers in the following dimensions:

• Simplicity: if a solution can be simple, it should be simple. Unnecessary complexity is a mistake to avoid.
• Readability: other developers will be interested in knowing the application's code and organization.
• Maintainability: the solution must be easy to keep running without technical problems and with a minimum of maintenance work.
• Ease of implementation: it should be easy to put the solution into production and share it with other users.
• Performance: the solution must be fast to run, free of hidden errors or potential delegation problems.
• Accessibility: the solution must be accessible to everyone, including those with physical limitations.

General naming conventions

CamelCase

You should use CamelCase for controls and variables. CamelCase starts with a lowercase prefix, removes all spaces from object or variable names and capitalizes the first letter of each word after the first. For example, a text input control could be called txtUserEmailAddress.

PascalCase

You should use PascalCase for data sources. PascalCase is sometimes referred to as "upper CamelCase". Like CamelCase, it removes all spaces and capitalizes the first letter of words. However, unlike CamelCase, PascalCase also capitalizes the first word. For example, a common data source in PowerApps is the Office365 Users API, which can be called by Office365Users in the code.