This meeting among the State Changers primarily focused on technical troubleshooting and strategic planning. The issues addressed included:
1. FlutterFlow: Nathan experienced some technical issues related to FlutterFlow, which he managed to resolve by following FlutterFlow's documentation and tweaking Google Console settings, indicating that the issues were not directly related to fonts. 2. Work on instances: Eddie discussed significant work on instances and highlighted the problem with some APIs, stating that some did not have their inputs or function stacks associated with them after being created. He highlighted the issue of draft mode, reliability concerns, and the need for differential comparisons. 3. Moving across instances with Xano: Some of the participants considered the possibilities and challenges of moving things across instances, a feature not inherently provided by Xano. They also discussed plans about how to improve the process, considering even the power user-type moves. 4. Security: A brief mention was made about a pending discussion on security issues, which was deferred for their next meeting. 5. Frequency of meetings: The group scheduled daily meetings for the rest of the week to focus on the issues at hand. The meeting did not involve direct discussion about WeWeb, Zapier, Make, Integromat, Outseta, Retool, Bubble, Adalo, AppGyver, AppSheet, Comnoco, Fastgen, Firebase, Google APIs and server settings, OAuth, Stripe, Twilio, Airtable, DraftBit, Javascript, Typescript, React, Vue.js, JSX, HTML, CSS, lambda, serverless, State Change, ScriptTag, OpenAI, AI21.
(Source: Office Hours 2/27 )
