watchOS With SwiftUI by Tutorials (Scott Grosch)（Z-Library）

【One-Line Pitch】 A hands-on guide to building Apple Watch apps with SwiftUI, covering the device-specific features that make watchOS different from iOS. Best for iOS developers who already know SwiftUI and want to ship a real Watch app without guessing at the platform's quirks. 【Book Arc】 - **Opening (~0%–10%)**: Sets up the case for the Apple Watch as a serious platform and gets you building a first watchOS app, showing how much existing iOS/SwiftUI knowledge transfers directly. - **Early (~10%–30%)**: Covers project structure (app vs. extension targets, schemes, display naming), the Digital Crown as an input, and Watch Connectivity for syncing data between the iPhone and Watch apps. - **Middle (~30%–50%)**: Moves into the Watch-specific surface area — Dock snapshots that show timely, contextual info, and notifications (short/long looks, sash, actions, local notifications). - **Late (~50%+ excerpt coverage thins here)**: The blurb points toward complications and HealthKit integration; the excerpts do not cover these chapters in detail, so treat that portion as promised rather than previewed. - **Ending**: Excerpts do not cover the closing chapters; expect the book to consolidate the above into a complete, shippable Watch app. 【Key Takeaways】 - **Your SwiftUI skills mostly carry over** (Opening): the first chapter deliberately shows that watchOS views are "just SwiftUI," which lowers the barrier for iOS developers. - **watchOS projects have a three-target structure** (Early): a wrapper target, a WatchKit App target, and a WatchKit Extension target — and it's the extension where your actual code lives. Understanding this prevents confusion when Xcode names or schemes don't match expectations. - **The Digital Crown is a first-class input** (Early): `digitalCrownRotation` lets you drive values from the crown, but you must handle floating-point precision and avoid redundant updates for performance. - **Watch Connectivity is not a single API** (Early): interactive messages are fast but not guaranteed (FIFO, async), while `transferUserInfo` and `updateApplicationContext` offer guaranteed or high-priority delivery — pick based on whether the data must arrive. - **Design for the wrist, not the phone** (Early): the book's movie-ticket example shows why posters and synopses get dropped on Watch — space is scarce, so prioritize what's glanceable. - **Snapshots should be contextual, not just "last screen"** (Middle): the Dock snapshot defaults to whatever was last visible, but a good app computes what the user actually wants to see (e.g., today's score vs. tomorrow's schedule) and schedules the next snapshot accordingly. - **Notifications have their own watchOS anatomy** (Middle): short look vs. long look, a customizable sash, and a system Dismiss button — and too many actions hurt the experience. - **HealthKit integration is part of the promise** (Late): the blurb highlights it as a capability you'll implement, though the excerpts don't detail the implementation. 【Reading Tips】 - **Deep-read the connectivity chapter**: the delivery-mode trade-offs (failable vs. guaranteed vs. high-priority) are the kind of detail that's easy to get wrong and hard to debug later. - **Skim the "Hello, Apple Watch" chapter if you're already fluent in SwiftUI** — its value is confirming what transfers, not teaching SwiftUI. - **Treat the snapshot chapter as a design lesson, not just an API lesson**: the real takeaway is anticipating user context, which applies beyond watchOS. - **Watch for the `#if os(watchOS)` / `#if os(iOS)` conditionals** in shared code — they're a recurring pattern for keeping one codebase across both platforms. - **Have Xcode open alongside**: this is a tutorial-driven book with sample projects (Pawsome, UHL, movie tickets), and the value comes from building, not just reading. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book (project setup through notifications); complications, HealthKit, and the closing chapters are referenced in the blurb but not detailed in the excerpts, so those sections are described only at the level the source material allows.