Interacting with nearby points of interest

At a glance

Project structure

Source bundle/
├── PointsOfInterest-UIKit/
│   ├── AppDelegate.swift
│   ├── BaseMapItemViewController.swift
│   ├── SearchResultsViewController.swift
│   ├── MapViewController.swift
│   ├── SceneDelegate.swift
│   └── SidebarViewController.swift
├── PointsOfInterest/
│   ├── PointsOfInterestApp.swift
│   ├── ContentView.swift
│   ├── MapModel.swift
│   ├── MapView.swift
│   └── NavigationModel.swift
└── Shared/
    └── MapSearchConfiguration.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 7 project/configuration file(s) and 29 source declaration(s).

Overall architecture

flowchart LR
    Bundle["Sample bundle"]
    V1["PointsOfInterest-UIKit"]
    V2["PointsOfInterest"]
    Boundary["MapKit APIs"]
    Bundle --> V1
    V1 --> Boundary
    Bundle --> V2
    V2 --> Boundary

Reference code

PointsOfInterest-UIKit/AppDelegate.swift:10 — architecture anchor

@main
class AppDelegate: UIResponder, UIApplicationDelegate {
    
}

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
    Row *-- String : header
    Row o-- MKMapItem : mapItem
    Row o-- UICollectionViewDiffableDataSource : dataSource
    Row o-- UICollectionView : collectionView

Ownership evidence

PointsOfInterest-UIKit/BaseMapItemViewController.swift:18 — stored dependency or nearest verified ownership anchor

        var header: String?
        var mapItem: MKMapItem?
        
        init(header: String) {
            self.header = header
        }

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

PointsOfInterest-UIKit/SearchResultsViewController.swift:178 — representative type boundary

protocol SearchResultsViewControllerDelegate: NSObjectProtocol {
    /// The search results that `SearchResultsViewController` displays.
    func searchResultsViewController(_ viewController: SearchResultsViewController, didUpdate searchResults: [MKMapItem])
    
    /// The search results view controller calls this when the user selects a search result.
    func searchResultsViewController(_ viewController: SearchResultsViewController, didSelect mapItem: MKMapItem)
}

The source explicitly defines local protocol relationships: SidebarViewController → SearchResultsViewControllerDelegate.

Access control

Reference code

PointsOfInterest-UIKit/BaseMapItemViewController.swift:40 — representative boundary

    private func configureViewHierarchy() {
        collectionView = UICollectionView(frame: view.bounds, collectionViewLayout: createLayout())
        collectionView.autoresizingMask = [.flexibleWidth, .flexibleHeight]
        view.addSubview(collectionView)
    }

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: PointsOfInterestApp; Controller: BaseMapItemViewController, MapViewController, SearchResultsViewController, SidebarViewController; DataSource: SearchDataSource; Delegate: AppDelegate, SceneDelegate, SearchResultsViewControllerDelegate; Model: MapModel, NavigationModel; Service: LocationService; View: ContentView, MapItemRowView, MapView, SearchCompletionItemView, SettingsView.
• Protocols: SearchResultsViewControllerDelegate.
• Methods: viewDidLoad, configureViewHierarchy, createLayout, configureDataSource, updateCollectionViewSnapshot, configureHeaderCell, configureResultCell, presentMapItemDetail.
• Files: PointsOfInterest-UIKit/AppDelegate.swift, PointsOfInterest/PointsOfInterestApp.swift, PointsOfInterest-UIKit/BaseMapItemViewController.swift, PointsOfInterest-UIKit/SearchResultsViewController.swift, Shared/MapSearchConfiguration.swift, PointsOfInterest-UIKit/MapViewController.swift.

Architecture takeaways

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