Let’s say that the three accounts are different people.
If you click the button 3 times on the first account, the point is 3.
If you click the button four times on the second account, it’s point four.
If you click the button 7 times on the third account, it’s point 7.
Like this, I want to save different variables for each other.
You should create the object with a score value of zero. But you need to create the object when the user first signs up, not when the button is clicked.
Sorry, I misspoke. When a user signs in with Firebase, Thunkable provides a green block called userId. You can check to see if User/userId exists (is not null) and if it doesn’t, then create an object. That way, the object only gets created one time, the first time the user signs in to your app.
Try this. I would test it without the Navigate block. You might need a slight delay between the cloud variable block and the Navigate block so leave it out for now. If the =null condition doesn’t trigger when you first sign in, then you may have to check the properties of Users/ or whatever your top Firebase level is for the existence of [user id] but I think the =null condition will work. Make sure you are using an account that has been verified by clicking the link your receive from Firebase in your email account.
