I haven’t studied Darren’s video very closely, but it appears that he is maybe onboarding a user BEFORE they sign in whereas what we are explaining in onboarding AFTER a user signs in. I’m not sure if his “form submission” table is intended to be the user table or not.
It’s up to you when you want onboarding to happen and will have to adjust your Privacy settings accordingly.
Ultimately, tab visibility can only be controlled by values in the user profile table. If you are performing your onboarding prior to a user signing in, you can still write data to the user profile table, but you will have to make sure that the user uses the same email when they actually sign in, so they can attach to their existing user profile row that they created prior to signing in. If you are performing onboarding after a user signs in, then they can automatically attach to their autogenerated user profile row, and can just update that existing row.
If you don’t use the user profile table to handle your onboarding, then it’s going to be a lot harder to control tab visibility. So, I’d focus mainly on getting that onboarding data into the user table, rather than attempt with yet another table.
It also should be noted that Darren is using a different approach. He is using what we call Custom Forms, which are not a native Glide forms. He is updating data in a helper table, which he might possibly be writing to the user table afterwards. It’s a more advanced approach, so I’d probably try to first understand what we users call Custom Forms. It can have advantages and disadvantages depending on the user case
Overall, there are a thousand ways to skin a cat. Darren’s is one way. Other people use a different method. It’s best to first understand what you want your app flow to be. What should a brand new user experience when they want to use your app for the very first time? Also, be mindful of your end goal. You want to ultimately control tab visibility to force users into an onboarding flow by showing only an onboarding tab, and when it’s completed, hide it and show the rest of the app tabs. Tab visibility can only be controlled by values in a user’s user profile row, such as email and/or a profile completed value. To get that value, a user has to create a new row or edit an existing row. That row is created when a user signs in for the first time, but it can also be added through a form prior to signing in (depends on the app flow you want).