🪻 Indigo Stack CE — Apple Platforms

Getting Started

The Indigo stack uses Tuist for organizing and managing the project structure, dependencies, and build settings for Apple platform applications.

Setup

1- Configure project settings: Update the values in Tuist/ProjectDescriptionHelpers/Config.swift to match your project:

public let teamReverseDomain = "com.yourcompany"  // Replace with your domain
public let appName: TargetReference = "YourApp"   // Replace with your app name

2- Install Tuist by running:

curl https://mise.jdx.dev/install.sh | sh
mise install

This will install the Mise tool which manages Tuist versions, and then install the specific Tuist version for this project based on the .mise.toml file.

3- Install project dependencies by running:

tuist install

This will fetch and install all Swift Package Manager dependencies defined in the project's Package.swift.

4- Generate the Xcode project by running:

tuist generate

This will generate the Xcode project and workspace from the Tuist project models.

You can now open App.xcworkspace in Xcode and build/run the project.

Update Tuist Version

If you need to update the Tuist version, you can run:

mise up --bump

Project Architecture

This project is organized into multiple modules:

• App: The main iOS/macOS application targets that depend on Core, Components, and feature modules
• Core: Business logic, data models, and external dependencies
• Components: Reusable SwiftUI components with no external dependencies for maximum portability
• Indigo: Core TCA infrastructure and shared utilities for feature modules
• FeatureA and FeatureB: Example TCA-based feature modules with their respective reducers and views

Dependency Graph

App
├── Core (business logic + external dependencies)
├── Components (reusable UI components, no dependencies)
├── FeatureA (TCA-based feature → Indigo)
└── FeatureB (TCA-based feature → Indigo)

Indigo (TCA shared utilities)

This architecture ensures that:

• UI components remain reusable across different projects
• Business logic is separated from presentation
• External dependencies are contained within the Core module
• Feature modules follow consistent naming conventions (XFeature, XView)
• TCA infrastructure is shared through Indigo

Project Settings

• OTHER_LDFLAGS is set to -ObjC to allow Objective-C dependencies.

Updating Dependencies

If you make changes to the Package.swift to add/update dependencies, re-run:

tuist install
tuist generate

Editing Project Models

If you make changes to the Tuist project models (e.g. adding a new target), re-run to generate the Xcode project:

tuist generate

Targets

The project contains the following targets:

Target: App

• Type: iOS/macOS Application
• Deployment Target: iOS 18.0, macOS 15.0
• Dependencies:
  • Core (business logic and data layer)
  • Components (reusable UI components)
  • FeatureA (counter feature example)
  • FeatureB (todo list feature example)

Target: Core

• Type: Framework
• Deployment Target: iOS 18.0, macOS 15.0
• Purpose: Contains business logic, data models, and external dependencies
• Dependencies: None (simplified from previous dependencies)

Target: Components

• Type: Framework
• Deployment Target: iOS 18.0, macOS 15.0
• Purpose: Reusable SwiftUI components with no external dependencies
• Dependencies: None (intentionally kept dependency-free for maximum reusability)

Target: Indigo

• Type: Framework
• Deployment Target: iOS 18.0, macOS 15.0
• Purpose: Shared TCA infrastructure and utilities for feature modules
• Dependencies: ComposableArchitecture, other TCA-related packages

Target: FeatureA

• Type: Framework
• Deployment Target: iOS 18.0, macOS 15.0
• Purpose: Example counter feature using TCA
• Dependencies: Indigo
• Main Types: FeatureAFeature (reducer), FeatureAView (SwiftUI view)

Target: FeatureB

• Type: Framework
• Deployment Target: iOS 18.0, macOS 15.0
• Purpose: Example todo list feature using TCA
• Dependencies: Indigo
• Main Types: FeatureBFeature (reducer), FeatureBView (SwiftUI view)

Schemes

The project includes the following schemes:

Scheme: App Debug

• Configuration: Debug
• Purpose: Development and debugging
• All actions (Run, Archive, Profile, Analyze) use the Debug configuration

Scheme: App

• Configuration: Release
• Purpose: Production builds
• All actions (Run, Archive, Profile, Analyze) use the Release configuration