swift-ios

Topics in the source

• Swift iOS
• Quick Start
• When to Use
• Best Practices
• SwiftUI Views
• State Management
• Concurrency
• Networking & Persistence

Building native iOS apps with Swift and SwiftUI. Native iOS/macOS/watchOS apps Modern SwiftUI interfaces Teams using Swift concurrency Apps for the App Store Build declarative views from state Use @State, @Binding, @Observable Keep views small and composable Use SwiftUI navigation and sheets Model state with @Observable classes Derive views from published state Use environment for shared objects Avoid storing derived data Use async/await and actors Scope tasks to view lifecycle Use Task and MainActor for UI Avoid data races with actors Fetch with async/await Decode with Codable Cache with SwiftData or Core Data Handle errors and retries 1. Create a SwiftUI project. 2. Model the domain with Codable types. 3. Build views from @Observable state. 4. Add navigation and sheets. 5. Fetch data with async/await. 6. Persist with SwiftData when needed. 7. Handle errors and loading states. 8. Test with XCTest/XCUITest. 1. Project builds without errors 2. Views react to state changes 3. Async work is scoped and safe 4. Navigation works end to end 5. Unit/UI tests pass Main actor errors: mark UI code @MainActor. Data races: use actors for shared state. Broken decoding: align Codable with the API

This is an excerpt. Refer to the complete source and its current requirements.