The State Changers meeting focused on solving a problem related to sending data to Xano and improving the user interface experience. The issue raised was that whenever a change was made in a form that sends data to Xano, all the fields display "undefined" while loading the report.
The solution suggested involved creating a duplicate get tied to the button push in an effort to avoid a temporary blank statement after the button is pushed. To further improve the process, the data obtained from this second get request was stored in a variable, and any changes were made through this variable, thereby avoiding the flashing or "blinking" on the user interface. Additionally, it was advisable to use an "optimistic" update method which localizes the changes until the new information is available from Xano. This differs from the currently "pessimistic" approach where information is in loading state and the fields show "undefined" until the response from Xano comes back. The application of these concepts to resolve the issue and improve the UI experience will be documented in a video for future reference and shared with others facing similar challenges. The meeting then shifted the focus to discuss Flutterflow. There was no mention of WeWeb, Zapier, Retool, Bubble, Adalo, AppGyver, AppSheet, Comnoco, Fastgen, Firebase, Google, OAuth, Stripe, Twilio, Airtable, DraftBit, Javascript, Typescript, React, Vue.js, JSX, HTML, CSS, lambda, serverless, State Change, ScriptTag, OpenAI, and AI21 in the conversation.
(Source: Office Hours 3/2 )
