When the splash screen disappears in Native Mobile Beta?

[reunisens.reunion]

Hi everyone,

I’m trying to understand what exactly happens behind the splash screen in the Native Mobile Beta builder.
Right now, my app takes several seconds to load (especially the first time a user downloads and opens it). That’s a big issue for user acquisition — most users quit before even seeing the first screen.

So I’d like to confirm:

• When exactly does the native splash screen disappear?

• Is it directly linked to when the root view finishes loading/rendering?

• If I make my root view extremely lightweight (just a simple static layout or loading bar), would that help reduce the perceived loading time and make the splash disappear faster?

In other words, can a minimal custom “fake splash” view, set as root, speed up the transition between the system splash and the first interactive screen ('“fake splash” view) ?

Any technical clarification from the Bubble team or someone who’ve profiled this behavior would really help.

Thanks in advance.

Arthur

[reunisens.reunion]

Here’s what I found after testing things myself:

The system splash screen actually stays visible while the root view is loading in the background. So if your root view is making heavy database calls or loading lots of data, the splash screen will remain until all that’s done — which makes the initial load feel painfully long.

To reduce that friction, I created a second lightweight “fake splash screen” view and set it as the root. It only displays an image, a few texts, and a short countdown before moving to the real content.

Result: the system splash screen dropped from 20–30 seconds down to about 5 seconds, then the homemade splash adds another 5 seconds — but those are controlled and smooth.

If anyone has run similar experiments or found other optimizations, I’d be glad to hear and discuss them.