"The best feature is scalability, which allows you to target potential clients worldwide by connecting the application to a local server. This makes the application readily accessible, and the response time will be much better."
"It's a platform as a service, so we don't have to manage the infrastructure to hold the websites."
"I like that it's a ready-to-use, out-of-the-box solution that provides all of the necessary functions for customers, such as codes that can be quickly switched from the production version, or from test and DEV versions to production."
"Debugging using Application Insights is a valuable feature."
"The technical support from Microsoft Azure App Service is good."
"Azure data factory is a good tool."
"We have no complaints surrounding both the scalability and stability of this solution."
"The flow editor is the most valuable feature. It is simple and intuitive, and it can guide you step-by-step."
"The technical support is perfect."
"The scalability of OutSystems is very good, it scales automatically very useful for us."
"We used almost all of the features, themes, styling guide, and approach components. They are useful in our applications."
"The scratch coding is useful. The solution is easy to understand."
"One thing I like about OutSystems is that there's no lock-in. You can keep running your applications because it's on .NET and hosted centrally. That's one of the advantages I see there in terms of not having an IT strategy that has a dependency on a particular platform."
"The architecture of OutSystems is quite simple, and the features are similar to Mendix's. OutSystems has connectors for different enterprise apps and solid reporting capabilities. You can also integrate with any content management platform like SharePoint or Adobe Enterprise Manager, or something like that. You can also create and integrate workflows."
"The logging and monitoring could improve in Microsoft Azure App Service."
"Lacking somewhat in template data flows."
"It would be fantastic if Microsoft morphed after my exit service, removing it from subscriptions and moving it to different regions, especially for that service."
"The solution needs better integration capabilities on the network side."
"Initially, there were some rare instances when the server went down because it was deployed on Linux."
"If you're on the cloud, you just get a web interface without much detail for additional configuration or the authority to configure the root or system-level configuration."
"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."
"The solution is costly."
"There are not enough resources on the market."
"The prices should be lower. It is a little bit too high for a small market."
"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."
"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."
"OutSystems could improve by being more like GitHub. It would be more helpful for us for division management and version control for our application."
Microsoft Azure App Service is ranked 4th in Mobile Development Platforms with 6 reviews while OutSystems is ranked 3rd in Mobile Development Platforms with 13 reviews. Microsoft Azure App Service is rated 8.6, while OutSystems is rated 8.0. The top reviewer of Microsoft Azure App Service writes "Good backup and restore, with vertical, horizontal, and DEV scaling options". On the other hand, the top reviewer of OutSystems writes "You can keep running your applications because it's on .NET and hosted centrally". Microsoft Azure App Service is most compared with Microsoft PowerApps, Oracle Application Express (APEX), Pega BPM, ServiceNow and HCL Domino, whereas OutSystems is most compared with Microsoft PowerApps, Mendix, ServiceNow, Oracle Application Express (APEX) and Zoho Creator. See our Microsoft Azure App Service vs. OutSystems report.
See our list of best Mobile Development Platforms vendors and best Rapid Application Development Software vendors.
We monitor all Mobile 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.
