So if I have a reusable header and I put onto it a custom state that is a list of things, and from Page A I set the custom state of that list of things on the reusable header, that when my user navigates to Page B or Page C, whereby the page is loaded, that the values in the custom state on the header set from Page A are still set on the header that is visible on Page B or Page C without needing to run a set state action and that there would be no need to refetch those values from the database again, implying the values carry over from the reusable on Page A to the reusable on Page B or Page C?

I was always under the impression that each iteration/use of a reusable is materially different from another, as we can use the same reusable element more than once on the same page and have the ability to set different values to the custom states for each of those. And I was also under the impression that when a page is loaded all custom states set are lost and would need to be set again.

I’m very intrigued by the concept you outlined, but feel as if I am lacking clarity on how it is implemented.

I’ve only recently began utilizing local storage in apps and really like what it can do, especially for remembering who a non-logged in user is.

When you use it for things like blog posts, are you saving to local storage the blog posts as JSON? I’m curious how to make use of this in an app.