How apple/sample-backyard-birds works
Project type and purpose
• This is a multi-platform SwiftUI sample app (iOS/macOS, watchOS, interactive widgets) demonstrating:
• A local persistence layer powered by SwiftData (BackyardBirdsData)
• A reusable UI library built with SwiftUI (BackyardBirdsUI)
• Modular artwork via a layered Swift package (LayeredArtworkLibrary)
• Interactive widgets using App Intents
• In-app purchases via StoreKit’s ProductView and SubscriptionStoreView
A. Swift Package Modules (code + assets)
1. BackyardBirdsData
– Contains @Model entity definitions, relationships, data-generation helpers
– Persists to a local SwiftData store (on-device SQLite under the hood)
2. BackyardBirdsUI
– Reusable SwiftUI Views and Styles (BackyardList, BirdIcon, SupplyGauge, etc.)
– Depends on BackyardBirdsData for Observable models
3. LayeredArtworkLibrary
– Asset Catalogs and composition helpers for birds, plants, buildings, clouds
B. App Targets
1. Multiplatform App
– Entry: BackyardBirdsApp.swift
– Imports BackyardBirdsData, BackyardBirdsUI, LayeredArtworkLibrary
– Configures SwiftData container and injects into SwiftUI environment
– Renders core UI, handles StoreKit ProductView & SubscriptionStoreView
2. Watch App
– Entry: BackyardBirdsWatchApp.swift
– Lightweight SwiftUI UI tailored for watchOS
– Shares BackyardBirdsData models for persistence & logic
3. Widget Extension
– Entry: WidgetsBundle.swift
– Uses App Intents (ResupplyBackyardIntent, WidgetConfigurationIntent)
– Displays timelines via BackyardSnapshotTimelineProvider
– Shares BackyardBirdsData for live data
C. External Frameworks & Services
1. SwiftData
– Underlying persistence engine for BackyardBirdsData
2. SwiftUI / Observation
– UI framework and Observable integration for real-time updates
3. StoreKit
– ProductView & SubscriptionStoreView for in-app purchases
4. App Intents
– Interactive and configurable widget intents
• App Targets → import → Swift Package Modules
• App Targets ↔ SwiftData store (read/write)
• App Targets → render → SwiftUI views
• UI Views → bind → Observable models from BackyardBirdsData
• Widgets → handle → App Intents → invoke → SwiftData updates
• App Targets → request/display → StoreKit views (ProductView, SubscriptionStoreView)
Architectural patterns & principles
• Modularity via Swift Packages: clear separation of Data, UI, and Artwork
• MVVM-style separation: @Model classes (models) ↔ SwiftUI Views (views)
• Dependency injection: pass SwiftData container into environment
• Reuse of code across platforms: share Packages between iOS, watchOS, Widgets
• Single source of truth: persistent models are the canonical data