Improve Efficiency and Resolve Refresh Issue in Web Application Development
In this meeting, Scott brings up a question about reducing the number of collections in his front-end on Xano and Weweb. He suggests using a variable for the Epic ID instead of creating a new collection for each opportunity. The group discusses the problem they are trying to solve, which includes improving efficiency and preventing data loss when someone refreshes the page. They explore the idea of using the URL and local storage to maintain state and recover the progress in the process. They also discuss the possibility of using a spinner during loading and connecting the application state with the URL. The meeting ends with Scott asking if the issue can be worked on later, and the group agrees to dive deeper into the topic in future meetings.