The meeting involved the State Changers discussing and problem-solving multiple technical issues using various platforms. They discussed strategies for developing reusable sets of Actions and authentications for Flutterflow and Webflow. Specifically, the primary issue centred around creating a unified authentication with FlutterFlow that logs out users when the token expires.
The idea of adding a privacy screen, coming into focus only when the user need to log in, was discussed as a possible solution. The State Changers considered it essential to create a universal, reusable solution to avoid updating multiple screens when adjustments are made. They also talked about creating an interstitial component that can layer on all the screens and deal with user authentication. The interstitial, understood as a component with its own load workflow, would be able to check if the session is still active and, if not, redirect the user to the login page. The session concluded with the State Changers agreeing to follow up on a pre-existing video tutorial to further investigate this approach. An upcoming task was assigned involving an in-depth exploration of how to do anonymous logins. No mentions of "Xano", "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".
(Source: Office Hours 4/14 )
