A splashscreen is shown when your app starts up, while the actual app views are being loaded. Currently splashscreens are defined in the AppGyver Build Service, separately for each cloud-deployed application. When you build a new Ad Hoc or App Store build, the uploaded custom splashscreens will be used instead of the default AppGyver splashscreen. If you build a custom Scanner build, the custom splashscreen will be used also when loading an application by scanning a QR code.

There is currently no way to set up a custom splashscreen for a Supersonic project without using the Cloud Build Service. In the current Steroids app architecture, the splashscreens are set up when the app binary is built, and thus cannot be changed dynamically for apps loaded with the store-downloaded AppGyver Scanner.

iOS Splashscreens

For iOS splashscreen configuration, see the iOS Build Settings guide.

Android Splashscreens

Android supports a special 9-Patch image format, which can be used to create splashscreens that scale to various display dimensions without distorting the image. For info on creating and configuring Android splashscreens, see the Android Build Settings guide.

Programmatic Usage

Splashscreens can be hidden and shown programatically with the supersonic.app.splashscreen API, the full reference is appended below.

API Reference: supersonic.app.splashscreen.hide()

Hides the splashscreen programmatically.

Example usage



supersonic.app.splashscreen.hide: () =>

A Promise that is resolved when the splashscreen is hidden.

Also supports callbacks.

API Reference: supersonic.app.splashscreen.show()

Shows the splashscreen programmatically.

Example usage



supersonic.app.splashscreen.show: () =>

A Promise that is resolved when the splashscreen is shown.

Also supports callbacks.