Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
- Drag-and-drop Interfaces (47)9.292%
- Reusability (49)8.787%
- Platform Security (46)8.585%
- Visual Modeling (47)7.777%
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of OutSystems, and make your voice heard!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
- Tech Details
- Supported: Visual development environment, extensible with custom code
- Supported: Integrate any existing system and database
- Supported: Deploy to any device
- Supported: No technology lock-in
- Supported: Model complex offline behavior
- Supported: Integrate native device capabilities (GPS, barcode, etc.)
|Deployment Types||On-premise, Software as a Service (SaaS), Cloud, or Web-Based|
|Operating Systems||Windows, Linux, Mac, Web-based, Android, iPhone-iPad, Windows Phone, Mobile Web App|
|Mobile Application||Apple iOS, Android, Mobile Web|
|Supported Countries||Asia, Australia, Brazil, Canada, China, Europe, Germany, India, Japan, Latin America, Mexico, Middle-East and Africa, United Kingdom, United States|
|Supported Languages||Arabic, Chinese (Simplified), Chinese (Traditional), Czech, Danish, Dutch, English, Finnish, French, German, Hebrew, Hungarian, Indonesian, Irish, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Russian, Spanish, Swedish, Taiwanese, Thai, Turkish, Ukrainian|
- Rapid development
- Create good looking and responsive applicatoins
- With OutSystems you will have happy customers
- Documentation in different languages
- Reactive Web Apps
- Mobile Apps
- Training Videos
- Documentation in multiple languages
- Database integrations: These integrations allows users to speed up development processes by providing ready to use methods.
- Error handling: Error handling is excellent. It is showing errors in real time while you are programming. Syntax errors are avoided and changes in variable names, input parameters and other definitions are automatically performed on site where it is referenced.
- Fast deployment: Deployments between development and test, and test to production are fast and avoid many of the possible deployment errors caused by human intervention.
- OutsySystems needs to improve in web services. Support SOAP 1.2 and also do a better handling of date types when they are used as input parameters in web services.
- OutSystems needs to handle better integration with databases that do not have tables with a single field primary key defined. Some tables have a primary key composed of two or three fields and those are not well managed by OutSystems. I am specifically talking about the fact that in those cases inserts, updates and other database actions are not created.
- Content management. Nowadays there is no available and reliable content management to develop web sites with CMS capabilities.
- Online training
- in-person training
- Quick to learn
- Development environment agility
- Develop as you Go
- Prototyping approach
All topics that can be developed, like simple workflows or action triggers, are well suited to use OutSystems.
A few examples include invoice financial approvals, meetings action trackers, automatic escalations flows, email automation triggers, operational process simplification for day to day tasks, etc.
- It provides very clean and intuitive flow editor.
- All "parts" in OutSystems (flows, UI, data, logic) are fully interconnected. A change in data will be immediately propagated through all layers.
- I've never, yet, experienced any bug in interconnectivity. For example when you change the size or type of a column, and expect it to be reflected in the properties of some UI field.
- It's very easy to start being productive in OutSystems as a complete noob. Even for complex matters it is just a matter of a quick google search on how it's done. There is a flat learning curve.
- The flow editor provides the ability to debug in a way that just works.
- It integrates very well with custom C# code, if you want to. But we only added custom code during the first few years. After a little more experience we found ways to circumvent the need to implement custom code, but it's nice to know that you at least can extend any functionality in case you really need to.
- It would be nice if OutSystems provided a way to import and export the YAML for any API.
- The "servicecenter" and "lifecycle" modules can seem to be a little daunting at first. I would like to see a little more intuitive approach. But this is but a small problem, hardly worth mentioning, because even these modules have a rather flat learning curve.
- Coding inside OutSystems is "data oriented" and as such follows more database-like architecture instead of good old Object Oriented design. Even when the latter is actually possible, working in OutSystems seems to recommend a more point to point and procedural approach. There are no "interfaces" or "base classes", which is both a strength and a weakness.
Not so well suited for full fledged web design. An OutSystems application must serve one particular business need, if gets too much functionalities and responsibilities it tends to get chaotic and complex.
With OutSystems driving innovation to bring disrupting and enabling cost reductions and increase user engagement by more and better UX applications.
- Drive innovation
- Rapid great UX App development
- Integrates with everything
- Performant and scalable
- Your goto modern application development environment
- Going so fast the backlog dries up :)
- macOS support for Service Studio and Integration Studio (although that will be there soon)
- Ease to Learn
- Quickness in the app
- Development of an application in a short time.
- Be aware of market needs and converge there.
- More information and content for seniors.
- Contents better explained.
- High paced development.
- Integrated solution.
- It's not flexible enough.
The event manager we built in OutSystems was a big success, as we could extend the SAP functionality but also improved the process tremendously.
On other terminals, SAP is not used, but Navision. Our goal is to have our external web sides integrated with SAP in Navision. At this moment it's a big challenge.
- Very good user interface. Easy and simple to use. We were able to make a website for external users, without giving them training or an explanation.
- The ability to upload/download documents as transport papers and customs papers.
- The ease of developing. Development really speeds us up, and is very simple.
- The possibility to solve defects/do changes in a very short time.
- We had very much trouble with synchronizing data between an app in the central database. We had to take into account that the app was temporarily not online. Data synchronization gave us a hard time.
- Changing characteristics of data elements. E.g. if the length/name of a data element has to change, a new data element is created and we need to adjust all software using this data model.
- It's easy to maintain code.
- You save a lot of time while using OutSystems.
- As a developer, I would love to see a native solution for Service Studio in macOS.
- It can put an application into production in less time than other technologies, ensuring good performance and safety.
- It is a rapidly growing technology that has always available support to help its partners and customers no matter what the problem.
- It seeks to innovate with each version, and is always looking for new solutions to everyday problems by adapting new trends and introducing them into their development platform.
- I think the key point I would like to see improved would really be the issue of versioning. I think you can try to find a better solution to create versioning.
I think where I can say that it might be less appropriate, will be in mobile applications where you want very different things, with many effects being intruded. In OutSystems it turns out to be possible, but I think in these cases it is better to develop a native application. But be aware, today with OutSystems, you can develop great, and better, mobile applications.
At the moment, we use it for our drivers, for maintenance repairs, and for a select group of our customers. We have at the moment a fully functioning OutSystems applications within our company.
- The rapidity.
- The fact that you can easily make a good looking application.
- The flexibility.
- The vendor lock-in.
- Maybe integrate better with the Apple store.
- Rapid visible results
- Easy integration with APIs
- Customizing styles
- Development of interaction elements outside the "defaults" is a lot of work.
Less suited for rebuilding an entire application. This was our greatest mistake. Never rebuild. Build something next to it.
- Integration based on APIs.
- Architectural principles.
- The UI part for an eCommerce platform.
- Fast time to market.
- A better user experience, and easier to work with.
- It's easy to understand due to the modeling part.
- License model.
- Integrations with ie Kafka streams.
- The speed of results to show to end users.
- The ease of use even if you do not have any experience.
- More templates for non financial businesses.
- Very easy to start using OutSystems.
- Easy use of external APIs or to use JS
- Even if your computer is lost or damaged you can continue working with another computer
- Easy to test your apps
- Synchronizing from the local storage to the server database
- Implementation of other Code-snippets like Java or C
- Debugging Server actions
- The quick drag and drop way of building the application
- Easy way to deploy to next stage in development process
- Nice look and feel
- Upgrade to next version of product is slow
- Support doesn't communicate very well in an escalation
The following processes are managed within this system:
- Ecommerce / Mobile app
- Price calculation (sales and purchase)
- Time to market
- Low cost
- Easy to use
- Frontend HTML and CSS
- Dutch voice support
- Price of the product
- Super easy to use
- Saves time
- Automated testing
- Icons usage - they look quite outdated.
- Driving innovation, building applications and services to address our customer's needs
- Integration of internal applications
- ERP modernization
- Operational efficiency and process automation/improvement
- Custom applications which replace off-the-shelf solutions with are not extensively used (reduce licensing costs)
- Scalable: being a cloud native platform with great usability, scalability is almost unlimited.
- Innovation, releasing new features: the platform keeps developing, you keep getting more value for your money.
- Strong, solid technology. Performance has not been an issue so far at all
- Great usability and easy to manage.
- Adhering to the latest security standards.
- Support desk response times. We had several occasions with non-critical issues where we had to wait more than a week to get a proper response.
- Flexibility - We can do anything in it.
- Speed - The solutions are done much quicker.
- Quality - We make good user experiences both for our staff and our customers.
- The upgrade processes have been pretty painful.
- Visual insight in your code since it is modular.
- Quick but not dirty.
- Easy of use.
- Ability to peer review code changes.
- Integration with Okta.
- New templates.
- Easy to develop a new program without IT education.
- Easy to change parts of your program.
- Helps in fast digital transformation.
- More help in setting up the correct architecture.
- Problems with multiple developers working and then publishing the same module.