In this meeting, the participants discussed the process of identifying and saving user identity. They mentioned using social authentication and generating an ID token using Kakaal for user authentication. The ID token is then sent to the Xano backend for verification and to register the user in the system. They clarified that the purpose of their project is to send push notifications, not to socialize. They also mentioned the need to have email and password stored in Firebase while the rest of the details can be stored in Xano. They talked about creating Firebase identifiers for authentication and using them as the basis for push notification tokens. They acknowledged that they are not experts in Firebase and inquired about the steps they need to take to implement these processes. The meeting participants referred to previous video sessions and documentation about authorization and authentication in Flutterflow. They planned to schedule an additional session specifically focusing on Flutterflow and authentication to bring everyone up to speed. The summary also mentioned the importance of continuing to invest in building user profiles using Xano and integrating Firebase for authentication when the time is right. The participants highlighted the need to focus primarily on their core business logic and to seek advice from others who have successfully implemented similar systems. They briefly touched on the topic of refreshing the authentication token, expressing a desire to discuss it further.
(Source: Office Hours 3/30 )
