Deep linking as an input language

What a URL should be able to do

Deep linking has a reputation as plumbing. A marketing link opens the app, the app opens a screen, everyone moves on. The contract stays thin because the input is assumed to be rare and polite: one URL, arriving alone, into an app sitting quietly at its home screen.

None of those assumptions survives automation. The moment URLs become the way tests drive the app, the way demo recordings are staged, and the way a Shortcut or an agent reaches a feature, they arrive in bursts, mid-animation, into whatever state the app was left in. A deep-linking layer that only handles the polite case fails quietly everywhere else: stacked sheets, half-applied navigation, a screen that belongs to the previous URL.

Deep Link Kit is the layer I built for the impolite cases. It turns one URL into a deterministic sequence of structural navigation steps and side effects, applied in order, with cooperative cancellation when the next URL lands before the last one has finished. Four properties carry the weight.

• Race-safe. Racing URLs collapse to last-writer-wins. Cancelled runs leave no half-applied state behind, and every cancellation is a recorded trace event that tests assert against.
• State-aware. The same short URL means the right thing from anywhere. Settings arrives as a sheet from the root and as a push from inside a thread, decided by a frozen snapshot of where the app is, not by routing instructions leaked into the URL.
• Contained. The consumer can answer “where does your URL handling live?” with a folder name and a low percentage. The domain layer never learns the kit exists.
• Programmable. Taps, URLs, tests, and automated screen capture all converge on one apply path. The bar is not “open a screen”; one URL can hand the user a primed draft, two sheet layers deep.

Every claim in this series is measured against a demo messaging app built as the kit’s consumer. The recordings are captures of that app running; the numbers come from its codebase. The app exists so the kit has somewhere honest to prove itself.

The panel below replays the kit’s signature scenario: six URLs fired in under a second, each cancelling the one before, the last one winning, nothing stacking. The recorded version, captured from the demo app with no animation tricks, opens the first article in the series.