Just in case you forgot (and needed to know) the name of the application you’re using seconds after its execution, there is the utterly pointless splash screen.
A true splash screen has a fine, albeit mostly aesthetic purpose. While the application is loading, a resource-light branded image is shown as a kind of virtual waiting room. Some companies, such as Adobe, will use the splash screen to run a small ticker of the resources being loaded for your viewing pleasure.
A splash screen becomes pointless when either the application has already loaded or, worse, before the application begins loading. We all remember old school websites whose home page came after a splash page informing us we had successfully arrived there: “Welcome to Bob’s World!!1! [Enter]” Take this gem from a fitness app I use almost every day. The splash screen begins in a useful way. However, once the app loads, you have to navigate away from it in order to get to your data. It’s also very confusing because the user might not even understand the app has already loaded if they’re still staring at the logo.
“Before I commit to anything, I need to know about the inspiration underlying this seemingly casual, yet understatedly elegant, neighborhood pub. Were the owners seeking to strike a balance between contemporary American cuisine and authentic fare from their grandparents’ homeland? Are the owners three regular guys who were looking for a bar that served good food in a relaxed atmosphere with a world-class selection of beers who decided to build it themselves? And if I see a ‘Testimonials’ tab that has quotes from recent diners (along with their respective cities), I’m sold!”—That guy who already has your hours, address, phone number, menu and reservation policy memorized, and won’t need to find them online (via neversaidaboutrestaurantwebsites)