I’m using the Facebook and Google authentication to allow users to register /login to my app. Once logged in they are returned to the app, on the menu I have conditional logic to hide the Signup/login buttons and display the logout button.
There is a clear visual lag upon page load, with the conditional formatting working successfully after 1/2 - 1 seconds after loading. This doesn’t affect the login process when using a bubble.io integrated account.
Anybody have any suggestions on how I can resolve this?
The crucial part here is checking the status of authentication on load and that seems to be causing the delay. You can for instance show a loading spinner or placeholder while validating the authentication, so when it happens as is still quick they will not see those buttons flashing. You can also experiment by setting up a workflow that checks the user login status upfront, possibly on page load or as a background process so that it would reduce this visual lag.
Thanks for coming back to me. The workflow upfront or background progress seem an interesting way to address this. Would you do this by just doing the standard “Current User is logged in” and then this check is cached for subsequent checks within page elements? As I can’t seem to find the right way to do this with “page is loaded” workflow
I am also looking for a solution for this. When Facebook redirects to my Bubble page, there is a 1 or 2 second lag before the user is truly authenticated or any Facebook data points are available. This means I have no way to hide my login screen and/or show a spinner prior to them getting redirected to another page. Not an ideal UX as the user is left to briefly wonder if authentication worked.