This article pretends to be a guideline of best practices when designing apps for GeneXus ecosystem. Developers will appreciate this!
Avoid default layer naming. Instead, describe what it is representing.
| Do |
 |
| Don't |
 |
Also, avoid extremely large names or names with non-alphanumeric characters (starting always with alphabetical characters).
Group everything that should be together. A group will represent a table container for those controls you had defined.
| Do |
 |
| Don't |
 |
If the content you place in your design does not change, use Static convention.
| Do |
 |
| Don't |
 |
Avoid defining the appearance of each element in your design. Instead, try to define Layer or Text Styles for reusing them on multiple elements.
| Do |
 |
| Don't |
 |
Avoid making multiple copies of a group of elements in different artboards. Instead, conceptualize your groups and define symbols for them which should be overridden when it is required.
| Do |
Where the symbol defined by Button Confirm is as follows:
. |
| Don't |
 |
Labels for an user input should be defined by the Static convention. If you have a complex control (e.g. radio-button), the label must be defined outside the group that contains the control drawing itself.
| Do |
 |
| Don't |
 |
| Generators |
.NET, .NET Core, Java, Android, Apple , Angular |
|