OutSystems vs Studio Creatio Comparison

No coding... Integration

Service Studio can be improved...

Easy to read and maintain code, it's very visual and organized.

The only con I have is really the Service Studio. The team behind Service Studio should focus on stabilizing it.

The capability of producing code with small development bases.

Memory consumption and crashes on the service studio

The easyness thats give to the developer to understand the logic implemented. In other words, anyone that see the code for the first time can understand, without too much effort what are suppose to do.

The Imtegration studio (tool used to make integrayion with other libraries) seemsto be stopped in time.

Ease of use, rapid prototyping a easy deployment

General responsiveness is a joke, really easy to deliver a product with low quality standards, "code" merges are always a mess, the service studio crashes more often then not.

Outsystems allows a great level integration into the SDLC process. The tools are easy to use and allow us to produce high quality enterprise applications

The lack of ability customize certain aspects of the basic building blocks. The service studio should allow the ability for the developer to work in an offline mode as well.

It's great to develop quickly apps, without having the hurdle of any legacy problems. Fun to learn! Nice environment design studio to develop in Clear and gives overview Mobile apps with offline functionality are great

It's hard to design UX/design stuff yourself, it can be time consuming

I really liked the integrated workflow, particularly deployment (and the rollback functionality), and the fact that it already takes care of scale out scenarios, security, and other common headaches.

Is the Agile Platform for everyone? No, it isn’t. But for developers working on typical Web applications

-Easy to use and built in ui and template gets people up and running in few mins. -Structured development -Built in widgets prevents developers from developing the same components again and again (like pagination, menu bars, navigation and many more) -Focus on solving business problems instead of technical challenges -Code reuse is encouraged as AOs are tied to licensing -Deployment is nothing to worry about. Database scripts, versioning of code and migration all taken care by the platform -Refactoring is piece of cake with TrueChange. -Developing CRUD applications is a breeze but complicated applications can also be developed with ease. -Monitoring and logging taken care by default no setup is needed.

-Although custom code can be written via integration studio, it would nice if we could write code inside of the service studio itself. -Some features like event based programming or reflection or looping fields of an object could be supported as out of the box features -Updating shared extensions will result in all the applications (that are using the extension) being redeployed -For the mobile apps, it will be good if the apps converted to purely native. (only an opinion) -Could have licensing for individuals (free lancers) :D

Outsystems uses the latest UI designs so we can focus on building out the business process. We are able to deploy in on environment and then quickly send it over to a test environment for our customers to be engaged in the SDLC. Code changes and security enable quality deployment into our production environment and minimizes any breaks in our application.

You can sometimes reach a roadblock and the customer support might take a bit longer to answer your questions if you did not purchase the higher SLA support package. Certain bugs can occur when using the Service Studio but patches usually fixes it in a timely manner.

The speed in which we can deliver web and mobile applications for our customer, and the developer experience, where most repetitive work is taken care of by OutSystems. Also the fact that it is a complete platform with all the DevOps build in is great! Last but not least the OutSystems community is a very active community of professionals, help is always available very promptly why you get stuck.

Debugging capabilities not (yet) up to par with traditional development tools like Visual Studio, especially the ability to change values on the fly and to alter execution path. Then again visual debugging mobile application in an iPhone or iPad from my Windows developer laptop is amazing!

Business processes are easy to map and associate with business rules and the user interface. A very intuitive interface. Visual Studio integration is great, and application development is a much more manageable process. Built-in version control, repository contains all logic and business rules. Change management is less painful thanks to the abstraction of business rules within the system.

The cost was much higher than we could afford. This platform is ideal for larger development shops that need the efficiency of a well-managed platform.

I really like the OutSystems IDE. The developers have made it look great and it's pretty stable. I love how easy it is to set up the data structure then add basic pages. I really liked the training paths offered on the OutSystems website.

Low code is sometimes code for difficult-to-extend. I evaluated more than a dozen different PaaS companies in an effort to build a multi-tenant web-based application. I started to get the feeling that most of them catered to the insurance industry. While the out-of-the-box features can be very useful (albeit somewhat difficult to implement for a newcomer) extending the functionality of the platform is a nightmare. Also, while I really liked the training paths offered, the content tended to run a few versions behind. Also, they don't have great training videos on the more complex features. You get good (though dated) training on core functionality and you're left to your own devices on more complex methods.

Outsystems offers a low code, rapid application development and distribution platform. It integrates with all your existing systems and offers management and analysis screens within itself. Complex workflows can be designed using visual development tools. Another feature is that we can use the application we developed in both mobile and web environments. Complex workflows can be designed using visual development tools. Another feature is that we can use the application we developed in both mobile and web environments.

Requires training to use the system. Another disadvantage is that to develop applications, you need to install a program in your local (Service Studio). We develop the application using this program and deploy it to the cloud environment. It is easy to do these operations, the documentation is guiding enough, but making the application with the web interface is nicer and easier, as in quickbase and caspio.

No pros were added to this review

No cons were added to this review

Speed of Development Ease of technical implementations Open Community around Outsystems

Since I'm an expert Outsystems users, I don't like the initial responses of the support desk. It takes time to get to the right person at the support desk.

Integrated development, version control, packaging, deployment and hosting.

Documentation

No pros were added to this review

No cons were added to this review

Well, the motto is not mine, but I surely have to apply it in here: "The IDE of my dreams!" This is certainly a good reason to drive the adoption of the platform. Any developer keened to fulfill the business needs on time will surely understand the advantages of using it for development. The simplicity allied to the legibility of the written code in this IDE, reduce the gap between the business requirements and its materialization into lines of code. For last but not least, the built-in application Lifetime - which is part of the platform - is surely a gem for any DevOps team, providing them a powerful mean to control and to revert any deployment between environments.

Knowing that the road to perfection always ends up in the horizon, there are definitely two points that should be mentioned: the first concerns the lack of legibility of the application's Javascript and the second one, the lack of built-in Unit Tests. If your application is mainly a client-side application, written in Javascript, the platform may not be the right solution for it. In the other hand, if it's intended to execute all the business logic at the server-side, you should definitely spend some time evaluating it.