Apple’s “Human Interface Design Guidelines ” documentation assists Developers in producing a great user interface and user experience. In line with Apple’s guidelines, Our Purely CRM development team has produced some guidelines for the folks we work with to ensure that we deliver the best possible user interface and user experience that we can when delivering Microsoft Dynamics 365 CRM, Power Apps, and Portal solutions.

A few highlights …

‍

Here are just a few highlights from our comprehensive, and ever-evolving, interface guidelines:

• When labeling buttons, you should almost always use a verb.
• Buttons should be written using “title case”, not “sentence case”.
• Alerts should be written using “sentence case”, not “title case”.
• Ensure all fields have their descriptions complete so that when you hover over a field it informs the user what the field is used for.
• If you have a drop-down for a “yes/no” response, change the wording from “yes” and “no” to something more descriptive, like “yes, a support contract exists” or “no, a support contract does not exist”.
• Change the theme of your Dynamics 365 solution to match the client’s brand identity, make users feel at home on the platform, and give people a consistent experience.
• Audit the theme you applied to your solution to ensure it works well in both light and dark modes of the operating system.
• Avoid unnecessary references to specific genders when encountered (e.g., any icons you add should remain non-gendered).
• If you do need to know a person’s gender in your solution, be sure to include inclusive options, such as self-identify, non-binary, and decline to state.
• Place required and important fields near a form’s top and left-hand side because people tend to look and read from the top to bottom on the left-hand side first.

Consistency is key.

We are incredibly proud of our team’s internal standards and methodologies for delivering customer solutions. We have always been able to raise the bar over time. We are not only committed to delivering solutions that meet our clients’ needs, but we are also committed to improving our craft (i.e., software engineering).

Happy Engineering Everyone!