Showcase

The Showcase tab is a demo catalog — a self-guided tour of everything the template ships, built so you can delete it in one sitting and lose nothing. It's the one feature labeled Removable demo, and for most buyers the first thing you'll want is the removal recipe at the bottom of this page.

The one rule: dependencies point one way

Core never names a Showcase type. The Showcase may name anything in core.

This is the single invariant that makes deletion safe. The Showcase only ever launches core feature views (TodosView, UploadView, PermissionsView, ReferView, AccountSecurityView, PaywallView, …) inside its own navigation stack (ShowcaseTabView). It never becomes the sole home of a core feature and never hands off to another tab. Because nothing in core imports a Showcase type, removing the module can't break a core feature.

Concretely:

• ShowcaseRoute lives in Features/Showcase/, not in Navigation/MainRoute.swift. MainShellView mounts ShowcaseTabView(onOpenMenu:) and holds no Showcase navigation state.
• When you add a demo you touch three Showcase-local places — a ShowcaseRoute case, a CapabilityCatalog entry, and a destination in ShowcaseTabView — and never reach back into the app shell. If a demo needs a shell affordance, it takes a generic closure (like onOpenMenu), never a Showcase type.

The CapabilityCatalog data model

The catalog is data-driven: every row is one TemplateCapability value in Core/Showcase/CapabilityCatalog.swift, and both the Showcase list and Home's "What's inside" tiles render from it. Adding a capability is a one-line edit — no view changes.

TemplateCapability(
    id: "todos",                    // stable slug, unique across the catalog
    titleKey: "showcase.todos.title",
    summaryKey: "showcase.todos.summary",
    category: .backendData,         // section grouping
    systemImage: "checklist",       // SF Symbol row glyph
    route: .todos,                  // ShowcaseRoute pushed on tap (nil = no demo)
    status: .liveDemo               // how runnable it is in this build
)

The supporting types:

CapabilityStatus maps directly onto the feature-status vocabulary used across these docs:

So a row like paywall shows requiresKeys until you add a RevenueCat key, and push-notifications shows deviceOnly because the simulator never receives a token — the catalog is honest about what will actually run.

How to remove the Showcase

Deleting the demo is a small, mechanical operation. After step 2 the project still builds and every core feature (Todos, Upload, Permissions, Refer, Account/Security, Paywall) stays reachable through its own entry point.

rm -rf SoarStarterSwift/Core/Showcase/
rm -rf SoarStarterSwift/Features/Showcase/

Removing the Showcase does not require touching any core feature, repository, controller, or view model. Rebuild after step 2 to confirm — the xcodebuild command should stay green.

Related pages