@christianv makes sense, or i suppose you could do an cc-hide until data is ready but that pretty much is what ng-clock would do anyway. 

btw, the navbar (on worst case scenarios) would probably hit some slow responding api endpoints. Would it make sense to throw in some spinners for the individual elements instead of suppressing the whole bar with ``ng-cloak``? At least the user settings dropdown could probably be exempt from the cloak maybe.