<-- Back

How Offline-First works

Introduction

The term "Offline-First" refers to the app's ability to function offline after the initial setup, not during the first launch or cold start. This article explains the technical reality of how Offline-First works.

Environment

  • Native Mobile
  • Progressive Web Apps (PWA)

Details

Cold start requirement (By Design):

  • Every cold start requires a stable network connection to authenticate and fetch initial session data
  • The get_session_data call is synchronous by design and must complete before the app can proceed
  • This is a fundamental architectural requirement of the Mendix platform. The entire runtime depends on this session initialization completing
  • On slow networks (2G/3G and congested 4G), this process will take as long as the network requires
  • This applies to anonymous users as well. Even though no credentials are required, the platform still needs to establish a session with the server before the app can initialize

 
What "Offline-First" actually provides:

  • Once the initial data sync completes, all data is cached locally
  • Users can work completely offline until their authentication token expires
  • Changes sync back to the server when connectivity is restored

Internal information related

  • 268802
  • C07BE6K6F5L/p1767947474637239

Additional information

Mendix documentation: Offline-First Data

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.

To provide feedback, please open a ticket here. Don't forget to include the article's URL along with the feedback you would like to provide.