[removed151214]

I still think it's too long. A slash screen is long enough, a video with sound is going to be annoying after the first load.

Actually that might be a good option - enable it for the first load after install, then disable unless the user chooses to leave it on.

This might be a good opportunity to learn from those companies who have the millions to invest in consumer research over a ridiculous number of platforms with various performance: e.g. Microsoft. Certainly I've noticed since Windows XP (though it may have been present in earlier versions, and has been suggested in earlier posts) that the loading animation is two parts. Part 1, a general animation which brings the logo into view. Part 2, a repeatable animation which can continue as long as it takes for the actual program to load. In the case of samfishers incredible work, everything up to the unfolding of the corners could be considered part 1, the unfolding (with minor modifications to be repeatable) could be part 2. Have to say that any animation which required the part to be completed before the system loaded would go against my sensibilities (an animation is fine - nay great )- but if it actually delays me using the app in question then, well that's an issue. And goes against the guidelines provided by iOS, MacOS, Windows Phone and Windows App Store (and probably Android, though I've never looked into that...)

Every guidelines I've read suggest that any animation should be used to help indicate the application is loading, not to continue once the application is loaded (at which point the animation becomes about completing the animation, not indicating to the user that the application is still loading) - the idea is consistently to show the app as fast as possible, using any loading screens to indicate to the user that the app is loading/loaded, not to delay it in any way.