Not an issue: No need for secondary splash screen

[Ahmed-gubara]

Thanks to this comment by @0x48Maciek

You can keep native splash screen as long as you want by the following code:

Future<void> main() async {
  final binding = WidgetsFlutterBinding.ensureInitialized();

  // Prevents app from closing splash screen, app layout will be build but not displayed.
  binding.deferFirstFrame();
  binding.addPostFrameCallback((_) async {
    BuildContext? context = binding.renderViewElement;
    if (context != null) {
      // Run any sync or awaited async function you want to wait for before showing app layout
      await Init.instance.initialize(context);
    }

    // Closes splash screen, and show the app layout.
    binding.allowFirstFrame();
  });

  runApp(...);
}

class Init {
  Init._();
  static final instance = Init._();
  Future initialize(BuildContext context) async {
    // This is where you can initialize the resources needed by your app while
    // the splash screen is displayed.  Remove the following example because
    // delaying the user experience is a bad design practice!
    await Future.delayed(const Duration(seconds: 3));
  }
}

[jonbhanson]

Thank you @Ahmed-gubara! I will add this to the documentation.

[justinenerio]

Thanks for this update! One thing, can you expose BuildContext in initializeFunction. It can be useful for precaching images.

[jonbhanson]

@justinenerio thanks for the suggestion. I made an update that exposes BuildContext as you requested. Please let me know if it works OK.

[justinenerio]

Looks great, works as intended. Thanks!