What is your primary use case for OutSystems?

We use the solution to automate some of our internal processes and to integrate with platforms like SAP and ServiceNow. We use it mainly for internal toolsets, streamlining repetitive tasks, and process automation.

The primary use cases are mostly related to the rapid low-code framework. Currently, I'm working on a business use case where we need to create a responsive website that enhances the customer's experience.

I am a consultant for another organization. We've been using OutSystems to develop in-house applications and a convention-type application.

We use OutSystems for developing applications that are used by clients in Canada, USA, and Europe. OutSystems has been very effective for us in developing both web and mobile applications. It has reduced our development time by around 30 to 40 percent.

OutSystems has use cases in the health care, accounting, banking, insurance, and automotive industries.

We used OutSystems to develop different applications, especially those concerning environmental and sustainability governance.

I use OutSystems in my company to develop web applications and mobile applications to be released by an insurance company.

The solution can be used to develop apps, websites, and core applications. We are working for an insurance company on an application to digitize hundreds of documents. We also work for a bank on an application to manage time and time sheets.

OutSystems is a versatile development platform that I find incredibly useful for various purposes. It is great for building both web and mobile applications, making it suitable for large enterprises and small to mid-sized businesses across different industries like banking, healthcare, manufacturing, and more. With its visual development, pre-built components, and easy maintenance, OutSystems has significantly expedited software development in my experience, offering a rapid and efficient solution for a wide range of applications.

My company uses OutSystems for developing mobile applications and web applications.

Wherever there's a mobile platform in use, there tends to be a fair amount of application activity as well. In these situations, we've observed that it's straightforward for us to integrate our systems, and this process is also highly consultative.

We use OutSystems for our customers in the banking and utility sectors.

We have been actively following the below strategy for our application development: * Core applications and systems (SaaS-based external products) * Bespoke Applications (using Microsoft Azure and Dotnet Application development technologies and tools) * Quick turnaround applications for web and mobile (Outsystems) * Portal knowledge and corporate portals (WordPress, SharePoint, DocuWare) * Cloud Platform (Azure and AWS) * Support within two hours on the community portal * Access to native functionalities (camera, geolocation, QR code reader, and access to file systems, address book, and device calendar) * Supports custom branding * Supports custom plugins * Silk UI response framework * Big focus on performance * Best practice for CSS and JS * Tested on several modern browsers and devices * Support and community (52000+ members, 500+ projects, and two-hour response time)

The solution helps to build mobile and web applications on SOAP and REST. You can integrate it with backend systems by submitting a code.

My client is the owner of the OutSystems platform, which we have utilized for various purposes, including an event app. This app tracks agendas, speakers, and registration for events.

I was only testing OutSystems.

We are using all aspects of OutSystems. We use it in almost all of our applications, application development, migration, and modernization. Basically, we use it for almost any traditional technology like .NET and Java.

My engagement with the solution was primarily as a private contractor for our banks. We were doing several RPA developments for banks. So they had some processes whereby they wanted to use a low-code approach. They wanted to create workflows out of that. That's what I was focusing on.

I'm using OutSystems to build an ERP system and a customer portal.

It is kind of used for reactive and web applications. We're also working on the mobile applications as well. I use it in a banking environment. I've been onboarded there and then I'm just doing the activities for both internet banking as well as mobile banking, handling both servers as well as the front end. Currently, this banking application can consist of both mobile as well as internet banking. We have it for eight different countries. For mobile, we have eight different applications, and for internet banking, it is a single application, however, it'll support eight entities in eight countries including Bahrain, the UK, Iraq, et cetera.

We use OutSystems for the same purpose as Mendix, but we recommend Mendix for mobile applications and OutSystems for B2C or B2B web portals. OutSystems has strong features for creating web-based portals or eCommerce marketplaces. Mendix supports Java, while OutSystems supports .NET. We are using the latest versions of OutSystems. We are partnered with Mendix and OutSystems. We have access to their partner portal, so we don't need to worry about developing applications, proofs of concept, or prototypes using OutSystems. OutSystems has on-premise and cloud versions. It can be deployed on AWS, Azure, or GCP. OutSystems is available as a Platform-as-a-Service, as well. OutSystems can be hosted on Azure, GCP, or AWS, and you can deploy OutSystems components on OutSystems PaaS.

We use the product for developing applications.

Our use case is mainly for the manual control systems. There are about 20 developers using this solution in my company.

We are a financial institution, and our primary credit solution is developed in OutSystems. We have several small apps, not for mobiles, but apps that are developed to support our core business, which is factoring and credit.

We are a reseller and OutSystems is one of the products that we provide to our customers.

For some of the business processes, we want the process owners to be able to set up their own flow-throughs, process flows, workflows, etc. They don't need to have any kind of prior coding experience. They should be able to establish workflows for their respective processes by just dragging and dropping elements.

One of our clients is a union, like a labor union, and therefore they're using it to develop an engagement-type app, for member engagement applications.

We have used OutSystems to develop a simple portal in the cloud. This portal is mainly for internal use and not for actual customers or external users. It's generally not for daily usage, so there's only a small team that uses OutSystems as their primary tool in their day-to-day work, but because it's open for any and all kinds of developers, there are probably hundreds of users throughout our organization.

We use OutSystems to analyze disparate applications that are about to become obsolete. As we currently can't afford it, we are still in the testing and evaluating phase.

We don't sell OutSystems as a separate solution. We sell it as a platform. And then you win a lot of solutions on top of it. So that can be a second process, it can be a middle phase, it can be a portal, it can be many things, but it is useful for small apps to complete ERP systems and everything in-between.

Created an operational-risk-management and issue-management application.

The primary use case is to build applications for internal users.

In the last months, OutSystems has become our primary development tool. Grendene is a huge producer of footwear and our development in OutSystems is supporting the construction of a large set of applications in these areas: Factory and production-level systems (industrial apps) There are already many applications built to provide information to our offices and for production control of factory processes, simulation, and machine setup. In addition to the already running analytics apps, we are in the process of integrating OutSystems with machines' programmable logic controllers (PLCs). We believe that OutSystems can support factory-level systems that respond quickly. Beginning with the less critical processes, we have already started to build web/mobile applications to be used on the assembly lines and loading docks in the distribution center. Integration and ETL There are many APIs built in OutSystems to provide process automation and information to internal and partner systems. An example is the Melissa branch website that is sustained by a third-party and the product profile is provided by OutSystems APIs. ETL architecture is also developed to synchronize data among some SQL databases and the company’s units. Business and ERP Apps Apps for business and ERPs are a fast-growing set of applications developed in OutSystems, accessed within the ERP portal. New developments are made in OutSystems using the ERP’s database as the information source and connections to many other specialized systems. Corporative Apps In addition to the above, there are many office processes, human resources, and product development/design teams that use OutSystems. Our "Careers" website was built in OutSystems with a dynamic approach that allows the human resource team to create and upload their own pages as a self-service website builder.

First and foremost, OutSystems is one of the most robust platforms I've ever tried. Our primary goal was to reduce the overall development time and deliver to the customer faster than anyone else can.

I use OutSystems' platform to build mobile apps for our customers as well as good old-fashioned web applications.

I use OutSystems to develop web applications. OutSystems is a low-code platform that lets you visually develop your entire application, easily integrate with existing systems, and add your own custom code when you need it.

Customer track and trace. We get information from SAP which is updated later by carriers (via EDI). The user interface is built in OutSystems.