# Managing Menu Bloat - Hiding Items? **URL:** \ **Category:** Ask for Help\ **Created:** [April 20, 2022, 11:14pm UTC](https://community.glideapps.com/t/managing-menu-bloat-hiding-items/40982 "2022-04-20T23:14:53Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![todd.y](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/todd.y/32/41350_2.png) [@todd.y](https://community.glideapps.com/u/todd.y)\ **Post date:** [April 20, 2022, 11:14pm UTC](https://community.glideapps.com/t/managing-menu-bloat-hiding-items/40982/1 "2022-04-20T23:14:53Z")
Hey Glide Community, I need help with my tabs and menu items. I’m coming up on 12 different options and it’s going to be overwhelming for the user if they see all of them at once. If I “hide” the menu, it becomes locked, and I can’t navigate to it. ![Glide Menu](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/3/1/31fcd5ac92fb7e4ce8dafd8959387be47926f336.png) In GlidePages, I have the ability to uncheck “Show in Menu”, but I don’t see a comparable feature in GlideApps. I did a forum search and saw a reference to discussions about CSS edits, but I couldn’t find anything that answered the question specifically. Does anyone know how to achieve this? Your help is much appreciated! ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [April 21, 2022, 12:56am UTC](https://community.glideapps.com/t/managing-menu-bloat-hiding-items/40982/2 "2022-04-21T00:56:57Z")
Honestly, I would probably categorize and merge multiple tabs together. For example, how about Community, Circle, and Beneficiary tabs, and inside each tab you can navigate to different screens through button actions, or use a choice component as a navigation tool to hide or show different components that serve different functions. I’m more inclined to create separate screens instead of multiple tabs. You would probably have to rebuild your screens though. Choice component to hide/show multiple components that serve different functions: ![Screenshot_20220420-195053-315](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/b/bbb80751e7901e469626d4ed76ed89834542dcbc.jpeg) Floating buttons to navigate to different screens: ![Screenshot_20220420-195237-218](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/0/6/06cc418effd41954766b2636ba58dfa605cf8c4e.png) Buttons to navigate to different screens: ![Screenshot_20220420-195247](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/0/6/064746b6a110f0d4b593ffeeeb290023894709c6.png) ---
**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:** [April 21, 2022, 2:44am UTC](https://community.glideapps.com/t/managing-menu-bloat-hiding-items/40982/3 "2022-04-21T02:44:34Z")
I second what Jeff suggested about consolidating multiple tabs into a single tab. In terms of navigation to “sub tabs”, in addition to the options that Jeff mentioned, another option that works quite well is to use an Inline List - usually a tiles layout, although it doesn’t have to be - with each list item navigating to a separate screen. Setting this up just requires a custom action with a separate logic branch for each list item. Here’s an example of how it can look: ![Screen Shot 2022-04-21 at 10.39.32 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/9/c9d90265d7e27c78dff7dde207bee96c3145434b.jpeg) ---
**Author:** ![todd.y](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/todd.y/32/41350_2.png) [@todd.y](https://community.glideapps.com/u/todd.y)\ **Post date:** [April 21, 2022, 3:01pm UTC](https://community.glideapps.com/t/managing-menu-bloat-hiding-items/40982/4 "2022-04-21T15:01:08Z")
Hm, I see what you’re getting at. I’m still working to understand the considerably large suite of features/functions offered by Glide. Coming from GlidePages first, I was hoping there would be a similar feature to make pages invisible, but this seems like a good work-around. I don’t mind having to rebuild pages if the UX is improved. Thank you, Jeff! I’ll report back on the redesign. ---
**Author:** ![todd.y](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/todd.y/32/41350_2.png) [@todd.y](https://community.glideapps.com/u/todd.y)\ **Post date:** [April 21, 2022, 3:52pm UTC](https://community.glideapps.com/t/managing-menu-bloat-hiding-items/40982/5 "2022-04-21T15:52:19Z")
Looks like I need to play around with inline lists. Can you expand a bit on what you mean by a separate logic branch for each item? I assume you mean “on submit” button actions? ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [April 21, 2022, 3:57pm UTC](https://community.glideapps.com/t/managing-menu-bloat-hiding-items/40982/6 "2022-04-21T15:57:57Z")
You can set different actions for whenever you click on an inline list item. If you choose a custom action then you can place IF conditions in that custom action to perform different actions based on a value in the row of the item you clicked. For example, you can have set an If condition to open a new screen if the item contains Circle. If the item you clicked says something else, then you can have it perform a different action. ---
**Author:** ![todd.y](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/todd.y/32/41350_2.png) [@todd.y](https://community.glideapps.com/u/todd.y)\ **Post date:** [April 21, 2022, 6:48pm UTC](https://community.glideapps.com/t/managing-menu-bloat-hiding-items/40982/7 "2022-04-21T18:48:28Z")
“If you choose a custom action then you can place IF conditions in that custom action to perform different actions based on a value in the row of the item you clicked” This provided the detail I needed. Thanks again, @Jeff_Hager!