The State Changers had a productive meeting discussing about Flutterflow, Xano and how they are handling a situation related to the preference feature on their platform. It seems that toggle icons in FlutterFlow can only be determined by Boolean values or if it's from a list; and to remember the user's preference, they considered keeping a list of likes as a separate variable, which gets updated each time a post is liked. However, since it's a page state, the list gets deleted when users navigate away.
To avoid this, they discussed two alternatives: include the likes in the model, or create another API endpoint that gets the list of liked posts. The meeting resolved to decide according to a 'half one' time discipline approach; test one solution for a short span of time (30min), if progress is made, extend the time, if not, reconsider the plan. They concluded the meeting with the understanding that further hacking is necessary and scheduled further discussions on following days. There was no mention of WeWeb, Zapier, Make, Integromat, Outseta, 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 or AI21 in this meeting.
(Source: Office Hours 4/5 )
