Create new layouts with Tabs Container and Tabs Component
Please share feedback in this thread 
As a reminder, Preview features should not be used in Production apps. Read more about Glideās product release cycle in our Glide Doc.
This is awesome!! 
Really appreciate the focus on components like this lately.
Ćwesome! Great! Well done!
Iāve been waiting for this for so long!
Thank you so much for the implementation ā it will be very useful for my projects.
Incredible feature that will enhance UIs!
Love this! And agreed really loving the focus on some core components ā they make a huge difference
The Tab component is perfect, rather in production.
But it would be great to be able to create Tabs from the table or from m.rel. or query. Often, customers ask to change the names of the Tabs and have to keep them in the table and pull them up in different columns to have a dynamic name of the Tabs. This will save a lot of time to create an environment for the dynamic names of the Tabs.
Otherwise, the component is beautiful!
Nice!!! My most wanted feature! 
You can use a column as the display name if that helps!
Dynamic number of tabs is a good suggestion
Do some magic and bring submenus in the navbar into the game @DJP 
This is really great - my most wished-for feature! I canāt wait to delete all of those button blocks and screens that Iād been using to hack aroundā¦
As a stretch-goal, are there any plans to permit nested tab containers? Being able to put tabs in tabs would be incredible.
I mean, like in custom collection, where each tab is a row of table
Great work team!!
Tabs Container
What would be a use case for the separate Name and Display as fields?`
Containers are useful for 2 unrelated reasons. For the user interface: container layout, width, background, padding. And for the developerās experience: grouping components together to be able to move a section of the page/screen up or down quickly. So for these two reasons, on the screens I build a component lives inside a container and these make the tab container less attractive (despite its UI appeal).
Any chance you might then introduce component grouping, a group that can be collapsed and move up and down the page?
Tabs Component
Is the idea here that regardless of the data source of the screen, we select a column in the users table for the tabs component? This is a nice and easy setup.
You kind of can already. Thatās why thereās 2 separate components. One thatās standalone component and one thatās a container. Using the standalone components, you can control the view of other containers or components. Itās not a nested container per-se (which could be useful), but it gives the impression that it is. Iām glad Glide gave us the flexibility with two components. In my screenshot below, Iām using two standalone tab components to control the visibility of other components or containers on the screen.
My above screenshot is a use case. āSinglesā needs to write āSingles, Freestyleā to the table, so my collection can pick up newer āSinglesā records as well as older āFreestyleā records to remain backwards compatible.
This is so great! What a great year for Gliders!
Should probably be rewritten toā¦Value and Display as
Loving the Tabs Component especially with Custom Collection.
Hereās a simple application on a User Profile screen.
Nice. Now I have an alternative to using choice components with some custom CSS to make them look like tabs 
So happy to see this feature. Great work!
Butā¦ it seems to have been designed with mobile in mind. The styling is quite, um, underwhelming on desktop. Itāa little anemic compared with the buttons it would replace for many of us implementing pseudo tab structure now.
I would say this is more useful to me on Tabs, not Tab Containers. Tabs would write the āNameā to a field I choose, and I can use that field to establish relations that directly power what I display in each tab.
In many cases, I use rowIDs/numbers to establish said relations, thatās where it comes in useful. I would love the ability to do the same thing on Tab Containers.
