Internet Requirement:

To fetch the onboarding flow from the server, an internet connection is required. This is essential not only for retrieving the onboarding data but also for displaying the onboarding sequence and the paywall with products that follow. Both onboarding and paywall content are dynamically loaded from the server, ensuring they are always up-to-date.

Cloudflare CDN Integration:

We use Cloudflare CDN to ensure fast and reliable delivery of content globally. Cloudflare stores cached versions of your onboarding data across multiple servers around the world, which reduces latency and accelerates the load times by serving content from the nearest server to the user. This ensures a smooth experience, even during peak traffic or when users are accessing the app from various geographic locations.

Loading Speed Optimization:

To optimize the user experience, OctopusFlow loads the onboarding sequence efficiently:

• Initial Screen Load: Only the first screen of the onboarding flow is required to be loaded initially. This allows us to minimize load times, even on slower mobile connections such as 3G or 4G.
• Preloading: Once the first screen is loaded and displayed, we immediately start preloading the subsequent screens (including fonts, videos, images) in the background. This approach ensures that users experience minimal delays while progressing through the onboarding flow.

This technique enables fast and smooth onboarding display, providing the best possible user experience, even on mobile networks. We are continuously working on improving preloading mechanisms, so the experience will only get better over time.

Offline Mode:

In case a user loses internet connectivity during the onboarding process, they will encounter an error screen. This screen provides two options:

• Try Again: Upon pressing the "Try Again" button, the system will reattempt to load the onboarding flow. If the connection is restored and the content is successfully loaded, the onboarding will resume from where the user left off, with all progress preserved.
• Close: If the user decides to close the onboarding, the close event with "action_id": "error" will be triggered:

This ensures that the user is properly informed about the failure to load content and can either retry or exit the onboarding process gracefully.