Hello FlutterFlow Community,
I hope this message finds everyone well. I've encountered a challenge that I believe many of us might have faced at some point. My goal is to enhance user experience within a FlutterFlow application by preventing unnecessary page rebuilds and API calls when navigating back to a previously visited page.
Here's the situation: Upon initial launch, the user visits a search page where the expected behaviour of page building and API fetching occurs. However, when the user navigates away to, say, the home page, and then returns to the search page, the entire search page is rebuilt from scratch. This includes making API calls again and resetting list scrolls and filters, which is not an ideal user experience. Ideally, the state of the search page (including scroll positions and any applied filters just like when you view a post and then use the back button) should be preserved and remain as the user left it upon navigating back.
This behavior of preserving page states when navigating to a previously visted page is common in applications, providing a smoother and more intuitive user experience. While I have seen suggestions within our community, such as building the application into a single page and using the tabs widgest as navigation between the different tabs where each tab will act as a separate page, I find this solution to be less than ideal for our needs.
I'm reaching out to gather insights, experiences, or any potential solutions that could help achieve this functionality of preserving page states upon navigation. Your contributions and suggestions would be greatly valued and could benefit many of us facing similar challenges.
Thank you in advance for your time and assistance. Any help or pointers in the right direction would be immensely appreciated.
Thank you