What is your primary use case for Microsoft Power Apps?

PowerApps is currently the best low-code platform because of Microsoft's investments—not just in low-code development but also in generative AI in order to accelerate development. The Power Platform integrates really well with all the new technologies, including AI. It's maturing fast, though I haven't had the chance to fully compare it with others like Mendix, which has been around for a while. To make a completely informed and unbiased decision on which is better, I'd need more experience with other platforms. But from my perspective, for most customers, it ticks a lot of boxes, especially in terms of rapid development. Power Platform also supports developers when they hit the limits of drag-and-drop features. If you want to build something more native, that’s doable too. Our use cases vary depending on the customer. Because we're a company that helps customers automate processes using Power Platform. Power Platform has a very industry-agnostic nature, meaning it can be applied across various sectors—whether it's healthcare, banking, construction, automotive, or manufacturing. Wherever there are processes still relying on paper, currency, or Excel that need automation, PowerApps is a good fit.

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.

We use Microsoft Power Apps to support some IT processes and for employee evaluation. Sometimes, we use the solution to prepare electronic forms where we cannot use Microsoft Forms. We also use Microsoft Power Apps to prepare small custom applications.

We use the solution for collaboration modules within our company. For example, we use Power Apps to handle requests when investing in projects abroad and needing approval.

We use the solution to implement new Teams apps. Some customers want apps on every mobile phone in their company. This is implemented using Dynamics or SharePoint, with a list of plan data displayed on the mobile phones. Everyone enters the data and plans when holidays or machines, like magnetic resonance scanning machines, are to be used. Everyone enters this data and coordinates using that Blackboard application. It is for enterprise resource planning or HR planning.

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.

The solution is a low-code platform that quickly develops solutions for general business processes. Companies can integrate it with their existing systems, access data flows, and deploy applications within a matter of days or even a couple of days.

We have built a couple of apps ourselves, but mainly, we are building the apps for our customers.

We use the product for sales and customer service features.

We use the solution to create applications. We were getting ideas, fine-tuning, and putting them in different queues that are available to the whole organization.

The solution is used internally in my company.

We are a big global company that is involved in a large volume of setups involving Microsoft solutions like Power Apps, Power BI, and Power Automate for different environments across departments in organizations functioning at a global level. So we are involved in delivering services while focusing on the setup processes for different environments and departments. It helps the people at work since solutions like Power Apps and Power Automate function excellently.

We are using Microsoft Power Apps for data collection and processing for small intergroup business applications for our internal needs.

I had to upload a form, an invoice, specifically, and then using an Azure function, I had to get that form from the Dataverse database and feed it to an Azure form recognizer and write the data back to the Azure Power App.

We use this solution to integrate our apps, and send processed data via the different connectors it provides.

We use this solution to provide a cloud-based platform for our clients to develop, connect, and store data from across the full Microsoft suite.

Power Apps is a tool to create forms and solutions for collecting information from the floor. We have 10 or 15 users at the moment, but we expect to add more.

The primary use case for this solution for us is building in-house applications rather than having to purchase them. We build fairly basic applications and we would rather use Power Apps to deploy them or create them in-house.

My primary use case for Microsoft Power Apps are mostly demos for my customers and in trainings. I am a Microsoft Registered Trainer.

We predominantly use the product for a lot of intake forms. There is a lot of data collection and a lot of intake forms. We use Power Application for validation rather than using spreadsheets. It's good for automation, where we need a data repository of the input, which we get from the resource.

We have a partnership with Microsoft.

We use Microsoft PowerApps for very small use cases. For example, conducting internal surveys, or say some of the key business stakeholders want day-to-day reporting. Using PowerApps, we are creating such reports for those executives. We connected PowerApps to the relational database, which generates the report. Also for contract review and approval of these types of use cases. Those are, in my opinion, very simple use cases. There are no complex rules or decision-making processes, which is why PowerApps was designed.

We had a new requirement from a business in the clinical domain and the business wanted to identify risk at a study or site level. We created an application using PowerApps, which works well as we usually interact with the SQL Server on Azure.

The solution is for rapid application development software. There is a specific environment, in part a platform of PowerApps, in which you can just deploy the solutions and then you share the link with the users and they are able to open them using iPads or mobile devices, or even a computer. We have been working to build a maintenance events app for assets, it's an app to manage and show all the assets that have been working or down for maintenance in an operation, inside one bigger mining company. They have many trucks and many other, let's say, machines in the operation and sometimes they have to put these machines just through a maintenance mode, to see what's happening, or to change some part specifically, or even if the machine is having some kind of issue. That's due to the fact that if it's down, they have to manage how long it's down and what was the part that was the issue, the cause of the issue. They have to change the parts and everything's very costly in terms of money for the company when we have one specific asset that's down. Previously, they were using a board in a room, just to manage all these statuses. Instead of this, now we have one specific app that is working in live modes in almost real-time. Just getting the data from the services and showing it on a big board in PowerApps can show what's happened, what's the status, and what's the reason for the issue. This app allows for adding some comments. It's a collaborative app where many people can just go there and add comments and notes about what's happening with the machine.

We use Microsoft PowerApps for internal business solutions that eliminate the need for Excel workbooks.

We use it as part of our analytics offering. We are basically into analytics. Maybe sometimes we use it to build small apps to instrument the research process. That's what we do.

We are user integrators and partners with Microsoft.

I use it for internal purposes and also to advise our customers.

I'm working for a company that provides services and develops projects for our clients. I am a solution architect and I use Microsoft PowerApps.

We're using it for our business processes. We have applications for expenditure requests, travel requests, and accident reporting. I am using the latest version of the solution.

PowerApps is mostly a front end. It's a form where users can input information, and it gets goes into a database.

I belong to a consulting company that develops applications using PowerApps.

We are into software consulting. We have been developing various solutions and leveraging PowerApps to do it.

We use the solution for making forms for Office 365.

We use the solution as part of Dynamics 365 Online. Within that, we use Power Apps and we've integrated something on the on-prem database. The app is located within Dynamics 365 Online. It draws data from an on-prem data source. We use it to perform certain actions in Teams, so we have Dynamics 365 and Teams integration. We've created an email reader using Power Apps.

We use Microsoft PowerApps to get insight into the business. We use it for BI.

This is a low-code solution that I am using for making applications.

We migrated all the applications to the PowerApps Server and are sending some to other users.

I primarily use the solution for its business application. My business needed an application and so that's what we're using Power Apps for.

We are customers and resellers. We mainly collaborate with Microsoft and supplemental applications.

Our primary use case of this solution is for when we're integrating something and need to extract some data. We use PowerApps to extract the data and create our own module inside PowerApps and create our own app. We extract data and integrate it with PowerApps.

My organization deals with the implementation of PowerApps and Salesforce. We are currently scaling up our capacity in low-code, no-code platforms. Essentially, this solution is for building forms from a front-end loan application and quickly rate a particular application.

We primarily use the solution to create apps for business users which navigates them from within our platforms.

We are currently piloting the solution, we are checking it with our workflow.

We're working on B2E applications and therefore we can't really get into specific use cases.

I am using Microsoft PowerApps for small apps for internal company management. I have been working only on small and simple apps. I haven't used it for making complex apps. I am using the latest version of Microsoft PowerApps.

We use this product to develop small apps that are used internally. Nothing major.

We're not in production yet. We're still very much in the early stages of this solution.

Microsoft has come at the right time. To come out with a RAD (Rapid Application Development) tool where you can develop your apps on the cloud much faster, and deploy them for multiple devices, whether it is mobile, cloud, laptops, or desktops. It is similar to Oracle APEX or Oracle developer tools where you just drag and drop into your application within minutes. The primary use case of this solution is case management reporting. If, for example, you have a set of engineers who have been assigned a particular case or project they will need to record all of their activities and their visits. Using the application created in PowerApps, they report everything, then it goes through a workflow. The workflow goes from recording the daily activities of the team for the specific project. The project then goes through a series of approvals and gets logged, completed, and the report is generated. Expenses are also being logged. We have Power BI as well, and it moves the data from the source to the data warehouse then generates a report. This is quite a short term, six-week engagement. We wanted to create an application and have it up and running within four to six weeks, rather than spending three to six months on bigger projects on the platform. We wanted it to be quick and fast. PowerApps is best suited for those cases where you have a small scenario and an application to support that project or scenario. You can call these departmental applications, which are needed on the fly. We create a much shorter development lifecycle and then deploy, and then people start using it. Take an example of the COVID-19 situation. We wanted all of our branches to log their COVID cases or what exactly are they doing daily to manage the COVID cases and to know what the process is. All of those details are logged into the COVID folder and then the reports are generated daily or weekly.

We use the Microsoft PowerApps platform to create low-code applications that are used for optimizing internal business processes.

We use this solution for process authorization in our company.

We primarily use the solution for in-house management. For example, for human resources.

Our sales reps use it in the field on a daily basis. I get the data from there and then analyze it for my needs. We are also developing an application to start using Microsoft PowerApps. I would assume we have the latest version.

I am not a PowerApps user, but recently I have been evaluating and scoring no-code to low-code platforms (for developing mobile apps). The score chart is divided into sections, such as usability and features like the ability to test and multi-platform. Due to these evaluations, I learned the systems well enough to be able to build a sample application on all of these platforms and then fill in my evaluation.

We primarily use the solution as a general business process improvement. We use it as more of a digital transformation to eliminate some archaic manual processes that the business has built up over time. We're working to make everything more streamlined.

Once you have a cloud solution, for instance, and you work within a Microsoft suite, such as Dynamics CRM, ERP, or another dynamic platform and you want to extend it with a mobile app, Microsoft PowerApps is the right solution. Main limits will be the "vendor lock-in" concept, pricing for mass external users, and the training could be better. It is not intend to serve ex-Azur assets or on-prem.

Our primary use case is for the three locations in our company. We use it mainly for setting up meetings in our various conference rooms. Numerous choices need to be made - size of room, number of phones and projectors, date, time, number of participants. It's a great way to keep track of everything. We have 200 users. We're gold partners and I'm a lead consultant in our company.

Our primary use for Microsoft PowerApps is to develop production-ready applications.

The primary use case of this solution is to automate the interaction between documents and departments. For example, it's a flow for someone who has to validate a request, a file, or to review another file. A flow is put in place to avoid email communication.

We primarily use the solution to create and arrange a number of requests, including requests for expenses, requests for leave, requests for documents, etc. Depending on the type of business, we can customize the request application.

I'm a developer and we use the product for in-house development and finding in-house solutions. We have a developer relationship with Microsoft. I'm currently working on a smart parking app for a college here in Kuwait. It would be a big time saver and enable drivers to know where there are available parking spots when it's a busy time and would maximize free space usage. It would make things easier for everyone.

The primary use case of this solution is for developing Proof of concepts and for preparing some use cases to present or to showcase them to the customers. Nothing related to production. It's only for presentations and for showing the merchandise to the customers. The deployment model we are using is cloud-based.