Introducing Magic Deeplink 1.0.1
Every link lands on the right screen.
Universal Links on iOS and App Links on Android through one API on top of app_links. The driver also runs on macOS and is inert on web.
One API. Every link.
A link can come from the OS, from a push notification or from your own code. Magic Deeplink sends each one through the same handler chain.
-
One handler chain
Learn more about One handler chainDeeplinkManagerruns a handler chain and the first match wins (registerHandler,handleUri). Each link arrives as aDeeplinkSource:osLink,pushormanual. -
Links to routes
Learn more about Links to routesRouteDeeplinkHandlermaps link paths to app routes throughMagicRoute, and aTenantSwitchGateguards tenant switches.DeeplinkHandleris the contract for your own. -
Push-tap routing
Learn more about Push-tap routingOneSignalDeeplinkHandlerroutes push-notification taps. It is wired automatically when the notifications service is bound (magic_notifications). -
Association files
Learn more about Association filesdeeplink:generatewrites the Appleapple-app-site-associationfile and the Androidassetlinks.jsonfrom your config. -
Setup checks
Learn more about Setup checksdeeplink:doctorchecks your iOS and Android setup. Native project setup is still yours to do: iOS associated domains and an Android intent filter. -
Driver and events
The
Learn more about Driver and eventsDeeplinkDrivercontract hasAppLinksDriveras the default.DeeplinkOpenedandDeeplinkNavigatingevents feed Magic's breadcrumbs.
Add it in seconds
Or add to pubspec.yaml:
dependencies:
magic_deeplink: ^1.0.1
Or give your AI agent this prompt: