Traditional web apps are slow, not available offline, and cannot be installed on smart phones. They must be fully reloaded after each closing. As a result, they become unavailable for many use cases and are being replaced by native apps from the App Store. Native apps must be redeveloped for each platform. Web apps, on the other hand, are platform independent.
They run device-independent via the browser. The so-called Progressive Web Apps (PWAs for short) are enriched with various functions. These offer all the advantages of native apps without having to be developed several times.

What is a Fiori or UI5-Web app?


  • “classic” web application, developed with the SAP UI5 framework
  • The SAP UI5 framework offers ready-made interface elements that adapt to the end device (smart phone, tablet, desktop) in terms of appearance and function
  • The UI5 apps will open in the browser
  •  The interface design is defined in the SAP Fiori design guidelines

What are the disadvantages of a Fiori or UI5 web app?

  • As all websites, it comes without offline features. The app cannot be used or loaded without an internet connection.
  • Depending on the end device, full access to interfaces such as push notifications and background updates is not possible via standard web apps. Either native apps are developed for this or PWA functions are required.

What is PWA?

Progressive web apps are created from web applications such as the standard SAP UI5 apps. For this purpose, the applications are supplemented with a few features and can be installed and used as native apps from the app stores. In contrast, however, they do not require an app store and do not create any additional costs for development and maintenance on any platform.

The greatest strengths of PWAs:

  • Offline Features:
    • Data can be backed up at any time. If there is no network, they will be first cached on the device.
    • Calling up and loading the app is also possible without a network connection.
  • Access to device interfaces enables functionalities such as Apple Pay, Google Pay, push notifications, background updates and also access to device hardware such as Bluetooth, fingerprint sensors, face recognition and temperature or acceleration sensors.
  • Very high performance due to the use of multiple threads in the browser.
  • Real “app feeling”: The application is first installed on the device and as an app from the App Store can then be started via the tile on the home screen. It no longer needs to be called up via the web browser.

What are the differences between PWA and native apps?

Native apps can use all resources released by the device manufacturer and are therefore more efficient and high-performance than browser-based apps. On the other hand, there are high development costs as native apps are developed separately for all platforms. PWAs are highly available and can be installed on any device via any browser. The performance of web apps – and thus the PWAs – has developed very positively with ever faster browser engines and can keep up with native apps. Native apps can only demonstrate their advantages in applications that require a lot of performance, such as rendering software.

What distinguishes PWA from the alternatives SAP Mobile Platform and Cordova?

The SAP Mobile Platform (SMP) offers many of the PWA concepts as ready-made components. This reduces development time for native apps. Cordova is a native app and is used as a wrapper around existing web apps to be used on mobile devices with increased functionality. Originally, in 2009, Cordova’s raison d’être was due to the browser’s poorly developed hardware interfaces.

Advantages of SMP:

  • Central management of mobile applications in the SAP environment
  • Fast creation and extension of the apps
  • Easy connection to SAP ERP or S/4HANA
  • Many integrated services and tools
  • Simplified integration of existing business processes

Disadvantages SMP

  • Increase in system complexity
  • Integration and maintenance in an existing system landscape is time-consuming

PWAs combine the advantages of SMP and Cordova and are significantly simpler. Like all UI5 apps, they are made available via a SAP gateway and do not require any additional tools or containers.

Conclusion: SMP / PWA / Cordova

With the further development of browser technology, there will be more and more interfaces available in the future, via which web apps and thus PWAs communicate with the hardware of end devices. Therefore, they approach native apps in terms of user experience and available functions. Ultimately, PWAs will gradually become more prominent in the future. They are preferred to native apps, due to the lower development and maintenance costs.