Microsoft Power Apps Reviews

We are building many tools, like an audit tool or a dashboard for our operations team, where they input values and store them in some bucket. Instead of doing a web-based application, we are using Microsoft Power Apps as a low-code platform. 

We are also developing a single pane of glass for the operations team that navigates multiple systems in the background through Power Automate Flow, gathers information, and displays it in a grid. This combination of both time-saving, ease-of-use applications, and a single pane of glass provides all the required information to work on.

The most valuable features for us are predominantly on the user interface front. It provides ease of development with many modules. The integration with SharePoint is part of the enterprise package, making it cost-effective. This allows our operations team to use existing functionalities without incurring extra costs. We utilize Microsoft Office licensing to take advantage of PowerApps for sixty to seventy percent of its potential, which is very beneficial.

I work with Microsoft Power Apps for multiple solutions. The first one is automating the process by emailing our users. In our company, we receive some Excel files with the email addresses of our users. With Microsoft Power Apps, I create a data flow and define what type of user we have, like if the user is premium or if the user has to pay some charges or not, and based on that, I send different emails to the users. That is one process. The other process we use is Microsoft Power Apps, mostly with Microsoft Power Pages platform, to create a UX.

The tool's most valuable feature stems from the fact that in our company, we spend a lot of time sending emails and get involved in identifying what type of users we have. The most valuable feature of the tool is that, with the budget, we can reduce the time we invest in our various processes.

The one that we currently have is only to SharePoint Online as we want to be able to have analysts be able to maintain data, and we want a graphical user interface, a GUI front end, to do that. Especially if it's interfaced with PowerBI, it allows analysts to have a research tool to identify what data needs to be updated right there, and to then be able to do that through PowerApps is a huge benefit. Right now, we're only able to write back to SharePoint Online.

Right now, it's only write-back to a SharePoint Online list, however, I have proof of concepts. I've got a business case that I'm currently trying to get pushed through. I've got other services within our organization that I need to get buy-in from so that we can get this business case approved and get the funding.

Initially, we used it mainly to wrap up Power BI reports for BetterView, creating straightforwardapps. About a year ago, it evolved into more robust apps for collecting information, particularly for logistics. We developed apps to streamline workflow and gather data for specific operations.

We then built a more advanced app that allowed us to communicate with customers—connecting workflow issues, creating problem reports, and sharing shipment updates via SharePoint, which integrates easily with Microsoft Power Apps.

Power Apps is used mostly locally, within one or two departments. Each app is developed locally, and it’s not used for enterprise-wide purposes. In our organization of about a thousand people, around six developers work with Power Apps. There are likely a couple of hundred users across all apps.

Over time, it became a key part of our operations, and we've developed around three or four apps in total. However, the main use case remains to display Power BI reports. By wrapping reports within Power Apps, we can present them in different formats to create better dashboards, making the process more efficient

We mainly use Power Apps for small applications. Ninety-nine percent of the work is on Internet or intranet solutions, specifically E2E and B2E. These solutions are designed to be developed quickly without being overly complex or requiring high performance or extensive handling of large datasets. In addition to these scenarios, integrating with other platform tools like Power BI and SharePoint enhances the solution. We generally avoid developing for B2C or B2B scenarios due to licensing issues and the nature of those markets.

Power Apps facilitates form creation, application planning, and automation. We have encountered scenarios where automation was crucial, such as managing emails according to SOPs and handling basic ERP tasks like user password changes and role assignments. Power Apps and Power Automate have automated these processes efficiently.

I work in the architecture and construction industry. We use Power Apps to create applications for users to enter updates on our projects. The data collected is linked to SharePoint and then used to update our dashboards. 

We also use Power Apps for site inspection and issue tracking on our construction sites, connecting it with SharePoint for critical use cases.

Power Apps is user-friendly and allows easy application creation without extensive programming experience. It integrates seamlessly with Power Automate for process automation and connects with email, SharePoint, Power BI, and MS Teams, facilitating everyday processes. 

Issue tracking and centralized issue management are significantly enhanced with Power Apps, reducing lengthy data consolidation processes across departments.

It's for building custom apps, which is very similar to APEX. We also use it to build small business applications related to any Microsoft products.

In Power Apps, it's the native integration with Microsoft products. This is definitely the most powerful feature.