Internal DeepLink Routing

[wessmith]

Purpose

We build a deep link routing mechanism to route incoming URIs to states within our apps, delegating responsibility to handlers for fetching and processing data and ViewControllers for presenting the resources we request.

Ideally we create and maintain one navigation system and this should be the URI -> app state mapping mechanism that we current delegate only to deep link handling.

High Level Requirements

• All ViewController states have URIs which are a way of serializing and reproducing the current state
• There is an object responsible for managing the presentation of ViewControllers based on incoming URI & current state
• Current states can be 'drilled from' by adding partial URLs (e.g. if at /products/123 navigating to "related" navigates to /products/123/related)
• More to come..

[alcarvalho]

I will just repost part of my comment here so we can follow up.

... delegating responsibility to handlers for fetching and processing data and ViewControllers for presenting the resources we request.

I have never thought that fetching data could belong to the route handler. Do you think that's a good idea? For instance, how could we present any feedback (progress, connection error) to the user, if you don't have a UI to do it in the handler?

I either don't get it or are you planning deeper modifications to the route handler?