It is valid for an app to start and not be ready to use for a while, so long as the user cannot interact with it (or see the broken bits:)).
It is valid for an app to start and not be ready to use for a while, so long as the user cannot interact with it (or see the broken bits:)) Better to ensure your app has a splash screen/login page etc that displays until such time as the required resources are loaded. Once loaded you can set an app state to then show the main screen. I had the same problem with a website that loaded the menu items via a service (as the text was data driven).
Wound up running a progress spinner over the top (with a full-screen background).
Great, thanks. Very helpful. – will Aug 30 '10 at 20:40.
I don't think you can. The application runtime occurs on the client's machine. I would suggest putting up a loading dialog while you bring those items down from the database.
What Best practice for this is to use a splash screen or login page. You can also have your buttons (and interaction) disabled by default, and after the data is loaded, enable the UI. I would go with the spash screen though..
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.