1. Mobile app development capabilities

The OutSystems low-code platform enables enterprise-grade mobile application development with capabilities that span four key categories:

  • Mobile apps: These apps can be installed on users' phones, with access to device sensors, offline functionality, and native user experience for Android (APK) and iOS (IPA) all with a single IDE and visual language.
  • Progressive web apps: Accessible through mobile browsers, these apps adapt seamlessly to different devices and browsers without installation.
  • UI/UX: The part of your mobile app that engages users and enables them to accomplish tasks, order items, and much more.
  • Mobile frontends and backends: These support custom native mobile apps built both with the OutSystems platform and industry-standard tools like XCode, Android Studio, or Visual Studio, and respective native languages.

Table of contents

Simplified cross-platform mobile app development

With OutSystems, you can develop mobile apps that are deployable and functional on iOS and Android devices. These apps automatically adapt to varying form factors, maintaining consistency and using a unified code base. Developers implement client-side logic and local data storage, and craft the UI and front-end code just once. This eliminates the need to modify the codebase for individual devices.

To enable this streamlined process, the OutSystems platform generates highly performant applications with an optimized responsive JavaScript application at its core, wrapped by a native shell that deals with all interactions with the device, offline data, and logic.

mobile and web application dashboard

Native app development options

To create native mobile apps with OutSystems, you don’t need a Mac to build your iOS app, nor do you have to install Java and Android Studio to build for Android. Instead, all you do is configure the app, add your keys or certificates, and click a button. The platform takes care of generating native builds for Android and iOS with all the required content and plugins. OutSystems native apps are constructed on the Ionic Capacitor and Apache Cordova frameworks, which allow developers to access a wide range of native device functions for their apps seamlessly. They simply refer to the git repository for the plugin, and they’re good to go.

ios mobile app development

This access includes geolocation, camera, notifications, barcode scanners, beacons, and more, all made possible by the simplicity of the OutSystems language. There are three types of plugins developers can use.

Platform-supported plugins are available on the OutSystems Forge and are certified and fully supported by OutSystems.

Community-supported plugins are uploaded to the Forge by members of the OutSystems Community, which also provide best-effort support for them.

When the plugin you need isn’t available on the Forge, you can create your own. Simply select from one of the thousands of available Capacitor or Cordova plugins, add your GitHub address, and wrap the plugin code with an OutSystems API. From there, the new native functionality will be available in all your OutSystems apps. If the business requires something very specific, it’s possible to create a new custom plugin. Check out these articles for more information on using existing plugins and building custom plugins.

example of mobile app plugin in action

Learn more about the array of available plugins for your mobile applications

Offline functionality and data synchronization

OutSystems provides all the tools you need to build applications that run offline or in poor network conditions. You can quickly and easily model all offline requirements for everything from a very simple app that just caches data and content for performance to very complex apps that do offline calculations and require complex conflict resolution. As a result, the platform enables you to overcome the following challenges:

  • Limited space for storing data locally
  • Data synchronization between devices and the server
  • Data conflicts and outdated client-side code
  • Security of sensitive information

Applications built with the platform automatically store all the application's content on your device for performance and offline access, and the OutSystems visual language provides everything you need to control which data goes to the device.

user's device with offline access

To address the limited space on data stored locally, OutSystems allows you to visually define the information you want to store on the device. This means you have total control over which data should be stored offline without losing the speed and flexibility of the visual language. Data on the device is stored on a local database, using SQLite as an underlying technology. There are no limits to how much data is stored other than the physical size of the storage, and data remains even if the app is closed, the device is rebooted, or power is lost.

Likewise, all data synchronization is done with the OutSystems visual language. You have control over when the synchronization process occurs, and you have full flexibility to use the synchronization pattern that matches your business specification, no matter how complex. This process can be started by your application at any time, or automatically in specific instances, such as when the user logs in, when the application starts, or when connectivity to the server is restored.

application runtime architecturemobile app offline functionalities

This diagram outlines the runtime architecture of a typical application built using OutSystems with offline support. The native application includes all the resources required to run standalone from the server without any connectivity. When connectivity is available, the application will automatically check for newer versions of the resources and update itself—which you can also control and customize.

To address conflicts, the platform enables you to use a synchronization pattern where:

  • The server database holds the master data that can change over time.
  • The local storage database holds a subset of the master data and can be modified.
  • Synchronization sends the modified data from the local storage to the server database and vice versa.
  • In the server, data is updated and any conflicting changes are registered for later resolution.

When the server-side code changes (but the data doesn’t) and the client is running an older version, synchronization updates the client by sending the new or modified code from the server.

If there is a need to secure sensitive information, you simply activate the data encryption on your application. This will ensure secure 256-bit AES encryption of your data on the device.

On the back-end, REST APIs are automatically generated and exposed to enable the client to send and receive data from the server. These are secure APIs that ensure only authenticated users can start the synchronization process, and all connections run over SSL so data remains secure.

Mobile-specific debugging tools

To debug native mobile capabilities, such as mobile plugins, OutSystems provides specific debugging capabilities for both Android and iOS. In both cases, you’ll need to establish a connection to the actual device, typically through a USB cable. These options enable you to debug and troubleshoot your app's behavior with greater precision, aiding in the discovery, comprehension, and resolution of issues. They allow you to actively interact with and utilize the device's hardware and sensors, such as the camera or GPS location.

To learn more about debugging applications built with OutSystems, check out our technical documentation.

Progressive web app distribution

Progressive web applications (PWAs) are a type of application delivered through the web, built using common web languages, including HTML, CSS and JavaScript. Because PWAs can work offline, send push notifications, and access device hardware, their user experiences are similar to native applications.

During the development of a mobile app using OutSystems, developers can enable PWA distribution, and the PWA will automatically be prepared for use and fully compliant with Lighthouse, Google's open-source automated tool for evaluating web page quality. Since OutSystems and the OutSystems Community are consistently expanding the range of components that support native and PWAs, you can use a single code base without the need for additional specific logic, and the same mobile plugin will function in native applications and PWAs.

PWAs built with OutSystems are an excellent match for specific scenarios, given their numerous advantages:

  • Faster and simplified distribution: PWAs bypass the need for public store (App Store, Google Play) upload processes and approvals.
  • Sharing and discovery: PWAs are easy to share via URLs (including on social media) and can be indexed by search engines, making them easier to find and grow organic traffic. They’re also a strong option for organizations that want to distribute internal mobile apps without going through an app store.
  • Fewer installation hassles: Users access PWAs directly from a web browser—no app store needed. This lowers barriers to entry and fosters increased engagement.
  • Ongoing updates: Being web-based, PWAs are automatically updated, sparing users from manual app updates.
  • Minimal impact on device resources: PWAs are not installed, so they don't use many device resources. This is advantageous for users with devices that have limited storage.
今すぐ利用を開始無償トライアル評価ガイドTOPモバイルアプリケーション開発モバイルアプリ開発機能評価ガイドTOPOutSystemsを選択すべき理由Getting Started with OutSystemsOutSystemsを使用した開発セキュリティOutSystemsのデプロイアーキテクチャライフサイクル管理PerformanceScalabilityIntegrationモバイルアプリケーション開発モバイルアプリ開発機能モバイルアプリのライフサイクル管理Artificial IntelligenceOutSystemsのクラウドサービス前へモバイルアプリケーション開発次へモバイルアプリのライフサイクル管理トップへ戻る