iOS manages the first frame through a `LaunchScreen` storyboard (or `UILaunchScreen` in Info.plist); Android has done it via the `SplashScreen` API since Android 12. Both share one constraint — this has to be a completely static snapshot, no network calls, no text that changes at runtime. It's closer to the word's original sense (a single splash) than to a progress indicator.
Because the system draws it before your own code runs, there's a hard limit on how much the logo can be animated — Android 12+ ships a built-in zoom-out transition for the icon, but anything beyond that has to be handled by app code once the real first screen takes over.
The most common mistake is treating it as a branding opportunity and adding a long fade-in or spin. That only slows down how fast the app feels to open — show it as briefly as possible and hand off to real content, or a skeleton, as fast as you can.
When to use
Use it only for a cold start — actually launching the app. Don't reuse it for screen transitions or data loading; a spinner or skeleton belongs there instead.