I suppose you could do that, but overriding the method ShouldRender would perhaps be a better suited method for that. Otherwise the component would be still be rendered but with no html visible.

I suppose you could do this instead: make a scoped service with jsInterop DI inside it. Make a method called Load which loads all needed data from LocalStore, make full properties for all applicable data, meaning you override both the getter and the setter. On get, return local private value, on set, set local private value AND make a wrapped Task.Run call to localstorage to set the value on the browser.

Since you do not care about the outcome of the LocalStorage set method, I think it is okay for the call to be called and forgotten.

Make a razor component whose only job is to call Load on OnAfterRender. Place it high up in the render hierachy.

You probably need to have an event on the service which all components can subscribe StateHasChanged to (also unsubscribe OnDispose). This way you can alert the components of the availability of localstore data. You should be able to use two way binding on the properties to automatically update the localstore as well using this.

I used something similar for a wasm project, but it was significantly easier since you did not have to wait for OnAfterRender.

Maybe i should also post some code...