Glide screens should default to Custom layout only, and the ability to switch styles at the screen (tab) level should be removed.

**Summary**

Glide screens should default to Custom layout only, and the ability to switch styles at the screen (tab) level should be removed.

All style selections should exist only inside Collections, not at the screen level. This prevents accidental layout switches that break components, actions, and app structure.

**Current Problem**

Currently, Glide allows switching the entire screen style (Card, List, Table, Data Grid, Checklist, Calendar, Kanban, Custom). If a user mistakenly switches from Custom to any other style, Glide
immediately:

1. Deletes or breaks all components
2. Removes layout structure
3. Breaks actions
4. Causes irreversible loss of work

This transition happens instantly and without warnings, which results in major productivity loss and can destroy complex screens built with custom layouts.
Screens are becoming containers for multiple collections and components. But the legacy screen-level style selector still exists, creating a high-risk point of failure.

**Examples / Scenarios**

_Scenario — Accidental Click_

A user working on a detailed custom screen (multiple collections, containers, buttons, actions) accidentally clicks “List” instead of “Custom”.
Everything disappears immediately — no backup.

_Scenario 2 — Large Screens with Nested Logic_

Apps with complex logic (e.g., CRM dashboards, management systems, inventory screens) contain:

1. Multiple collections
2. Action rows
3. Visibility logic
4. Inline editing
5. Custom containers

Switching away from “Custom” deletes all of that silently.

**Why This Matters**

Prevents accidental catastrophic data loss — a single click currently wipes the entire screen.

Reduces support load — many developers report losing hours of work due to accidental layout switches.

Aligns with Glide’s design direction — Collections already support all styles individually.

**Suggested UX**

1. Default all screens to “Custom”
Every new screen = Custom layout by default.
2. Remove all screen-level layout options

Remove:

- Card
- List
- Table
- Data Grid
- Checklist
- Calendar
- Kanban

Only “Custom” remains at the top level.

3. Allow layout styles inside Collections only
Collections already support:

- List
- Grid
- Table
- Kanban
- Calendar
- Checklist
- Cards

This is the correct place for style selection.

4. If Glide must keep the selector (temporary fallback)
Add a confirmation modal:
“Changing the screen style will permanently delete all components on this screen. Are you sure?”
But best approach: remove completely.

5. Updated UX Flow

Screen → Always Custom

Add Components → Add Collections → Choose styles inside Collections

Components become stackable, safe, and independent

This keeps Glide consistent and prevents accidental screen destruction.