Hey everyone, I know this question was asked before but I couldn’t find an answer to my proper case. I have an app with optional sign in. Non-signed in user has access to a tab with various element, and if he signs in, he has access to the same tab but with more options. If user wants to create …

If you want to do it all on a single screen, organise your components into containers and apply visibility conditions to the containers.

I don’t necessarily want to do all of this one a single screen, the set up screen can be another tab but yeah having all on the same is possible too. However, it doesn’t answer to my question at all. Basically my issue doesn’t come from if I should apply visibility condition… it comes from WHAT vi…

Hey Lucas! Take a look at this :point_down: [image] wave How to create Onboarding screens Flow Community Resources Hey guys! wave Pretty soon, I’ll be launching a new video and app template for all of you to create an amazing onboarding expererience in your app! Wait f…

[image] Lucas_R: WHAT visibility conditions I should apply precisely Add an OnboardedTimestamp basic date column in the the Users table. When a user finishes the onboarding, the click on the final button will write the ‘Now’ timestamp to that column and perform a ‘Go to tab’ action back to a …

Hey, your proposal is interesting, sadly a condition is also applied to guests (non signed in). Ex.: show only if X is not empty will also hide it for guests. The issue I’m talking about is the complete user flow. User is a guest, then user register. At this point I need that the freshly arrived u…

[image] Lucas_R: At the moment, the only way I found to execute this is to have a copy of the tab. One made for guest, one made for logged in users. My aim is to change strategy and have only one tab for both logged and guest. The condition must hide everything but the onboarding screen (or ele…

It won’t, the central element which is a list, should be displayed to both guest and logged in user with onboard completed. So both of users must share the same visibility conditions. Now the problem is that it’s difficult to find a visibility condition that both can share. Your solution would work…

Why do you need to put a condition on something that doesn’t need a condition and is visible to everyone?

It shouldn’t be visible to logged in users who didn’t onboard.

Then it would be a condition with an OR. Show when onboarding complete OR user profile email is empty.

Force Onboarding screen after sign-in

Ask for Help

Lucas_Pires December 19, 2023, 9:52pm 13

@Lucas_R check it out!

Topic		Replies	Views
App - Static Onboarding screens Ask for Help	2	497	February 9, 2023
Create a login and a sign in screen Ask for Help	1	1085	December 13, 2023
Compulsory User Sign Up Page on Entry Ask for Help	10	1228	July 14, 2020
Creating an onboarding flow using tab visibility Project Showcase	91	7995	May 10, 2023
Onboarding before sign in Ask for Help	3	345	July 10, 2021

Force Onboarding screen after sign-in

Related topics