Structuring recognized text on a document

At a glance

Project structure

Source bundle/
├── BusinessCompanion/
│   ├── AppDelegate.swift
│   ├── BusinessCardContentsViewController.swift
│   ├── DataGatheringViewController.swift
│   ├── DocumentScanningViewController.swift
│   ├── ReceiptContentsViewController.swift
│   ├── OtherContentsViewController.swift
│   ├── RecognizedTextDataSource.swift
│   ├── Base.lproj/
│   │   ├── LaunchScreen.storyboard
│   │   └── Main.storyboard
│   └── Info.plist
└── BusinessCompanion.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

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 6 project/configuration file(s) and 11 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["BusinessCardContentsViewController"]
    N3["Vision / VisionKit APIs"]
    N1 --> N2
    N2 --> N3

Reference code

BusinessCompanion/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

}

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 VisionKit.

Ownership and state

classDiagram
    AppDelegate o-- UIWindow : window
    BusinessCardContents *-- String : name
    BusinessCardContents *-- String : website
    BusinessCardContents *-- String : address

Ownership evidence

BusinessCompanion/AppDelegate.swift:13 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

}

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

BusinessCompanion/RecognizedTextDataSource.swift:11 — representative type boundary

protocol RecognizedTextDataSource: AnyObject {
    func addRecognizedText(recognizedText: [VNRecognizedTextObservation])
}

The source explicitly defines local protocol relationships: BusinessCardContentsViewController → RecognizedTextDataSource, OtherContentsViewController → RecognizedTextDataSource, ReceiptContentsViewController → RecognizedTextDataSource.

Access control

Reference code

BusinessCompanion/AppDelegate.swift:11 — representative boundary

class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

}

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: Controller: BusinessCardContentsViewController, DataGatheringViewController, DocumentScanningViewController, OtherContentsViewController, ReceiptContentsViewController; DataSource: RecognizedTextDataSource; Delegate: AppDelegate.
• Protocols: RecognizedTextDataSource.
• Methods: availableContents, tableView, addRecognizedText, parseTextContents, viewDidLoad, scan, processImage, documentCameraViewController.
• Files: BusinessCompanion/AppDelegate.swift, BusinessCompanion/BusinessCardContentsViewController.swift, BusinessCompanion/DataGatheringViewController.swift, BusinessCompanion/DocumentScanningViewController.swift, BusinessCompanion/ReceiptContentsViewController.swift, BusinessCompanion/OtherContentsViewController.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, Vision, VisionKit 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.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation