If you’re running the app in a web browser, there’s no additional setup
required. Route paths are handled in the same way as an iOS or Android deep
link. By default, web apps read the deep link path from the url fragment using
the pattern: /#/path/to/app/screen, but this can be changed by
configuring the URL strategy for your app.

If you are a visual learner, check out the following video:

Deep linking in Flutter

Get started

To get started, see our cookbooks for Android and iOS:

Android

iOS

Migrating from plugin-based deep linking

If you have written a plugin to handle deep links, as described in
Deep Links and Flutter applications
(a free article on Medium),
it will continue to work until you opt-in to this behavior by adding
FlutterDeepLinkingEnabled to Info.plist or
flutter_deeplinking_enabled to AndroidManifest.xml, respectively.