One Screen

Screen Navigation that navigates to a new Screen is the most common in mobile development. Usually, when the user taps on a button or when an event happens (for example: successful login), the application navigates to a new screen, which in Kodika is called destination screen.

Each Screen Navigation has some specific properties that you need to fill in order for it to work efficient and reduce bugs and development time. These are:

1. Screen Navigation Name (Optional)
2. Destination Screen
3. Presentation Style
4. Use of Navigation Controller
5. Animation options

Screen Navigation Name

The name of the created/edited Screen Navigation helps you differentiate one Screen Navigation from another. This property is not shown to the users.
Tip: Screen Navigation Name is optional, and you can leave the field empty to autogenerate a name based on its properties.

Destination Screen

Destination Screen is the most important property. It is the new Screen that the application will show when Screen navigation is triggered.

Presentation style

In order to understand the presentation style property, we will need to explain how Screen navigation stacks work. There are 3 different ways to navigate to a new screen.

1. Clear stack, and set the new Screen as the only Screen in the stack.
2. Push the new Screen in the navigation controller’s stack.
3. Present the new Screen on top of the current Screen.

Set as Root Screen

Set as Root Screen clears the current stack, removes all previously presented screens, and sets the Destination screen as the only Screen in the stack. This means that now there is only one Screen in the whole running application and the user cannot go back to previous screens.
Tip: This presentation style is usually useful when you don’t want the user to go back to the previous stack. For example, after a successful login, you don’t want the user to back again to the Login Screen without logout.

Push in Navigation controller

It presents the Destination Screen using the navigation controller. To go back to the previous Screen, you need either to have the default navigation bar enabled or manually implement the pop screen action.
If Animation is enabled, the new Screen will appear using a right-to-left animation.

Note: For the Push in Navigation controller to work, the current Screen that triggers the Screen Navigation should be part of a navigation controller’s stack.

Present Modally

It presents the destination screen on top of the current Screen without clearing the stack. If Animation is enabled, then the new Screen will appear with an upwards animation.

Flip Horizontal

It presents the destination screen on top of the current Screen without clearing the stack. If Animation is enabled, then the new Screen will appear with a horizontal flip.

Dissolve

It presents the destination screen on top of the current Screen without clearing the stack. If Animation is enabled, then the new Screen will appear with a dissolving animation.

Create Navigation controller

For the new Screen to be part of a navigation controller’s stack you will need to enable this option.
Note: You cannot use the Push in Navigation controller style when this is enabled.

Animation

Enabling the Animation property means that all the animations mentioned in Presentation style while showing the Destination Screen will occur. If disabled, then the Destination Screen will be presented without any animation.

Transparent

If enabled, the parent screen of the Destination Screen will be visible in cases where the destination screen is not fully opaque.
Tip: This property can only be useful in the Presentation style cases of Present Modally, Flip Horizontal, and Dissolve.
Note: You need to have a transparent background to the new Screen.