A Blazor component library enabling smooth page transition animations by managing both current and previous routes.
BlazorTransitionableRoute is a Blazor component library that enables smooth page transition animations in Blazor applications. It solves the limitation where Blazor's default routing only allows one active route at a time, making page transitions impossible. The library manages both current and previous routes simultaneously, providing developers with the necessary hooks to implement custom animations when users navigate between pages.
Blazor developers building single-page applications who want to add polished page transition animations to improve user experience. This is particularly valuable for developers creating dashboard applications, admin panels, or any Blazor app where smooth navigation enhances perceived performance.
Developers choose BlazorTransitionableRoute because it's the only library specifically addressing Blazor's route transition limitation with a simple, focused API. It provides maximum flexibility by supporting both Blazor-coded and JavaScript-interop animations while maintaining compatibility with Blazor's routing system and browser history.
Allows current and previous route to exist enabling page transition animations.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Solves Blazor's core limitation by allowing both current and previous routes to coexist, enabling smooth transition animations as demonstrated in the README's demo GIF.
Supports both Blazor-coded animations and JavaScript interop, giving developers implementation choice based on project needs, as outlined in the usage section.
Provides transition data like route types and direction, allowing for custom animations based on navigation context, which enhances user experience differentiation.
Requires only a few file changes, such as modifying App.razor, making it relatively easy to add to existing Blazor applications, as highlighted in the feature summary.
The library only provides hooks for transitions; developers must implement all animation styles themselves, adding significant development overhead compared to turnkey solutions.
Requires changes to core routing files like App.razor and potential custom components for AuthorizeRouteView, as noted in example usage commits, which can be error-prone.
Handling page state persistence during transitions, such as scroll position, requires careful configuration and can lead to interaction issues if ForgetStateOnTransition is misused.