Principal at a consultancy with 1-10 employees
Real User
Great for quickly making apps, with reasonable pricing, but doesn't scale well externally
Pros and Cons
  • "The solution is excellent at figuring how to build an application in three months. It makes it very quick and easy."
  • "The documentation isn't great. It's only 75% of what you need to know. If you go beyond that and run into issues, it's really not going to help you."

What is our primary use case?

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.

How has it helped my organization?

We've been pleased with it. I would say that it has improved the way our organization functions. It makes app-building faster and easier.

What is most valuable?

The solution is excellent at figuring how to build an application in three months. It makes it very quick and easy.

The pricing is very reasonable. it's not overly expensive.

What needs improvement?

I can't recall any missing features. Currently, the solution is doing a good job of meeting my needs.

My target is to have an application that I can use for clients. I don't see Power Apps as being the long-term solution. They get expensive when you start to go to non-internal users. If there were to be external users, the solution would get expensive.

The documentation isn't great. It's only 75% of what you need to know. If you go beyond that and run into issues, it's really not going to help you.

For example, the software is almost guilty of being too powerful. The particular problem I had was that they recommended that I use Azure to do the login, to do the user authentication. Therefore, I set it up. However, it didn't work. I could not find the solution via documentation or online at all. Without knowing I could access technical support, I paid someone a couple of hundred dollars to try and figure it out for me and they couldn't figure it out. Eventually, I was just looking around and I came across one setting hidden away and it was set to false. I instinctively realized that it looked like it might be related and so I set it to true and all of a sudden everything worked. However, that whole issue could have been mitigated if the documentation just took that extra step and got into the nuances of the product.

What I'd love to see them do is to sit down and clean up the interfaces. There are three different ways that you can program. I'm particular to using a Power Apps portal. There are three different ways I can edit my Power Apps portal website. Each of them kind of does a better job of doing some things than the other ones do. Therefore you're kind of in this in-between realm of having to choose between certain things if you decide to go with a specific approach. They really need to clean up the development environment so that t's straightforward and predictable across the different ways to program. 

It does things, such as, if you want to delete a particular field or table, you get this message that says you can't due to the fact that it has dependencies. It's really hard to find what those dependencies are. Items like that need to be clarified. 

The application is working great now, however, every once in a while it gets complicated and it's hard to navigate.

Buyer's Guide
Microsoft Power Apps
April 2024
Learn what your peers think about Microsoft Power Apps. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
769,236 professionals have used our research since 2012.

For how long have I used the solution?

I've recently delved into using the product. I've been using the solution for at least the last seven or eight months or so. It's been less than a year. I haven't used it that long just yet.

What do I think about the stability of the solution?

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. its performance is reliable.

What do I think about the scalability of the solution?

The scalability is limited if you want to scale externally. A company needs to keep that in mind.

I only launched my first application sometime around Christmas, or just after. It's still quite new. I have about a dozen or so people that move in and out of it. It's just a small app.

As a company, we are quite small. All of our users would be external. And, due to the fact that the solution gets expensive for external users, it's not a solution we plan to expand upon or use for the long term. 

How are customer service and support?

The technical support is not easy to find. It's a bit of a well-kept secret. However, once you locate them, they are quite helpful and responsive. 

Truthfully, they are hard to find due to the fact that you just don't realize they're there. I had spent a month, six weeks phoning around trying to find internet solutions to problems and resources and paying people to help me, and nobody knew the answer. 

This was done without ever realizing that there was a very capable tech support resource available in Power Apps through the subscription. Once we found them, they were able to fix all of the issues we were struggling with very quickly.

How was the initial setup?

The initial setup is quite straightforward. A company shouldn't have any issues with the setup process. It's not overly complex. 

What's my experience with pricing, setup cost, and licensing?

The pricing is excellent. It's not too expensive.

However, once you get into adding non-internal users, the solution can get pricey. It's only reasonable if you are trying to create internal team-based apps.

Which other solutions did I evaluate?

I haven't looked at any other low-code development platform.

What other advice do I have?

We're just customers and end-users.

We are using the latest version of the solution.

From a perspective of me doing a full test of the application and how I want it to run, it just met all of my needs and there are other storage locations for data. That said, the data is sitting in the CDS.

From my perspective, it was a great place to start and a great place to sit and test the waters. I'm looking to migrate it into something else in a little while. I won't stay with it forever. That's not the plan.

I'd rate the solution at a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Information Technology Operations Analyst at a construction company with 10,001+ employees
Real User
Straightforward to setup, stable, and the automized processes are useful
Pros and Cons
  • "The most valuable feature is automized processes."
  • "The connectors are the main components that reference the data sources, and these need to be improved."

What is our primary use case?

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

What is most valuable?

The most valuable feature is automized processes.

What needs improvement?

The connectors are the main components that reference the data sources, and these need to be improved. They have to both improve the ones that are already there and add new ones.

For how long have I used the solution?

We have been using this product for a couple of years, since 2018

What do I think about the stability of the solution?

This is a pretty stable product. So far, we haven't had any critical issues with it.

What do I think about the scalability of the solution?

There are some options for scaling the product but we haven't used them, so I am not sure about scalability. We have approximately 1,000 users.

How are customer service and technical support?

I would rate the technical support a nine out of ten. They are very good but the response time could be improved.

How was the initial setup?

The initial setup is straightforward. It is a self-service solution, so there is no real deployment. It is a case of enabling that functionality within the Microsoft account, and then telling the people that it is enabled and available. At that point, I think that that they can create their own applications if they need to.

What other advice do I have?

My advice for anybody who is implementing this solution is to research the material that is available in the documentation, as well as videos on YouTube. These sources contain a lot of information and recommendations for how to implement and use the platform.

They also have a really good community with Microsoft the websites, where many people post their issues and the solutions as well.

Overall, this is a really good product.

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Microsoft Power Apps
April 2024
Learn what your peers think about Microsoft Power Apps. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
769,236 professionals have used our research since 2012.
Business Intelligence Consultant at FumAstra Management Consulting
Consultant
Affordable, customizable, and easy to set up
Pros and Cons
  • "There are a lot of different applications; you can connect PowerApps, or Flow, or Power BI to many different types of applications to interchange data."
  • "The solution is evolving very fast and every month new features are introduced. Sometimes it's difficult to catch up with all the evolution that's happening. I had to focus on Power BI for a while and left PowerApps at the side for a couple of months and when I came back, it had changed its interface and moved components around."

What is our primary use case?

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.

How has it helped my organization?

In our organization, PowerApps is used to manage internal requests for expenses, leaves, documents, company resources. One connects to the application, enter the details of the requests and the request flows directly to the appropriate approvers. Less paperwork and more efficient management of the requests.

What is most valuable?

The most valuable aspect of the solution is the fact it is highly customizable. All types of forms can be created to collect information, pictures, and files. With PowerApps, you can connect your application to a wide variety of databases and applications where your data lives to read or write to it. If a connector doesn't exist, it's also possible to create a custom one.

With a plan starting at 10 USD, it makes it very affordable for anyone to create a low-code, no-code application. Very little costs are needed to run the solution. Furthermore, PowerApps has a community plan for free, and usually offer a trial period of about 2 months. Plenty of time and potential to learn, discover and develop.

The solution has a large community, so it's quite easy to find tutorials, how-to, and help.

PowerApps is part of the PowerPlatform from Microsoft, with Flow, or Power BI and enhances the possibilities to collect data, to automate processes, and to create rich and visually appealing data visualizations.

What needs improvement?

The solution is evolving very fast and every month new features are introduced. Sometimes it's difficult to catch up with all the evolution that's happening. I had to focus on Power BI for a while and left PowerApps at the side for a couple of months and when I came back, it had changed its interface and moved components around. 

Some connectors are not very easy to use and sometimes they lack proper documentation.

There should be better connectivity with other applications. I tried connecting with IBM and it brings errors at each refresh. The PostgreSQL connector is useless as it doesn't work. There's a lot of research needed and you often need to download extra drivers or equivalent components that end up not working well.

For how long have I used the solution?

I've been using the solution for a year now.

What do I think about the stability of the solution?

The solution is very stable. There are a few issues with the environment, where we would have needed to create a new one. This would have been a problem if we had a lot of data. However, but I haven't faced any stability issues.

What do I think about the scalability of the solution?

Scalability is okay, but they recently changed the pricing. Depending on what we do and what we use it for, the pricing is a bit confusing now. They're also offering a bit of a delay on the adjusted pricing for those who have a certain subscription, so I'm still figuring out what that means for us.

How are customer service and technical support?

Technical support is very fast, with answers within 24 hours. Most of the time they either call directly or send an email. I've found them very good and they are helpful. They try to give a solution and offer direct service.

I've had experience with IBM and it was a bit more difficult to find the right solution and obtain results. As with some other PRN providers, I was expecting a slower turnaround, so this has been a nice surprise. Microsoft and PowerApps have been very good.

How was the initial setup?

The solution is very easy to set up. Deployment is almost instantaneous. It's on the cloud, so you connect the logins and it's ready to go. You don't have to download it onto any device.

What about the implementation team?

I handled the implementation myself.

What's my experience with pricing, setup cost, and licensing?

The pricing is pretty good. Right now, I'm paying for a two or three-month trial that is priced well. This trial period gives a company time to try an application, develop it, test it, and decide as to whether they will go ahead and pay for a modular plan.

I find their pricing quite affordable.

What other advice do I have?

We use the cloud deployment model. I'm a consultant; I work mainly with other companies.

Already with what exists, the solution is quite good and we can do quite a lot. I don't think too much can be improved.

I'd advise others to make sure they have good parameters and documentation before they get started. It's a good idea to follow the tutorial at the beginning. There are a lot of things about the solution that are good to understand beforehand, including how the different components work.

I'd rate the solution ten out of ten. For me, it has worked very well.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Owner at a tech services company with 1-10 employees
Real User
Top 5Leaderboard
Makes client communication easy; high level of tech support
Pros and Cons
  • "The most valuable feature is the completeness of the concept. It is not restricted by where you are allowed to use it and that is its greatest strength."
  • "There is room for improvement in error handling and debugging."

What is our primary use case?

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

What is most valuable?

The most valuable feature is the completeness of the concept. It is not restricted by where you are allowed to use it and that is its greatest strength.

What needs improvement?

There is room for improvement in error handling and debugging. I would appreciate it if Microsoft created something like the social network graphs Facebook sometimes shows you (potential connections). It would be great for Microsoft to take a similar point of view regarding the data and data flow in Power Apps. It would help us see which field is changing and which is influencing the follow-up field or display or workflow, etc.

As a chief financial officer, I would like to see the mark of chain retracement and where the money flows. Imagine dropping a little drop of ink onto a handkerchief and seeing the ink sucked into the fibers of the handkerchief and distributing itself. Similar things happen to money if you put it into a small market and a chief financial officer needs to have that information. 

For how long have I used the solution?

I have been working with Microsoft Power Apps since 2018. 

What do I think about the stability of the solution?

Microsoft Power Apps is definitely stable. It is as stable as SharePoint and this app model has been in place since 2013. Essentially, it requires you to put code onto a SharePoint site which is not executed there, but rather on a client or on specific workflow codes, which are client. If code executions are well work-flowed, it is capable of saving your script and of the global resources. That capability to take off where you left off, including external resources, is a great strength.

What do I think about the scalability of the solution?

Microsoft Power Apps is scalable. SharePoint is a farm. It is a big forest of machines interconnected by a messaging system, Windows Azure Service Bus. It can be understood as a telepathic network between the machines. As long as one machine is running, the system's running and as soon as more machines are adding the capabilities, the load is distributed automatically.

How are customer service and support?

Microsoft's technical support is at a high level. 

Which solution did I use previously and why did I switch?

We did previously use a different Microsoft workflow operating system, but it was complicated to program and difficult to provide interactions with the users. All of that is much easier now that we use SharePoint platforms like Teams. Microsoft has the best of all worlds. I am confident that it will rock the market.

What's my experience with pricing, setup cost, and licensing?

I have an MSD end subscription; it's a flat rate subscription.

What other advice do I have?

My advice for anyone looking to implement Microsoft Power Apps is: please have a closer look at the Azure infrastructure and do not underestimate the complexity of Azure Active Directory and SharePoint. I recommend spending a week or so letting someone informed like me introduce you to the complexity of Azure Active Directory, SharePoint, and Windows Azure. Not having this information is like driving a car without having put oil into the motor and air into the tires. In other words, it would not be wise.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Andy Chen - PeerSpot reviewer
Technical Manager at Coming Computer and IT services
Real User
Top 5Leaderboard
Stable, easy to use, and simple to implement
Pros and Cons
  • "The solution is very straightforward. Its context is obvious and everything is easy to understand."
  • "I have heard from developers that there is documentation missing in the reporting."

What is our primary use case?

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

How has it helped my organization?

We are a small business. We keep up all sales and duties within our organization. One day someone might be part of the development team, however, next week we want him on the sales team to directly involve them in a small project that we've done for the client. We don't have to go to a different person from an agency or organization or have someone that is always dedicated to a position. We need to be flexible in order to move our employees from here to here. And this solution allows us to change or play around with our own system to reflect the changes of our personnel.

What is most valuable?

The solution is very straightforward. Its context is obvious and everything is easy to understand.

Compared to previous applications which developed by Visual Basic, we can quickly update the whole business process without spending weeks or a month dealing with those aspects.

What needs improvement?

I can't think of any features that are lacking.

The pricing could always be less.

I have heard from developers that there is documentation missing in the reporting.

It would be useful if Power Apps were capable of providing more flexible reporting to allow the developer to really to manipulate the data, and get into more details - for example, why it's being changed and how it's been changed. If there was a way they could comment right in the reports, that would be very helpful. 

There should be more document management capabilities.

For how long have I used the solution?

We've been using the solution for a year and a half at this point.

What do I think about the stability of the solution?

The stability is pretty good from a business point of view. It was reliable and easy to understand and work with.

What do I think about the scalability of the solution?

We haven't really tested the scalability, however, we've noticed that, since everyone is working from home, it's much slower than if everyone works from the office.

With everything going on, we don't really have the right scenario to really test for scalability. That may happen in the future. COVID-19 has put a lot of plans on hold.

We currently have 12 people using it. They are mostly project managers and developers. We also have two sales people and the CEO on it.

How are customer service and support?

We've never had to reach out to technical support. That's a good thing. It means we haven't had any issues.

Which solution did I use previously and why did I switch?

The last solution we used was old and it was built in-house. It was time to retire it, which is why we adopted this product.

How was the initial setup?

Although I'm not the person who handles the initial setup, my understanding is that it's not too difficult and pretty straightforward.

Deployment typically takes two months. The last deployment we did started in May and was completed by July.

There isn't a lot of maintenance needed. We have one developer that's dedicated to the maintenance and changing the environment as needed. It's pretty hands-off though.

What about the implementation team?

We handled the implementation ourselves. We didn't need any outside assistance.

What's my experience with pricing, setup cost, and licensing?

The solution is subscription-based, however, I don't handle billing, and therefore don't have insights into the costs. We don't have any extras that we pay for. We just have a standard subscription package.

I'd recommend the solution. Overall, I'd rate it eight out of ten. If the reporting and pricing were better, I'd rate it higher.

I've definitely learned about the power of the cloud. Before everyone used to use the VPN connection to the head office. When we pushed into the cloud and everyone can just see everything and the system is very sound. It also allows our developers to see what they can change. It's been great.

What other advice do I have?

I'm not sure which version of the solution we're using.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
EVP, Solutions at a tech services company with 11-50 employees
Real User
Easy to set up, integrates well with native systems, and offers good stability
Pros and Cons
  • "I have found the technical support to be helpful."
  • "When we talk of integrating with external applications, that's one area where, even today, I had to loop in my code developers. If this area can be streamlined so that my techno-functional consultants, who are on-site, can immediately start working on something without the assistance of developers, that would be ideal."

What is our primary use case?

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

What is most valuable?

What I like about it is that it is coming from Microsoft. It is very easy for us, our techno-functional consultants to spin an application in days, not in months. 

This is easily integrated with native systems including the Microsoft stack. If we have to integrate with other products such as SharePoint, we can leverage any services using Azure or the same platform.

In terms of scalability, it can scale quite well. It's so scalable with forthcoming technologies. We can develop something in PowerApps, and that can easily be scaled to a bot. We can quickly make a bot there and make it work in conjunction with applications.

We had it integrated earlier with voice channels. You can manage an omnichannel kind of scenario between Voice, Teams, WhatsApp, social integration platforms like Twitter, Facebook, et cetera. 

The RPA is very closely integrated onto the same platform and BI as well. It's great.

The initial setup is very easy.

The product is very stable. 

I have found the technical support to be helpful.

What needs improvement?

When we talk of integrating with external applications, that's one area where, even today, I had to loop in my code developers. If this area can be streamlined so that my techno-functional consultants, who are on-site, can immediately start working on something without the assistance of developers, that would be ideal.

For how long have I used the solution?

I've used the solution for four and a half or five years. 

What do I think about the stability of the solution?

The stability has been great. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

What do I think about the scalability of the solution?

It's so scalable. We can scale to all the latest technologies and we can integrate with the social platforms. We can integrate with the document management system (SharePoint). We can integrate with the Active Directory exchange server. It's limitless.

It is so much more scalable once you have everything available over in the Dataverse so that you can write triggers and automate a lot of the BPM. Once you have everything with you, you can spin any dashboards, reports, schedules, and then those can go through mail alerts. You can schedule alerts through WhatsApp messages. You can schedule it through voice IVRs. You name a thing, or you can schedule it. You build it over here and then schedule it over there. 

How are customer service and support?

My experience with technical support has been very, very hood. They've been very supportive. The only thing is that you have to have the right support plan. If you have one, they adhere to the SLA quite well.

How was the initial setup?

The initial setup is not overly complex or difficult. It's pretty simple and straightforward. 

What about the implementation team?

I have done the initial setup multiple times for the various installations. I can handle it on my own and do not need outside assistance. 

What's my experience with pricing, setup cost, and licensing?

The pricing is a subjective thing. Whenever we are positioning PowerApps to an enterprise that is already into Dynamics 365 ER PCRMs, it is very easy to position it as they have already made initial investments there. It is just simply that the number of users that are based on the number of applications and it can be scaled. For them, I've never faced any issues. For example, for a hospital with it, we were already reaching out to, say, 40 units. When they wanted to scale to their smaller units, the 70 of them, it was a cakewalk. Then we had a plan to extend it to their pharmacies, say, 50 of them. That, again, was a cakewalk as they were already on that platform.

However, when I go and reach out to a smaller business SMB segment, the challenge over there is that we are faced with competition - with other software which has been built on PHP. If we host it on-prem, of course, then that discussion of cloud versus on-prem and those fundamental discussions creep in and then there is the minimum unit price per license, meaning per user or per app. When you look at it that way, an SMB will see it as expensive compared with open-source options.

What other advice do I have?

I'd rate the solution at a nine out of ten. If the external integration process was easier, I would give it a perfect ten. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
PeerSpot user
Developer at Australian College of Kuwait
Real User
Data integrates easily on all Microsoft apps but the solution is limited
Pros and Cons
  • "It's a very workable solution because it's an automated way of making applications. You have a template, you have the application know-how,"
  • "The product could be improved by making it a production application and enabling the export of apps."

What is our primary use case?

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.

What is most valuable?

The common data point would be the most valuable feature. PowerApps is also usable for data mining, it can be used with Power BI or SQL. All the data integrates easily on all Microsoft apps. And it comes with most of the subscriptions and extras.

What needs improvement?

The product could be improved by making it a production application and enabling the export of apps. If you want to set up a site for home rentals, for example, just a basic outline as a starting point, this can be done. The issue is that it cannot be exported. It can be applied in-house, for demonstration purposes for your employees, for example, but you can't really make use of it otherwise. It's a problem.

On the whole, it's a very workable solution because it's an automated way of making applications. You have a template, you have the application know-how, etc. If it could be exported into different languages and could enable different ways of outputting the information, that would be great. For now, it's limited and that's a bit of an issue. Enabling all the applications on internet-based devices to transfer data in and out would make it an excellent product. 

For how long have I used the solution?

I've been using the product for six months and we're using the latest version.

What do I think about the stability of the solution?

It works as intended, it's not going to be a magical solution, but it just does what it's meant to do. That's the beauty of it.

What do I think about the scalability of the solution?

I believe the product is very scalable.

How are customer service and technical support?

Customer service has been pretty good. Actually I tried contacting them today and they've put up this bot that can get a response for you, but it takes more than a day, I think. I could do with some support. I can't access Azure Maps here, and I need Azure Maps to set up the smart parking system. 

Which solution did I use previously and why did I switch?

I previously used BlinkID but nothing else really has the same power as PowerApps. Google has its Cloud Suite but they've been a bit slack, and Amazon is iffy. They're not really workable here. I live in Kuwait, and there are a lot of contracts with Microsoft - they have the App Center here, but they haven't enabled much of it other than for government contracts, I think.

How was the initial setup?

The initial setup was very straightforward. I tend to think the documentation and the community forms are more than enough to help improve your setup experience. It's very, very, straightforward. I don't think it took more than five minutes to set up and that's amazing. Previously, it might have taken a week to complete setup - all the code, database, linking. 

What's my experience with pricing, setup cost, and licensing?

I have no idea about licensing costs. I tried contacting Microsoft about this because the information isn't easily available and it was unclear where I could search for this. My guess is that the cost is dependent on the company and product needs. I tried to make a calculation and it looks like it's going to be much cheaper to purchase the product than if I were to hire an engineer, get him to develop an app, and have it maintained. This is a much more scalable and less expensive solution.

What other advice do I have?

Previously, we had a whole department using the product. When I lived in Australia, it was used for assembling websites and to upload photos, videos and the like. It worked well because it was for internally-based users. 

My suggestion to anyone searching for a product would be to invest in a solution if you know that it works. Don't go for anything high-risk. This product works as it's intended. It's missing a few key features to make it really stand out but I believe it has the potential to be the best app for access to the database.

The product can be easily integrated - with Microsoft Graph, with common data links, and Power BI especially. You can have a dashboard ready, all the information you want, displayed in whatever form you want. It can present your data in whatever way, shape, and form you want it to.

I would rate this product a seven out of 10. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PaulDe Groot - PeerSpot reviewer
Power Platform Consultant at BE-SYNC
Consultant
Good for automation and creating small apps for Microsoft Office but needs to be more stable
Pros and Cons
  • "It is good for using for small apps and automation on Office stuff."
  • "The stability of this solution could be better."

What is most valuable?

The performance is showing signs of improvement. 

Technical support is okay.

It is good for using for small apps and automation on Microsoft Office items.

What needs improvement?

The stability of this solution could be better. It's getting better, the performance. However, it's not there yet.

We'd like to be able to leverage more reuse of the code we are implementing in the apps.

For how long have I used the solution?

I've been using PowerApps for two years.

What do I think about the stability of the solution?

The solution needs to improve stability and performance. However, they are working on it. 

How are customer service and support?

Technical support is okay and we are mostly satisfied with it. 

How would you rate customer service and support?

Neutral

What other advice do I have?

I'm a customer and an end-user.

I would advise other users to try out the product. We've had a largely positive experience. It's good for using for small apps, and automation specifically for Office stuff. If a company needs that kind of specific usability, I'd suggest they use PowerApps.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Microsoft Power Apps Report and get advice and tips from experienced pros sharing their opinions.
Updated: April 2024
Buyer's Guide
Download our free Microsoft Power Apps Report and get advice and tips from experienced pros sharing their opinions.