- Deployment management – OutSystems has a built in robust, multi-environment deployment system that helps ensures the clean and error free deployment of applications through the development, testing and production product lifecycle
- Rapid application development – Through the low code, graphical development environment you can develop applications far quicker than with more traditional development environments
- Cross platform mobile development – OutSystems handle the development and building of mobile application for both iOS and Android in a simple streamlined way that removes 90% of the problems normally associated with multi platform development
- Price – The licensing model of OutSystems is very expensive and not suitable for small scale developments. This is offset by the time to develop and stability for larger scale developments
- Flexibility on PaaS version – The PaaS hosted version of OutSystems limits your flexibility to access the front end and backend database systems which can significantly restrict your options on high data volume developments or where anything requiring slightly out of the ordinary access is required
- Same price for PaaS and self-hosted system. Licensing model dictates that you pay the same price even when you host the system on your own hardware which effectively means you pay more to manage the infrastructure yourself
OutSystems is extremely well suited where you require a fast time to market combined with a robust deployment process. It also provides enterprise grade redundancy and vertical scalability with SLA’s approaching those available with any other tier 1 application.
OutSystems is not well suited for small scale or “cheap” application due to it’s high “per object” licensing costs and minimum license fees.
- Simply develop fast and deliver apps so you benefit with extreme short time to market.
- Maintainablility is even better compared to traditional development tools.
- Work on the same module simultaneously without losing code by useful compare and merge options.
- Well working staging / development tooling available in the form of Lifetime.
- Fast learning curve, especially for experienced developers bu also for complete newbies.
- Come up with a license model for SME. Now only medium and large companies are in focus. The basic license is just too expensive.
- Introduce reporting tooling.
- Being low-code, even people without any experience can start building with OutSystems immediately.
- OutSystems has a great and very helpful community, giving advice and pre-build features to beginning engineers.
- OutSystems is very flexible and easy to use; it enables us to build something useful within minutes.
- Being relatively new in the IT world, I could use some kind of quick reference guide inside OutSystems (instead of going to the website or forum)
- Filtering aggregates could perhaps be done in an easier way. I struggle with them, sometimes.
- I'd like more pre-made layouts.
Our applications/customers are from all types of business so we don't have a specific business problem.
- When we present a MVP to our customers most of the product is almost done. With the tool we can make a very fast product and with a very good quality.
- The development of and application web or mobile is very intuitive and very easy to implement. One example is our survey application: on the web part is the back-office to create the survey and the mobile is only to reply to that specific survey.
- Sometimes we face some problems to integrate external applications in our outsystems product.
OutSystems has become the core platform for two different start-ups that I did in the past 3 years. At first, we needed a revolutionary way to create new innovative solutions & products at a speed never seen before. These new products needed to go from idea to market in weeks not months.
Enhancements need to rollout in days not weeks. Specifically, the products and services we created are B2C and B2B for Dental & Vision financial products and healthcare provider customers.
As we had amazing success creating products & services for our B2B2C customers, we then decided to forego SaaS-based Sales, Service, and B2B On-boarding and we built it ourselves using the pre-build sales & cases apps (from OutSytems) and the BPM capability in OutSystems for B2B On-boarding.
In short - at the startup that I did, we are using OutSystems as the core for the entire business and integrating it with 3rd party services like Office 365, Google G-Suite, RingCentral, etc.
- Skip prototyping phase - we create very quick designs that actually use our brand standard experiences and connect to real or stub services directly in OutSystems. We've found we co-create in OutSystems. The result is our "prototypes" are really 1st release candidates.
- SWAGGER 2.0 - AWESOME! If you have access to swagger APIs, integration is so very simple, fast, and robust. Click click click - done! Then the swagger API looks just like any other module that your app needs to access.
- Web, Mobile-Web, and Native all in ONE platform. We all have heard the dream and promise of "write once, run everywhere." OutSystems is the closest I have ever seen us come to that vision in almost 30 years in software. We truly have ONE module for Web & Mobile web (all responsive out of the box with SilkUI). We truly have ONE module for both Android and iOS thanks to the ReactJS-based solution from OutSystems.
- LOW-CODE Heaven: No longer to we spend our life slinging code. Now, the OutSystems "robots" generate all the code for us. I will say it's super clean too. I tried to hand-build code that runs faster... I couldn't. On average, OutSystems generated code was 40% faster than mine both on the .NET and SQL side.
- This is a hard one - I'd say continue to expand support and integration of micro-services. It's come a long way and certainly works - but keep on pouring the gas on micro-services as it's a huge part of our ecosystems.
It's excellent as a "swiss army knife" for creating everything from high-end native mobile apps to responsive web apps and even headless API services.
The built-in BPM is a good general purpose solution if you need it embedded in your apps. However, if you have extremely complex and large-scale BPM needs that span large organizations, you may want to consider a specialized BPM and have OutSystems create the user experience and connect into the 3rd-party BPM.
- Time to market
- Fast to integrate with other softwares
- API enabled allowing you to expand the software
- Easier than code
- Managing the Database. Sometimes it crashes when you remove a populated column (what it should) but it should also try to truncate it first and then remove it. Same happens when you change a column type or name.
- The BPM sometimes takes time to start and you don't know what's is hanging there.
- They allow their customers to share information about issues and fixes to reduce downtime and obtain a wider view of the capabilities of the products through a customer posting section on the OutSystems website.
- OutSystems also holds conferences during the year at different locations making it easier for customers to interact and openly discuss what they have learned and how they have used the product.
- OutSystems also has resources that can be contracted to help a company get started using their products very quickly.
- Because OutSystems is growing so quickly it can be hard to get business questions, (contract issues, availability date), answered quickly.
- It is sometimes difficult to find employees with OutSystems product experience.
- Rapid build
- Ease of deploy
- Intuitive flow based IDE
- Can get Base level of dev skills quickly
- Expert support required (supplied as part of the purchase)
- Requires considered cost-benefit analysis before purchase
- The platform has vast capabilities, requires external expertise to get up to speed
- Complex logic that is easy to read
- Code easy to debug and mantain
- Fun to use and easy to learn
- One of the aspects that have been evolving and I think where there is still much to be done, are improvements related to developing and maintaining CSS classes. It is not possible to merge CSS files, some styles are not well interpreted by the IDE; even the creation of new CSS classes could be improved.
- Another aspect I would like to see improve is lifetime performance, and also more features like new analytics performance and adoption metrics.
- Low code makes it really fast and visual.
- Version and deployment management out of the box.
- Great patterns and solutions available to be re-used and adapted to the [business] needs.
- Mobility is done by using Cordova. It has great functionality, but sometimes you need to have more interaction with the device
- End user's API is developed more quickly in Outsystems.
- Business processes are well handled by Outsystems.
- Agile concept.
- Timers may be handled in another way. Sometimes when there are problems, it seems that the timer is still running but actually it's not. The Service Center should be improved to give more options and feedback about the times when it is still running or allow users to stop timers.
- It would be an improvement if I could set up a timer to run more than 3 times from the service center.
- The entities are accessed directly from the web screens, it should have another concept that abstracts it. Instead of entities, another technical element like 'view' should automatically be created. With this new technical element, only 'view' is used in he web screen preparation.
- Single platform for Web, IOS and Android development.
- The platform allowed us to give analysts the ability to develop the solution directly.
- Application lifecycle management no longer requires dedicated people.
- The pricing and metrics around which the platform is priced is expensive and not suitable for all project types.
- The development interface does not work on MacOS, and requires you to run a Windows Virtual Machine.
- Installing the on-premise software is relatively complex.
- Great user interface, accessible via mobile and web applications.
- Easy communication with other core systems, making it a really good option to interact with older systems. This gives them a great lift up with the Outsystems user interface.
- It is very easy to transform business cases in technology.
- Great database management.
- Strong community where problems can be addressed
- In mobile applications, it should be more easy to integrate with existing browser capabilities.
- It should be easier to move entities and business processes across different applications.
- Should provide more testing capabilities, like, an easy way test business actions without having to publish.
- The out-of-the-box functionality that processes a SOAP endpoint is very useful.
- The functionality of using one application as a dependency of others.
- The low code functionalities.
- Projects that use native cordova plugins sometimes have lots of conflicts generating native mobile apps.
- The merging system when working with other developers.
- The customization system has to be more extendable to other non out-of-the-box features.
- Unbeatable speed, with a special focus on deployment (not just on coding), DevOps and response to change requests.
- Unbreakable. Really, you'll have to put in a big effort to get it to break.
- Happy, motivated team that always says "Yes!" when something new comes up!
- Integration Studio (one of the IDE components) needs a revamp.
- The platform is too server centric, should evolve to containers so it could go more easily to private cloud.
- The licensing model is a bit overwhelming for some smaller companies that need to get their use cases really valuable.
- Very well suited for web and mobile apps
- Not a good document management system
- Extremely fast to prototype ideas.
- Develop beautiful user experiences with very little efforts.
- Integrate very well with legacy applications.
- The licensing model is complicated.
- Developer community in our region is limited.
- More UI widgets for mobile.
OutSystems platform is not that well suited for gaming kinds of applications, augmented reality apps, or intensive 3D Graphics kinds of apps.
- Very easy to create and use tables (we are using Oracle on the backend).
- Creating and using web services is very effective (doesn't matter if you are exposing or consuming web services).
- Creating a mobile application is so easy and fast.
- License costing is a bit high, but again value for money.
- Solution deployment time is a bit high.
On a personal level, I developed a survey-like Facebook app for my master degree thesis because it was fast, easy and I was familiar and comfortable with the technology.
- Integration with external systems like SAP and REST webservices. Data is easy to read, edit, delete...
- Web development is really fast and the starting point alone saves a week of work with sessions, logins, acess management...
- App development is now cross-platform (iOS and Android only).
- There is a single community of OutSystems' experts online, so support is much faster than finding the right site to ask. You just need to search for the right topic in the forum.
- You can connect to several database technologies, generate code in .Net or Java, and there is no lock-in.
- It is so much faster (officially 6 to 10 times, but it feels more).
- There is a list of improvements suggested by the community on the site.
- Native apps to Windows Phone are missing.
It is not recommended when only small adjustments are needed to existing sites/apps because the 6 to 10 times faster time to build new apps would probably be worse than the adjustment to something that is almost ready.
OutSystems Scorecard Summary
OutSystems Support Options
|Free Version||Paid Version|
|Video Tutorials / Webinar|
OutSystems Technical Details
|Deployment Types:||On-premise, SaaS|
|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|