Compact Development Scenario

In the Compact Development Scenario, a mobile application is developed as a standard Web Dynpro (WD) application.

The Compact Development Scenario is intended to make simple scenarios even faster to develop by avoiding the overhead of enforcing strict separation of business logic and UI layers. This is often desirable when developing test or demo scenarios.

The compactness is achieved by making data access and business logic part of the WD model itself and not placing them into a Mobile Service Component. In the Compact Development Scenario, the WD model is initially created by importing Data Objects from the Data Orchestration Engine (DOE) and then enhancing it by adding data structures and queries as dedicated WD model classes.

The user interface itself is subsequently developed in the same way as a standard Mobile UI Component in the Composite Development Scenario: WD's concepts, tools, meta-model, and APIs are used in exactly the same way

More information: Composite Development Scenario

The Compact Development Scenario does not support a set of features that are often used in the Composite Development Scenario:

• The WD template for generating the controller from the structure of dependent mobile service components cannot be used.

• Custom methods, such as validation logic can only be added indirectly within the custom code of the controller or as independent Java beans that are then imported as WD model classes.

• Strict separation of layers, which improve readability of the implementation and offer clearer separation of work in team development scenarios, is not available.