I have a Splash activity and a Loading activity. Then the current idea when the app is started normally (from the app icon in phone home screen) is having the Splash activity show initially and then have Loading activity display an animation until app asynchronous initialization is finished. Then the first Relevant activity is launched.
This is working ok, but the problem arrives when I want to start the app from some implicit or explicit intent (example: click on a notification after app has been killed) that targets an activity other than the Splash activity. Aforementioned activity flow does not happen, and so the Relevant activity starts before the asynchronous app initialization is finished.
I have been thinking about how to fix this, and I came up with this idea:
Make sure that all requests that come from outside the app to start an activity, target the Splash activity so that normal initialization can happen. Then pass the intent through to the Relevant activity.
I believe that this could make the app's logic more complex, and I could still find unforeseen problems, so I would like to find a simpler/better alternative. Any ideas?
Thanks in advance.
