Maquette Power Apps - Identité

How to create applications with Power Apps?

This feedback (REX) on Power Apps developments is simple and straightforward, without frills or philosophical considerations :). This is the one I wish I had found when I first started on Power Apps.

Of course, and as always, you have the right to have a different, even opposite, experience. And that’s good!

Last precision: it is far from being exhaustive.

Do not go directly into development!

Create a 1: 1 mock-up of the expected result.

Make the mockup with pencil, PowerPoint, Visio, Balsamiq, etc. : whatever. The breathtaking capabilities of Microsoft PowerPoint have convinced me for a long time. Sorry Jeff!

The mockup must be complete, detailed and precise. The sequences must be clearly defined: when the user clicks on this button, this happens, and so on.

Beware because changes are expensive once development has started. Indeed, the changes are simple to make but very tedious. This obviously depends on the number of screens involved.

Power Apps Mockup - Weekly Tracking
Power Apps Mockup – Weekly Tracking

Feedback (REX) on Power Apps : Define base values ​​

The base values ​​are the main colors: the main theme and the associated sub-theme (RGBA (62, 96, 170, 1), AliceBlue, etc.)

This is also the chosen font (Arial, etc.), as well as the default size that will be used for the font (14pt, etc.).

Also define the default size of the icons, taking into account that there will be large icons (64x64px, etc.) and small icons (30x30px, etc.).

Optionally, you can also define the color of the gallery headers for the fill and the color of the text. You can also set the default height of the gallery template. Thus, you will have a uniform presentation of the contents.

All of these defaults should be stored in global variables. It probably never happens to you, but sometimes people change their mind :).

Valeurs de base
Valeurs de base

Feedback (REX) on Power Apps : Define a naming plan

Name your controls, variables and collections according to a naming plan.

Indeed, there is no Find / Replace function: manually renaming a variable is tedious and long. It is therefore important to adopt a naming plan from the start.

For example, global variables start with GLB, local variables start with LOC.

Also note that unlike controls, collections and variables do not automatically rename.

You can take inspiration from Microsoft’s document « PowerApps canvas app coding standards and guidelines.pdf« . This document offers simple naming rules (extract):

  • Button: btn
  • Label: lbl
  • Text input: txt
  • Collection: col
  • Gallery: gal
  • Combo box: cmb
  • Shapes (rectangle, circle, … ): shp
  • Drop down lists: drp
  • Date: dte
  • Icon: ico
  • Image: img
  • Timer: tim
  • Html text: htm
  • etc.

In the list above, the first value is the name of the control, followed by the proposed suffix. The suffix comes before the name of the control.

Power Apps Volet Arborescence
Power Apps Volet Arborescence

Feedback (REX) on Power Apps : Check the values ​​and your reasoning

Developing is making assumptions.

Also, add temporary labels to check the validity of the assumptions and to control the intermediate results.

Then, trace the progress of an application (if authorized), in particular with the Patch() function.

Power Apps Trace
Power Apps Trace

You can read a similar article in french https://questcequecest.com/retour-dexperiences-rex-sur-les-developpements-power-apps/

Commentaires

Laisser un commentaire

Votre adresse e-mail ne sera pas publiée. Les champs obligatoires sont indiqués avec *