We performed a comparison between Microsoft PowerApps and OutSystems based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Users of both solutions seem to be satisfied with their ease of deployment, features, and overall technical support. However, users seem to favor Microsoft PowerApps slightly because it is more affordable.
"The cloud aspect has been great. We don't have to do a lot of research in order to begin integrations. It's so easy to integrate with other solutions."
"I like the containerization of Azure."
"I like the galleries, which are really powerful."
"Can design apps quickly and can connect to any database."
"The model that allows you to establish flow automation is getting a lot of traction from the customer side. It offers a lot of flexibility."
"Flexibility, easy setup, and fairly quick results are valuable features of the product."
"The most valuable feature is automized processes."
"The solution allows you to use data to create excellent UI and quickly deliver an app. It speeds up production time."
"The most valuable features of OutSystems are the user interface, the flexibility to quickly integrate with almost anything in the system, and the ability to connect with databases."
"OutSystems is easy to use."
"We used almost all of the features, themes, styling guide, and approach components. They are useful in our applications."
"The most valuable feature of OutSystems is the drag and drop and toolchains in the small AI developing environment. Additionally, the documentation is helpful."
"Scalability proved to be an exceptionally beneficial feature."
"Their out-of-the-box UI is quite good."
"Our previous solution had other overheads such as release management, version management, code management, monitoring, etc., all of which are built-in with OutSystems."
"OutSystems is a low-code solution. Most features are like drag-and-drop, so it's pretty easy to work. Thus it helps the organization by saving time for developers."
"Can be improved to cater to complex developments."
"This tool doesn't have an internal database. It only relies on the data layer of Microsoft Cloud."
"Microsoft PowerApps is not responsive in nature."
"In my experience, the solution's deployment can be tricky."
"If the price was reduced and the quality of the user interfaces was improved it would be beneficial."
"The set up of the solution could be simpler."
"PowerApps can't do a lot of things that users need now. For example, it can't handle signatures."
"It would be beneficial to have a feature that allows users to split the opportunity into separate logs for each product."
"The integration points need to be increased. People have also started to adopt this solution for their regular needs. That means it's not only the big enterprises that are adopting this solution. There are also small and medium enterprises that are adopting it. I've read that where you have large deployments, OutSystems starts to crumble a bit. That is the idea that no customer would know at the beginning and would also not like to hit the wall there. When it is on the client, there are a lot of applications already on low-code, and then suddenly you realize that you want to do some big applications, and you face hurdles. This is the general feedback for all such platforms."
"The product could be improved if there was a shortcut, or predefined, predictable templates provided."
"Since we first started using OutSystems, they switched their language support from Java and .NET to .NET only, which was a bit of a surprise. Their language support could be better in this sense, although on our resource side it is now a bit more flexible."
"One of the biggest areas for improvement is that every time an existing data element is modified, it creates a new data element. It doesn't really modify that particular data element. So, a user has to follow an extra step of removing the existing data element and bringing in the new and modified data element that is being added, which sort of goes into negative productivity."
"We had some lagging issues under high data loads, and the solution needed to be customized to improve this."
"Writing custom code still needs to be done via Integration Studio. This might have been added to the IDE."
"In my opinion, the support and the pricing could be better."
"Mobile apps should have been fully native."
Microsoft Power Apps is ranked 1st in Low-Code Development Platforms with 77 reviews while OutSystems is ranked 3rd in Low-Code Development Platforms with 46 reviews. Microsoft Power Apps is rated 7.8, while OutSystems is rated 8.4. The top reviewer of Microsoft Power Apps writes "Low-code, low learning curve, and reduces manpower". On the other hand, the top reviewer of OutSystems writes "The visual program provides the advantage of only requiring one skill set for both the front and backend ". Microsoft Power Apps is most compared with Oracle Application Express (APEX), Mendix, ServiceNow, Appian and Salesforce Platform, whereas OutSystems is most compared with Appian, Mendix, ServiceNow, Oracle Application Express (APEX) and Pega BPM. See our Microsoft Power Apps vs. OutSystems report.
See our list of best Low-Code Development Platforms vendors and best Rapid Application Development Software vendors.
We monitor all Low-Code Development Platforms reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.