Start of Content Area

Procedure documentation Creating a Mobile UI Component  Locate the document in its SAP Library structure

Use

Mobile development for Handheld Applications uses standard Web Dynpro (WD), in which applications are built using declarative programming techniques. Mobile Applications for Handhelds support the WD concept, its development tools and a large subset of its model entities, and of the Web Dynpro Runtime API. Thus, any experienced WD developer can quickly develop user interfaces for mobile applications.

Note

Not all of the Web Dynpro (WD) model entities, UI controls, and their properties are supported by the Web Dynpro Runtime that is part of Mobile Client for Handhelds. For this reason, only supported objects are actually shown in the Handhelds UI Explorer. This helps you avoid modeling objects that can later not run on the mobile device.

More information: Supported UI Elements in the Developer Studio

Prerequisites

You have created a Mobile Service Component.

More information: Creating a Mobile Service Component

Procedure

1. Create a Development Component

To create a Mobile UI component, you first need to create an empty development component of type Mobile UI Component.

More information: Creating Development Components

2. Define the Dependencies of the Component

After creating the Mobile UI Component, its dependencies, especially to Mobile Service Components, must be defined.

More information: Defining Dependencies Between Components

3. Create a Web Dynpro Application

More information: Creating a Web Dynpro Application

4. Apply a Template to the Component Controller

By applying the Mobile Service Component Template to the component controller, the Web Dynpro (WD) model, the component controller context, all supply functions, as well as some convenience methods are generated from the Mobile Service Component’s service operations. You can then modify this code or continue with UI development.

Note

The template requires Mobile Service Components and can only be used in the composite development scenario.

More information: Applying Controller Templates

If the template’s generation output does not fit your needs, you can also create WD model, component controller context, and supply functions manually through standard WD means.

More information:

Creating a Web Dynpro Model

5. Define the UI and Navigation

User interface (UI) development and navigation follows the standard development procedures for Web Dynpro (WD) and employs the same development tools.

More information: Defining the UI and Navigation

Result

You have created a Mobile UI Component and modeled the interface. If the Mobile Service Component is also available, as required in the Composite Development Scenario, you can proceed with composing the application or build and deploy your developments directly on the Mobile Client for Handhelds.

End of Content Area