Pick all that apply

• 1Choice 1.

  Instead of scattering URL parsing and navigation across each ViewController, have a central router that normalizes every entry path (URL scheme, Universal Link, push, in-app link) into one Route value

• 2Choice 2.

  A deep link to a screen that requires login isn't dropped; it's held as pending and resumed after authentication finishes

• 3Choice 3.

  Universal Links install the app automatically and open it even when it isn't installed, so no separate web fallback is needed

• 4Choice 4.

  Feature modules register a Route handler for their own screens with the router, and the router must not know the concrete screen types so no circular dependency forms between modules

• 5Choice 5.

  When the app is launched cold from a deep link, only scene(_:openURLContexts:) is called, so handling it in that one method is enough