chore: sync content to repo (#10177)

Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>
2026-09-24 15:00:31 +08:00 · 2026-07-24 12:42:47 +02:00
parent 459680e17a
commit 33df3b1757
169 changed files with 540 additions and 831 deletions
@@ -1,8 +1,8 @@
 # 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.

-The Accessibility Inspector is a powerful tool in Xcode that helps developers ensure their iOS applications are accessible to users with disabilities. It provides a comprehensive view of an app's accessibility features, allowing developers to inspect and test various accessibility attributes of UI elements. The inspector displays information such as accessibility labels, hints, and traits for each element on the screen. It enables real-time simulation of different accessibility settings, such as VoiceOver, to test how the app behaves under various accessibility conditions. Developers can use the Accessibility Inspector to identify and fix issues related to screen reader compatibility, color contrast, and touch target sizes. This tool is crucial for creating inclusive apps that comply with accessibility guidelines and standards, ensuring that apps are usable by people with visual, auditory, motor, or cognitive impairments. Regular use of the Accessibility Inspector throughout the development process helps in building more universally accessible and user-friendly iOS applications.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Accessibility Inspector](https://developer.apple.com/documentation/accessibility/accessibility-inspector)
 - [@official@Inspecting the accessibility of the screens in your app](https://developer.apple.com/documentation/accessibility/inspecting-the-accessibility-of-screens)
@@ -1,6 +1,7 @@
 # Accessibility
+
 With built-in accessibility features, accessibility APIs, and developer tools, Apple operating systems provide extraordinary opportunities to deliver high-quality experiences to everyone, including people with disabilities. Take advantage of VoiceOver — the revolutionary screen reader for blind and low-vision users — Music Haptics, Switch Control, Guided Access, Text to Speech, closed‑captioned or audio‑described video, and more.

 Visit the following resources to learn more:

- [@official@Accessibility](https://developer.apple.com/accessibility/)
+- [@official@Accessibility](https://developer.apple.com/accessibility/)
@@ -1,8 +1,8 @@
 # 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.

-Alamofire is a popular third-party networking library for iOS, built on top of Apple's URLSession. It offers a more elegant and simplified interface for common networking tasks, making it easier to write concise and readable networking code. Alamofire provides a chainable request/response API, automated JSON parsing, authentication handling, and convenient methods for common HTTP operations. It supports features like request/response interceptors, network reachability monitoring, and robust error handling. The library is particularly useful for working with RESTful APIs, offering easy integration with JSON and Swift's Codable protocol. Alamofire's modular architecture allows for easy extension and customization, making it adaptable to various project needs. While it adds an external dependency to projects, many developers find that Alamofire's convenience and feature set outweigh this consideration, especially in complex networking scenarios where it can significantly reduce boilerplate code and simplify network request management.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@opensource@Alamofire/Alamofire](https://github.com/Alamofire/Alamofire)
 - [@article@Alamofire Tutorial with Swift (Quickstart)](https://codewithchris.com/alamofire/)
@@ -1,18 +1,10 @@
 # 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.

-App Store distribution is the process of preparing and submitting an iOS application for release on Apple's App Store. This involves several key steps: 
-
-1. App Store Connect Setup: Registering your app in App Store Connect, including adding app metadata, screenshots, and descriptions.
-2. Certificates and Provisioning Profiles: Creating the necessary certificates and provisioning profiles in the Apple Developer portal to sign your app for distribution.
-3. Build and Archive: Using Xcode to build and archive your app, ensuring it meets Apple’s guidelines and standards.
-4. Submission: Submitting the app for review through App Store Connect, where Apple’s review team evaluates it for compliance with their guidelines.
-5. Release and Updates: Once approved, the app is published to the App Store. Developers can manage updates, monitor app performance, and respond to user feedback through App Store Connect.
-
-This process ensures that apps are of high quality, secure, and provide a good user experience before reaching the end users.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Distribute on App Store](https://developer.apple.com/distribute/)
 - [@official@Distributing Custom Apps](https://developer.apple.com/custom-apps/)
- [@video@Submit App to App Store (Upload iOS App)](https://www.youtube.com/watch?v=bz_KJdXylh0)
- [@article@Creating the iOS Provisioning Profiles](https://support.staffbase.com/hc/en-us/articles/115003598691-Creating-the-iOS-Provisioning-Profiles)
+- [@article@Creating the iOS Provisioning Profiles](https://support.staffbase.com/hc/en-us/articles/115003598691-Creating-the-iOS-Provisioning-Profiles)
+- [@video@Submit App to App Store (Upload iOS App)](https://www.youtube.com/watch?v=bz_KJdXylh0)
@@ -1,9 +1,9 @@
 # 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.

-App Store Optimization (ASO) is the process of improving the visibility and ranking of a mobile app within app stores like Apple's App Store and Google Play. The goal of ASO is to increase app downloads and user engagement. Key strategies include optimizing the app title and description with relevant keywords, creating compelling and clear app icons, and using high-quality screenshots and videos to showcase the app's features. Additionally, gathering positive user reviews and ratings, regularly updating the app to fix bugs and add new features, and encouraging user engagement can significantly enhance an app’s ranking. ASO also involves monitoring and analyzing performance metrics to continually refine and improve the app’s visibility and attractiveness to potential users. Effective ASO leads to higher organic downloads and better overall app performance.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

+- [@article@What is App Store Optimization (ASO)?](https://appradar.com/academy/what-is-app-store-optimization-aso)
 - [@video@5 Essential ASO Strategies to Boost Your App Store Ranking in 2024](https://www.youtube.com/watch?v=bqM9x-oRZOA)
- [@video@Advanced App Store Optimization Strategies for 2024](https://www.youtube.com/watch?v=d8TOuMnMv74)
- [@article@What is App Store Optimization (ASO)?](https://appradar.com/academy/what-is-app-store-optimization-aso)
+- [@video@Advanced App Store Optimization Strategies for 2024](https://www.youtube.com/watch?v=d8TOuMnMv74)
@@ -1,11 +1,9 @@
 # ARKit
-
-ARKit is Apple’s framework for creating `augmented reality (AR) experiences` on iOS devices.
-
-`Augmented reality (AR)` describes user experiences that add 2D or 3D elements to the live view from a device’s sensors in a way that makes those elements appear to inhabit the real world.
+ 
+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:

 - [@official@ARKit](https://developer.apple.com/documentation/arkit)
 - [@official@Setting up access to ARKit data](https://developer.apple.com/documentation/visionos/setting-up-access-to-arkit-data)
- [@article@Everything you need to know about Apple's augmented reality platform](https://www.pocket-lint.com/ar-vr/news/apple/141615-apple-ar-kit-explained/)
+- [@article@Everything you need to know about Apple's augmented reality platform](https://www.pocket-lint.com/ar-vr/news/apple/141615-apple-ar-kit-explained/)
@@ -1,8 +1,8 @@
 # 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.

-Async/await in Swift is a modern approach to handling asynchronous operations, introduced to simplify complex asynchronous code and mitigate the challenges of callback-based programming. This feature allows developers to write asynchronous code that looks and behaves like synchronous code, improving readability and maintainability. The 'async' keyword marks functions that can be suspended and resumed, while 'await' is used to call these functions and wait for their completion without blocking the entire thread. This pattern integrates seamlessly with Swift's error handling mechanism, allowing for more natural try-catch blocks in asynchronous contexts. Async/await works with Swift's structured concurrency system, including tasks and actors, to manage complex asynchronous operations more easily.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Async await in Swift explained with code examples](https://www.avanderlee.com/swift/async-await/)
 - [@article@Swift async await](https://www.hackingwithswift.com/swift/5.5/async-await)
@@ -1,7 +1,3 @@
 # Auto layout
-
-Auto Layout dynamically calculates the size and position of all the views in your view hierarchy, based on constraints placed on those views. For example, you can constrain a button so that it is horizontally centered with an Image view and so that the button’s top edge always remains 8 points below the image’s bottom. If the image view’s size or position changes, the button’s position automatically adjusts to match.
-
-Learn more from the following resources:
-
-[@official@Understanding Auto Layout](https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/AutolayoutPG/index.html)
+ 
+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.
@@ -2,7 +2,7 @@

 AVFoundation is a comprehensive framework for working with time-based audiovisual media on iOS-based platforms. It enables developers to play, create, and edit QuickTime movies and MPEG-4 files, as well as handle HLS streams. AVFoundation offers robust tools for audio and video capture, editing, and playback, allowing for advanced media functionalities like precise control over audio sessions, media composition, and real-time processing. It ensures high performance and flexibility for building rich multimedia experiences in apps.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@AVFoundation Documentation](https://developer.apple.com/av-foundation/)
 - [@article@Learning AVFoundation](https://medium.com/@divya.nayak/learning-avfoundation-part-1-c761aad183ad)
@@ -1,6 +1,8 @@
 # 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.

-Azure DevOps is a suite of development tools and services offered by Microsoft to support the entire software development lifecycle. It includes Azure Repos for source code management with Git repositories, Azure Pipelines for continuous integration and continuous deployment (CI/CD), Azure Boards for agile project management and tracking, Azure Artifacts for managing and sharing packages, and Azure Test Plans for manual and exploratory testing. Azure DevOps integrates seamlessly with a variety of third-party tools and services, offering flexibility and extensibility. It provides robust security features, comprehensive reporting, and scalable infrastructure, making it suitable for teams of all sizes. By using Azure DevOps, development teams can collaborate more effectively, automate their workflows, and deliver high-quality software more quickly and efficiently.
+Visit the following resources to learn more:

 - [@official@Azure DevOps Website](https://azure.microsoft.com/en-gb/products/devops)
 - [@article@Build, test, and deploy Xcode apps](https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/xcode?view=azure-devops)
@@ -1,11 +1,11 @@
 # 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.

-UIKit Basic Interfaces refer to the fundamental user interface elements provided by the UIKit framework for creating standard iOS app layouts. These include navigation bars (UINavigationBar) for hierarchical navigation, tab bars (UITabBar) for switching between app sections, toolbars (UIToolbar) for displaying action buttons, and status bars for system information. Basic interfaces also encompass common screen layouts like list views (UITableView), grid layouts (UICollectionView), and scroll views (UIScrollView) for handling content that exceeds screen size. Mastering these basic interfaces ensures developers can create consistent, platform-native app experiences that users find familiar and intuitive, while providing a solid foundation for more complex UI designs.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@UINavigationBar](https://developer.apple.com/documentation/uikit/uinavigationbar)
 - [@official@UITabBar](https://developer.apple.com/documentation/uikit/uitabbar)
 - [@official@UIToolBar](https://developer.apple.com/documentation/uikit/uitoolbar)
 - [@official@UITableView](https://developer.apple.com/documentation/uikit/uitableview)
- [@official@UICollectionView](https://developer.apple.com/documentation/uikit/uicollectionview)
+- [@official@UICollectionView](https://developer.apple.com/documentation/uikit/uicollectionview)
@@ -1,11 +1,10 @@
 # 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.

-Creating animations with Core Animation involves manipulating `CALayer` properties over time. Developers can use `CABasicAnimation` for simple property changes, or `CAKeyframeAnimation` for more complex, multi-step animations. Animations are added to layers using the `addAnimation(_:forKey:)` method. Common properties animated include position, bounds, transform, and opacity. Core Animation provides timing functions to control the pace of animations, and allows for grouping multiple animations using `CAAnimationGroup`. For view-level animations, UIView's animate methods serve as a convenient wrapper around Core Animation.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@CALayer Documentation](https://developer.apple.com/documentation/quartzcore/calayer)
- [@official@CABasicAnimation Documentation]
 - [@official@CAKeyframeAnimation Documentation](https://developer.apple.com/documentation/quartzcore/cakeyframeanimation)
-(https://developer.apple.com/documentation/quartzcore/cabasicanimation)
- [@article@What is CALayer?](https://www.hackingwithswift.com/example-code/calayer/what-is-calayer)
+- [@article@https://developer.apple.com/documentation/quartzcore/cabasicanimation](https://developer.apple.com/documentation/quartzcore/cabasicanimation)
+- [@article@What is CALayer?](https://www.hackingwithswift.com/example-code/calayer/what-is-calayer)
@@ -1,18 +1,8 @@
 # Benefits over Objective-C
-
-**Safety and Reliability:** Swift includes features like optionals and type inference that reduce common programming errors and crashes.
-
-**Modern Syntax:** Swift’s concise and clean syntax improves readability and maintainability.
-
-**Performance:** Swift is designed for speed and efficiency, often outperforming Objective-C in benchmarks.
-
-**Interoperability:** Swift can easily coexist with Objective-C, allowing for a gradual transition of codebases.
-
-**Memory Management:** Automatic Reference Counting (ARC) in Swift handles memory management across both procedural and object-oriented code, reducing memory leaks.
-
-**Playgrounds:** Swift's interactive playgrounds provide a dynamic environment for testing and learning Swift code.
+ 
+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:

- [@article@Swift vs Objective-C](https://www.waldo.com/blog/swift-vs-objective-c)
- [@feed@Explore top posts about C Programming](https://app.daily.dev/tags/c?ref=roadmapsh)
+- [@roadmap@Visit the Dedicated Swift & Swift UI Roadmap](https://roadmap.sh/swift-ui)
+- [@article@Swift vs Objective-C](https://www.waldo.com/blog/swift-vs-objective-c)
@@ -1,19 +1,8 @@
 # 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.

-Xcode debugger breakpoints are powerful tools for pausing program execution at specific points, allowing developers to inspect the application state and diagnose issues. Key features include:
-
-1. Line breakpoints: Set on specific code lines to pause execution.
-2. Symbolic breakpoints: Trigger on function or method names.
-3. Exception breakpoints: Pause when exceptions occur.
-4. Conditional breakpoints: Only activate when certain conditions are met.
-5. Action breakpoints: Perform custom actions when hit, like logging or running scripts.
-6. Breakpoint navigator: Centralized management of all breakpoints.
-7. Enable/disable options: Easily toggle breakpoints without removing them.
-8. Breakpoint groups: Organize and manage sets of related breakpoints.
-
-Breakpoints can be set by clicking in the gutter of the source editor or through the Breakpoint Navigator.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Setting breakpoints to pause your running app](https://developer.apple.com/documentation/xcode/setting-breakpoints-to-pause-your-running-app)
 - [@article@How to add and use a breakpoint in XCode](https://www.delasign.com/blog/xcode-add-use-breakpoint/)
@@ -1,9 +1,9 @@
 # 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.

-SwiftUI is Apple's modern framework for building user interfaces across all Apple platforms using Swift. It employs a declarative syntax where UI is described using Swift code, defining what should appear rather than how to create it. Xcode provides real-time previews of the UI as you code, enhancing the development experience. SwiftUI uses property wrappers like `@State` for managing UI state, and offers a flexible layout system with VStack, HStack, and ZStack. Complex UIs are built by composing smaller, reusable views, and data flow between views is managed using `@Binding` and `@ObservedObject`. The framework provides chainable modifiers for customizing view appearance and behavior, easy-to-implement declarative animations, and built-in support for common gestures. SwiftUI simplifies UI development by reducing boilerplate code and offering a more intuitive way to create responsive, adaptive interfaces that can target iOS, macOS, watchOS, and tvOS from a single codebase.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@ZStack](https://developer.apple.com/documentation/swiftui/zstack)
 - [@official@VStack](https://developer.apple.com/documentation/swiftui/vstack)
- [@official@HStack](https://developer.apple.com/documentation/swiftui/hstack)
+- [@official@HStack](https://developer.apple.com/documentation/swiftui/hstack)
@@ -1,8 +1,8 @@
 # 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.

-Callback hell, also known as the pyramid of doom, is a common issue in asynchronous programming where multiple nested callbacks create code that is difficult to read, understand, and maintain. This problem typically arises when dealing with multiple asynchronous operations that depend on each other's results. As callbacks are nested within callbacks, the code structure becomes deeply indented, resembling a pyramid shape. This nesting not only hampers code readability but also makes error handling and flow control more complex. To mitigate callback hell, developers often employ techniques such as modularizing code, using named functions instead of anonymous closures, or adopting more advanced asynchronous patterns. Modern Swift development addresses this issue through the use of promises, futures, completion handlers, and most recently, the async/await pattern, which provides a more linear and readable approach to handling asynchronous operations.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Avoiding callback hell in Swift](https://swiftrocks.com/avoiding-callback-hell-in-swift)
 - [@article@Say Goodbye to Callback Hell: A Beginner’s Guide to Async/Await in Swift](https://medium.com/@asumahbanda3/say-goodbye-to-callback-hell-a-beginners-guide-to-async-await-in-swift-4c3230183218)
@@ -1,9 +1,7 @@
 # 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.

-Callbacks in Swift provide a mechanism for asynchronous communication between different parts of an application. They allow a function to pass control back to the caller once a task is completed, making them particularly useful for handling time-consuming operations or events that occur at unpredictable times. In Swift, callbacks are often implemented using closures, which are self-contained blocks of functionality that can be passed around and executed later. This approach is commonly used in network operations, user interface events, and any scenario where the result of an operation isn't immediately available.
-
-While simple to implement for basic use cases, callbacks can lead to complex nested structures (often referred to as "callback hell") in more intricate scenarios. To mitigate this, Swift offers more advanced patterns like completion handlers, promises, and async/await syntax, which provide cleaner ways to handle asynchronous operations while maintaining the core concept of passing control back to the caller upon completion.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Use callback in swift (UIKit)](https://medium.com/@ravenst/use-callback-in-swift-uikit-7d5a85d37c9e)
@@ -1,8 +1,8 @@
 # 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.

-Capturing values in closures is a powerful feature in Swift that allows closures to access and retain variables from their surrounding context. When a closure captures a value, it creates a strong reference to that value, potentially extending its lifetime beyond its original scope. This behavior is crucial for maintaining state in asynchronous operations but can lead to memory management challenges if not handled carefully. Swift provides capture lists to explicitly define how values should be captured, allowing developers to specify weak or unowned references to avoid retain cycles. Proper management of captured values is essential for preventing memory leaks, especially in scenarios involving self-referential closures or delegate patterns. Understanding the implications of value capture and employing appropriate memory management techniques ensures efficient and leak-free use of closures in Swift applications, particularly in complex asynchronous and event-driven programming scenarios.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Capture lists in Swift](https://www.hackingwithswift.com/articles/179/capture-lists-in-swift-whats-the-difference-between-weak-strong-and-unowned-references)
 - [@article@Swift’s closure capturing mechanics](https://www.swiftbysundell.com/articles/swifts-closure-capturing-mechanics/)
@@ -1,8 +1,8 @@
 # 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.

-Carthage is a decentralized dependency manager for iOS and macOS development, offering a lightweight alternative to CocoaPods. It focuses on building frameworks rather than integrating directly into projects, giving developers more control over their project structure. Carthage fetches and builds dependencies as specified in a Cartfile, creating standalone frameworks that can be easily integrated into Xcode projects. This approach keeps the project's structure intact and allows for easier version control. Carthage supports both Swift and Objective-C libraries and works well with dynamic frameworks. It's particularly favored for its simplicity and non-invasive nature, as it doesn't modify project files or create workspaces. While Carthage requires manual framework linking, which can be more time-consuming initially, it offers faster build times and more flexibility in managing dependencies. This tool is often preferred by developers who desire more control over their dependency integration process and project structure.
+Visit the following resources to learn more:

-Learn more from the following resources:
-
- [@opensource@carthage/carthage](https://github.com/Carthage/Carthage)
- [@course@Carthage - Getting Started](https://www.kodeco.com/7649117-carthage-tutorial-getting-started)
+- [@course@Carthage - Getting Started](https://www.kodeco.com/7649117-carthage-tutorial-getting-started)
+- [@opensource@carthage/carthage](https://github.com/Carthage/Carthage)
@@ -1,9 +1,3 @@
 # CI / CD
-
-Continuous Integration (CI) and Continuous Deployment (CD) are practices aimed at improving software development efficiency and quality by automating the integration and delivery processes.
-
-Continuous Integration (CI) involves automatically integrating code changes from multiple contributors into a shared repository several times a day. Each integration is verified by an automated build, allowing teams to detect and address issues early. CI tools like Jenkins, GitHub Actions, and Travis CI run automated tests and ensure that new code commits do not break the existing functionality.
-
-Continuous Deployment (CD) extends CI by automating the release of validated changes to production. Every change that passes the automated tests is automatically deployed to the production environment, ensuring that the software is always in a release-ready state. This practice reduces the time between development and release, allowing for faster delivery of features and updates.
-
-Together, CI/CD practices help teams achieve rapid, reliable, and repeatable software delivery, fostering a culture of continuous improvement and agility.
+ 
+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,8 +1,8 @@
 # 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.

-CircleCI is a cloud-based continuous integration and continuous deployment (CI/CD) platform that automates the software development process, allowing teams to build, test, and deploy code efficiently. It offers both cloud and on-premises solutions, providing flexibility for different project requirements and security needs. CircleCI supports the definition and management of complex workflows with multiple jobs and dependencies, enabling parallel execution to optimize build times. It integrates seamlessly with Docker, allowing developers to use containers to ensure consistent environments across builds. Configuration is managed through YAML files, which define build processes and make them easily maintainable and version-controlled. The platform also offers extensive integrations with various version control systems, deployment services, and notification tools. CircleCI automatically scales to handle multiple concurrent builds, making it suitable for growing teams and larger projects. Its robust feature set and ease of use make it an excellent choice for streamlining CI/CD processes and improving software delivery performance.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@CircleCI Website](https://circleci.com)
 - [@article@Deploy iOS applications](https://circleci.com/docs/deploy-ios-applications/)
@@ -1,3 +1,3 @@
 # Closures
-
-Callback closures in Swift are a powerful and flexible way to handle asynchronous operations and event-driven programming. These closures are functions passed as arguments to other functions, which can be executed once a specific task or operation is completed. They allow for non-blocking execution of code, enabling the program to continue running while waiting for long-running tasks to finish. Callback closures are particularly useful in scenarios like network requests, file I/O operations, or user interface events. Swift's syntax for closures makes them concise and easy to use, with features like trailing closure syntax and capture lists for managing memory. While callback closures offer great flexibility, they can lead to nested code structures in complex scenarios, which has led to the development of more advanced patterns like promises and async/await to manage asynchronous code more elegantly.
+ 
+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,7 +1,3 @@
 # Cocoa Touch
-
-The Cocoa Touch layer in iOS provides the key frameworks needed to create apps for iOS devices. It offers extensive support for various user interface elements, gestures, animations, and event handling, making it central to developing interactive and visually appealing applications. Key components include UIKit for managing the graphical user interface, Foundation for essential data and network access, and Core Motion for handling device motion data. Additionally, frameworks like GameKit, MapKit, MessageUI, EventKit, and AVFoundation extend functionality for gaming, mapping, communication, event management, and multimedia.
-
-Cocoa Touch is responsible for the seamless integration of user interfaces and multimedia, supporting touch-based input, complex animations, and gesture recognizers through UIKit. AVFoundation provides robust tools for handling audio and video, essential for media-rich applications. GameKit offers features for game development, while MapKit integrates mapping services. MessageUI enables in-app communication via email and messages, and EventKit manages calendar events and reminders. These frameworks collectively empower developers to create rich, interactive, and high-performing iOS applications.
-
-You can learn more in depth information on the elements of the Cocoa Touch layer further down the roadmap in the UI Design & Framework sections.
+ 
+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.
@@ -6,4 +6,4 @@ Visit the following resources to learn more:

 - [@official@CocoaPods](https://cocoapods.org/)
 - [@video@How to install Cocoapods on Mac M1](https://www.youtube.com/watch?v=0EbUBgO681w)
- [@video@How to Fix Cocoapods Install Errors on an Apple Silicon Macs](https://www.youtube.com/watch?v=uZD2EQbBqPg)
+- [@video@How to Fix Cocoapods Install Errors on an Apple Silicon Macs](https://www.youtube.com/watch?v=uZD2EQbBqPg)
@@ -1,3 +1,3 @@
 # Code Quality Tools
-
-Code quality tools in iOS development are essential for maintaining high standards of code cleanliness, efficiency, and maintainability. These tools automate the process of identifying potential issues, enforcing coding standards, and improving overall code quality. Popular options include SwiftLint, which checks Swift code for style and conventions; SonarQube, which provides comprehensive code analysis for bugs, vulnerabilities, and code smells; and Codebeat, offering automated code reviews. Static analysis tools like Clang Static Analyzer help detect bugs and security issues. Continuous integration platforms often integrate these tools, running checks automatically with each commit. Code coverage tools measure the extent of test coverage, while performance profilers like Instruments help optimize app efficiency. By incorporating these tools into the development workflow, teams can catch issues early, maintain consistent coding standards, and produce more robust, maintainable iOS applications. Regular use of code quality tools contributes significantly to reducing technical debt and improving long-term project health.
+ 
+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,8 +1,8 @@
 # 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.

-Combine and MVVM (Model-View-ViewModel) form a powerful combination in iOS development. Combine's reactive approach complements MVVM's separation of concerns. In this pairing, ViewModels use Combine publishers to expose data streams to Views, which subscribe to these streams for reactive UI updates. Models can publish changes through Combine, which ViewModels then process and transform. This setup allows for clean, declarative bindings between Views and ViewModels, reducing boilerplate code and improving testability. Combine's operators facilitate complex data transformations within ViewModels, while its handling of asynchronous operations simplifies tasks like network requests.
-
-Learn more from the following resoureces:
+Visit the following resources to learn more:

 - [@article@MVVM Design Pattern with Combine Framework](https://medium.com/@mshcheglov/mvvm-design-pattern-with-combine-framework-on-ios-5ff911011b0b)
 - [@article@MVVM and Combine](https://betterprogramming.pub/uikit-mvvm-combine-912c80c02262)
@@ -1,9 +1,8 @@
 # Combine
-Combine is Apple's built-in framework for reactive programming, using the same publisher-subscriber pattern as most modern approaches to this issue.
-Combine introduces the concept of a `Cancellable` (i.e. a subscription) and many different operators to use on these Cancellables.
-When writing Combine code, developers will notice complex generic types. For this reason, type-erasure can be done through `AnyCancellable`.
+
+Combine is Apple's built-in framework for reactive programming, using the same publisher-subscriber pattern as most modern approaches to this issue. Combine introduces the concept of a `Cancellable` (i.e. a subscription) and many different operators to use on these Cancellables. When writing Combine code, developers will notice complex generic types. For this reason, type-erasure can be done through `AnyCancellable`.

 Visit the following resources to learn more:

 - [@official@Combine](https://developer.apple.com/documentation/combine)
- [@video@Understanding Combine](https://youtu.be/rz0yx0Qz2jE)
+- [@video@Understanding Combine](https://youtu.be/rz0yx0Qz2jE)
@@ -1,8 +1,8 @@
 # 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.

-UIKit components are the building blocks of iOS user interfaces, offering a wide range of pre-designed elements for creating functional and visually appealing apps. These include basic controls like `UIButton`, `UILabel`, and `UITextField` for user input and display; container views such as `UITableView` and `UICollectionView` for organizing content; `UINavigationController` and `UITabBarController` for app navigation; and `UIAlertController` for displaying alerts and action sheets. UIKit also provides components for more specialized functions, like `UIImageView` for displaying images, `UIScrollView` for scrollable content, and `UIPickerView` for selection interfaces. 
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@UIKit Component Styling](https://medium.com/@greenSyntax/uikit-component-styling-in-ios-ae218ae4823e)
 - [@article@Customizable UI Components on iOS Using UIKit](https://pspdfkit.com/blog/2023/customizable-ui-components/)
@@ -2,8 +2,8 @@

 Components are built by composing primitive views like Text, Image, and Button, along with container views such as VStack and HStack. They can accept parameters for customization and use `@State` and `@Binding` for internal state management and data flow. SwiftUI's modifiers allow for styling and behavior adjustments. Components can be extracted into separate files for reusability across the app. This approach encourages a modular design, improving code organization and maintainability.

-Learn more from the following resources:
+Visit the following resources to learn more:

- [@article@SwiftUI Components](https://designcode.io/swiftui-handbook-components)
 - [@course@Building Reusable SwiftUI Components](https://peterfriese.github.io/Building-SwiftUI-Components-Tutorial/tutorials/tutorial-table-of-contents/)
+- [@article@SwiftUI Components](https://designcode.io/swiftui-handbook-components)
 - [@video@Building SwiftUI Components](https://www.youtube.com/playlist?list=PLsnLd2esiGRTfzn8pq4ZMYyDsL8GEMZO8)
@@ -1,3 +1,3 @@
 # Concurrency and Multithreading
-
-Concurrency and multithreading in iOS development enable applications to perform multiple operations simultaneously, improving responsiveness and performance. iOS provides several mechanisms for managing concurrent tasks, including Grand Central Dispatch (GCD) and Operation queues. GCD offers a low-level API for dispatching tasks to concurrent queues, while Operation queues provide a higher-level, object-oriented approach. Swift's modern concurrency features, including async/await and actors, offer a more intuitive way to write asynchronous code, reducing complexity and potential threading issues. These tools allow developers to offload time-consuming tasks from the main thread, ensuring a smooth user interface. Proper use of concurrency involves careful management of shared resources to avoid race conditions and deadlocks. Understanding thread safety, queue priorities, and synchronization techniques is crucial for developing efficient and responsive iOS applications that can effectively utilize modern multi-core devices.
+ 
+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,5 +1,3 @@
 # Concurrency (GCD, async/await)
-
-Concurrency in iOS development refers to executing multiple tasks simultaneously, improving app performance and responsiveness. Grand Central Dispatch (GCD) is a low-level API that manages concurrent operations through queues, while async/await is a modern Swift feature that simplifies asynchronous code. These tools allow developers to perform time-consuming tasks (like network requests or complex calculations) in the background without freezing the UI. By leveraging concurrency, iOS apps can efficiently utilize device resources, handle multiple operations simultaneously, and maintain a smooth user experience even during intensive processing tasks.
-
-iOS specific concurrency is covered later in the roadmap.
+ 
+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,9 +1,9 @@
 # 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.

-Swift's concurrency model centers on async/await syntax, allowing asynchronous code to be written in a clear, sequential manner. It employs actors to manage shared mutable state safely, and the Task API for handling concurrent work. Structured concurrency ensures proper task lifecycle management. The language also offers async sequences and streams for working with asynchronous data, and the Sendable protocol to guarantee thread-safe data sharing. This comprehensive approach enables developers to write efficient, safe concurrent code while minimizing common issues like race conditions and deadlocks.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Swift Documentation (How to interact)](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/concurrency/)
 - [@official@Apple Documentation (Signatures for interaction)](https://developer.apple.com/documentation/swift/concurrency)
- [@article@Concurrency bu Example](https://www.hackingwithswift.com/quick-start/concurrency)
+- [@article@Concurrency bu Example](https://www.hackingwithswift.com/quick-start/concurrency)
@@ -2,7 +2,7 @@

 Core Animation is a robust animation framework in iOS that enables developers to create smooth and visually engaging animations. It provides a simple yet powerful API for animating views and other visual elements, allowing for complex motion effects with minimal code. Core Animation handles the rendering and compositing of animated content efficiently, ensuring high performance and fluid user experiences in applications.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Core Animation Documentation](https://developer.apple.com/documentation/quartzcore)
 - [@video@Introduction to Core Animation](https://www.youtube.com/watch?v=93bfh3GK79s)
@@ -2,6 +2,6 @@

 Core Animation is a powerful framework in iOS that allows developers to create rich and interactive animations. It works by compositing layers, each representing a view, and uses hardware acceleration to ensure smooth animations. Core Animation simplifies the process of animating properties such as position, scale, and opacity, providing implicit and explicit animation techniques. It enhances the user interface experience by enabling complex visual effects, transitions, and animations with minimal impact on performance, making it essential for crafting visually appealing iOS applications.

-Learn more from the following resources:
+Visit the following resources to learn more:

- [@official@Core Animation Documentation](https://developer.apple.com/documentation/quartzcore)
+- [@official@Core Animation Documentation](https://developer.apple.com/documentation/quartzcore)
@@ -2,7 +2,7 @@

 Core Audio is a low-level framework in iOS designed for handling audio. It provides developers with advanced capabilities for recording, processing, playing back, and streaming audio. Core Audio supports various audio formats and offers precise control over audio data, enabling tasks such as real-time audio manipulation, audio mixing, and effects processing. With its high-performance and low-latency features, Core Audio is ideal for professional audio applications and complex audio signal processing tasks.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Core Audio Documentation](https://developer.apple.com/documentation/coreaudio)
 - [@article@Working with Core Audio](https://medium.com/@ios_guru/core-audio-for-working-with-audio-7c293382ffca)
@@ -1,9 +1,8 @@
 # Core Data
-Use Core Data to save your application’s permanent data for offline use, to cache temporary data, and to add undo functionality to your app on a single device. To sync data across multiple devices in a single iCloud account, Core Data automatically mirrors your schema to a CloudKit container.
-
-Through Core Data’s Data Model editor, you define your data’s types and relationships, and generate respective class definitions. Core Data can then manage object instances at runtime to provide the following features.
+ 
+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:

 - [@official@CoreData](https://developer.apple.com/documentation/coredata/)
- [@video@iOS Core Data Quick Start](https://www.youtube.com/watch?v=O7u9nYWjvKk)
+- [@video@iOS Core Data Quick Start](https://www.youtube.com/watch?v=O7u9nYWjvKk)
@@ -2,7 +2,7 @@

 Core Graphics, also known as Quartz, is a powerful 2D graphics rendering framework in iOS. It provides essential functions for drawing shapes, images, and text, handling low-level graphic operations with precision and efficiency. Core Graphics supports advanced features like color management, path-based drawing, and anti-aliasing, enabling developers to create detailed and visually appealing graphics within their applications.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Core Graphics Documentation](https://developer.apple.com/documentation/coregraphics)
 - [@video@Introduction to Core Graphics](https://www.youtube.com/watch?v=won0gA05ce0)
@@ -2,7 +2,7 @@

 Core Image is a powerful framework in iOS for image processing and analysis. It provides a wide array of built-in filters for tasks such as enhancing photos, applying artistic effects, and performing face detection. Core Image leverages GPU acceleration to ensure high performance and real-time processing capabilities. With support for custom filters and flexible integration with other graphics technologies, Core Image enables developers to create complex visual effects and perform sophisticated image manipulations within their applications.

-Learn more from the following resources:
+Visit the following resources to learn more:

- [@official@Core Image Documentation](https://developer.apple.com/documentation/coreimage)
- [@course@Core Image Tutorial](https://www.kodeco.com/30195423-core-image-tutorial-getting-started)
+- [@course@Core Image Tutorial](https://www.kodeco.com/30195423-core-image-tutorial-getting-started)
+- [@official@Core Image Documentation](https://developer.apple.com/documentation/coreimage)
@@ -1,7 +1,8 @@
 # Core ML
+
 Use `Core ML` to integrate machine learning models into your app. Core ML provides a unified representation for all models. Your app uses Core ML APIs and user data to make predictions, and to train or fine-tune models, all on a person’s device.

 Visit the following resources to learn more:

 - [@official@Core ML](https://developer.apple.com/documentation/coreml/)
- [@official@Create machine learning models for use in your app.](https://developer.apple.com/machine-learning/create-ml/)
+- [@official@Create machine learning models for use in your app.](https://developer.apple.com/machine-learning/create-ml/)
@@ -1,14 +1,10 @@
 # Core OS
-
-The Core OS layer in iOS is the foundation upon which the entire operating system is built, providing essential low-level services that ensure the system’s security, performance, and efficiency. This layer includes the kernel, which manages system resources and hardware abstraction, and device drivers that facilitate communication between the OS and hardware. Core OS also encompasses security frameworks, such as the Secure Enclave for handling encryption keys and biometric data, and Keychain Services for secure storage of sensitive information.
-
-Core OS supports essential functionalities like the Apple File System (APFS), which offers features like encryption and snapshotting, efficient memory management, and robust networking capabilities. It also includes power management features to extend battery life, inter-process communication (IPC) mechanisms for multitasking, and core system libraries like libdispatch for concurrency. By providing these foundational services, Core OS ensures that higher-level software can operate efficiently and securely on iOS devices.
+ 
+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:

 - [@article@Kernel API](https://developer.apple.com/documentation/kernel)
 - [@article@System Configuration](https://developer.apple.com/documentation/systemconfiguration)
 - [@article@Apple File System Guide](https://developer.apple.com/documentation/foundation/file_system/about_apple_file_system)
- [@article@Keychain Services](https://developer.apple.com/documentation/security/keychain_services)
- [@article@LibDispatch](https://developer.apple.com/documentation/dispatch)
- [@article@LibXPC](https://developer.apple.com/documentation/xpc)
+- [@article@Keychain Services](https://developer.apple.com/documentation/security/keychain_services)
@@ -1,9 +1,8 @@
 # Core Programming Concepts

-Core programming concepts for iOS development encompass fundamental principles essential for creating efficient and robust applications. These include understanding variables, data types, control structures (like loops and conditionals), functions, and object-oriented programming principles. iOS developers should also be familiar with memory management, error handling, and basic algorithms. 
+Core programming concepts for iOS development encompass fundamental principles essential for creating efficient and robust applications. These include understanding variables, data types, control structures (like loops and conditionals), functions, and object-oriented programming principles. iOS developers should also be familiar with memory management, error handling, and basic algorithms.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Programming Fundamentals](https://www.theknowledgeacademy.com/blog/programming-fundamentals/)
- [@article@What are the basic fundementals of programming?](https://www.educative.io/answers/what-are-the-basic-fundamental-concepts-of-programming)
-
+- [@article@What are the basic fundementals of programming?](https://www.educative.io/answers/what-are-the-basic-fundamental-concepts-of-programming)
@@ -1,16 +1,7 @@
 # Core Services
-
-The Core Services layer in iOS provides essential system services that support app development by offering a wide range of fundamental frameworks and capabilities. These services are crucial for enabling basic app functionality such as data management, networking, location services, motion sensing, and web content integration. By leveraging these core frameworks, you can efficiently handle tasks like data storage and persistence, network communication, and user location tracking, ensuring their apps are robust, responsive, and capable of interacting with various hardware and software components.
-
-Core Services are responsible for managing fundamental utilities and services that underpin iOS applications. This includes providing efficient data management solutions, robust networking capabilities, precise location data, and motion sensing features. Additionally, they facilitate seamless integration and manipulation of web content within apps.
+ 
+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:

- [@article@Core Services Layer Overview](https://developer.apple.com/documentation/coreservices)
- [@article@Core Foundation](https://developer.apple.com/documentation/corefoundation)
- [@article@Core Data](https://developer.apple.com/documentation/coredata)
- [@article@Core Location](https://developer.apple.com/documentation/corelocation)
- [@article@CFNetwork](https://developer.apple.com/documentation/cfnetwork)
- [@article@Core Motion](https://developer.apple.com/documentation/coremotion)
- [@article@Foundation](https://developer.apple.com/documentation/foundation)
- [@article@WebKit](https://developer.apple.com/documentation/webkit)
+- [@article@Core Services Layer Overview](https://developer.apple.com/documentation/coreservices)
@@ -2,7 +2,7 @@

 SwiftUI data binding is a mechanism that creates a two-way connection between a piece of data and a UI element. It uses the `@Binding` property wrapper to allow child views to share and modify data owned by parent views. Bindings ensure that changes in data are immediately reflected in the UI and vice versa. They are typically created using the `$` prefix on a `@State` property. This approach facilitates the flow of data through an app's view hierarchy, enabling reactive UI updates and maintaining a single source of truth.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Binding](https://developer.apple.com/documentation/swiftui/binding)
 - [@official@Apple Tutorials: Passing data with bindings](https://developer.apple.com/tutorials/app-dev-training/passing-data-with-bindings)
@@ -1,7 +1,7 @@
 # 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.

-Data persistence in iOS applications involves storing and retrieving data beyond the app's current runtime, ensuring information remains available across app launches and device restarts. Swift and iOS offer several mechanisms for data persistence, each suited to different needs and data complexities. Core Data provides a robust framework for managing and persisting large, structured datasets, offering features like data modeling, querying, and synchronization. For simpler data storage, UserDefaults is ideal for storing small amounts of key-value data. File system storage allows direct saving and loading of data to and from files in the app's sandbox. Keychain Services offer secure storage for sensitive information like passwords and tokens. SQLite databases can be used for more complex relational data storage needs. Additionally, CloudKit enables data synchronization across devices via iCloud. Choosing the appropriate persistence method depends on factors such as data structure, size, security requirements, and the need for synchronization across devices or with remote servers.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Apple Dev Training - Persisting Data](https://developer.apple.com/tutorials/app-dev-training/persisting-data)
@@ -1,20 +1,8 @@
 # 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.

-The Xcode Debug Navigator is a powerful tool in the Navigator pane that provides detailed information about the running application during debugging sessions. Key features include:
-
-1. Process hierarchy: Displays all running processes and threads.
-2. CPU and memory usage: Shows real-time performance metrics.
-3. Disk activity: Monitors file system operations.
-4. Network activity: Tracks network requests and responses.
-5. Energy impact: Measures the app's energy consumption.
-6. GPU usage: Monitors graphics processing utilization.
-7. iCloud activity: Tracks iCloud-related operations.
-8. Thread states: Visualizes the state of each thread (running, blocked, etc.).
-9. Stacktrace view: Allows navigation through the call stack of selected threads.
-
-The Debug Navigator helps developers identify performance bottlenecks, memory leaks, and other runtime issues. It's particularly useful for optimizing app performance and troubleshooting complex multi-threaded scenarios.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Debugging](https://developer.apple.com/documentation/xcode/debugging)
 - [@article@Exploring Xcode's Debugging Tools](https://cocoacasts.com/debugging-applications-with-xcode-exploring-xcode-debugging-tools)
@@ -1,3 +1,3 @@
 # Debugging Techniques
-
-Debugging techniques in iOS development include using Xcode’s integrated debugger, which allows developers to set breakpoints, inspect variables, and step through code to identify issues. Utilizing the LLDB (Low-Level Debugger) commands in the console helps examine program state and perform complex operations. Instruments, another powerful tool within Xcode, is used for profiling and identifying performance bottlenecks, memory leaks, and energy usage. Logging with NSLog or print statements can also provide insight into runtime behavior. Additionally, employing unit tests and running the application on real devices can help uncover device-specific issues and ensure code reliability.
+ 
+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.
@@ -2,7 +2,7 @@

 SwiftUI's declarative syntax allows developers to describe the desired UI state rather than the step-by-step process to achieve it. This approach uses Swift code to define what views should appear and how they should behave, with SwiftUI handling the underlying implementation details. Developers create views by combining and modifying smaller view components, using modifiers to adjust appearance and behavior. State management is integrated into this syntax, with UI automatically updating when state changes.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Declarative and Imperative Programming using SwiftUI and UIKit](https://medium.com/@rmeji1/declarative-and-imperative-programming-using-swiftui-and-uikit-c91f1f104252)
 - [@article@Apple's SwiftUI Declarative Framework](https://www.linkedin.com/pulse/apples-swiftui-declarative-framework-vivek-singh/)
@@ -1,8 +1,8 @@
 # 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.

-The delegate pattern is a widely used design pattern in iOS development that facilitates communication between objects in a flexible and decoupled manner. It allows one object to delegate certain responsibilities or decisions to another object, typically through a protocol. This pattern is particularly useful for handling events or customizing behavior without creating tight dependencies between classes. In implementation, a delegate protocol defines methods that the delegating object can call, while the delegate object conforms to this protocol and provides specific implementations. This approach promotes loose coupling, enhances reusability, and allows for easy customization of component behavior. The delegate pattern is extensively used in UIKit for handling user interactions, data source management, and event callbacks, making it a fundamental concept in iOS app architecture and design.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Mastering Swift Delegates](https://www.dhiwise.com/post/mastering-swift-delegates-a-comprehensive-guide)
 - [@article@A Step-by-Step Guide to the Delegate Pattern in Swift](https://medium.com/@afonso.script.sol/a-step-by-step-guide-to-the-delegate-pattern-in-swift-91a28de1baf8)
@@ -1,3 +1,3 @@
 # Dependency Manager
-
-Dependency managers in iOS development are tools that automate the process of adding, updating, and managing third-party libraries and frameworks in Swift and Objective-C projects. These tools simplify the integration of external code, ensuring version compatibility and reducing manual setup errors. The most popular dependency managers for iOS are CocoaPods, Carthage, and Swift Package Manager (SPM). CocoaPods, the oldest and most widely used, integrates directly with Xcode projects and offers a vast library of pods. Carthage provides a more decentralized approach, building frameworks separately from the main project. Swift Package Manager, integrated into Xcode, is Apple's official solution, offering seamless integration with Swift projects. Each manager has its strengths, with developers choosing based on project needs, team preferences, and specific library support. Effective use of dependency managers streamlines development workflows, promotes code reuse, and helps maintain up-to-date, efficient codebases in iOS applications.
+ 
+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,8 +1,8 @@
 # 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.

-Dynamic libraries in iOS development are code modules that are loaded into an app's memory at runtime rather than being compiled into the app's executable. They are typically distributed as .dylib files or packaged within frameworks. Unlike static libraries, dynamic libraries remain separate from the app's main binary, allowing for more efficient memory usage and smaller app sizes. Multiple apps can share a single copy of a dynamic library in memory, reducing overall system resource consumption. This approach facilitates easier updates to the library without requiring a full app recompilation. In iOS, dynamic libraries are primarily used within frameworks, as Apple restricts the use of standalone dynamic libraries in App Store submissions. Dynamic frameworks offer benefits like code modularity, easier sharing of code between apps, and potential performance improvements through reduced launch times. However, they introduce a slight runtime overhead for library loading. The use of dynamic libraries in iOS is subject to Apple's guidelines and is generally recommended for larger, frequently updated codebases or when sharing code across multiple apps.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Overview of Dynamic Libraries](https://developer.apple.com/library/archive/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/OverviewOfDynamicLibraries.html)
- [@article@Static Library vs Dynamic Library in iOS](https://pratheeshbennet.medium.com/static-library-vs-dynamic-library-in-ios-55478ed53a03)
+- [@article@Static Library vs Dynamic Library in iOS](https://pratheeshbennet.medium.com/static-library-vs-dynamic-library-in-ios-55478ed53a03)
@@ -1,7 +1,8 @@
 # Dynamic Type
+
 The Dynamic Type feature allows users to choose the size of textual content displayed on the screen. It helps users who need larger text for better readability. It also accommodates those who can read smaller text, allowing more information to appear on the screen. Apps that support Dynamic Type also provide a more consistent reading experience.

 Visit the following resources to learn more:

 - [@official@Dynamic Type](https://developer.apple.com/documentation/uikit/uifont/scaling_fonts_automatically/)
- [@official@WWDC24: Get started with Dynamic Type](https://www.youtube.com/watch?v=ZqDZjW9TpFw)
+- [@official@WWDC24: Get started with Dynamic Type](https://www.youtube.com/watch?v=ZqDZjW9TpFw)
@@ -1,17 +1,8 @@
 # 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.

-Xcode editors are the central workspace for code creation and modification. The main types include:
-
-1. Source Editor: For writing and editing code, featuring syntax highlighting, code completion, and inline documentation.
-2. Interface Builder: A visual editor for designing user interfaces, supporting both Storyboards and XIB files.
-3. Assistant Editor: Allows viewing related files side-by-side, useful for simultaneously editing header and implementation files.
-4. Version Editor: For comparing and merging different versions of a file.
-5. Property List Editor: A specialized editor for working with .plist files.
-6. Core Data Model Editor: For designing and managing Core Data models.
-
-The Editor area supports multiple tabs and split views, enabling developers to work on multiple files simultaneously.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Creating a source editor extension](https://developer.apple.com/documentation/xcodekit/creating-a-source-editor-extension)
 - [@official@Source Editor](https://developer.apple.com/documentation/xcode/source-editor)
@@ -1,8 +1,8 @@
 # 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.

-Error handling is a crucial programming concept for managing unexpected situations or failures during code execution. It involves anticipating potential issues, detecting when they occur, and responding appropriately. Common techniques include try-catch blocks, throwing and catching exceptions, and using error codes or result objects. Effective error handling improves program robustness, prevents crashes, aids in debugging, and enhances user experience by providing meaningful feedback. It allows developers to gracefully manage issues like invalid inputs, resource unavailability, or network failures, ensuring the program can recover or fail safely when problems arise.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@General Error Handling Rules - Google](https://developers.google.com/tech-writing/error-messages/error-handling)
 - [@article@Error Handling Patterns](https://andreabergia.com/blog/2023/05/error-handling-patterns/)
@@ -1,16 +1,8 @@
 # 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.

-Fastlane is an open-source platform designed to simplify and automate the deployment process of iOS (and Android) applications. It provides a suite of tools to streamline various tasks such as building, testing, and releasing apps. Key features of Fastlane include:
-
-1. Automated Build and Distribution: Automate the creation and distribution of beta builds through services like TestFlight or Google Play.
-2. Continuous Integration: Integrate with CI/CD systems to ensure continuous testing and deployment.
-3. Code Signing Management: Simplify and automate the management of certificates and provisioning profiles.
-4. App Metadata Management: Automatically update app metadata, screenshots, and other related information on App Store Connect.
-5. Error Reporting: Receive detailed logs and error reports to debug issues quickly.
-
-Fastlane uses a configuration file (Fastfile) where developers can define lanes for different workflows, making the deployment process more efficient and less error-prone. This tool is highly valuable for teams looking to maintain consistency and save time in their release processes.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@FastLane Website](https://fastlane.tools)
 - [@opensource@fastlane/fastlane](https://github.com/fastlane/fastlane)
@@ -1,8 +1,8 @@
 # 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.

-The iOS file system provides a structured way for apps to store and access data directly on the device. Each app operates within its own sandbox, a dedicated directory structure that isolates the app's data for security and privacy. Within this sandbox, apps can create, read, write, and organize files and directories. The system offers several key directories, including Documents for user-generated content, Library for app-specific data, and tmp for temporary files. File management in iOS is primarily handled through the FileManager class, which provides a comprehensive API for file and directory operations. When working with files, developers must consider factors such as data persistence across app updates, iCloud backup settings, and efficient management of storage space. The file system is particularly useful for storing larger datasets, binary files, or data that doesn't fit well into structured storage systems like Core Data or User Defaults.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@File System Basics](https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html)
 - [@official@About File System](https://developer.apple.com/documentation/foundation/file_system/about_apple_file_system/)
@@ -1,3 +1,3 @@
 # Frameworks & Library
-
-Frameworks and libraries in iOS development are collections of reusable code that provide specific functionality, enhancing development efficiency and maintaining code consistency. Frameworks are more structured than libraries, offering a hierarchical directory that bundles code, resources, and documentation. They can include dynamic or static libraries, header files, and additional resources like images or localization files. iOS provides numerous built-in frameworks like UIKit, Foundation, and CoreData, which form the backbone of app development. Third-party frameworks expand functionality further, often distributed via dependency managers. Libraries, typically in the form of static or dynamic libraries, contain compiled code that can be linked into an app. They're generally simpler than frameworks but less self-contained. The choice between using a framework or a library often depends on the complexity of the functionality needed and how it integrates with the existing project structure. Effective use of frameworks and libraries can significantly reduce development time and improve code quality in iOS applications.
+ 
+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,3 +1,3 @@
 # Frameworks

-Frameworks in iOS development are modular, reusable packages of code and resources that provide specific functionality to applications. They offer a hierarchical structure containing compiled code, header files, resources like images and localization files, and often documentation. iOS provides numerous built-in frameworks such as UIKit for user interface elements, Foundation for fundamental data types and collections, and Core Data for data management. These frameworks form the backbone of iOS app development, offering standardized and optimized implementations of common functionalities. Third-party frameworks extend this ecosystem, providing additional features and tools. Frameworks can be static or dynamic, with dynamic frameworks offering more flexibility in terms of memory usage and updates. The use of frameworks promotes code reuse, maintains consistency across projects, and often improves development efficiency. Effective utilization of both system and third-party frameworks is crucial for building robust, feature-rich iOS applications while minimizing development time and effort.
+Frameworks in iOS development are modular, reusable packages of code and resources that provide specific functionality to applications. They offer a hierarchical structure containing compiled code, header files, resources like images and localization files, and often documentation. iOS provides numerous built-in frameworks such as UIKit for user interface elements, Foundation for fundamental data types and collections, and Core Data for data management.
@@ -2,8 +2,8 @@

 Functional programming is a style of programming where code is written using pure functions, avoiding changing state and mutable data. It emphasizes the use of mathematical functions to process data, which leads to more predictable and bug-resistant code. This approach helps in writing concise, readable, and testable code.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@video@Functional programming - A general introduction](https://www.youtube.com/watch?v=8z_bUIl_uPo)
 - [@video@Intro to Swift for Functional Programmers](https://www.youtube.com/watch?v=rYC-TnKoi40)
- [@feed@Explore top posts about Functional Programming](https://app.daily.dev/tags/functional-programming?ref=roadmapsh)
+- [@feed@Explore top posts about Functional Programming](https://app.daily.dev/tags/functional-programming?ref=roadmapsh)
@@ -1,8 +1,8 @@
 # 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.

-GameKit is a framework provided by Apple for iOS, macOS, and tvOS that facilitates the implementation of social gaming features. It offers a set of tools and APIs for integrating multiplayer functionality, leaderboards, achievements, and player authentication in games. GameKit simplifies the process of adding real-time multiplayer capabilities, allowing developers to create peer-to-peer connections or use Apple's Game Center servers for matchmaking. The framework provides APIs for managing leaderboards, enabling players to compare scores globally or among friends. It also supports a system for creating and tracking in-game achievements, enhancing player engagement. GameKit handles player authentication through Game Center, offering a unified gaming identity across Apple platforms. While primarily designed for games, some of GameKit's features, like peer-to-peer connectivity, can be useful in non-gaming apps as well. By leveraging GameKit, developers can create more interactive and socially engaging gaming experiences on Apple platforms without having to implement complex networking and social features from scratch.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@GameKit](https://developer.apple.com/documentation/gamekit)
 - [@article@How to integrate GameKit](https://medium.com/swlh/how-to-integrate-gamekit-ios-794061428197)
@@ -1,9 +1,9 @@
 # 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.

-Grand Central Dispatch (GCD) is a powerful concurrency framework in iOS that simplifies the execution of parallel code. It abstracts the complexities of thread management, allowing developers to focus on the tasks to be performed rather than the underlying threading details. GCD uses a queue-based model where tasks are submitted to dispatch queues and executed by a managed pool of threads. It offers both serial and concurrent queues, enabling fine-grained control over task execution order and parallelism. The framework provides global queues with different quality of service levels, allowing prioritization of tasks based on their importance. GCD's dispatch groups facilitate the coordination of multiple asynchronous operations, while dispatch semaphores help manage access to shared resources. By leveraging GCD, iOS developers can efficiently distribute work across multiple cores, improve app responsiveness, and avoid common pitfalls associated with manual thread management, making it an essential tool for building high-performance, concurrent applications.
+Visit the following resources to learn more:

-Learn more from the following resources:
-
- [@official@Dispatch@](https://developer.apple.com/documentation/DISPATCH)
+- [@official@Dispatch](https://developer.apple.com/documentation/DISPATCH)
 - [@article@Grand Central Dispatch (GCD) in iOS: The Developer's Guide](https://hackernoon.com/grand-central-dispatch-gcd-in-ios-the-developers-guide)
 - [@article@Grand Central Dispatch in iOS](https://medium.com/@knoo/gcd-grand-central-dispatch-in-ios-b2dd665cabd5)
@@ -2,9 +2,9 @@

 Git is a distributed version control system **(VCS)** used to track changes in source code during software development. It allows multiple developers to collaborate on a project by managing different versions of the code, enabling them to work on separate branches, merge changes, and keep a complete history of modifications.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@roadmap@Visit Dedicated Git & GitHub Roadmap](https://roadmap.sh/git-github)
- [@article@Git by Example - Learn Version Control with Bite-sized Lessons](https://antonz.org/git-by-example/)
- [@video@Git & GitHub Crash Course For Beginners](https://www.youtube.com/watch?v=vA5TTz6BXhY)
 - [@course@Why use Git? (Interactive Lesson)](https://inter-git.com/lessons/introduction)
+- [@article@Git by Example - Learn Version Control with Bite-sized Lessons](https://antonz.org/git-by-example/)
+- [@video@Git & GitHub Crash Course For Beginners](https://www.youtube.com/watch?v=vA5TTz6BXhY)
@@ -1,9 +1,9 @@
 # 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.

-GitHub Actions is a CI/CD tool integrated directly into GitHub, allowing developers to automate workflows, such as building, testing, and deploying code directly from their repositories. It uses YAML files to define workflows, which can be triggered by various events like pushes, pull requests, or on a schedule. GitHub Actions supports a wide range of actions and integrations, making it highly customizable for different project needs. It provides a marketplace with reusable workflows and actions contributed by the community. With its seamless integration with GitHub, developers can take advantage of features like matrix builds, secrets management, and environment-specific configurations to streamline and enhance their development and deployment processes.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@GitHub Actions Documentation](https://docs.github.com/en/actions)
- [@video@How to build an iOS app with GitHub Actions](https://www.youtube.com/watch?v=Sd7YhlxZrJw)
- [@article@How to build an iOS app with GitHub Actions](https://www.andrewhoog.com/post/how-to-build-an-ios-app-with-github-actions-2023/)
+- [@article@How to build an iOS app with GitHub Actions](https://www.andrewhoog.com/post/how-to-build-an-ios-app-with-github-actions-2023/)
+- [@video@How to build an iOS app with GitHub Actions](https://www.youtube.com/watch?v=Sd7YhlxZrJw)
@@ -2,9 +2,8 @@

 GitHub is a web-based platform that uses Git for version control and collaboration. It provides a centralized repository for hosting and managing Git repositories, allowing developers to share their code, collaborate on projects, and track issues.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@GitHub Docs](https://docs.github.com/en)
- [@video@How to Use GitHub](https://www.youtube.com/watch?v=v_1iqtOnUMg)
 - [@article@What is GitHub](https://blog.hubspot.com/website/what-is-github-used-for)
- [@feed@Explore top posts about GitHub](https://app.daily.dev/tags/github?ref=roadmapsh)
+- [@video@How to Use GitHub](https://www.youtube.com/watch?v=v_1iqtOnUMg)
@@ -1,8 +1,8 @@
 # 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.

-GitLab is a comprehensive DevOps platform that provides source code management, CI/CD, and project management tools in a single application. It enables teams to manage their entire software development lifecycle, from planning and coding to testing, deployment, and monitoring. GitLab's built-in CI/CD capabilities allow developers to automate the build, test, and deployment processes using pipelines defined in YAML files. It integrates with various version control systems and supports Docker, Kubernetes, and other deployment environments. GitLab's features include issue tracking, code review, and merge request workflows, which enhance collaboration and code quality. The platform also offers robust security features, such as vulnerability management and dependency scanning, to ensure the safety and integrity of the codebase. GitLab can be hosted on-premises or used as a cloud-based service, providing flexibility and scalability for different project needs. Its all-in-one nature simplifies the development process, making it a popular choice for teams seeking to streamline their workflows and improve productivity.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@GitLab Website](https://about.gitlab.com/)
 - [@article@Tutorial: iOS CI/CD with GitLab](https://about.gitlab.com/blog/2023/06/07/ios-cicd-with-gitlab/)
@@ -1,8 +1,8 @@
 # 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.

-GraphQL is a query language and runtime for APIs, offering an alternative to traditional REST APIs in iOS development. It allows clients to request specific data structures, reducing over-fetching and under-fetching of data common in REST. In iOS apps, GraphQL enables more efficient network usage by allowing precise data requests tailored to UI needs. Developers typically use libraries like Apollo iOS to integrate GraphQL, which handles query execution, caching, and data normalization. GraphQL's strong typing system aligns well with Swift, facilitating type-safe API interactions. It supports real-time data with subscriptions, useful for live updates in iOS apps. While GraphQL offers flexibility and performance benefits, it requires a mindset shift from REST, including different approaches to error handling and caching. Implementing GraphQL in iOS involves crafting queries, managing the schema, and often requires coordination with backend teams to design effective GraphQL APIs that cater to mobile app needs.
+Visit the following resources to learn more:

-Learn more from the following resources:
-
- [@official@GraphQL Website](https://graphql.org/)
- [@official@GraphQL Roadmap](https://roadmap.sh/graphql]
+- [@roadmap@Visit the Dedicated GraphQL Roadmap](https://roadmap.sh/graphql)
+- [@official@GraphQL Website](https://graphql.org/)
@@ -1,17 +1,7 @@
 # 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.

-Xcode groups are organizational tools used to structure and manage files within a project. They provide a logical hierarchy for arranging source code, resources, and other project files without affecting the actual file system structure. Key aspects of Xcode groups include:
+Visit the following resources to learn more:

-1. Visual organization: Groups appear as folders in the Project Navigator, helping developers categorize and locate files easily.
-2. Flexible structure: Files can be organized into groups based on functionality, feature, or any other logical division.
-3. No impact on build: Grouping doesn't affect how Xcode compiles or packages the application.
-4. Color coding: Groups can be color-coded for quick visual identification.
-5. Nested groups: Support for subgroups allows for more detailed organization.
-6. References vs. folders: Groups can be created as simple references or as folder references that mirror the file system.
-7. Drag-and-drop management: Easy reorganization of files and groups within the Project Navigator.
-
-Using groups effectively helps maintain clean, organized projects, especially as they grow in size and complexity.
-
-Learn more from the following resources:
-
- [@official@Managing files and folders in your Xcode project](https://developer.apple.com/documentation/xcode/managing-files-and-folders-in-your-xcode-project)
+- [@official@Managing files and folders in your Xcode project](https://developer.apple.com/documentation/xcode/managing-files-and-folders-in-your-xcode-project)
@@ -1,11 +1,9 @@
 # HealthKit

-HealthKit is a powerful framework that allows developers to create health and fitness applications that can interact seamlessly with the iOS `Health app`.
-
-HealthKit provides a central repository for health and fitness data on iPhone and Apple Watch. With the user’s permission, apps communicate with the HealthKit store to access and share this data.
+HealthKit is a powerful framework that allows developers to create health and fitness applications that can interact seamlessly with the iOS `Health app`. HealthKit provides a central repository for health and fitness data on iPhone and Apple Watch. With the user’s permission, apps communicate with the HealthKit store to access and share this data.

 Visit the following resources to learn more:

 - [@official@HealthKit](https://developer.apple.com/documentation/healthkit)
 - [@official@Creating a Mobility Health App](https://developer.apple.com/documentation/healthkit/creating_a_mobility_health_app)
- [@article@How I use Apple's Health app to track my fitness](https://www.pocket-lint.com/apps/news/apple/131130-apple-healthkit-and-health-app-how-they-work-and-the-medical-records-you-need/)
+- [@article@How I use Apple's Health app to track my fitness](https://www.pocket-lint.com/apps/news/apple/131130-apple-healthkit-and-health-app-how-they-work-and-the-medical-records-you-need/)
@@ -2,6 +2,6 @@

 Human Interface Guidelines (HIG) by Apple are a set of recommendations and best practices for creating user interfaces on Apple devices. These guidelines help developers and designers create applications and interfaces that provide a high-quality experience and consistency with the Apple ecosystem.

-Learn more from the following resources:
+Visit the following resources to learn more:

- [@official@Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines)
+- [@official@Human Interface Guidelines](https://developer.apple.com/design/human-interface-guidelines)
@@ -1,18 +1,9 @@
 # History and Why Swift?
-
-**History**
-
-Swift was introduced by Apple in 2014 as a modern replacement for Objective-C.
-
-It was developed to address the limitations and complexities of Objective-C, providing a more powerful and user-friendly programming language.
-
-**Why Swift?**
-
-Swift offers improved performance, safety, and readability. It reduces common programming errors with features like optionals and type inference.
-
-Swift’s concise syntax and modern language constructs enhance developer productivity, making it easier to write and maintain code. Its open-source nature also allows a wider community to contribute and improve the language.
+ 
+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:
+
+- [@roadmap@Visit the Dedicated Swift & Swift UI Roadmap](https://roadmap.sh/swift-ui)
 - [@official@About Swift](https://www.swift.org/about/)
- [@video@A Brief History](https://www.youtube.com/watch?v=4P_ZsOqELBo)
- [@feed@Explore top posts about Swift](https://app.daily.dev/tags/swift?ref=roadmapsh)
+- [@video@A Brief History](https://www.youtube.com/watch?v=4P_ZsOqELBo)
@@ -1,8 +1,8 @@
 # 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.

-HTTP (Hypertext Transfer Protocol) and HTTPS (HTTP Secure) are fundamental protocols for data communication on the internet, extensively used in iOS app networking. HTTP facilitates request-response interactions between clients and servers, defining how messages are formatted and transmitted. HTTPS extends HTTP by encrypting the data exchange using SSL/TLS protocols, ensuring secure communication. In iOS development, URLSession handles both HTTP and HTTPS requests seamlessly, automatically managing the encryption for HTTPS connections. Developers typically use HTTPS for all network communications to protect user data and maintain privacy. iOS enforces App Transport Security (ATS) by default, requiring secure connections for network requests. When working with web APIs, iOS apps use these protocols to fetch data, submit forms, upload files, and perform various other network operations. Understanding HTTP methods (GET, POST, PUT, DELETE, etc.), status codes, and headers is crucial for effective API integration and troubleshooting in iOS app development.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@URLSession](https://developer.apple.com/documentation/foundation/urlsession)
 - [@article@Mastering URLSession in Swift](https://elamir.medium.com/mastering-urlsession-in-swift-a-comprehensive-guide-d3a3aa740f6e)
@@ -1,19 +1,8 @@
 # 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.

-Xcode IBActions are methods that connect user interface elements to code, allowing the app to respond to user interactions. Key features include:
+Visit the following resources to learn more:

-1. Definition: Declared as methods in view controller classes.
-2. Connection: Made by ctrl-dragging from UI elements to code in Interface Builder.
-3. Purpose: Handle user interactions like button taps, slider changes, etc.
-4. Method signature: Can include a sender parameter of the interacting UI element's type.
-5. Multiple connections: One IBAction can be connected to multiple UI elements.
-6. Event types: Can be set to respond to specific events (e.g., touch up inside, value changed).
-7. Naming convention: Often prefixed with 'ib' for clarity.
-8. Refactoring support: Xcode updates connections when renaming.
-
-IBActions provide a clean way to separate UI logic from business logic, enhancing code organization. They allow developers to centralize the handling of user interactions, making it easier to manage and modify app behavior in response to user input.
-
-Learn more from the following resources:
-
- [@video@IBOutlet & IBAction](https://www.youtube.com/watch?v=ztPpThdBHT0)
- [@article@From outlets to actions: creating an IBAction](https://www.hackingwithswift.com/read/2/5/from-outlets-to-actions-creating-an-ibaction)
+- [@article@From outlets to actions: creating an IBAction](https://www.hackingwithswift.com/read/2/5/from-outlets-to-actions-creating-an-ibaction)
+- [@video@IBOutlet & IBAction](https://www.youtube.com/watch?v=ztPpThdBHT0)
@@ -2,6 +2,6 @@

 An outlet is a property of an object that references another object. The reference is archived through Interface Builder. The connections between the containing object and its outlets are reestablished every time the containing object is unarchived from its nib file. The containing object holds an outlet declared as a property with the type qualifier of IBOutlet and a weak option.

-Learn more from the following resources:
+Visit the following resources to learn more:

- [@official@Outlets](https://developer.apple.com/library/archive/documentation/General/Conceptual/CocoaEncyclopedia/Outlets/Outlets.html)
+- [@official@Outlets](https://developer.apple.com/library/archive/documentation/General/Conceptual/CocoaEncyclopedia/Outlets/Outlets.html)
@@ -1,8 +1,8 @@
 # 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.

-Implementing delegates in Swift involves creating a protocol that defines the methods the delegate should implement, and then using this protocol to establish a communication channel between objects. The process typically begins with defining a protocol that outlines the required and optional methods. Next, a weak delegate property is declared in the delegating class to avoid retain cycles. The delegating class then calls the delegate methods at appropriate times, often in response to specific events or state changes. On the delegate side, the class conforms to the protocol and implements the required methods, providing custom behavior as needed. This implementation allows for flexible and reusable code, as the delegating object doesn't need to know the specific type of its delegate, only that it conforms to the protocol.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Delegates in Swift](https://medium.com/@muhammad.cse11/delegates-in-swift-ios-application-6dfb37897f9b)
 - [@article@What is a delegate in Swift](https://www.hackingwithswift.com/example-code/language/what-is-a-delegate-in-ios)
@@ -1,10 +1,8 @@
 # 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.

-The Xcode Integrated Development Environment (IDE) can only be installed on MacOS given it's nature as an iOS IDE. It can be installed simply like any application on the Mac, via the iStore using an Apple ID.
+Visit the following resources to learn more:

-If you wish to do any development using the Command Line Interface (CLI) you will need to install Xcode Command Line Tools via the `Xcode-select --install`. Popular CLI tools such as `clang`, `gcc` & `git` will require the installation of Xcode Command Line Tools.
-
-Learn more from the following resources:
-
- [@video@How to Install Xcode on Mac](https://www.youtube.com/watch?v=F6QZ2atZrDw)
 - [@article@Xcode Command Line Tools Installation](https://mac.install.guide/commandlinetools/4)
+- [@video@How to Install Xcode on Mac](https://www.youtube.com/watch?v=F6QZ2atZrDw)
@@ -1,20 +1,8 @@
 # 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.

-Xcode Interface Builder is a visual design tool for creating user interfaces in iOS, macOS, watchOS, and tvOS applications. Key features include:
-
-1. Drag-and-drop UI design: Easily add and arrange UI elements on the canvas.
-2. Storyboards: Create and manage multiple screens and their connections.
-3. Auto Layout: Set up adaptive layouts using constraints.
-4. Size classes: Design interfaces for different device sizes and orientations.
-5. Custom controls: Integrate custom UI components alongside system-provided ones.
-6. IBOutlets and IBActions: Connect UI elements to code.
-7. Preview: Visualize designs on different devices and orientations.
-8. Accessibility inspector: Ensure UI elements are accessible.
-9. Localization: Manage multiple language versions of the interface.
-
-Interface Builder integrates seamlessly with Xcode's coding environment, allowing developers to switch between visual design and code implementation. It supports both .xib files for individual view controllers and .storyboard files for more complex, multi-screen interfaces.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@course@iOS Storyboards: Getting Started](https://www.kodeco.com/5055364-ios-storyboards-getting-started)
 - [@article@A bit about Interface Builder](https://medium.com/swlh/a-bit-about-interface-builder-ceffaf484580)
@@ -1,13 +1,3 @@
 # Interface overview
-
-Xcode's interface is designed for efficient iOS, macOS, watchOS, and tvOS development. The main window is divided into several key areas:
-
-1. Toolbar: Contains run buttons, scheme selector, and status display.
-2. Navigator Area (left): Includes file navigator, search, issue navigator, and test navigator.
-3. Editor Area (center): The main coding space, supporting multiple editors and Interface Builder.
-4. Utility Area (right): Shows file inspectors, Quick Help, and Interface Builder libraries.
-5. Debug Area (bottom): Displays console output and variables during debugging.
-6. Assistant Editor: Allows viewing related files side-by-side.
-7. Version Editor: For managing and comparing different versions of code.
-
-The interface is highly customizable, allowing developers to adjust layouts and show/hide areas as needed for their workflow. This integrated environment provides tools for coding, UI design, testing, and debugging all in one application.
+ 
+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,19 +1,8 @@
 # Interoperability with Swift
-
-Swift is designed to work seamlessly with Objective-C, allowing developers to integrate and use both languages within the same project. This interoperability enables:
-
-**Gradual Migration:** Developers can incrementally migrate their codebase from Objective-C to Swift without needing a complete rewrite.
-
-**Mixed-Language Projects:** Swift and Objective-C files can coexist, and developers can call Objective-C code from Swift and vice versa.
-
-**Access to Existing Libraries:** Swift code can leverage existing Objective-C libraries and frameworks, ensuring continued use of valuable resources and tools.
-
-**Bridging Header:** A bridging header file allows Swift to interface with Objective-C code, facilitating communication between the two languages.
-
-**Compatibility:** Swift supports dynamic libraries, ensuring compatibility with existing Objective-C runtime and APIs.
+ 
+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:

 - [@official@Swift and Objective-C Interoperability](https://developer.apple.com/videos/play/wwdc2015/401/)
- [@video@Bridging Swift And Objective C](https://www.youtube.com/watch?v=Wp_-8tE85hE)
- [@feed@Explore top posts about Swift](https://app.daily.dev/tags/swift?ref=roadmapsh)
+- [@video@Bridging Swift And Objective C](https://www.youtube.com/watch?v=Wp_-8tE85hE)
@@ -2,10 +2,9 @@

 iOS architecture refers to the design principles and patterns used to build iOS applications. It focuses on how to structure code, manage data, and ensure a smooth user experience. These architectural patterns help developers create maintainable, scalable, and testable applications while following best practices specific to iOS development. Use cases of these architectures may vary according to the requirements of the application. For example, MVC is used for simple apps, while MVVM is considered when the app is large and complex.

-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@Model-View-Controller Pattern in swift (MVC) for Beginners](https://ahmedaminhassanismail.medium.com/model-view-controller-pattern-in-swift-mvc-for-beginners-35db8d479832)
- [@video@MVC Design Pattern Explained with Example](https://youtu.be/sbYaWJEAYIY?t=2)
 - [@article@MVVM in iOS Swift](https://medium.com/@zebayasmeen76/mvvm-in-ios-swift-6afb150458fd)
- [@video@MVVM Design Pattern Explained with Example](https://www.youtube.com/watch?v=sLHVxnRS75w)
-
+- [@video@MVC Design Pattern Explained with Example](https://youtu.be/sbYaWJEAYIY?t=2)
+- [@video@MVVM Design Pattern Explained with Example](https://www.youtube.com/watch?v=sLHVxnRS75w)
@@ -1,8 +1,8 @@
 # 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.

-Jenkins is an open-source automation server widely used for continuous integration (CI) and continuous deployment (CD). It automates the process of building, testing, and deploying software, enhancing productivity and consistency in development workflows. Jenkins supports an extensive range of plugins, enabling seamless integration with various version control systems, build tools, and deployment environments. One of its key features is the Pipeline as Code functionality, which allows developers to define complex build and deployment pipelines using a domain-specific language (DSL) in Groovy. This enables version control and easier maintenance of pipelines. Jenkins is highly extensible, with over 1,500 plugins available for integration with tools such as Git, Maven, Docker, and Kubernetes. It also supports distributed builds, allowing the load to be spread across multiple machines for improved performance. Automated testing is another crucial aspect, as Jenkins can run unit, integration, and UI tests as part of the CI process, helping to catch issues early. Jenkins' flexibility and extensive plugin ecosystem make it a popular choice for automating complex CI/CD workflows.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Jenkins Website](https://www.jenkins.io/)
 - [@article@What is Jenkins?](https://www.spiceworks.com/tech/devops/articles/what-is-jenkins/)
@@ -1,3 +1,3 @@
 # JSON / XML
-
-JSON (JavaScript Object Notation) and XML (eXtensible Markup Language) are widely used data interchange formats in iOS development, each with its own strengths and use cases. JSON has become increasingly popular due to its lightweight nature and ease of use, particularly in web services and APIs. Swift provides built-in support for JSON encoding and decoding through the Codable protocol, simplifying the process of converting between JSON data and Swift objects. XML, while less common in modern APIs, is still used in certain scenarios, especially for complex, hierarchical data structures. iOS provides the XMLParser class for parsing XML data, though it requires more manual handling compared to JSON. Both formats support data serialization and deserialization, allowing for easy storage and transmission of structured data. When working with external APIs or services, the choice between JSON and XML is often dictated by the service provider, but for internal data storage or custom APIs, JSON is generally preferred for its simplicity and performance in mobile environments.
+ 
+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,16 +1,9 @@
 # Keeping Updated with WWDC
-
-WWDC (Worldwide Developers Conference) is an annual conference held by Apple for software developers. The main objectives of the conference are:
-
-1. **Presenting New Products**: Apple uses WWDC to announce new versions of its operating systems, such as iOS, macOS, watchOS, and tvOS, as well as new products and technologies.
-2. **Developer Training**: The conference includes numerous technical sessions, labs, and workshops where developers can receive tips and guidance from Apple engineers on using the latest tools and technologies.
-3. **Networking**: Developers from around the world gather at WWDC to share experiences and establish valuable connections.
-
-WWDC typically takes place in June and kicks off with a keynote presentation where Tim Cook and other Apple executives introduce major updates and new products.
+ 
+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:

 - [@official@Worldwide Developers Conference](https://developer.apple.com/wwdc)
 - [@official@Apple Developer YouTube channel](https://www.youtube.com/@AppleDeveloper)
- [@official@WWDC videos collection by year](https://developer.apple.com/videos/)
- 
+- [@official@WWDC videos collection by year](https://developer.apple.com/videos/)
@@ -1,8 +1,8 @@
 # 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.

-The Keychain in iOS provides a secure, encrypted storage system for sensitive data such as passwords, authentication tokens, and other confidential information. It offers a higher level of security compared to other local storage options, as the data is encrypted and protected by the device's security features. The Keychain Services API allows apps to store, retrieve, and manage small chunks of data in a way that's significantly more secure than alternatives like User Defaults. Data stored in the Keychain persists across app reinstalls and can be shared between apps from the same developer. While powerful, working with the Keychain API can be complex, leading many developers to use wrapper libraries that simplify its usage. It's crucial to manage Keychain items carefully, considering aspects like accessibility settings and access groups, to ensure data remains secure while still being available when needed by the app.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Keychain Services](https://developer.apple.com/documentation/security/keychain_services)
 - [@article@Local storage in iOS: Keychain](https://medium.com/@omar.saibaa/local-storage-in-ios-keychain-668240e2670d)
@@ -1,5 +1,7 @@
 # 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.

-The latest iOS SDK can be found in the following resources:
+Visit the following resources to learn more:

 - [@official@Apple Developer Website](https://developer.apple.com/develop/)
@@ -1,6 +1,8 @@
 # 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.

-The latest Swift version can be found in the following resources:
+Visit the following resources to learn more:

 - [@official@Official Swift Website](https://www.swift.org/download/)
- [@official@Swiftversion.net](https://swiftversion.net/)
+- [@official@Swiftversion.net](https://swiftversion.net/)
@@ -1,10 +1,9 @@
 # Lottie

-Lottie is a cross-platform library for iOS, macOS, tvOS, visionOS, Android, and Web that natively renders vector-based animations and art in realtime with minimal code.
-Lottie loads and renders animations and vectors exported in the bodymovin JSON format. Bodymovin JSON can be created and exported from After Effects with bodymovin, Sketch with Lottie Sketch Export, and from Haiku.
+Lottie is a cross-platform library for iOS, macOS, tvOS, visionOS, Android, and Web that natively renders vector-based animations and art in realtime with minimal code. Lottie loads and renders animations and vectors exported in the bodymovin JSON format. Bodymovin JSON can be created and exported from After Effects with bodymovin, Sketch with Lottie Sketch Export, and from Haiku.

 Visit the following resources to learn more:

 - [@official@Lottie for iOS](https://github.com/airbnb/lottie-ios)
 - [@article@How to Add Lottie Animations in iOS Apps](https://lottiefiles.com/blog/working-with-lottie-animations/how-to-add-lottie-animation-ios-app-swift)
- [@article@Lottie, with official support for SwiftUI](https://github.com/airbnb/lottie-ios/discussions/2189)
+- [@article@Lottie, with official support for SwiftUI](https://github.com/airbnb/lottie-ios/discussions/2189)
@@ -1,9 +1,9 @@
 # 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.

-MapKit is a powerful framework provided by Apple for integrating interactive maps and location-based services into iOS, macOS, and tvOS applications. It offers a rich set of tools for displaying maps, adding annotations and overlays, handling user interactions, and performing geocoding and reverse geocoding. The framework provides customizable map views that support various map types, including standard, satellite, and hybrid views. Developers can easily add pins, custom annotations, and polylines to highlight specific locations or routes. MapKit integrates seamlessly with Core Location for handling real-time user positioning and region monitoring. It also supports features like 3D map views, flyover mode, and turn-by-turn navigation. The framework handles map rendering and data management efficiently, optimizing performance even when dealing with large numbers of map elements. By leveraging MapKit, developers can create sophisticated location-aware applications, from simple map displays to complex navigation and geospatial analysis tools, enhancing user experience with visual and interactive geographical data.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@MapKit](https://developer.apple.com/documentation/mapkit/)
- [@video@Meet MapKit for SwiftUI](https://developer.apple.com/videos/play/wwdc2023/10043/)
- [@article@Implement MapKit APIs](https://medium.com/simform-engineering/mapkit-swiftui-in-ios-17-1fec82c3bf00)
+- [@article@Implement MapKit APIs](https://medium.com/simform-engineering/mapkit-swiftui-in-ios-17-1fec82c3bf00)
+- [@video@Meet MapKit for SwiftUI](https://developer.apple.com/videos/play/wwdc2023/10043/)
@@ -1,3 +1,3 @@
 # Media

-The iOS Media Layer is a collection of frameworks and technologies that enable developers to incorporate rich multimedia experiences into their apps. It includes tools for handling audio, video, and graphics. Key components are AVFoundation for working with time-based audiovisual media, Core Audio for low-level audio processing, Core Animation for fluid animations and visual effects, and Metal for high-performance graphics rendering. This layer also provides support for camera operations, audio recording, and media playback.
+The iOS Media Layer is a collection of frameworks and technologies that enable developers to incorporate rich multimedia experiences into their apps. It includes tools for handling audio, video, and graphics. Key components are AVFoundation for working with time-based audiovisual media, Core Audio for low-level audio processing, Core Animation for fluid animations and visual effects, and Metal for high-performance graphics rendering. This layer also provides support for camera operations, audio recording, and media playback.
@@ -1,15 +1,10 @@
 # Memory Management
-
-Memory management involves allocating memory for objects and freeing it after use. Manual Retain-Release (MRR) requires developers to explicitly manage memory using reference counting, provided by the Foundation class NSObject. Automatic Reference Counting (ARC) automates this process by inserting memory management method calls during compilation, though it still uses reference counting. In contrast, Garbage Collection (GC) automatically tracks object ownership and releases unreferenced objects, using a different mechanism than MRR and ARC, and is supported only in the macOS X runtime environment, not on iOS.
-
-> Beginning May 1, 2015, new Mac apps and app updates submitted to the Mac App Store may no longer use garbage collection, which was deprecated in OS X Mountain Lion. Instead, migrate your apps to Automatic Reference Counting, using the migration assistant in Xcode to help with this transition. Apps may continue to use retain/release for manual memory management. For more information, read the [Transitioning to ARC Release Notes](https://developer.apple.com/library/ios/releasenotes/ObjectiveC/RN-TransitioningToARC/Introduction/Introduction.html).
+ 
+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:

 - [@official@WWDC2021: ARC in Swift: Basics and beyond](https://developer.apple.com/videos/play/wwdc2021/10216/)
 - [@official@ARC(Automatic Reference Counting)](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/automaticreferencecounting/)
 - [@official@About Memory Management](https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/MemoryMgmt/Articles/MemoryMgmt.html)
- [@official@Mac Apps That Use Garbage Collection Must Move to ARC](https://developer.apple.com/news/?id=02202015a)
- [@official@MemoryLayout](https://developer.apple.com/documentation/swift/memorylayout)
- [@official@Detect and diagnose memory issues](https://developer.apple.com/videos/play/wwdc2021/10180/)
- [@official@WWDC24: Analyze heap memory](https://www.youtube.com/watch?v=X_JYRz-Hd0o)
+- [@official@Mac Apps That Use Garbage Collection Must Move to ARC](https://developer.apple.com/news/?id=02202015a)
@@ -2,7 +2,7 @@

 Metal is a high-performance graphics and compute framework for iOS, macOS, and tvOS, designed by Apple. It enables developers to harness the full power of the GPU for advanced 3D graphics, complex visual effects, and data-parallel computation. Metal provides low-level, low-overhead access to the GPU, allowing for fine-tuned performance optimizations in applications and games.

-Learn more from the following resources:
+Visit the following resources to learn more:

- [@official@Metal Documentation](https://developer.apple.com/metal/)
- [@course@Metal Tutorial](https://metaltutorial.com/)
+- [@course@Metal Tutorial](https://metaltutorial.com/)
+- [@official@Metal Documentation](https://developer.apple.com/metal/)
@@ -1,15 +1,9 @@
 # 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.

-UIKit navigation stacks support both modal presentations and hierarchical navigation:
-
-Modal presentations temporarily overlay new content using present(_:animated:completion:). They're suitable for self-contained tasks or information that doesn't fit the main navigation hierarchy.
-
-Hierarchical navigation uses push and pop operations on the navigation stack. pushViewController(_:animated:) adds a new screen, while popViewController(animated:) returns to the previous one.
-
-These can be combined: a modal can contain its own navigation stack, or a screen in the main navigation can present a modal. This flexibility allows developers to create complex navigation patterns that maintain clarity and context for users, adapting to various app structures and user flow requirements.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@animate(withDuration:animations:completion:)](https://developer.apple.com/documentation/uikit/uiview/1622515-animate)
- [@officialpushViewController](https://developer.apple.com/documentation/uikit/uinavigationcontroller/1621887-pushviewcontroller)
+- [@article@@officialpushViewController](https://developer.apple.com/documentation/uikit/uinavigationcontroller/1621887-pushviewcontroller)
 - [@video@UIKit Programmatic Navigation](https://www.youtube.com/watch?v=c0YSGtFmik8)
@@ -1,11 +1,9 @@
 # MVC
-
-The Model-View-Controller (MVC) design pattern assigns objects in an application one of three roles: model, view, or controller. The pattern defines not only the roles objects play in the application, it defines the way objects communicate with each other. Each of the three types of objects is separated from the others by abstract boundaries and communicates with objects of the other types across those boundaries. The collection of objects of a certain MVC type in an application is sometimes referred to as a layer—for example, model layer.
-
-MVC is central to a good design for a Cocoa application. The benefits of adopting this pattern are numerous. Many objects in these applications tend to be more reusable, and their interfaces tend to be better defined. Applications having an MVC design are also more easily extensible than other applications. Moreover, many Cocoa technologies and architectures are based on MVC and require that your custom objects play one of the MVC roles
+ 
+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:

- [@offical@Model-View-Controller](https://developer.apple.com/library/archive/documentation/General/Conceptual/DevPedia-CocoaCore/MVC.html)
- [@offical@Model-View-Controller](https://developer.apple.com/library/archive/documentation/General/Conceptual/CocoaEncyclopedia/Model-View-Controller/Model-View-Controller.html)
- [@article@MVC in iOS – A Modern Approach](https://www.kodeco.com/1000705-model-view-controller-mvc-in-ios-a-modern-approach)
+- [@article@Model-View-Controller](https://developer.apple.com/library/archive/documentation/General/Conceptual/DevPedia-CocoaCore/MVC.html)
+- [@article@Model-View-Controller](https://developer.apple.com/library/archive/documentation/General/Conceptual/CocoaEncyclopedia/Model-View-Controller/Model-View-Controller.html)
+- [@article@MVC in iOS – A Modern Approach](https://www.kodeco.com/1000705-model-view-controller-mvc-in-ios-a-modern-approach)
@@ -1,19 +1,8 @@
 # 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.

-The Model-View-Presenter (MVP) architectural pattern is a derivative of the Model-View-Controller (MVC) pattern, designed to improve separation of concerns and testability in iOS applications. 
-
-In MVP:
-
-**Model**: Represents the data and business logic.
-
-**View**: Responsible for displaying data and capturing user inputs. It's typically passive and doesn't contain business logic.
-
-**Presenter**: Acts as an intermediary between Model and View. It retrieves data from the Model, formats it for the View, and reacts to user inputs from the View.
-
-MVP reduces the responsibilities of the View compared to MVC, making the UI layer thinner and more easily testable. The Presenter contains the presentation logic and is usually paired with a specific View, facilitating unit testing of the user interface logic without needing to interact with the UI components directly.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@article@MVP Wikipedia](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93presenter)
- [@article@]Swift MVP: A Step-by-Step Guide for Clean Code](Swift MVP: A Step-by-Step Guide for Clean Code)
 - [@video@Discover the MVP architecture in less than 90 seconds](https://www.youtube.com/watch?v=DUX0nr5rvnU)
@@ -1,14 +1,8 @@
 # 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.

-MVVM-C (Model-View-ViewModel-Coordinator) is an extension of the MVVM architectural pattern that adds a Coordinator component to manage navigation flow and app structure. In this pattern:
+Visit the following resources to learn more:

-Model, View, and ViewModel retain their roles from MVVM.
-
-**Coordinator**: Handles navigation logic and flow between different screens or modules of the app.
-
-The Coordinator pattern decouples view controllers from each other, centralizing navigation logic. This approach simplifies view controllers, improves modularity, and makes it easier to change or reuse flows within the app. Coordinators can be nested for complex navigation hierarchies.
-
-Learn more from the following resources:
-
- [@video@Everything you need to know about client arthitecture patterns](https://www.youtube.com/watch?v=I5c7fBgvkNY)
- [@article@iOS Architecture: MVVM-C, Introduction](https://medium.com/sudo-by-icalia-labs/ios-architecture-mvvm-c-introduction-1-6-815204248518)
+- [@article@iOS Architecture: MVVM-C, Introduction](https://medium.com/sudo-by-icalia-labs/ios-architecture-mvvm-c-introduction-1-6-815204248518)
+- [@video@Everything you need to know about client arthitecture patterns](https://www.youtube.com/watch?v=I5c7fBgvkNY)
@@ -1,18 +1,10 @@
 # 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.

-The Model-View-ViewModel (MVVM) architectural pattern is a design approach that separates an application's user interface logic from its business logic. In iOS development:
+Visit the following resources to learn more:

-**Model**: Represents data and business logic, independent of the UI.
-
-**View**: Displays information and captures user input. In iOS, this is typically a UIView or UIViewController.
-
-**ViewModel**: Acts as an intermediary between Model and View, containing the presentation logic and state. It exposes data and commands for the View to bind to.
-
-MVVM promotes a clear separation of concerns, enhances testability, and facilitates data binding. The ViewModel transforms Model information for View consumption and handles View-related logic, making the View as passive as possible.
-
-Learn more from the following resources:
-
- [@video@]MVVM In 100 Seconds](https://www.youtube.com/watch?v=-xTqfilaYow)
+- [@article@https://www.youtube.com/watch?v=-xTqfilaYow](https://www.youtube.com/watch?v=-xTqfilaYow)
 - [@article@Understanding MVVM: Model-View-ViewModel Architecture Explained](https://www.ramotion.com/blog/what-is-mvvm/)
 - [@article@MVVM - Wikipedia](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93viewmodel)
- [@article@MVVM - Microsoft](https://learn.microsoft.com/en-us/dotnet/architecture/maui/mvvm)
+- [@article@MVVM - Microsoft](https://learn.microsoft.com/en-us/dotnet/architecture/maui/mvvm)
@@ -1,12 +1,8 @@
 # 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.

-UIKit Navigation Controllers and Segues are key components for managing app navigation:
+Visit the following resources to learn more:

-Navigation Controllers (`UINavigationController`) manage a stack of view controllers, providing a hierarchical interface for navigating content. They handle push and pop transitions between screens, maintain a navigation bar, and support back-navigation functionality.
-
-Segues are visual connections between view controllers in storyboards, defining transitions between scenes. They can be triggered programmatically or through user interactions. Types include push, modal, and custom segues. Segues simplify the process of passing data between view controllers during transitions.
-
-Learn more from the following resources:
-
- [@video@How to Nav Bar Programmatically](https://www.youtube.com/watch?v=wcN3-E1_ZxU)
- [@official@UINavigationController](https://developer.apple.com/documentation/uikit/uinavigationcontroller)
+- [@official@UINavigationController](https://developer.apple.com/documentation/uikit/uinavigationcontroller)
+- [@video@How to Nav Bar Programmatically](https://www.youtube.com/watch?v=wcN3-E1_ZxU)
@@ -1,11 +1,8 @@
 # Navigation Stacks
-
-iOS 16 introduced a new concept of navigating through SiwftUI apps: NavigationStack.
-NavigationStack is data-driven, meaning that you specify navigationDestinations for each data type (models) that your app supports.
-These destinations are defined once for each NavigationStack and are valid throughout the app.
-Navigation itself is handled through the NavigationLink View, which allows setting a label and a value (your model).
+ 
+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:

 - [@official@NavigationStack](https://developer.apple.com/documentation/swiftui/navigationstack)
- [@video@NavigationStack](https://www.youtube.com/watch?v=DMsALlhObNk)
+- [@video@NavigationStack](https://www.youtube.com/watch?v=DMsALlhObNk)
@@ -1,3 +1,3 @@
 # Navigation Stacks
-
-UIKit Navigation Stacks, managed by UINavigationController, provide a hierarchical way to organize content in iOS apps. The stack operates on a last-in-first-out basis, where view controllers are pushed onto or popped from the top. The root view controller remains at the bottom, while subsequent screens are added above it. This structure allows for intuitive drill-down interfaces and easy back-navigation. Navigation stacks automatically handle transitions between view controllers, maintain a navigation bar with titles and back buttons, and can be customized for specific navigation patterns. They are fundamental to creating depth in app navigation, enabling users to traverse complex information hierarchies efficiently.
+ 
+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,9 +1,7 @@
 # Navigation View
-A view for presenting a stack of views that represents a visible path in a navigation hierarchy.
-Use a NavigationView to create a navigation-based app in which the user can traverse a collection of views. Users navigate to a destination view by selecting a NavigationLink that you provide. On iPadOS and macOS, the destination content appears in the next column. Other platforms push a new view onto the stack, and enable removing items from the stack with platform-specific controls, like a Back button or a swipe gesture.
-> [!WARNING]
-> Deprecated. Use NavigationStack and NavigationSplitView instead. For more information, see Migrating to new navigation types.
+ 
+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:

- [@official@Navigation View](https://developer.apple.com/documentation/swiftui/navigationview)
+- [@official@Navigation View](https://developer.apple.com/documentation/swiftui/navigationview)
@@ -1,11 +1,10 @@
 # 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.

-SwiftUI navigation offers a declarative approach to managing app structure and flow, primarily utilizing NavigationView for creating hierarchies and NavigationLink for inter-view navigation. The framework supports both push-based navigation for hierarchical content and modal presentations for overlays, with programmatic navigation achieved through state management for dynamic, logic-driven navigation. SwiftUI automatically handles navigation bars, back buttons, and view transitions, while supporting customization of navigation bar appearances and titles. For tab-based interfaces, TabView facilitates the creation of multi-tab applications. This navigation system integrates seamlessly with SwiftUI's state management, ensuring consistent UI updates as navigation states change, thereby simplifying the implementation of complex navigation patterns while maintaining an intuitive user experience across Apple platforms.
-
-Learn more from the following resources:
+Visit the following resources to learn more:

 - [@official@Apple Tutorials: Navigation and modal presentation - Creating a navigation hierarchy](https://developer.apple.com/tutorials/app-dev-training/creating-a-navigation-hierarchy)
 - [@official@Apple Tutorials: Navigation and modal presentation - Managing data flow between views](https://developer.apple.com/tutorials/app-dev-training/managing-data-flow-between-views)
- [@official@Apple Tutorials: Navigation and modal presentation - Creating the edit view](https://developer.apple.com/tutorials/app-dev-training/creating-the-edit-view)
- [@article@The complete guide to NavigationView in SwiftUI](https://www.hackingwithswift.com/articles/216/complete-guide-to-navigationview-in-swiftui)
- [@opensource@pointfreeco/swiftui-navigation](https://github.com/pointfreeco/swiftui-navigation)
+- [@opensource@pointfreeco/swiftui-navigation](https://github.com/pointfreeco/swiftui-navigation)
+- [@article@The complete guide to NavigationView in SwiftUI](https://www.hackingwithswift.com/articles/216/complete-guide-to-navigationview-in-swiftui)
@@ -4,4 +4,4 @@ Navigation helps users easily find their way around an app and locate the inform

 Visit the following resources to learn more:

- [@official@WWDC2022: Explore navigation design for iOS](https://developer.apple.com/videos/play/wwdc2022/10001/)
+- [@official@WWDC2022: Explore navigation design for iOS](https://developer.apple.com/videos/play/wwdc2022/10001/)
--- a/Show More
+++ b/Show More