You don’t need local storage for this feature. You can have a true/false parameter for the users called “Onboarding Complete”
When a user has registered, set the default value of the Onboarding Complete parameter to “False”.
You can then direct the users back to your onboarding screen with a condition on the action.
For example:
Sign up action > Link to onboarding screen
Login action > Link to onboarding screen (if logged-in user > onboarding complete > is false) & Link to home (if logged-in user > onboarding complete > is true).
You can add a countdown timer to your home screen with the visibility settings sometimes when logged-in user > onboarding complete > is false to link the user back to the onboarding process if they have not completed it.
On the last step of your onboarding sequence, update the logged-in user’s onboarding complete parameter to true.
You can generate a temp user data (email/password/name) and login in behalf of the user as a temporary account to store the needed information, and once decided to create a real user then sign-out and redirect to signup screen
You can have a screen like welcome screen ( the screen that user see first ) and add a button and add the Signup action and fill the email,password and id ( a number property ) fields with values.
For the email you can add like user,guest and you can add custom formula that you can add all users > max +1 inside it ( you need a number property on the Users collection like ID to get max ) and you can add @gmail.com. ( guest1@gmail.com , guest2@gmail.com ) For the password you can add guest with that all users max formula. And you can add a link action to Home screen. After if the user needs to update the profile you can add a form with the Update Logged in user option.
Sorry for the delay in thanking you.
I still can’t use local storage, so I have to manipulate the database on the developer’s side.
Thank you very much.
Sorry for the delay in thanking you.
Thank you for giving me some specifics on how to do this!
It certainly doesn’t put a burden on the user this way, so it looks like the abandonment rate will go down.
I implemented it right away!
Thanks for your response!