Translating text within your app

At a glance

Project structure

Source bundle/
└── TranslatingText/
    ├── TranslatingTextApp.swift
    ├── ViewModel/
    │   ├── ViewModel.swift
    │   └── AvailableLanguage.swift
    ├── Views/
    │   ├── Availability/
    │   │   ├── LanguageAvailability/
    │   │   │   └── LanguageAvailabilityView.swift
    │   │   └── PrepareTranslation/
    │   │       └── PrepareTranslationView.swift
    │   ├── CustomUI/
    │   │   ├── Batch/
    │   │   │   └── BatchOfStringsView.swift
    │   │   ├── BatchAsSequence/
    │   │   │   └── BatchAsSequenceView.swift
    │   │   └── SingleString/
    │   │       └── SingleStringView.swift
    │   ├── RowView.swift
    │   └── SystemUI/
    │       ├── ReplaceTranslationView.swift
    │       └── ViewTranslationView.swift
    └── ContentView.swift

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 4 project/configuration file(s) and 13 source declaration(s).

Overall architecture

flowchart LR
    N1["TranslatingTextApp"]
    N2["ContentView"]
    N3["ViewModel"]
    N4["Translation APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

TranslatingText/TranslatingTextApp.swift:10 — architecture anchor

@main
struct TranslatingTextApp: App {
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Translation.

Ownership and state

classDiagram
    TranslatingTextApp *-- ViewModel : model
    ViewModel *-- Bool : isTranslationSupported
    ViewModel *-- Array : availableLanguages
    LanguageAvailabilityView *-- Language : selectedFrom

Ownership evidence

TranslatingText/TranslatingTextApp.swift:12 — stored dependency or nearest verified ownership anchor

    @State private var model = ViewModel()

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Class and protocol design

TranslatingText/TranslatingTextApp.swift:11 — representative type boundary

struct TranslatingTextApp: App {
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

TranslatingText/TranslatingTextApp.swift:12 — representative boundary

    @State private var model = ViewModel()

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: App: TranslatingTextApp; View: BatchAsSequenceView, BatchOfStringsView, ContentView, LanguageAvailabilityView, PrepareTranslationView; ViewModel: ViewModel.
• Protocols: no local protocol declaration in the scanned source.
• Methods: reset, prepareSupportedLanguages, translate, translateAllAtOnce, translateSequence, checkLanguageSupport, performCheck, triggerTranslation.
• Files: TranslatingText/TranslatingTextApp.swift, TranslatingText/ViewModel/ViewModel.swift, TranslatingText/Views/Availability/LanguageAvailability/LanguageAvailabilityView.swift, TranslatingText/ContentView.swift, TranslatingText/Views/Availability/PrepareTranslation/PrepareTranslationView.swift, TranslatingText/Views/CustomUI/Batch/BatchOfStringsView.swift.

Architecture takeaways

• TranslatingTextApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, Translation through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation