App Designer

The App Designer is the central starting point for low-code application development. This is where you design the interface of your application, implement functionalities, and integrate data from resources.

The App Designer is the starting point for the following actions:

  • Building mobile and desktop applications

  • Creating new HTML5 UIs

  • Updating the existing UI

The App Designer is a low code building environment that meets the requirements for programming apps of almost any level of complexity.

In the App Designer, you drag and drop components to build an application. You can use the following component types:

  • Resource components, for example, to use JavaScript and RestAPIs

  • Highchart components to create graphs and plots

  • Bootstrap components to design and structure your application and give it a non-SAP look and feel

  • OpenUI5 components to design and structure your application

  • Custom components for developing applications in fragments that are reusable

Application types

You can develop the following types of applications in the App Designer:

Application

These applications are the typical and go-to choices for developing solutions using a low-code approach. They have the capability to run both as stand-alone applications and on a launchpad.

Adaptive template

This type is meant for creating templates that represent the foundation and structure for different types of adaptive applications. Read more at Adaptive templates.

Launchpad

The launchpad application is similar to the adaptive template but its purpose is to develop a general custom launchpad to host your application. Neptune DXP - Open Edition provides you the standard version and is also available in the Neptune DXP Marketplace

Application building block

Application building blocks provide quick-to-implement sections of user interfaces or logic that can be added to any application to speed up development. Read more at Application building blocks

Custom component

Custom components are a way of creating reusable components in the App Designer. Similar to building blocks, they can be added to any application, but their content is stored in a single object within the App Designer tree and cannot be directly edited. When a custom component is updated, all applications using it will be marked as updated and will incorporate the changes upon their next load.

Further custom components can be added to parent custom components as child custom components. To avoid cyclical relationships, a parent custom component cannot be added to a child custom component that is already contained in the same parent custom component. As long as you avoid creating cyclic relationships, the App Designer supports extensive nesting of custom components.