This meeting among the State Changers revolved around solving the issue of a flash of unformatted content (FAUC) causing UX disruptions in an application that uses Xano for data management. They discussed the problem in which, for a half a second delay during a page load, the previous screen is visible, leading to a questionable user experience.
Three solutions were proposed:
1. Delay the entire screen until data comes in from Xano.
2. Default to a loading state until the auth token is not empty, and then display the data.
3. Overlay a spinner on the page until the data has loaded, at which point the spinner is removed (mimicking Xano's behavior).
They decided that using a spinner as a default state best addressed the problem, as it would remove the FAUC without adding too much complexity. It was also mentioned that such a spinner might be necessary on every page of a site that requires a login, particularly in a Single Page Application (SPA). This implementation is contextual and varies according to the requirement of the application.
(Source: Office Hours 11/3 )