diff --git a/rules/blazor-appstate-pattern-with-notifications/rule.md b/rules/blazor-appstate-pattern-with-notifications/rule.md
index 6cbd0c1d0cd..a3ea73d5d7e 100644
--- a/rules/blazor-appstate-pattern-with-notifications/rule.md
+++ b/rules/blazor-appstate-pattern-with-notifications/rule.md
@@ -156,3 +156,5 @@ The Counter page example below calls `StateHasChanged()` when the `PropertyChang
 Whenever the `IncrementCount()` or `Reset()` methods are invoked, any listeners on the page will invoke the handling code attached to the `PropertyChanged` event - and be able to invoke `StateHasChanged` in order to update their respective views.
 
 The real value of implementing `INotifyPropertyChanged` (or by using an abstraction like `BaseClass<T>` above) is when the same shared state object is used multiple times on the same page and having the `PropertyChanged` event handlers invoked from a single interaction and automatically keeping the view up to date for all components.
+
+Although this mitigates an issue with the [AppState pattern](blazor-basic-appstate-pattern), it is still not a complete solution for all scenarios. For more complex scenarios, consider using a Redux state management pattern. [Fluxor](https://github.com/mrpmorris/Fluxor) is a NuGet package implementing the Redux pattern for Blazor.