# App Start Up Shows Cycling Through of Components Set with Visibility Conditions Before Screen Becomes Functional **URL:** \ **Category:** Report a Bug\ **Tags:** actions\ **Created:** [March 9, 2025, 3:29am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592 "2025-03-09T03:29:50Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Rob\_Field](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rob_field/32/84139_2.png) [@Rob\_Field](https://community.glideapps.com/u/Rob_Field)\ **Post date:** [March 9, 2025, 3:29am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/1 "2025-03-09T03:29:51Z")
Problem described in title. Terrible user experience where each time the app loads the app lags through start up and temporarily shows and cycles though components which shouldn’t be showing due to visibility conditions. ---
**Author:** ![Adam\_Crossley](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam_crossley/32/24083_2.png) [@Adam\_Crossley](https://community.glideapps.com/u/Adam_Crossley)\ **Post date:** [March 20, 2025, 7:45am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/2 "2025-03-20T07:45:56Z")
Yes my apps do this and I agree it’s a terrible user experience. Does anyone know of a workaround? ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [March 20, 2025, 8:00am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/3 "2025-03-20T08:00:04Z")
I’ve never seen this, and I’ve built or worked on well over 100 Apps. My initial thought would be there are probably visibility settings that are driven by very processor intensive computations, so that’s where I would start looking. ---
**Author:** ![Adam\_Crossley](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/adam_crossley/32/24083_2.png) [@Adam\_Crossley](https://community.glideapps.com/u/Adam_Crossley)\ **Post date:** [March 20, 2025, 8:23am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/4 "2025-03-20T08:23:51Z")
Yes that is what it is. Do you have any ideas for a workaround or are we just not supposed to create visibility functions on intensive computed columns? ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [March 20, 2025, 9:43am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/5 "2025-03-20T09:43:14Z")
It’s hard to say. Every situation is different. Without understanding what is going on inside your App all I can really say is have a close look at what you have and explore ways to simplify it. ---
**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\ **Post date:** [March 20, 2025, 10:29am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/6 "2025-03-20T10:29:21Z")
> [@Darren\_Murphy](#): > > have a close look at what you have and explore ways to simplify it. Adam, Rob, see if you can set your visibility conditions to look at basic columns rather than computed columns. @Adam_Crossley @Rob_Field ---
**Author:** ![Rob\_Field](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rob_field/32/84139_2.png) [@Rob\_Field](https://community.glideapps.com/u/Rob_Field)\ **Post date:** [March 20, 2025, 2:42pm UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/7 "2025-03-20T14:42:35Z")
Nothing complex about my visibility conditions. They are simple true false boolean columns. ---
**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\ **Post date:** [March 20, 2025, 2:54pm UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/8 "2025-03-20T14:54:17Z")
It could be an worthwhile test to set the visibility condition on another basic column which is not a boolean. ---
**Author:** ![Rob\_Field](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rob_field/32/84139_2.png) [@Rob\_Field](https://community.glideapps.com/u/Rob_Field)\ **Post date:** [March 20, 2025, 11:12pm UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/9 "2025-03-20T23:12:01Z")
I have attempted various columns to control the visibility with no luck. Anyways think I’ll give up on glide. My app’s front end for the last 2 days won’t even load now? Time to find a better solution ---
**Author:** ![NFNHello](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nfnhello/32/3371_2.png) [@NFNHello](https://community.glideapps.com/u/NFNHello)\ **Post date:** [March 20, 2025, 11:32pm UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/10 "2025-03-20T23:32:59Z")
I noticed this issue pop up around October 2024. Screens that used to load visibility conditions lightning fast started showing a significant lag, usually around 5-10 seconds. Support suggested a workaround of a landing page that just says “loading” or something equivalent until the visibility conditions fully loaded which then hid the loading page. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [March 21, 2025, 12:28am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/11 "2025-03-21T00:28:31Z")
> [@Darren\_Murphy](#): > > I’ve never seen this, and I’ve built or worked on well over 100 Apps. Granted I have never seen this as well, can there be a (non) problem of us being from the same part of the world? Can ISPs be a problem here? Just throwing ideas out there. I would use the Performance Mode analyzer to see those conditions take how much time to load as well. ---
**Author:** ![Marcel\_at\_Glide](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/marcel_at_glide/32/60371_2.png) [@Marcel\_at\_Glide](https://community.glideapps.com/u/Marcel_at_Glide)\ **Post date:** [March 21, 2025, 9:42pm UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/12 "2025-03-21T21:42:52Z")
> [@Rob\_Field](#): > > My app’s front end for the last 2 days won’t even load now? This may be related to the [glide.page domain issue](https://community.glideapps.com/t/active-issue-glide-apps-on-glide-page-domains/80882). ---
**Author:** ![kingzy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kingzy/32/15690_2.png) [@kingzy](https://community.glideapps.com/u/kingzy)\ **Post date:** [March 22, 2025, 5:35pm UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/13 "2025-03-22T17:35:14Z")
One of my app can’t load on Firefox, will try the others tomorrow. ---
**Author:** ![NFNHello](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nfnhello/32/3371_2.png) [@NFNHello](https://community.glideapps.com/u/NFNHello)\ **Post date:** [March 23, 2025, 2:30am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/14 "2025-03-23T02:30:43Z")
@Darren_Murphy @ThinhDinh you may want to revisit apps that previously worked for you. I’ve found that every app that I set up with a welcome screen to gather a user name and details shows the welcome screen for users who have already completed the onboarding process. I stored a welcome completed date on the user table that I used for visibility conditions on some apps, and an ITE column on the user table for others, and both types started showing the welcome screen for a few seconds on app load after Oct '24. These apps didn’t show the completed welcome screen before then. I’m interested to know if you experience something similar if you revisit any of those completed apps as a user from the app player. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [March 23, 2025, 5:53am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/15 "2025-03-23T05:53:58Z")
I just checked one and it’s working as expected. Below are the visibility conditions I have on the tab: ![CleanShot 2025-03-23 at 13.51.44@2x](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/a/f/af23ad7765aad4d6f9ef22b232699812d60eeaaa.png) hmm… two conditions, I should move that to the Data Editor 🫤 ---
**Author:** ![Simon\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/simon_hill/32/94730_2.png) [@Simon\_Hill](https://community.glideapps.com/u/Simon_Hill)\ **Post date:** [March 23, 2025, 8:40am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/16 "2025-03-23T08:40:40Z")
I have experienced this on most of my apps for many years. It’s not great. I always wondered if there was a fix, for example sorting the order of the Glide tables in the builder screen… but I think the visibility conditions simply read blank for key tab visibility cells until the data is loaded. This causes a brief glimpse of Welcome screens. You can experience this with my app 21Jobs.ai > **[21 Jobs](https://21jobs.ai)** > > Designed to help you land a great job ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [March 23, 2025, 9:58am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/17 "2025-03-23T09:58:57Z")
I think the order of tabs can make a difference. In the one I mentioned above, the first two tabs are: - Home screen: this is the screen that users land on once their profile is complete. This tab (and most other tabs) are shown when a boolean column in the user profile row is checked. - Welcome screen: users without a completed profile will see this tab and no other tab. This tab is shown when a boolean column in the user profile row is _not_ checked. There are several other tabs, but the point is - it works perfectly with the above setup. The Welcome screen is never seen on startup once a user has completed their profile. ---
**Author:** ![Simon\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/simon_hill/32/94730_2.png) [@Simon\_Hill](https://community.glideapps.com/u/Simon_Hill)\ **Post date:** [March 23, 2025, 10:04am UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/18 "2025-03-23T10:04:22Z")
Ok thanks for the tip… I will try managing the tab order. Update: Looks like I already had the preferred tab sequence, so this cannot be the solution. ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/6/d684026a3557c5c28f60c1c913c649ae5d577002.png) ---
**Author:** ![NFNHello](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nfnhello/32/3371_2.png) [@NFNHello](https://community.glideapps.com/u/NFNHello)\ **Post date:** [March 23, 2025, 1:21pm UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/19 "2025-03-23T13:21:53Z")
The order of the tabs did make a difference for me before last October. Then the player briefly started showing my welcome screen. And when I placed my welcome screen lower in the order to adjust for this new lag, the player would instead show my home page for a few seconds for the people who hadn’t completed the welcome sequence (lose-lose). I had to put a loading screen first above everything so it would show while the player loaded the visibility conditions, and then when the visibility conditions loaded it would hide the loading screen and show the appropriate screen. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [March 23, 2025, 1:51pm UTC](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592/20 "2025-03-23T13:51:52Z")
> [@NFNHello](#): > > And when I placed my welcome screen lower in the order to adjust for this new lag, the player would instead show my home page for a few seconds for the people who hadn’t completed the welcome sequence (lose-lose). I have to admit, I hadn’t tested that scenario. But I did test it just now in my App using a different email address, and it does still work as expected. ie. only the Welcome screen is shown. Are you using Row Owners in your User Profiles table? (I am). I wonder if that makes a difference? If only a single row is loaded, I expect that’s going to be significantly faster. [Next page](https://community.glideapps.com/t/app-start-up-shows-cycling-through-of-components-set-with-visibility-conditions-before-screen-becomes-functional/80592.md?page=2)