PowerApps Naming Convention

When we have great ideas for an app, we tend to jump directly to app development and throw all our quick thinking to build our ideas. 

Most of the time, this starts to be simple and then eventually cluttered app resources. Even we, creators of the app, will find it cumbersome to trace and read our apps after day one.

It is one of the reasons why we need to follow some standards in naming our app resources.

 

We don't need to have a complex standard. We can start with simple and reusable rules and improve them over time.

 

If you are developing an app with more than one screen, not naming the screens will slow you down. So make sure to set a clear name for each screen, without a shortcut or abbreviation, and don't forget to append “Screen” at the end. Examples are:

 

 

If we do not name our controls, it will soon clutter and make our app complex to maintain our apps. It could lead to frustration when we have to do some updates or fix or when we documentation about it. So follow some simple abbreviations and rules when naming our controls: