My splashscreen is just the first frame of a 2-second animation showing my developer logo. The program plays the rest of the animation before fading away and fading up to the main menu. My app is lightweight, so I don't really need this. Indeed, I don't even load most of the game components until after the animation is removed from the stage and from memory, but I can get away with the indulgence it because it's a game.
It's interesting to know that there is manual control over the splashscreen duration for cases when you want to be sure that the app finishes running through a constructor class or something, but you might want to consider an in-app animation display or loading screen instead, which runs concurrently. It solves your problem and adds a little class to the proceedings :-) But of course, I wouldn't know if that would be more or less efficient without testing multiple methods.
I'm curious to hear what you end up going with and why.
