Training a Create ML Model to Classify Flowers

At a glance

Project structure

Source bundle/
├── FlowerShop/
│   ├── AppDelegate.swift
│   ├── ProductViewController.swift
│   ├── ViewController.swift
│   ├── VisionViewController.swift
│   ├── Base.lproj/
│   │   ├── LaunchScreen.storyboard
│   │   └── Main.storyboard
│   ├── Info.plist
│   └── Product Resources/
│       └── ProductCatalog.plist
├── Training/
│   └── ImageClassifierPlayground.playground/
│       └── Contents.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── FlowerShop.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 7 project/configuration file(s) and 4 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["ProductViewController"]
    N3["Vision APIs"]
    N1 --> N2
    N2 --> N3

Reference code

FlowerShop/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 Vision.

Ownership and state

classDiagram
    AppDelegate o-- UIWindow : window
    ProductViewController o-- UIView : productView
    ProductViewController o-- UILabel : label
    ProductViewController o-- UIImageView : productPhoto

Ownership evidence

FlowerShop/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

FlowerShop/AppDelegate.swift:11 — representative type boundary

class AppDelegate: UIResponder, UIApplicationDelegate {
    
    var window: UIWindow?
    
}

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

Access control

Reference code

FlowerShop/ViewController.swift:18 — representative boundary

    private let session = AVCaptureSession()
    
    private var previewLayer: AVCaptureVideoPreviewLayer! = nil
    private let videoDataOutput = AVCaptureVideoDataOutput()
    
    private let videoDataOutputQueue = DispatchQueue(label: "VideoDataOutput", qos: .userInitiated, attributes: [], autoreleaseFrequency: .workItem)

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: ProductViewController, ViewController, VisionViewController; Delegate: AppDelegate.
• Protocols: no local protocol declaration in the scanned source.
• Methods: dismissProductView, awakeFromNib, viewDidLoad, captureOutput, didReceiveMemoryWarning, setupAVCapture, startCaptureSession, teardownAVCapture.
• Files: FlowerShop/AppDelegate.swift, FlowerShop/ProductViewController.swift, FlowerShop/ViewController.swift, FlowerShop/VisionViewController.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, AVFoundation, Vision, CreateMLUI 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