Recently I had to debate over the usage of a skeleton screen vs a splash screen for web pages or web apps, although I am not a fan of either solutions here are my thoughts on the topic.
Fist things first, if you can avoid any of the above this would be the way to go, if you are on the other hand forced to decide between them you will find that each has a place and a time when it should or shouldn't be used. Forget the trends or the classic "Apple does this in ...." because I heard it so many times and some use this as a sole argument. Let's look deeper into the subject, later you can decide which one to use.
After I finished the first test with the Ethernet shield and serving your own page from Arduino (see post here Arduino - Talking plant, with HTTP server (or how to see sensor data via internet)) I said, ok, but if I don't have my own static IP address!?!? Most of us don't have a static IP address at home. Yeah it was fun with the other one to play in a LAN or use the university network to get an own IP, but at home this device renders useless. I tried with other social networks or email providers but it looks like Facebook, Yahoo mail and Gmail have quite some problems talking with Arduino and Arduino has some problems talking with them, the only one available remained Twitter.
One of the small assignments used for learning Arduino was the classical "talking plant". Actually was more of a build own humidity sensor, sensor reading and sending the data to the Ethernet shield and also use LED lights to display the status of the soil moisture.
Page 2 of 2