Microsoft Power Apps

Purpose:

Power Apps is low-code app builder that allows one to quickly build dynamic applications. It has a variety of data connectors, uses logic like Excel, and runs on the web, iOS, and Android devices.

Integrations:

As it is a part of the Microsoft Power Platform, it easily integrates with other Microsoft products like Outlook and Power Automate. There are also third-party integrations such as Google Calendar and Twitter. When designing a solution that uses Power Apps, make sure to look at the connector library to know what options are available for your use case.

Pricing:

There is a subscription and a pay-as-you-go plan with a pricing per user or per active app. If the client already has Microsoft licenses, they might already have access to Power Apps. For non-profit clients, discounted pricing can be gotten through TechSoup.

Resources:

The Power Platform is the best place to find answers about errors or questions about Power Apps. There also several blogs with detailed tutorials like matthewdevaney.com and sharepains.com but a google search with the exact error or question will bring up useful videos and webpages. For questions about pricing, you can contact Power Apps sales through chat, call, and email.

Important Development Notes:

• When creating an application for the first time, make sure to use a general admin account that the client has access to. This will prevent issues that could develop when your personal account no longer has access to the system.
• To make sure that changes are not overridden, only one person can edit the Power Apps application at a time. To give someone else access, the tab with Power Apps must be closed.
• When the names of a connection used in a Power Apps e.g., SharePoint Lists, Power Automate flow is edited, the changes are not saved in Power Apps. The old name will continue to show up.
• If an edit is made to a Power Automate flow used in a Power Apps application, Power Apps does not always register the change. To prevent errors, make a new Power Automate flow and delete the old one whenever changes are being made.
• Be extra careful when using variables across different screens. Make sure you understand where the variable was first initialized as well what screens use and update it. A variable error will persist throughout the application even if a mistake was only made in one screen. To fix these errors, trace back the screens where the variable appears or simply make a new variable.