Why are we doing this?
In a variety of different cases we will need to transition a user to a screen where we are unsure of what the destination will be at the time of click. In the case of a long delay, we will need a go to transition for these instances.
After tapping on a link I expect to see a response from the system that a page is being fetched.
If the link can be resolved and the destination can be resolved and pushed in under 500 ms (roughly), I should just see the destination open. If the destination isn't resolved or pushable after 500ms, I should see this while waiting for the transition.
Building off of the transition used in the Share-a-fact flow and the illustration style we have been using for on boarding screens, the proposed solution would utilize a white overlay over the last loaded page along with a small, animated illustration. In the animation the satellite planet would circle (orbit) around the larger planet. Tapping cancel would end the fetch and return the user to the last visited page.