SwiftUI Apprentice Beginning iOS Programming with SwiftUI (Audrey Tam Caroline Begbie)（Z-Library）

【One-Line Pitch】 A hands-on, project-driven introduction to building real iOS apps with SwiftUI, guiding you from tool setup through a complete multi-screen app with data persistence, polish, and even widgets. Best for Swift beginners and developers moving from UIKit who want to learn by building rather than by reading theory. 【Book Arc】 - **Opening (~0%–10%)**: Sets up your environment (Mac, Xcode, Apple ID) and frames app development as a planning problem — inventorying screens and separating what users see from what the app does. - **Early (~10%–30%)**: Builds the core app screen by screen: prototyping views, organizing data with structs and enums, and wiring up navigation, ratings, and timers. - **Middle (~30%–50%)**: Introduces data persistence — saving settings with AppStorage/SceneStorage, serializing history to property lists, and refining appearance with custom button styles and shadows. - **Late (~50%–70%)**: Broadens context with Apple platform history and the SwiftUI vs. UIKit trade-off, helping you understand where SwiftUI fits in the ecosystem. - **Ending (~70%–100%)**: Extends the app outward with WidgetKit — creating widget extensions, timelines, and deep links back into the app. 【Key Takeaways】 - **Plan before you code** (Opening): The book treats app design as an inventory exercise — list screens, describe contents, and prototype before writing views. - **Everything is a View, and small views win** (Early): SwiftUI encourages many small subviews over monolithic ones, keeping code DRY without hurting performance. - **Data modeling drives the UI** (Early): Structs, enums with raw values, and type properties (like a static `exercises` array) form the backbone that views read from. - **Persistence is a spectrum** (Middle): Simple settings fit AppStorage/SceneStorage, while structured history needs property list serialization and error handling. - **Styling is a first-class skill** (Middle): Custom button styles, shapes, and shadows (including neumorphism) show that polish matters even without a designer. - **SwiftUI has context and limits** (Late): Understanding Apple's platform history and the SwiftUI/UIKit relationship helps you know when to reach for each. - **Apps extend beyond the screen** (Ending): Widgets, timelines, and deep links turn a single app into part of the broader iOS surface. 【Reading Tips】 - **Deep-read the early chapters** on tooling and data organization — they set patterns you'll reuse throughout. - **Skim the platform history section** (~48%) if you're focused purely on coding; it's context, not instruction. - **Type the code yourself** rather than copying — the book's value is in the Xcode workflow, auto-suggestions, and error-fixing habits. - **Treat persistence chapters as the hardest stretch** — string indexing and property list serialization are the trickiest concepts. - **Build the widget chapter last** — it assumes the app is complete and working. 【Coverage Limits】 These excerpts cover the book's structure, early chapters, and selected middle/late topics; detailed content from later chapters (widgets, deep-linking) is only partially represented, so some specifics are inferred from chapter titles and section markers.