{"id":19735975,"url":"https://github.com/nventive/chinook.navigation","last_synced_at":"2025-06-23T13:33:25.141Z","repository":{"id":40257340,"uuid":"268981710","full_name":"nventive/Chinook.Navigation","owner":"nventive","description":"ViewModel-based navigation","archived":false,"fork":false,"pushed_at":"2025-05-20T13:44:42.000Z","size":10017,"stargazers_count":11,"open_issues_count":3,"forks_count":3,"subscribers_count":21,"default_branch":"main","last_synced_at":"2025-06-16T00:13:34.552Z","etag":null,"topics":["android","chinook","dotnet","ios","mobile","mvvm","navigation","uno-platform","uwp"],"latest_commit_sha":null,"homepage":"","language":"C#","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/nventive.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2020-06-03T03:38:51.000Z","updated_at":"2025-05-20T13:44:44.000Z","dependencies_parsed_at":"2024-11-12T01:04:38.587Z","dependency_job_id":"4531403a-99f2-4f9d-8eea-2c3fd228f6b7","html_url":"https://github.com/nventive/Chinook.Navigation","commit_stats":{"total_commits":80,"total_committers":18,"mean_commits":4.444444444444445,"dds":0.825,"last_synced_commit":"3ed0833601116d8770bfee7decd94f41ab195037"},"previous_names":[],"tags_count":2,"template":false,"template_full_name":"nventive/Template","purl":"pkg:github/nventive/Chinook.Navigation","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nventive%2FChinook.Navigation","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nventive%2FChinook.Navigation/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nventive%2FChinook.Navigation/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nventive%2FChinook.Navigation/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/nventive","download_url":"https://codeload.github.com/nventive/Chinook.Navigation/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nventive%2FChinook.Navigation/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":261487291,"owners_count":23166058,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["android","chinook","dotnet","ios","mobile","mvvm","navigation","uno-platform","uwp"],"created_at":"2024-11-12T01:04:26.725Z","updated_at":"2025-06-23T13:33:20.130Z","avatar_url":"https://github.com/nventive.png","language":"C#","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Chinook StackNavigation and SectionsNavigation\n\n[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg?style=flat-square)](LICENSE) ![Version](https://img.shields.io/nuget/v/Chinook.StackNavigation.Abstractions?style=flat-square) ![Downloads](https://img.shields.io/nuget/dt/Chinook.StackNavigation.Abstractions?style=flat-square)\n\nThis library provides unified cross-platform tools to perform ViewModel-based navigation using the [Frame](https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.controls.frame) navigation model.\n```csharp\n// Navigate to the PersonDetailsPage.\nawait navigator.Navigate(ct, () =\u003e new PersonDetailsPageViewModel());\n// Navigate back.\nawait navigator.NavigateBack(ct);\n```\n\n## Cornerstones\n- **Highly Extensible**\n  - Everything is interface-based to easily allow more implementations.\n  - A single framework can't cover everything.\n    Our architecture is designed in a way that allows you to integrate your favorites tools easily.\n- **UI-Independant**\n  - Navigation abstractions are not tied to a specific UI framework.\n  - Having the navigation code in the ViewModel layer allows for reusing the same code for multiple platforms.\n\n### More like this\nThe Chinook namespace has other recipes for .Net MVVM applications.\n- [Chinook.DynamicMvvm](https://github.com/nventive/Chinook.DynamicMvvm): MVVM libraries for extensible and declarative ViewModels.\n- [Chinook.DataLoader](https://github.com/nventive/Chinook.DataLoader): Customizable async data loading recipes.\n- [Chinook.BackButtonManager](https://github.com/nventive/Chinook.BackButtonManager): Abstractions to deal with hardware back buttons.\n\n## Before you start\nBefore getting started, you should understand the different navigators.\n\nThere are 2 types of navigators available:\n- `IStackNavigator` - Use this if your app would use a single `Frame`.\n\n  ![Section Navigation](docs/images/StackNavigation.png)\n\n- `ISectionsNavigator` - Use this if you want to use multiple frames (like sections tabs) or modals.\nNote that `IStackNavigator` is used as a building block by `ISectionsNavigator`.\n\n  ![Section Navigation](docs/images/SectionNavigation.png)\n\n  Here is how navigation around sections and modals are related to stack navigation:\n  - Dimension 1: **Stack Navigator**\n    - It's linear. You can go forward or back.\n  - Dimension 2: **Sections**\n    - Each section is a stack navigator.\n    - You can have multiple sections next to each other.\n    - You can change the active section freely (without limitations).\n  - Dimension 3: **Modals**\n    - Each modal is a stack navigator.\n    - You can have multiple modals on top of each other.\n    - You can't change the modal freely; you can only open a new modal and close existing modals.\n    - The active modal is always the one with the highest priority (set when opening).\n\n  Axis | Navigator            | Operations\n  :---:|----------------------|-----------\n  X    | `IStackNavigator`    | Navigate, NavigateBack\n  Y    | `ISectionsNavigator` | SetActiveSection\n  Z    | `ISectionsNavigator` | OpenModal, CloseModal\n\nThe following steps will show how to setup the `ISectionsNavigator`.\n\u003e 💡 If you want to create a single stack application, check [this doc](docs/StackNavigation-Setup.md) instead.\n\n## Getting Started\n\n1. Install the latest version of `Chinook.SectionsNavigation.Uno` or `Chinook.SectionsNavigation.Uno.WinUI` in your project.\n\n1. Create a base class that implements `INavigableViewModel` for your ViewModels.\n\n   You can use the MVVM framework of your choice.\n   In this sample, we use `ViewModelBase` from [`Chinook.DynamicMvvm`](https://github.com/nventive/Chinook.DynamicMvvm).\n   ```csharp\n   using Chinook.DynamicMvvm;\n   using Chinook.StackNavigation;\n   using Windows.UI.Xaml.Controls;\n   namespace ChinookSample\n   {\n     public class ViewModel : ViewModelBase, INavigableViewModel\n     {\n       public void SetView(object view)\n       {\n         // For Chinook.DynamicMvvm, we want to create an MVVM dispatcher using the CoreDispatcher of the Page.\n         Dispatcher = new CoreDispatcherDispatcher((Page)view);\n       }\n     }\n   }\n   ```\n\n1. Map your ViewModels to Pages.\n   \n   Create a method returning a dictionary associating the types.\n   You can put that method in `App.xaml.cs`.\n   ```csharp\n   private static IReadOnlyDictionary\u003cType, Type\u003e GetPageRegistrations() =\u003e new Dictionary\u003cType, Type\u003e()\n   {\n     // Assuming that MainPageViewModel is a class that inherits from the ViewModel class of the previous step.\n     { typeof(MainPageViewModel), typeof(MainPage) }\n   };\n   ```\n\n1. Add a `MultiFrame` at the root of your application's XAML.\n   \n   You can do this in various ways.\n   We suggest you create a `UserControl` which contains the `MultiFrame` and set that `UserControl` as the content of the application's `Window`.\n   \n   Here's a minimal example:\n   ```xml\n   \u003cUserControl x:Class=\"ChinookSample.Shell\"\n                xmlns=\"http://schemas.microsoft.com/winfx/2006/xaml/presentation\"\n                xmlns:x=\"http://schemas.microsoft.com/winfx/2006/xaml\"\n                xmlns:nav=\"using:Chinook.SectionsNavigation\"\u003e\n     \u003cGrid\u003e\n       \u003cnav:MultiFrame x:Name=\"NavigationRoot\"\n                      CommaSeparatedSectionsFrameNames=\"Home,Settings\"/\u003e\n    \u003c/Grid\u003e\n   \u003c/UserControl\u003e\n   ```\n   Make sure you publicly expose the `MultiFrame` instance from the code behind of your `UserControl`.\n\n   ```csharp\n   using Windows.UI.Xaml.Controls;\n   using Chinook.SectionsNavigation;\n\n   namespace ChinookSample\n   {\n     public sealed partial class Shell : UserControl\n     {\n       public Shell()\n       {\n         this.InitializeComponent();\n       }\n\n       public MultiFrame MultiFrame =\u003e NavigationRoot;\n     }\n   }\n   ```\n\n1. Adjust the `OnLaunched` of your `App.xaml.cs` so that it does the following.\n   - Set your newly added `Shell` as the content of the window.\n   - Create a `FrameSectionsNavigator` using the `MultiFrame` from the `Shell` and the page registrations.\n   - Do an initial navigation to display a page.\n   ```csharp\n   protected override void OnLaunched(LaunchActivatedEventArgs e)\n   {\n      var root = Window.Current.Content as Shell;\n      if (root == null)\n      {\n        // Set the Shell as the window content.\n        root = new Shell();\n        Window.Current.Content = root;\n        \n        // Create the navigator\n        var navigator = new FrameSectionsNavigator(\n          multiFrame: root.MultiFrame,\n          globalRegistrations: GetPageRegistrations()\n        );          \n\n        // Do an initial navigation\n        _ = navigator.SetActiveSection(CancellationToken.None, \"Home\", () =\u003e new MainPageViewModel());\n      }      \n      \n      Window.Current.Activate();\n   }\n   ```\n\n1. Start your application!\n\n   From there you probably want to publicly expose the your `ISectionsNavigator` instance to your ViewModels so that they can manipulate the navigation.\n   You can do that using the pattern of your choice.\n\n## Features\n\n### Stack Navigation\nStack navigation is the basic pattern for navigating forward and back.\nIt's reused in both sections and modals.\n\n#### Navigate forward and back\n```csharp\n// Navigate to the PersonDetailsPage.\nawait navigator.Navigate(ct, () =\u003e new PersonDetailsPageViewModel());\n// Navigate back.\nawait navigator.NavigateBack(ct);\n```\n\n#### iOS back gesture\nThe back swipe gesture is supported on iOS devices when using `FrameStackNavigator`.\n\n\u003cimg src=\"docs/images/iOS_Gesture_BackSwipe.gif\" alt=\"iOS Back Swipe Gesture\" width=\"250\"\u003e\n\n#### Navigate forward, clearing the backstack\nThis can be useful when you don't want the user to be able to navigate back.\n```csharp\n// Navigate to the HomePage, clearing all other previous pages from the backstack.\nawait navigator.NavigateAndClear(ct, () =\u003e new HomePageViewModel());\n```\n\n#### Remove previous pages\n```csharp\n// Navigate to Step 1\nawait navigator.Navigate(ct, () =\u003e new Step1PageViewModel());\n// Navigate to Step 2\nawait navigator.Navigate(ct, () =\u003e new Step2PageViewModel());\n// Navigate to Step 2.1\nawait navigator.Navigate(ct, () =\u003e new Step21PageViewModel());\n// Navigate to Step 3\nawait navigator.Navigate(ct, () =\u003e new Step3PageViewModel());\n\n// Remove the previous page (Step 2.1) from the backstack.\nawait navigator.RemovePrevious(ct);\n// Navigate back to Step 2\nawait navigator.NavigateBack(ct);\n```\n\n### Observe the StackNavigator's State\nYou can access the stack navigator's state using `IStackNavigator.State`.\nIt gives you access to the navigation stack as well as the last request.\nYou can observe the state with the `IStackNavigator.StateChanged` event.\n\n### Sections\nSections are independent stacks that live next to each other.\nOnly 1 section can be active at a time.\nApps that have a bottom navigation bar typically would use 1 section per bottom bar button and perhaps another for the login pages.\n\n#### Change between sections\n```csharp\n// Go to Home section.\nawait sectionsNavigator.SetActiveSection(ct, \"Home\");\n// Go to Messages section.\nawait sectionsNavigator.SetActiveSection(ct, \"Messages\");\n// Go to Settings section.\nawait sectionsNavigator.SetActiveSection(ct, \"Settings\");\n```\n\n#### Return to root of section\nThis can be useful to simply reset a section when returning to it.\n\n```csharp\n// Go to Home section.\nawait sectionsNavigator.SetActiveSection(ct, \"Home\", () =\u003e new HomePageViewModel());\n// Navigate forward to some details page in the Home section.\nawait sectionsNavigator.Navigate(ct, () =\u003e new PersonDetailsPageViewModel());\n// Go to Messages section.\nawait sectionsNavigator.SetActiveSection(ct, \"Messages\");\n\n// Return to Home section on the Home page, not the PersonDetails page.\nawait sectionsNavigator.SetActiveSection(ct, \"Home\", () =\u003e new HomePageViewModel(), returnToRoot: true);\n```\n\n\u003e 💡 When tapping on a bottom section button, some applications have a dual behavior:\n\u003e 1. Tap once: the app returns to that section.\n\u003e 1. Tap a second time: the section returns to its root.\n\u003e\n\u003e `ISectionsNavigator.SetActiveSection` supports such behavior.\n\n#### Navigate in an inactive section\nYou can navigate in sections that are not active.\nThis is useful if you want to _prepare_ a section before entering it to have smooth transitions.\n\n```csharp\n// Go to Home section.\nawait sectionsNavigator.SetActiveSection(ct, \"Home\", () =\u003e new HomePageViewModel());\n// Get the settings section navigator.\nvar settingsSection = sectionsNavigator.State.Sections[\"Settings\"];\n\n// Navigate forward to the SettingsPage, then the LicencePage in the Settings section.\n// The Settings sections is not currently active, so you don't actually see this change happen.\nawait settingsSection.Navigate(ct, () =\u003e new SettingsPageViewModel());\nawait settingsSection.Navigate(ct, () =\u003e new LicencePageViewModel());\n\n// Go to Settings section to see the Licence page.\nawait sectionsNavigator.SetActiveSection(ct, \"Settings\");\n// Navigate back to SettingsPage.\nawait sectionsNavigator.NavigateBack(ct);\n```\n\n### Modals\n`ISectionsNavigator` allows you to handle multiple stacks of navigation in your app, including modals.\nModals are navigation stacks that show up on top of all other sections.\nA modal stack behaves like any other section, meaning you can navigate back and forth in it.\nYour app can also navigate the pages behind the modals, without breaking the flow.\n\n#### Open and close modals\n```csharp\n// Open LoginPage in a modal.\nawait sectionsNavigator.OpenModal(ct, () =\u003e new LoginPageViewModel());\n// Close the modal.\nawait sectionsNavigator.CloseModal(ct);\n```\n\n#### Open modals behind other modals\nIt's possible to open a modal behind a modal that's already open.\nThis can be useful to show an optional extra step in a modal flow, while keeping nice transitions.\n```csharp\n// Open LoginPage in a modal with a priority of 2.\nawait sectionsNavigator.OpenModal(ct, () =\u003e new LoginPageViewModel(), priority = 2);\n\n// Open the SurveyPage in a modal behind the LoginPage page modal, using a lower priority of 1.\n// Because the SurveyPage opens with a lower priority, you don't actually see this change happen.\nawait sectionsNavigator.OpenModal(ct, () =\u003e new SurveyPageViewModel(), priority = 1);\n\n// Close the top-most modal (LoginPage) to reveal the SurveyPage modal behind it.\nawait sectionsNavigator.CloseModal(ct);\n```\n\n#### Change sections behind modals\nYou can navigate in sections that are not active.\nThis is useful if you want to _prepare_ a section before entering it.\n\n```csharp\n// Open LoginPage in a modal.\nawait sectionsNavigator.OpenModal(ct, () =\u003e new LoginPageViewModel());\n\n// Change the section to Messages.\n// Modals are displayed on top of sections, so you don't actually see this change happen.\nawait sectionsNavigator.SetActiveSection(ct, \"Messages\", () =\u003e new MessagesPageViewModel());\n\n// Close the modal to reveal the Messages section.\nawait sectionsNavigator.CloseModal(ct);\n```\n\n#### Navigate back or close modal\nThere are handy extension methods on `ISectionsNavigator` to easily check whether you can navigate back or close a modal.\nThis can be useful when dealing with an hardware back button.\n```csharp\n// Check whether the navigator can navigate back or close a modal.\nif (sectionsNavigator.CanNavigateBackOrCloseModal())\n{\n  // Navigates back within the modal if the modal has multiple pages in its stack\n  // Or closes the modal if there's a modal that has an empty backstack\n  // Or navigates back in the active section.\n  await sectionsNavigator.NavigateBackOrCloseModal(ct);\n}\n```\n\n#### Support Screen Reader\nConsider setting `MultiFrame.CollapsePreviousFrameWhenOpeningModals` to `true` to prevent previous frames (behind modals) from being focusable.\n\n### Observe the SectionsNavigator's State\nYou can access the sections navigator's state using `ISectionsNavigator.State`.\nIt gives you access to all section stacks and modal stacks as well as the last request.\nYou can observe the state with the `ISectionsNavigator.StateChanged` event.\n\n### Ready for Dependency Injection\nThe two navigation services are made from simple interfaces.\nYou can easily leverage containers such as Microsoft's [Generic Host](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host).\nHere is an example that registers and retrieves the `ISectionsNavigator` using  `Microsoft.Extensions.DependencyInjection` and `Microsoft.Extensions.Hosting`.\n\n```csharp\nvar serviceProvider = new HostBuilder()\n  .ConfigureServices(serviceCollection =\u003e serviceCollection\n    .AddSingleton\u003cISectionsNavigator\u003e(new FrameSectionsNavigator(\n      multiFrame: root.MultiFrame,\n      globalRegistrations: GetPageRegistrations()\n    ))\n  )\n  .Build()\n  .Services;\n\t\t\t\nvar navigator = serviceProvider.GetService\u003cISectionsNavigator\u003e();\n```\n\n### Ready for Integration Testing\nBecause this is ViewModel-based navigation and the navigator interfaces don't reference any UI type, you can use the navigators in **Test Projects** or **Console Applications** without changing your navigation logic\nJust install the `Chinook.SectionsNavigation` or `Chinook.StackNavigation` packages and use the `BlindSectionsNavigator` or `BlindStackNavigator` implementations.\n\n### Built-in Debounce\nImplementations of both `IStackNavigator` and `ISectionsNavigator` have a built-in debounce mechanism that prevents _double navigations_.\nIf you invoke 2 operations simultaneously (double tap, press 2 buttons with 2 fingers, etc.), only the first will actually run.\nThis is because the request state (Processing, Processed or FailedToProcess) is part of the `ISectionsNavigator.State`.\nIf a request is made while another is processing, the second request is cancelled.\n\n### Transitions and Animations\nThere are five statically available built-in transitions in `FrameSectionsTransitionInfo`.\n- `FrameSectionsTransitionInfo.SuppressTransition`\n- `FrameSectionsTransitionInfo.FadeInOrFadeOut`\n- `FrameSectionsTransitionInfo.SlideUp`\n- `FrameSectionsTransitionInfo.SlideDown`\n- `FrameSectionsTransitionInfo.NativeiOSModal` (available on iOS only)\n\n#### Stack navigation\nThe platform's default transition is used. Here are examples for iOS and Android respectively.\n\n\u003cimg src=\"docs/images/iOS_StackNavigation_DefaultTransition.gif\" alt=\"iOS Stack Navigation Default Transition\" width=\"250\" /\u003e\n\u003cbr /\u003e\u003cbr /\u003e\n\u003cimg src=\"docs/images/And_StackNavigation_DefaultTransition.gif\" alt=\"Android Stack Navigation Default Transition\" width=\"250\" /\u003e\n\nYou can also suppress the default transitions using `StackNavigatorRequest.SuppressTransitions`.\n\n```csharp\nawait navigator.Navigate(ct, () =\u003e new ResetPasswordPageViewModel(), suppressTransition: true);\n```\n\nHere is an example of the result on Android.\n\n\u003cimg src=\"docs/images/And_StackNavigation_SuppressTransition.gif\" alt=\"Android Stack Navigation Suppress Transition\" width=\"250\" /\u003e\n\u003cbr /\u003e\u003cbr /\u003e\n\n#### Section navigation\n\nYou can customize or remove the section navigation animations using `SectionsTransitionInfo`. \nThe default transition is `FrameSectionsTransitionInfo.FadeInOrFadeOut`. \nHere is an example on iOS.\n\n\u003cimg src=\"docs/images/iOS_SectionNavigation_DefaultTransition.gif\" alt=\"iOS Section Navigation Default Transition\" width=\"250\" /\u003e\n\nYou can specify transition info per request using `SectionsNavigatorRequest.TransitionInfo`.\n\n```csharp\nawait _sectionsNavigator.SetActiveSection(\n  ct,\n  SectionsNavigatorRequest.GetSetActiveSectionRequest(\n    sectionName: \"Settings\",\n    transitionInfo: FrameSectionsTransitionInfo.SuppressTransition\n  )\n);\n```\n\nYou can also specify section navigation transition info globally using the following when instanciating `FrameSectionsNavigator`:\n\n```csharp\nvar navigator = new FrameSectionsNavigator(root.MultiFrame, GetPageRegistrations())\n{\n  DefaultSetActiveSectionTransitionInfo = FrameSectionsTransitionInfo.SuppressTransition\n};\n```\n\n#### Modals\n\nYou can customize or remove the modals opening and closing animations using `SectionsTransitionInfo`.\nThe default modal transition for iOS is its native one, used by `FrameSectionsTransitionInfo.NativeiOSModal`.\n\n\u003cimg src=\"docs/images/iOS_Modal_NativeTransition.gif\" alt=\"iOS Modal Native Transition\" width=\"250\" /\u003e\n\nFor the other platforms, the default modal opening transition is `FrameSectionsTransitionInfo.SlideUp` and the default modal closing transition is `FrameSectionsTransitionInfo.SlideDown`.\n\n\u003cimg src=\"docs/images/And_Modal_DefaultTransition.gif\" alt=\"Android Modal Default Transition\" width=\"250\" /\u003e\n\nYou can specify transition info per request using `SectionsNavigatorRequest.TransitionInfo`. \n\n```csharp\nawait navigator.OpenModal(\n  ct,\n  SectionsNavigatorRequest.GetOpenModalRequest(\n    StackNavigatorRequest.GetNavigateRequest(() =\u003e new ResetPasswordPageViewModel()),\n    transitionInfo: FrameSectionsTransitionInfo.FadeInOrFadeOut,\n    newModalClosingTransitionInfo: FrameSectionsTransitionInfo.FadeInOrFadeOut\n  )\n);\n```\n\nYou can also specify modal opening and closing transitions info globally using the following when instanciating `FrameSectionsNavigator`:\n\n```csharp\nvar navigator = new FrameSectionsNavigator(root.MultiFrame, GetPageRegistrations())\n{\n  DefaultOpenModalTransitionInfo = FrameSectionsTransitionInfo.FadeInOrFadeOut\n  DefaultCloseModalTransitionInfo = FrameSectionsTransitionInfo.FadeInOrFadeOut\n};\n```\n\nThis is what the `FrameSectionsTransitionInfo.FadeInOrFadeOut` transition for modals looks like on Android.\n\n\u003cimg src=\"docs/images/And_Modal_FadeInFadeOutTransition.gif\" alt=\"Android Modal Fade In Or Fade Out Transition\" width=\"250\" /\u003e\n\u003cbr /\u003e\u003cbr /\u003e\n\n#### Custom animations\n\nYou can also create custom animations using the following classes:\n- `DelegatingFrameSectionsTransitionInfo`\n  - Available on all platforms.\n  - Allows you to create a transition in an async method where you can animate using `Storyboard`.\n- `UIViewControllerTransitionInfo`\n  - Available on iOS only.\n  - Allows you to customize the native behavior (such as dismissability via gestures and animations).\n\n\n## Breaking Changes\n\nPlease consult [BREAKING_CHANGES.md](BREAKING_CHANGES.md) for more information about migration.\n\n## License\n\nThis project is licensed under the Apache 2.0 license - see the\n[LICENSE](LICENSE) file for details.\n\n## Contributing\n\nPlease read [CONTRIBUTING.md](CONTRIBUTING.md) for details on the process for\ncontributing to this project.\n\nBe mindful of our [Code of Conduct](CODE_OF_CONDUCT.md).","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnventive%2Fchinook.navigation","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnventive%2Fchinook.navigation","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnventive%2Fchinook.navigation/lists"}