Sharing Your Location to Find a Park

At a glance

Project structure

Source bundle/
├── Park Finder (UIKit)/
│   └── Park Finder/
│       ├── main.m
│       ├── AppDelegate.h
│       ├── AppDelegate.m
│       ├── SceneDelegate.m
│       ├── ViewController.m
│       ├── SceneDelegate.h
│       └── ViewController.h
├── Park Finder (SwiftUI)/
│   └── Park Finder/
│       ├── ParkFinder.swift
│       ├── ContentView.swift
│       ├── Coordinator.swift
│       └── MapView.swift
└── Configuration/
    └── SampleCode.xcconfig

Structure observations

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

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["Park Finder (SwiftUI)"]
    V2["Park Finder (UIKit)"]
    Boundary["CoreLocation APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary

Reference code

Park Finder (UIKit)/Park Finder/main.m:11 — architecture anchor

int main(int argc, char * argv[]) {
    NSString * appDelegateClassName;
    @autoreleasepool {
        appDelegateClassName = NSStringFromClass([AppDelegate class]);
    }
    return UIApplicationMain(argc, argv, nil, appDelegateClassName);
}

Interpretation

The branches represent separate entry-bearing project variants in the downloaded bundle, not runtime calls between those variants. Each branch is intentionally collapsed at the documented framework boundary; the detailed target-local flow remains in the cited files. Ownership is claimed only where the next section cites a stored property or assignment.

Ownership and state

classDiagram
    ContentView *-- CLLocationManager : manager
    Coordinator o-- MapView : parent
    MapView o-- CLLocationManager : manager
    MapView *-- MKMapView : map

Ownership evidence

Park Finder (SwiftUI)/Park Finder/ContentView.swift:13 — stored dependency or nearest verified ownership anchor

    @State var manager = CLLocationManager()

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

Park Finder (UIKit)/Park Finder/AppDelegate.h:10 — representative type boundary

@interface AppDelegate : UIResponder <UIApplicationDelegate>


@end

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

Access control

Reference code

Park Finder (SwiftUI)/Park Finder/Coordinator.swift:19 — representative boundary

    private func addPins(location: CLLocation) {
        // ...
    }

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: ViewController; Coordinator: Coordinator; Delegate: AppDelegate, SceneDelegate; View: ContentView, MapView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: application, scene, sceneDidDisconnect, sceneDidBecomeActive, sceneWillResignActive, sceneWillEnterForeground, sceneDidEnterBackground, viewDidLoad.
• Files: Park Finder (SwiftUI)/Park Finder/ParkFinder.swift, Park Finder (UIKit)/Park Finder/AppDelegate.h, Park Finder (SwiftUI)/Park Finder/ContentView.swift, Park Finder (UIKit)/Park Finder/AppDelegate.m, Park Finder (UIKit)/Park Finder/SceneDelegate.m, Park Finder (UIKit)/Park Finder/ViewController.m.

Architecture takeaways

• main is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, CoreLocation, MapKit, SwiftUI 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