Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format
Destroy appLoadingIndicator element
I think the framework should destroy the appLoadingIndicator element automatically after the app is initiated, since it unnecessarily keeps using (pretty heavily actually) the CPU while the app is running.
One official ST example (particles) is already doing the same thing I do in my app launch method:
What if you wanted to keep the indicator around while sending a request to a server to see if a user is logged in? There are uses to allow the dev to destroy it when he/she chooses.
I'd imagine that you could add it to the painted event of the ext viewport or something?
Then your viewport wouldn't be painted until that user auth request is made?