- Screen Design: First, the screen that will work offline is designed. The screen is organized to support the offline functions of the application.
- Determining the Offline Screen Role: The Offline Screen role is assigned from the Properties panel of the designed screen. The role allows the screen to work in offline situations.
- Platform Specific Compilation: The application is compiled for iOS or Android. When the application is run on an Android or iOS device, it automatically switches to Offline Screen by showing a notification when the internet connection is lost.
- Design and Usage Details:
- A Standalone Design: Offline Screen should be designed to work without the need for an internet connection. For example:
- You should use images from the app's Image Library, not from an API.
- There should be no actions or elements that depend on an internet connection.
- Manual Navigation: All navigation on Offline Screen should be organized manually. For example:
- An exit button should be added on the screen for logging out.
- Master Page Integration: Offline Screen supports the Master Page structure. This integration allows common components (e.g. header, footer or menus) to be easily added during Offline Screen design. Specifying a common structure via Master Page during design ensures a consistent user experience across all screens.
These steps ensure that the application is user-friendly and functional in offline mode.
