State Management

State management in the Writer application is built using SwiftUI's Observation framework. The architecture centers around a set of specialized "Store" classes that manage specific domains of the application, such as file system operations, user interface themes, and layout configurations. These stores are initialized at the app's entry point and injected into the view hierarchy using the SwiftUI environment mechanism.

The primary goal of this system is to maintain a distraction-free editing environment by handling background tasks like autosave, security-scoped file access, and real-time markdown synchronization between the editor and preview components.

Sources: CLAUDE.md:15-17, Writer/WriterApp.swift:13-17

Centralized Architecture

The application follows a modular state architecture where different concerns are separated into distinct observable objects. These objects are managed at the WriterApp level and passed down as environment objects.

Core Store Components

Sources: CLAUDE.md:21-35, Writer/EditorStore.swift:17-45

File System & Document State

The EditorStore is the most complex state container, managing the interaction between the UI and the macOS file system. It uses FileNode to represent a hierarchical view of the workspace.

Security-Scoped Persistence

To maintain access to user-selected folders across app launches without repeated prompts, the system utilizes Security-Scoped Bookmarks.

Document Lifecycle & Autosave

The application manages document state through a combination of manual saves and an automated debounced task.

1. Selection: When a file is selected, selectFile(at:) loads the content into documentText.
2. Modification: UI changes to documentText trigger an onChange modifier in ContentView.
3. Debouncing: scheduleAutosave() cancels any existing task and creates a new one with a 350ms delay.
4. Persistence: If the task completes without cancellation, persistCurrentDocument() writes the text to disk if it differs from lastSavedText.

Sources: Writer/EditorStore.swift:316-339, Writer/ContentView.swift:42-44

UI and Theme State

Theme management allows for real-time updates to the preview rendering without affecting the raw markdown data.

Theme Synchronization

The ThemeStore holds the active PreviewTheme. When the user modifies settings in the ThemeEditorView, the ThemeStore updates, which in turn causes the WebView (via ContentView) to re-render the HTML with updated inline CSS.

Layout State

UI-specific state like the visibility of the preview pane is managed by LayoutStore. This is toggled via:

• Toolbar Button: An icon in the main window.
• Menu Command: "Show/Hide Preview" in the View menu.
• Keyboard Shortcut: Command + Option + P or Command + P.

Sources: Writer/WriterApp.swift:141-146, Writer/ContentView.swift:54-61

Conclusion

State management in Writer leverages the modern Swift Observation framework to create a reactive and decoupled architecture. By separating file system logic (EditorStore), visual styling (ThemeStore), and interface configuration (LayoutStore), the application ensures that complex operations like security-scoped file access and debounced autosaving remain transparent to the user, facilitating a "distraction-free" experience.

Sources: CLAUDE.md:15-17, Writer/EditorStore.swift:13-17