I’m glad @Joyce clarified that, because I was wondering the exact same thing.
I have my collections set to fetch automatically, but I do not preserve the results on navigation. I feel like most use-cases you would keep that off.
The way I have it set up is when the user is filtering collection results, the collection itself is being filtered by variables that keep getting updated. If the user clicks through to a product page, but then hits the back button to go back to the results, a new API request is made on page load, but the results look the same because the variables I do have set to preserve on navigation.
Then, if there are obvious behaviors like going back to the home page and trying to search again, or cases where the user would obviously be wanting to start a new search from scratch, I have a workflow that clears all of those variables.
My thinking is it’s a lot less data to preserve a handful of variables than an entire collection. But I’m also very new to WeWeb 