chore: sync content to repo (#10339)

Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>
2026-09-24 15:00:31 +08:00 · 2026-09-17 10:08:36 +02:00
parent 19db7968c8
commit d3c92b8ebc
127 changed files with 131 additions and 131 deletions
@@ -1,5 +1,5 @@
 # Accessibility Inspector
- 
+
 Accessibility Inspector is a tool in Xcode that audits UI elements for accessibility issues. It displays the accessibility properties of each element, runs automated audits to catch missing labels and low-contrast issues, and simulates VoiceOver navigation. It is the primary tool for testing and improving accessibility during development.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Alamofire
- 
+
 Alamofire is a Swift networking library built on top of URLSession that simplifies common networking tasks. It provides a clean, chainable API for making requests, handling authentication, and serializing responses. Alamofire is widely used in iOS projects that want a higher-level abstraction over raw URLSession without third-party dependencies for individual components.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # App Store Distribution
- 
+
 Distributing an iOS app through the App Store requires a paid Apple Developer Program membership, building a release archive signed with a distribution certificate, and submitting it through App Store Connect. The app goes through Apple's review process before becoming available to users. App Store Connect also manages metadata, screenshots, pricing, and release scheduling.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # App Store Optimization (ASO)
- 
+
 App Store Optimization (ASO) is the process of improving an iOS app's visibility and conversion rate in the App Store. It involves optimizing the app name, subtitle, keywords, screenshots, and description to rank higher in relevant searches. Effective ASO increases organic downloads without paid advertising spend.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # ARKit
- 
+
 ARKit is Apple's augmented reality framework for iOS. It uses the device's camera and motion sensors to track the physical world and overlay digital content on top of it. ARKit provides features like horizontal and vertical plane detection, image tracking, face tracking, and LiDAR scene reconstruction on supported devices.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Async / Await
- 
+
 Async/await is Swift's built-in structured concurrency model, introduced in Swift 5.5. Async functions can be suspended at await points without blocking a thread, allowing other work to proceed in the meantime. This makes asynchronous code significantly more readable and composable compared to callback and Combine-based approaches.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Auto layout
- 
+
 Auto Layout is a constraint-based layout system that defines the size and position of views relative to each other and to the container. It automatically adapts layouts for different screen sizes, orientations, and locales. Constraints are created visually in Interface Builder or programmatically using NSLayoutConstraint or anchor APIs.
@@ -1,5 +1,5 @@
 # Azure DevOps
- 
+
 Azure DevOps is Microsoft's suite of developer tools that includes a CI/CD pipeline service supporting iOS development. It uses macOS-hosted agents to run Xcode builds and Fastlane workflows, and integrates with Azure Repos, GitHub, and other source control systems. Azure DevOps is commonly used in enterprise organizations already invested in Microsoft tooling.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Basic Interfaces
- 
+
 Building a basic interface in UIKit involves adding views to a view controller's root view, setting up Auto Layout constraints, and wiring controls to code through IBOutlets and IBActions. Simple interfaces typically combine labels, buttons, text fields, and image views arranged into a readable, functional layout.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Basics / Creating Animations
- 
+
 Creating animations with Core Animation involves working with CALayer and CAAnimation subclasses. CABasicAnimation animates a single property from one value to another, while CAKeyframeAnimation defines multiple values along an animation path. Animations are applied to layer properties like position, opacity, transform, and background color.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Benefits over Objective-C
- 
+
 Swift offers several advantages over Objective-C including type safety with optionals, modern syntax that reduces boilerplate, cleaner closure support, and better performance in many scenarios. Swift code is generally easier to read, write, and maintain. The language also benefits from active development through the Swift Evolution open-source process.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Breakpoints
- 
+
 Breakpoints pause app execution at a specific line of code so the developer can inspect the current state of variables and the call stack. Xcode supports line breakpoints, symbolic breakpoints that trigger on a function name, and exception breakpoints that catch crashes automatically. Conditional breakpoints pause only when a specified expression evaluates to true.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Building Interfaces
- 
+
 Building interfaces in SwiftUI involves composing views using container types. VStack arranges views vertically, HStack arranges them horizontally, and ZStack layers them. The declarative approach means the layout is described statically and SwiftUI handles rendering and updates as state changes.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Callback Hell
- 
+
 Callback hell refers to deeply nested, hard-to-read code that results from chaining multiple asynchronous operations through callbacks. This pattern, sometimes called the pyramid of doom, was common in iOS development when completion handlers were the primary way to handle async work. Swift's async/await syntax resolves this by allowing sequential, readable async code.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Callbacks
- 
+
 Callbacks are functions passed as arguments to be executed when an asynchronous operation completes. In Swift, callbacks are implemented as closures. They are used for network completion handlers, animation callbacks, and event notifications, particularly in code that predates Swift's async/await concurrency model.

 Visit the following resources to learn more:
@@ -1,6 +1,6 @@
 # Capturing Values & Memory Mgmt.
- 
-Closures capture references to the variables and constants from their surrounding context. When a closure captures a class instance, it holds a strong reference by default, which can create retain cycles if the instance also holds the closure. Capture lists using [weak self] or [unowned self] break these cycles and are a required pattern in iOS Swift development.
+
+Closures capture references to the variables and constants from their surrounding context. When a closure captures a class instance, it holds a strong reference by default, which can create retain cycles if the instance also holds the closure. Capture lists using \[weak self\] or \[unowned self\] break these cycles and are a required pattern in iOS Swift development.

 Visit the following resources to learn more:

@@ -1,5 +1,5 @@
 # Carthage
- 
+
 Carthage is a decentralized dependency manager for iOS and macOS that builds frameworks from source and links them manually into the project. Unlike CocoaPods, Carthage does not modify the Xcode project file, giving developers full control over integration. Carthage has become less common as Swift Package Manager has matured.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # CI / CD
- 
+
 Continuous Integration and Continuous Delivery (CI/CD) for iOS automates building, testing, and distributing apps on every code change. CI/CD pipelines run on platforms like CircleCI, Jenkins, GitHub Actions, GitLab, and Azure DevOps. Automated pipelines catch regressions early, enforce code quality checks, and speed up the release process.
@@ -1,5 +1,5 @@
 # CircleCI
- 
+
 CircleCI is a cloud-based CI/CD platform that supports iOS development through macOS build environments with Xcode installed. It runs builds, executes test suites, and triggers Fastlane lanes for automated distribution. Pipelines are configured with YAML files and integrate with GitHub and Bitbucket repositories.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Closures
- 
+
 Closures are self-contained blocks of code that can capture and store references to values from the surrounding context. In Swift, closures are first-class types that can be passed as arguments, stored in variables, and returned from functions. They are the basis for callbacks, higher-order functions like map and filter, and completion handlers throughout the iOS SDK.
@@ -1,3 +1,3 @@
 # Cocoa Touch
- 
+
 Cocoa Touch is the topmost layer of the iOS architecture and provides the frameworks developers interact with most directly, including UIKit, SwiftUI, MapKit, and GameKit. It handles touch input, notifications, multitasking, and high-level app structure. Most iOS app code is written against Cocoa Touch APIs.
@@ -1,3 +1,3 @@
 # Code Quality Tools
- 
+
 Code quality tools for iOS enforce consistent style and detect potential issues in Swift code through static analysis. SwiftLint, Tailor, and SwiftFormat are the main tools available. Integrating them into the Xcode build process or CI pipeline ensures consistent code quality across the team.
@@ -1,5 +1,5 @@
 # Combine and MVVM
- 
+
 Combine integrates naturally with the MVVM pattern. ViewModels expose @Published properties that emit state changes, and Views subscribe to those values to update the UI automatically. Combine operators handle data transformation, network logic, and combining multiple sources within the ViewModel, keeping the UI layer simple.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Components
- 
+
 UIKit components are the built-in UI controls the framework provides, including UIButton, UILabel, UITextField, UISwitch, UISlider, UIImageView, and UITableView. Each component is a UIView subclass and can be customized through properties, subclassing, or delegation.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Concurrency and Multithreading
- 
+
 Concurrency and multithreading allow iOS apps to perform multiple operations simultaneously without blocking the main UI thread. iOS provides Grand Central Dispatch (GCD) and Operation Queues as the two main systems for managing concurrent work. Swift's async/await, introduced in Swift 5.5, is now the preferred approach for writing concurrent code.
@@ -1,3 +1,3 @@
 # Concurrency (GCD, async/await)
- 
+
 Concurrency in iOS allows multiple tasks to run in parallel to keep the UI responsive. Grand Central Dispatch (GCD) is the traditional approach, using dispatch queues to schedule work on background threads. Swift's async/await syntax, introduced in Swift 5.5, provides a more readable and structured way to write asynchronous code.
@@ -1,5 +1,5 @@
 # Concurrency
- 
+
 Swift's structured concurrency builds on async/await with additional primitives for parallel execution. async let runs multiple async operations concurrently, TaskGroup manages a dynamic set of concurrent child tasks, and actors protect shared mutable state from data races. The Swift concurrency model enforces safety through the Sendable protocol and actor isolation.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Core Data
- 
+
 Core Data is Apple's framework for persisting complex object graphs and relational data on iOS. It provides an abstraction layer over SQLite with tools for defining data models, fetching, filtering, and observing changes. Core Data supports undo/redo, background data operations, and CloudKit integration for syncing data across a user's devices.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Core OS
- 
+
 Core OS is the bottom layer of the iOS architecture, sitting directly above the hardware. It provides the Darwin kernel, security frameworks, and low-level system interfaces. Frameworks at this level include Security, Accelerate for math and signal processing, and ExternalAccessory for communicating with hardware accessories.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Core Services
- 
+
 Core Services is the second layer of the iOS architecture and provides fundamental system capabilities that apps depend on. It includes frameworks for networking, file access, data management, location, and iCloud. Higher-level frameworks in Cocoa Touch build on Core Services internally.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Data Persistence
- 
+
 Data persistence covers the different mechanisms iOS apps use to store data on-device across app sessions. Options include Core Data for complex object graphs, User Defaults for simple preferences, Keychain for sensitive credentials, SQLite for relational data, and the file system for arbitrary files.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Debug Navigator
- 
+
 The Debug Navigator appears during a debugging session and shows real-time data about the running app, including CPU, memory, disk, and network usage, as well as active threads and their states. It helps identify performance issues and excessive resource consumption without switching to a separate profiling tool.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Debugging Techniques
- 
+
 Debugging in iOS involves identifying and resolving issues in app behavior, performance, and memory. Xcode provides a built-in debugger with breakpoints and variable inspection, and Instruments provides deep profiling for CPU, memory, energy, and network usage.
@@ -1,5 +1,5 @@
 # Delegate Pattern
- 
+
 The delegate pattern is a core design pattern in iOS where one object delegates responsibility for certain behaviors to another through a protocol. UIKit uses delegation extensively, with UITableViewDelegate, UITextFieldDelegate, and URLSessionDelegate being common examples. Delegates allow customization of behavior without requiring subclassing.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Dependency Manager
- 
+
 Dependency managers automate adding, updating, and removing third-party libraries in an iOS project. The three main options are Swift Package Manager, CocoaPods, and Carthage. Each has different trade-offs around integration complexity, build speed, and the breadth of available packages.
@@ -1,5 +1,5 @@
 # Dynamic Library
- 
+
 A dynamic library is a compiled binary loaded into memory at runtime rather than being embedded in the app binary at link time. On iOS, third-party dynamic libraries must be bundled inside the app's framework folder. Dynamic frameworks allow code and resources to be shared between an app and its extensions.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Editors
- 
+
 Xcode provides different editor modes depending on the file being viewed. The standard editor shows a single file, the assistant editor displays two files side by side, and the version editor shows Git history for the current file. The editor area also hosts Interface Builder when a Storyboard or XIB file is open.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Error Handling
- 
+
 Swift provides a structured error handling model using the throw, try, and catch keywords. Functions that can fail declare throws in their signature, and callers handle errors using do-catch blocks. Swift also supports the Result type for propagating errors through asynchronous APIs.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # FastLane
- 
+
 Fastlane is an open-source automation tool for iOS development that handles repetitive tasks like building, testing, code signing, and uploading to App Store Connect. Workflows are defined in Ruby-based scripts called Fastfiles using reusable actions called lanes. Fastlane is widely used in iOS CI/CD pipelines to automate provisioning, screenshots, and App Store submissions.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # File System
- 
+
 The iOS file system sandboxes each app's data into private directories. The Documents directory is for user-facing files that should be backed up, the Caches directory is for regenerable data, and the tmp directory is for temporary files that do not need to persist. Apps use FileManager to create, read, write, move, and delete files within their sandbox.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Frameworks & Library
- 
+
 Frameworks and libraries are reusable packages of compiled code and resources that can be linked into iOS apps. Understanding the differences between XCFrameworks, static libraries, and dynamic libraries is important for packaging shared code, distributing SDKs, and managing binary dependencies.
@@ -1,5 +1,5 @@
 # GameKit
- 
+
 GameKit is Apple's framework for adding social gaming features to iOS apps. It provides APIs for leaderboards, achievements, multiplayer matchmaking, and real-time game sessions through Game Center. GameKit handles authentication with the user's Apple ID and integrates with the native Game Center UI.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # GCD
- 
+
 Grand Central Dispatch (GCD) is a C-based system for dispatching work to queues managed by the operating system. The main queue runs tasks on the main thread for UI updates, while serial and concurrent dispatch queues run background work. GCD is lightweight and efficient, and remains widely used alongside Swift's async/await model.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # GitHub Actions
- 
+
 GitHub Actions provides CI/CD automation directly within GitHub repositories. For iOS development, it uses macOS runners with Xcode installed to build apps, run tests, and trigger Fastlane workflows. Pipelines are defined in YAML workflow files and triggered by events like pull requests and pushes to main.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # GitLab
- 
+
 GitLab CI/CD is GitLab's built-in automation platform that runs pipelines on code changes. For iOS development, it uses GitLab Runners configured on macOS to execute Xcode builds and test suites. GitLab CI is tightly integrated with the GitLab source code platform and merge request workflow.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # GraphQL
- 
+
 GraphQL is a query language for APIs that allows clients to request exactly the data they need in a single request. iOS apps interact with GraphQL APIs using libraries like Apollo iOS. GraphQL reduces over-fetching and under-fetching of data, making it efficient for mobile clients on limited bandwidth.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Groups
- 
+
 Groups in Xcode are virtual folders used to organize files within the Project Navigator without necessarily reflecting the file system directory structure. They keep large projects organized by feature or layer. Developers can create and rename groups and move files between them without affecting how Xcode locates or compiles those files.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # History and Why Swift?
- 
+
 Swift was introduced by Apple in 2014 to address the limitations of Objective-C in terms of safety, performance, and developer experience. It was designed to be faster, more expressive, and safer by eliminating entire classes of bugs through optionals and strong typing. Apple open-sourced Swift in 2015, and it has since become one of the most widely adopted programming languages.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # HTTP / HTTPs
- 
+
 HTTP and HTTPS are the application-layer protocols used for communication between iOS apps and web servers. iOS enforces App Transport Security (ATS) by default, requiring HTTPS for most network requests. Understanding request methods, status codes, headers, and the request-response cycle is fundamental to working with any iOS networking stack.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # IBActions
- 
+
 IBActions connect UI controls in Interface Builder to methods in code that run when a user interacts with a control. Declaring a method with @IBAction allows it to be wired to a button, gesture recognizer, or other control in a Storyboard or XIB. When the user triggers the control, UIKit calls the connected method.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Implementing Delegates
- 
+
 Implementing a delegate involves defining a protocol with required methods, adding a weak delegate property to the delegating class, and calling delegate methods at the appropriate times. The conforming class implements the protocol methods to respond to events. The weak reference is necessary to prevent retain cycles between the delegate and the delegating object.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Installing
- 
+
 Installing Xcode is the first step in setting up an iOS development environment. Xcode is available for free from the Mac App Store and requires macOS and sufficient disk space. After installation, additional simulators and command-line tools can be added through Xcode settings.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Interface Builder
- 
+
 Interface Builder is the visual design tool embedded in Xcode for creating UI layouts without writing code. Developers drag UI elements onto a canvas, configure properties through the inspector, and set up constraints. Interface Builder generates XIB and Storyboard files that are compiled into the app bundle at build time.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Interface overview
- 
+
 The Xcode interface is organized into a navigator panel on the left, an editor area in the center, an inspector panel on the right, and a debug area at the bottom. The toolbar at the top provides controls for running, stopping, and switching build schemes. Understanding the layout helps developers move efficiently across code, assets, and project settings.
@@ -1,5 +1,5 @@
 # Interoperability with Swift
- 
+
 Swift and Objective-C can coexist in the same Xcode project through a bridging header mechanism. Swift code can call Objective-C APIs, and Objective-C code can use Swift classes marked with the @objc attribute. Interoperability is important when migrating legacy Objective-C projects to Swift incrementally.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Jenkins
- 
+
 Jenkins is an open-source automation server used for iOS CI/CD, particularly in enterprise environments. It runs on macOS machines and can execute Xcode builds, run tests, and invoke Fastlane workflows. Jenkins requires more infrastructure setup than cloud-based alternatives but offers maximum flexibility in configuration.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # JSON / XML
- 
+
 JSON and XML are the two most common data interchange formats used when communicating with web services or storing structured data locally. iOS apps frequently parse JSON responses from REST APIs and serialize Swift models into JSON before sending them. XML is less common but still used in some legacy APIs and standards like RSS.
@@ -1,5 +1,5 @@
 # Keeping Updated with WWDC
- 
+
 WWDC (Apple Worldwide Developers Conference) is Apple's annual developer event where new iOS, macOS, and framework announcements are made. Watching WWDC sessions, reading the associated documentation, and reviewing the release notes keeps iOS developers current with new APIs, deprecations, and best practices.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Keychain
- 
+
 The Keychain is iOS's secure, encrypted storage for sensitive data like passwords, tokens, and cryptographic keys. Data stored in the Keychain persists across app reinstalls and can be shared between apps from the same developer through Keychain Access Groups. Keychain access is managed through the Security framework's SecItem API.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Latest iOS SDK
- 
+
 The iOS SDK is updated each year with new APIs, deprecated frameworks, and changes to system behavior. New SDK features are announced at WWDC and documented in the release notes. Adopting the latest SDK allows apps to use new platform capabilities and ensures compliance with evolving App Store requirements.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Latest Swift Version
- 
+
 Apple releases new Swift versions annually alongside Xcode and iOS updates. New Swift versions introduce language features, performance improvements, and standard library additions. Tracking the Swift Evolution process and WWDC sessions on Swift helps developers adopt new capabilities and respond to deprecations promptly.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # MapKit
- 
+
 MapKit is Apple's framework for embedding maps and location-based features into iOS apps. It provides interactive map views, annotation pins, overlays, turn-by-turn directions, and local place search. MapKit uses Apple Maps as its data source and integrates with Core Location for GPS access.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Memory Management
- 
+
 iOS uses Automatic Reference Counting (ARC) to manage memory. ARC tracks how many strong references point to each object and deallocates it when the count drops to zero. Developers must understand strong, weak, and unowned references to avoid retain cycles, which cause memory leaks.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Modals and Navigation
- 
+
 Modal presentation in UIKit shows a view controller over the current content, typically for tasks that need the user's attention before they can continue. Modals are dismissed programmatically or by the user via drag or a dismiss button. Combining modal presentation with embedded navigation controllers creates flows like editing forms or settings sheets.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # MVC
- 
+
 MVC (Model-View-Controller) is the architectural pattern used by UIKit and historically recommended by Apple for iOS apps. The Model holds data and business logic, the View displays content, and the Controller mediates between them. In practice, UIKit view controllers tend to accumulate too much responsibility, a problem known as Massive View Controller.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # MVP
- 
+
 MVP (Model-View-Presenter) improves on MVC by separating UIKit view controllers into a passive View and a Presenter that contains all UI logic. The View delegates user interactions to the Presenter, which processes them and updates the View through a protocol-based interface. Moving logic out of the view controller makes it much easier to unit test.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # MVVM-C
- 
+
 MVVM-C extends the MVVM pattern by adding a Coordinator component that manages navigation between screens. Coordinators handle routing logic that would otherwise live in view controllers or ViewModels, making navigation testable and reusable. This separation is particularly valuable in apps with complex conditional navigation flows.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # MVVM
- 
+
 MVVM (Model-View-ViewModel) separates the UI layer from business logic using a ViewModel that exposes observable state. The View binds to the ViewModel and updates automatically when state changes, using Combine, RxSwift, or Swift's observation framework. MVVM is widely adopted in iOS development and works well with both UIKit and SwiftUI.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Navigation Controllers, Segues
- 
+
 UINavigationController manages a stack of view controllers with a navigation bar at the top. Segues are the transitions between view controllers defined in a Storyboard, triggered by user interaction or called programmatically. The prepare(for:sender:) method is used to pass data to the destination view controller before a segue executes.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Navigation Stacks
- 
+
 Navigation stacks in SwiftUI are managed by NavigationStack (iOS 16+), which maintains a path representing the current navigation state. Views are pushed onto the stack by navigating to a value, and the stack handles the back button automatically. The state-driven model enables programmatic navigation and full deep link support.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Navigation Stacks
- 
+
 The navigation stack in UIKit is managed by UINavigationController using a push-pop model. View controllers are pushed onto the stack when navigating forward and popped when the user taps the Back button or calls popViewController. The navigation bar automatically reflects the current top of the stack.
@@ -1,5 +1,5 @@
 # Navigation View
- 
+
 NavigationView is the SwiftUI component for hierarchical navigation, used before NavigationStack was introduced in iOS 16. It wraps a view and provides a navigation bar and back navigation behavior. NavigationView is still relevant for apps targeting iOS 15 and earlier.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Navigation
- 
+
 Navigation in SwiftUI is managed with NavigationStack (iOS 16+) or NavigationView for older deployment targets. NavigationLink connects the current view to a destination, and the navigation stack maintains a history that the user can traverse with the Back button. SwiftUI's navigation model is state-driven, enabling programmatic navigation and deep link support.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Navigators
- 
+
 The navigator panel contains multiple navigators for different purposes. The Project Navigator shows the file hierarchy, the Issue Navigator displays errors and warnings, the Test Navigator lists test suites, and the Debug Navigator shows runtime resource usage. Switching between navigators is done using the icons at the top of the panel.
@@ -1,5 +1,5 @@
 # Networking
- 
+
 Networking in iOS covers how apps communicate with remote servers and APIs. The native foundation is URLSession for HTTP requests, and Alamofire is a popular third-party library that simplifies common networking tasks. iOS apps commonly consume REST APIs over HTTPS and, increasingly, GraphQL APIs.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # New Feature Announcements
- 
+
 Apple announces new platform features at WWDC each year that affect how iOS apps are built and what they can offer users. Recent examples include StoreKit 2, Live Activities, WidgetKit updates, and Vision framework additions. Staying aware of these announcements helps iOS developers evaluate which new capabilities are relevant to their apps and plan adoption accordingly.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Objective-C Basics
- 
+
 Objective-C basics cover the core syntax and concepts needed to read and write Objective-C code. This includes pointers, message syntax, classes, categories, protocols, and property declarations. A working knowledge of these basics is useful when maintaining legacy codebases or interoperating with frameworks that expose Objective-C interfaces.
@@ -1,5 +1,5 @@
 # Objective-C
- 
+
 Objective-C is the original language for iOS and macOS development, widely used before Swift's introduction in 2014. It is a superset of C with Smalltalk-style message passing and object-oriented features. Many older iOS codebases and some Apple frameworks are still written in Objective-C, and it can be used alongside Swift in the same project.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Observables & observers
- 
+
 An Observable in RxSwift is a sequence that emits zero or more items over time before completing or erroring. Observers subscribe to Observables and receive emitted items, error notifications, or completion events. The relationship between Observable and Observer is the foundation of all RxSwift-based reactive code.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Operation Queues
- 
+
 Operation Queues manage collections of NSOperation objects and execute them concurrently or serially. Operations support dependencies on each other, cancellation, and priority settings. Operation Queues provide a higher-level abstraction than GCD and are useful when tasks have complex interdependencies or need explicit cancellation logic.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Operators & Pipelines
- 
+
 Combine operators transform, filter, and combine publishers into processing pipelines. Common operators include map, filter, flatMap, combineLatest, merge, and debounce. Chaining operators between a publisher and a subscriber creates a declarative pipeline that expresses complex asynchronous logic in a readable way.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Parsing
- 
+
 Parsing JSON in Swift is done using Codable and JSONDecoder, which automatically decode JSON data into Swift structs and classes. XMLParser provides a SAX-style parser for processing XML documents event by event. Correct parsing handles optional fields, nested structures, and type mismatches cleanly.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Pick a Language
- 
+
 iOS development primarily uses Swift and Objective-C. Swift is Apple's modern recommended language for new projects, while Objective-C is still present in many legacy codebases and system frameworks.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Presenting / Dismissing views
- 
+
 Presenting views in SwiftUI is done using modifiers like sheet, fullScreenCover, and popover that show views modally over the current screen. Dismissal is handled using the dismiss environment action or by toggling the Boolean binding that controls the presentation. Knowing when to present modally versus navigate is important for designing clear user flows.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Profiling Instruments
- 
+
 Instruments is a performance analysis tool bundled with Xcode that provides templates for profiling CPU usage, memory allocations, energy impact, network activity, and more. The Time Profiler identifies which functions consume the most CPU time, while the Allocations instrument tracks memory usage and helps detect leaks and retain cycles.

 Visit the following resources to learn more:
@@ -1,6 +1,6 @@
 # Project Files
- 
-The Project Navigator organizes all files in an Xcode project, including Swift source files, assets, configuration files, and frameworks. Files are listed hierarchically and can be added, deleted, or reorganized within the navigator. The project file (*.xcodeproj) stores build settings, targets, and file references.
+
+The Project Navigator organizes all files in an Xcode project, including Swift source files, assets, configuration files, and frameworks. Files are listed hierarchically and can be added, deleted, or reorganized within the navigator. The project file (\*.xcodeproj) stores build settings, targets, and file references.

 Visit the following resources to learn more:

@@ -1,5 +1,5 @@
 # Pushing Presenting
- 
+
 Pushing a view controller adds it to the navigation stack with a standard slide animation from the right. Presenting a view controller modally overlays it on the current screen, often as a sheet or full-screen cover. The choice between pushing and presenting depends on whether the new screen is part of the current flow or a separate, interruptive task.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # REST
- 
+
 REST (Representational State Transfer) is an architectural style for networked APIs that uses standard HTTP methods like GET, POST, PUT, PATCH, and DELETE. iOS apps consume REST APIs by making URLSession or Alamofire requests and decoding JSON responses using Codable. REST is the most common API style in iOS app development.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # RxSwift
- 
+
 RxSwift is the Swift implementation of the ReactiveX library, providing a comprehensive API for reactive programming. It introduces Observable sequences that emit items over time and a large set of operators for combining and transforming them. RxSwift was widely adopted in iOS development before Apple introduced Combine and remains in use in many codebases.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Schedulers
- 
+
 Schedulers in RxSwift control on which thread or queue Observable work executes. MainScheduler runs work on the main thread for UI updates, while ConcurrentDispatchQueueScheduler and SerialDispatchQueueScheduler run work on background queues. The observeOn and subscribeOn operators specify which scheduler handles observation and subscription respectively.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Serializing
- 
+
 Serializing converts Swift data structures into JSON or XML format for storage or network transmission. JSONEncoder turns Codable types into Data. Proper serialization handles date formats, custom key naming strategies, and optional values to produce valid output that the server or storage layer can interpret correctly.

 Visit the following resources to learn more:
@@ -1,3 +1,3 @@
 # Simple UI Building
- 
+
 Simple UI building in SwiftUI covers the fundamental skills for constructing working app screens. This includes composing layout containers, applying modifiers, connecting views to state, implementing navigation between screens, and adding animated transitions.
@@ -1,5 +1,5 @@
 # SQLite
- 
+
 SQLite is a lightweight, serverless relational database engine embedded in iOS. Apps can use SQLite directly through its C API or through higher-level Swift wrappers like GRDB or SQLite.swift. SQLite provides structured, queryable storage and serves as the underlying engine for Core Data and other data frameworks.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # State Management
- 
+
 State management in SwiftUI determines where data lives and how it flows through the view hierarchy. @State handles local view state, @StateObject owns an observable object, @ObservedObject observes an externally owned object, and @EnvironmentObject injects shared data across the hierarchy. Choosing the right property wrapper keeps the app's data flow predictable and organized.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Static Library
- 
+
 A static library is a compiled archive of object code that is copied directly into the app binary at link time. Static libraries increase binary size but have no runtime loading overhead. They are distributed as .a files and are commonly used to share compiled code between targets within the same Xcode project.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Stepping
- 
+
 Stepping controls in the Xcode debugger allow developers to move through code one statement at a time during a paused breakpoint session. Step Over executes the current line without descending into called functions, Step Into enters a called function, and Step Out completes the current function and returns to the caller.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Storyboards
- 
+
 Storyboards are XML-based files that define multiple view controllers and the transitions between them on a single visual canvas. Developers drag view controllers onto the canvas, design their views, and connect screens with segues. Storyboards give a visual overview of the app's entire navigation flow.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Subjects
- 
+
 Subjects in RxSwift act as both Observables and Observers, making them useful for bridging non-reactive code into reactive streams. PublishSubject emits only new items to subscribers; BehaviorSubject replays the last value to new subscribers; and ReplaySubject replays a configurable number of past values. Subjects are commonly used as input channels in MVVM ViewModels.

 Visit the following resources to learn more:
@@ -1,5 +1,5 @@
 # Swift Basics
- 
+
 Swift basics cover the fundamental syntax and language features needed to write Swift programs. This includes variables, constants, data types, control flow, functions, closures, classes, structs, enums, and optionals. A solid understanding of these basics is required before working with iOS frameworks and APIs.

 Visit the following resources to learn more:
@@ -1,10 +1,10 @@
 # Swift (Recommended)
- 
+
 Swift is Apple's modern, statically typed programming language for iOS, macOS, watchOS, and tvOS development. Introduced in 2014, it has become the recommended choice for new iOS projects. Swift features a clean syntax, strong type inference, optionals for safe null handling, and built-in concurrency support through async/await.

 Visit the following resources to learn more:

 - [@roadmap@Visit the Dedicated Swift & Swift UI Roadmap](https://roadmap.sh/swift-ui)
- [@official@Swift Documentation](https://www.swift.org/documentation/)
 - [@course@Programiz - Swift Programming Tutorials](https://www.programiz.com/swift-programming)
- [@course@HackingWithSwift - 100 Days of Swift](https://www.hackingwithswift.com/100)
+- [@course@HackingWithSwift - 100 Days of Swift](https://www.hackingwithswift.com/100)
+- [@official@Swift Documentation](https://www.swift.org/documentation/)
--- a/Show More
+++ b/Show More