• Single Screen Limit: Only one Offline Screen role can be assigned per project.
• Connection Status: Automatically activates when the internet connection is lost. Even if the connection is restored, the user must manually switch to the Online Screen.
• Device Features: Hardware features such as the camera or GPS can be used. However, backend calls that require internet access are not supported.
• Actions: Only Client Side actions can be used. Server Side actions are not supported.
• Platform Compatibility: Only applies to Android and iOS mobile applications. Cannot be used in web applications.
• SQLite Offline Recording: Screens marked as Is Offline write data directly to the local SQLite database on the device.
• Automatic Synchronization: Data recorded in offline mode is automatically transferred to the server via a defined sync mechanism when the connection is established.
• Offline Editable Tables: Tables marked with Enable Editing are downloaded as editable in offline mode, and any changes made are sent to the server during synchronization.

1. Screen Design:
   
   • Create the screen that will work offline in Designer.
   • Add images via the Image Library instead of the API.
   • Do not use elements and actions that require the internet.
2. Role Assignment:
   
   • Go to the Properties panel of the Screen.
   • Enable the Is Offline option.
   • The relevant screen automatically takes on the Default Offline Screen role.
3. Data Configuration
   
   • Select the tables to be used offline.
   • Download only the schema structure with the Schema Only option.
   • Enable Enable Editing for tables that need to be edited.
4. Platform-Specific Compilation:
   
   • Export the application for iOS or Android.
   • When the device loses its internet connection:
   • The user is notified.
   • The Offline Screen opens automatically.
   • Data begins to be written to SQLite.
5. Navigation and Design Details:
   
   • Manual Navigation: Navigation is not automatic in the Offline Screen; manually add buttons to inform the user.
   • Online Mode Transition: Add a button that directs the user to the main screen when the connection is established.
   • Master Page Integration: Manage common components with the Master Page.
   • Status Information: It is recommended to add an icon or text that clearly indicates to the user that they are offline.

By following these steps, you can ensure that your application provides a user-friendly and functional experience even in offline mode.