In the meeting, the State Changers thoroughly discussed the implementation and troubleshooting of Firebase for user authentication in their application, and integration with various other platforms, including Xano and Flutterflow. The focus was on improving the user experience, especially concerning error handling during user login.
They talked about different strategies for handling errors, such as verifying if an email address is formatted correctly and checking preconditions on the Flutterflow side to provide better error messages. The goal was to improve UX by preventing backend error messages from being displayed to the end-users. There was a detailed discussion on how to differentiate between identification/authentication (handled by Firebase) and authorization (managed by Xano). One major insight gathered was to delete the password column in Xano, making Firebase the sole responsible platform for password handling, leading to more secure and efficient user management. They also noted that having two separate API calls for login was acceptable if it improved the error handling experience. The session concluded with understanding that Firebase would verify user IDs, acting as an ID card, while Zeno would be responsible for providing access (acting as a key), maintaining robust security protocols. No mentions were made about WeWeb, Zapier, Integromat, Outseta, Retool, Bubble, Adalo, AppGyver, AppSheet, Comnoco, Fastgen, Google, OAuth, Stripe, Twilio, Airtable, DraftBit, Javascript, Typescript, React, Vue.js, JSX, HTML, CSS, lambda, serverless, State Change, ScriptTag, OpenAI, and AI21.
(Source: Office Hours 4/6 )
