iOS Roadmap
This iOS Roadmap is a free, full-text syllabus of 170 lessons in 34 stages, starting with Objective-C and ending with More topics. It suits anyone working towards a iOS role, from a first-year student to a working developer changing tracks. There is no fixed length: every lesson is open from the start, so you go at your own pace and skip what you already know.
Last updated
Reading is open to everyone. Sign in to join this roadmap and track what you finish.
Continue learning
1. Objective-CObjective-C
0%Objective-C
3 topics · 2 sub-topics · 0 completed
The diagram draws the same 170 lessons as a map, with lines showing the order. It needs JavaScript; the full syllabus below lists every lesson as text.
Full syllabus: every lesson in the iOS roadmap
34 stages and 170 lessons, in the order the roadmap suggests. Every lesson is free to read and open from the start.
Stage 1: Objective-C
Objective-C
Objective-C is the original language for iOS and macOS development, widely used before Swift's introduction in 2014. It is a superset of C with Smalltalk-style message passing and object-oriented features. Many older iOS codebases and some Apple frameworks are still written in Objective-C, and it can be used…
Interoperability with Swift
Swift and Objective-C can coexist in the same Xcode project through a bridging header mechanism. Swift code can call Objective-C APIs, and Objective-C code can use Swift classes marked with the @objc attribute. Interoperability is important when migrating legacy Objective-C projects to Swift incrementally.
Objective-C Basics
Objective-C basics cover the core syntax and concepts needed to read and write Objective-C code. This includes pointers, message syntax, classes, categories, protocols, and property declarations. A working knowledge of these basics is useful when maintaining legacy codebases or interoperating with frameworks that…
Stage 2: Pick a Language
Pick a Language
iOS development primarily uses Swift and Objective-C. Swift is Apple's modern recommended language for new projects, while Objective-C is still present in many legacy codebases and system frameworks.
Stage 3: Swift (Recommended)
Swift (Recommended)
Swift is Apple's modern, statically typed programming language for iOS, macOS, watchOS, and tvOS development. Introduced in 2014, it has become the recommended choice for new iOS projects. Swift features a clean syntax, strong type inference, optionals for safe null handling, and built-in concurrency support…
History and Why Swift?
Swift was introduced by Apple in 2014 to address the limitations of Objective-C in terms of safety, performance, and developer experience. It was designed to be faster, more expressive, and safer by eliminating entire classes of bugs through optionals and strong typing. Apple open-sourced Swift in 2015, and it has…
Benefits over Objective-C
Swift offers several advantages over Objective-C including type safety with optionals, modern syntax that reduces boilerplate, cleaner closure support, and better performance in many scenarios. Swift code is generally easier to read, write, and maintain. The language also benefits from active development through…
Swift Basics
Swift basics cover the fundamental syntax and language features needed to write Swift programs. This includes variables, constants, data types, control flow, functions, closures, classes, structs, enums, and optionals. A solid understanding of these basics is required before working with iOS frameworks and APIs.
Stage 4: iOS Architecture
iOS Architecture
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…
Core OS
Core OS is the bottom layer of the iOS architecture, sitting directly above the hardware. It provides the Darwin kernel, security frameworks, and low-level system interfaces. Frameworks at this level include Security, Accelerate for math and signal processing, and ExternalAccessory for communicating with hardware…
Core Services
Core Services is the second layer of the iOS architecture and provides fundamental system capabilities that apps depend on. It includes frameworks for networking, file access, data management, location, and iCloud. Higher-level frameworks in Cocoa Touch build on Core Services internally.
Cocoa Touch
Cocoa Touch is the topmost layer of the iOS architecture and provides the frameworks developers interact with most directly, including UIKit, SwiftUI, MapKit, and GameKit. It handles touch input, notifications, multitasking, and high-level app structure. Most iOS app code is written against Cocoa Touch APIs.
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…
Core Graphics
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,…
Core Animation
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,…
AVFoundation
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,…
Core Image
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…
Core Audio
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…
Metal
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…
Stage 5: Core Programming Concepts
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…
OOP
Object-Oriented Programming (OOP) is a style where code is organized around "objects," which are instances of classes combining data and methods. It emphasizes encapsulation, abstraction, inheritance, and polymorphism, enabling modular, reusable, and maintainable code. OOP allows developers to model real-world…
Functional Programming
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…
Memory Management
iOS uses Automatic Reference Counting (ARC) to manage memory. ARC tracks how many strong references point to each object and deallocates it when the count drops to zero. Developers must understand strong, weak, and unowned references to avoid retain cycles, which cause memory leaks.
ViewController Lifecycle
The ViewController lifecycle in iOS refers to the sequence of methods called as a view controller transitions between states. It begins with initialization, followed by loading the view, appearing on screen, disappearing, and potentially being deallocated. Key methods include viewDidLoad(), viewWillAppear(),…
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.
Concurrency (GCD, async/await)
Concurrency in iOS allows multiple tasks to run in parallel to keep the UI responsive. Grand Central Dispatch (GCD) is the traditional approach, using dispatch queues to schedule work on background threads. Swift's async/await syntax, introduced in Swift 5.5, provides a more readable and structured way to write…
Stage 6: Version Control
Version Control
Version control enables developers to track changes to code over time and collaborate with others. Git is the standard version control tool for iOS projects, and GitHub is the most common hosting platform for iOS team repositories and open-source libraries.
Git
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…
GitHub
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.
Stage 7: Xcode
Xcode
Xcode is Apple’s integrated development environment (IDE) for macOS, used to develop software for iOS, macOS, watchOS, and tvOS. It includes a suite of tools for designing user interfaces, writing and testing code, and debugging applications. Xcode supports multiple programming languages such as Swift and…
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.
Preferences
Xcode preferences allow you to customize your development environment to suit your workflow. They offer various settings across multiple tabs, including General, Accounts, Behaviors, Text Editing, Key Bindings, and more. These preferences let you manage your Apple developer accounts, configure source control,…
New Project
To create an Xcode project for your app, select a platform template such as iOS, macOS, watchOS, or tvOS, and choose the type of app you want to develop, like a single view, game, or document-based app. Xcode templates provide essential configuration and files, allowing you to quickly start developing your app.…
Stage 8: UIKit
UIKit
UIKit is Apple's foundational framework for building iOS and tvOS user interfaces. It provides the core building blocks including views, view controllers, navigation controllers, table views, and gesture recognizers. UIKit uses an imperative, event-driven model and has been the basis of iOS development since the…
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.
Views
UIKit views are the core visual elements in iOS interfaces, serving as the canvas for all user interface components. At its most basic, a view is an instance of UIView, representing a rectangular area on the screen. Views handle rendering content, laying out subviews, and responding to touch events. They can be…
View Controllers
A UIViewController manages a single screen of content in a UIKit app. It owns a root view, handles the lifecycle events for that view, and coordinates between the model layer and the UI. View controllers are the primary structural unit in UIKit apps and the main place for screen-level logic.
User Interactions
UIKit User Interactions encompass the various ways users can engage with an iOS app's interface. This includes touch events (taps, swipes, pinches), gesture recognizers for complex interactions, and control events for UI elements like buttons and sliders. UIKit provides a robust event handling system, allowing…
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.
Storyboards
Storyboards are XML-based files that define multiple view controllers and the transitions between them on a single visual canvas. Developers drag view controllers onto the canvas, design their views, and connect screens with segues. Storyboards give a visual overview of the app's entire navigation flow.
Xibs
UIKit Xibs (XML Interface Builder files) are resource files used to design individual view hierarchies or custom views in iOS development. Unlike Storyboards, which can represent an entire app's interface, Xibs typically focus on smaller, reusable UI components or single view controllers. They offer a visual way to…
Navigation
Navigation helps users easily find their way around an app and locate the information they need, minimizing confusion. Utilizing familiar navigation patterns can simplify complex interactions while preserving the app's unique character. Learn best practices and common pitfalls when working with tab bars, modals,…
View Transitions
View transitions control how the app animates when moving between screens. UIKit provides built-in transition styles like push and modal presentation, and custom transitions are created using the UIViewControllerAnimatedTransitioning protocol. Transitions provide visual continuity that helps users understand where…
Stage 9: SwiftUI
SwiftUI
SwiftUI is Apple's declarative UI framework for building apps across iOS, macOS, watchOS, and tvOS. Introduced in 2019, it replaces UIKit's imperative approach with composable views written entirely in Swift. SwiftUI automatically handles layout, animations, and UI updates when the underlying data changes.
Declarative Syntax
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…
Components
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.…
State Management
State management in SwiftUI determines where data lives and how it flows through the view hierarchy. @State handles local view state, @StateObject owns an observable object, @ObservedObject observes an externally owned object, and @EnvironmentObject injects shared data across the hierarchy. Choosing the right…
Data binding
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…
Interface overview
The Xcode interface is organized into a navigator panel on the left, an editor area in the center, an inspector panel on the right, and a debug area at the bottom. The toolbar at the top provides controls for running, stopping, and switching build schemes. Understanding the layout helps developers move efficiently…
Toolbar
The Xcode toolbar provides quick access to common actions, including running and stopping the app, selecting a target device or simulator, and showing or hiding the navigator and inspector panels. It also displays build activity messages and scheme selection controls.
Navigators
The navigator panel contains multiple navigators for different purposes. The Project Navigator shows the file hierarchy, the Issue Navigator displays errors and warnings, the Test Navigator lists test suites, and the Debug Navigator shows runtime resource usage. Switching between navigators is done using the icons…
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.
Project Files
The Project Navigator organizes all files in an Xcode project, including Swift source files, assets, configuration files, and frameworks. Files are listed hierarchically and can be added, deleted, or reorganized within the navigator. The project file (.xcodeproj) stores build settings, targets, and file references.
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…
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…
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.
Stepping
Stepping controls in the Xcode debugger allow developers to move through code one statement at a time during a paused breakpoint session. Step Over executes the current line without descending into called functions, Step Into enters a called function, and Step Out completes the current function and returns to the…
Stage 10: UI Design
UI Design
UI design for iOS focuses on how apps should look and behave to feel native and intuitive on Apple platforms. The primary reference is Apple's Human Interface Guidelines (HIG), which provides principles and specific guidance on navigation patterns, controls, typography, color, and accessibility. Applying these…
HIG
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.
Stage 11: UIKit
UIKit
UIKit is Apple's foundational framework for building iOS and tvOS user interfaces. It provides the core building blocks including views, view controllers, navigation controllers, table views, and gesture recognizers. UIKit uses an imperative, event-driven model and has been the basis of iOS development since the…
Views, View Controllers
Views and view controllers are the two primary building blocks of UIKit's architecture. Views are responsible for displaying content and receiving touch input, while view controllers manage a screen's lifecycle and coordinate between views and data. Every visible screen in a UIKit app is managed by at least one…
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…
Navigation Stacks
The navigation stack in UIKit is managed by UINavigationController using a push-pop model. View controllers are pushed onto the stack when navigating forward and popped when the user taps the Back button or calls popViewController. The navigation bar automatically reflects the current top of the stack.
Pushing Presenting
Pushing a view controller adds it to the navigation stack with a standard slide animation from the right. Presenting a view controller modally overlays it on the current screen, often as a sheet or full-screen cover. The choice between pushing and presenting depends on whether the new screen is part of the current…
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…
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…
IBOutlets
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…
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.
Auto layout
Auto Layout is a constraint-based layout system that defines the size and position of views relative to each other and to the container. It automatically adapts layouts for different screen sizes, orientations, and locales. Constraints are created visually in Interface Builder or programmatically using…
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.
Views and Modifiers
SwiftUI views are lightweight structs that describe a piece of UI. Modifiers are methods called on views that return a new, modified version, allowing chaining. Common modifiers include padding, frame, background, foregroundStyle, and font. Building layouts by composing views and chaining modifiers is the primary…
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,…
View Transitions
View transitions in SwiftUI animate changes in the view hierarchy when views appear or disappear. The transition modifier specifies how a view enters and exits the screen using effects like slide, opacity, scale, and move. Combined with animation, transitions make state changes and navigation feel smooth and polished.
Stage 12: Core Animation
Core Animation
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…
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,…
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…
Stage 13: SwiftUI
SwiftUI
SwiftUI is Apple's declarative UI framework for building apps across iOS, macOS, watchOS, and tvOS. Introduced in 2019, it replaces UIKit's imperative approach with composable views written entirely in Swift. SwiftUI automatically handles layout, animations, and UI updates when the underlying data changes.
Navigation Stacks
Navigation stacks in SwiftUI are managed by NavigationStack (iOS 16+), which maintains a path representing the current navigation state. Views are pushed onto the stack by navigating to a value, and the stack handles the back button automatically. The state-driven model enables programmatic navigation and full deep…
Navigation View
NavigationView is the SwiftUI component for hierarchical navigation, used before NavigationStack was introduced in iOS 16. It wraps a view and provides a navigation bar and back navigation behavior. NavigationView is still relevant for apps targeting iOS 15 and earlier.
NavigationLink
NavigationLink is a SwiftUI component used to create navigation hierarchies within an app. It enables developers to define navigation paths between views, typically within a NavigationView. When tapped, a NavigationLink pushes a new view onto the navigation stack. It can be configured with a destination view and…
Presenting / Dismissing views
Presenting views in SwiftUI is done using modifiers like sheet, fullScreenCover, and popover that show views modally over the current screen. Dismissal is handled using the dismiss environment action or by toggling the Boolean binding that controls the presentation. Knowing when to present modally versus navigate…
Stage 14: Architectural Patterns
Architectural Patterns
iOS development architectural patterns are structured approaches to organizing code for better maintainability, testability, and scalability. Each pattern has its strengths, and the choice often depends on project size, complexity, and team preferences. Understanding these patterns helps developers create more…
Stage 15: Reactive Programming
Reactive Programming
Reactive Programming is a declarative programming paradigm focused on data streams and the propagation of change. It emphasizes the automatic distribution of changes through data flows. Key concepts include observable streams of data, operators to transform and combine streams, and subscribers that react to stream…
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…
Publishers / Subscribers
The Combine framework in iOS uses Publishers and Subscribers as core components for reactive programming. Publishers are types that can emit a sequence of values over time, representing sources of asynchronous events or data. Subscribers receive and process these values, defining how to handle the published data.…
Operators & Pipelines
Combine operators transform, filter, and combine publishers into processing pipelines. Common operators include map, filter, flatMap, combineLatest, merge, and debounce. Chaining operators between a publisher and a subscriber creates a declarative pipeline that expresses complex asynchronous logic in a readable way.
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…
MVC
MVC (Model-View-Controller) is the architectural pattern used by UIKit and historically recommended by Apple for iOS apps. The Model holds data and business logic, the View displays content, and the Controller mediates between them. In practice, UIKit view controllers tend to accumulate too much responsibility, a…
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…
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…
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…
TCA
The Composable Architecture (TCA) is an opinionated architecture library for Swift developed by Point-Free. It organizes app logic around unidirectional data flow with state, actions, reducers, and effects. TCA emphasizes testability and composability, allowing large app features to be built from smaller,…
VIPER
VIPER is an architectural pattern that divides app code into five distinct components: View, Interactor, Presenter, Entity, and Router. Each component has a single, clearly defined responsibility, making the codebase highly modular and testable. VIPER is commonly used in large iOS projects where strict separation…
Stage 16: Delegate Pattern
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…
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…
RxSwift
RxSwift is the Swift implementation of the ReactiveX library, providing a comprehensive API for reactive programming. It introduces Observable sequences that emit items over time and a large set of operators for combining and transforming them. RxSwift was widely adopted in iOS development before Apple introduced…
Observables & observers
An Observable in RxSwift is a sequence that emits zero or more items over time before completing or erroring. Observers subscribe to Observables and receive emitted items, error notifications, or completion events. The relationship between Observable and Observer is the foundation of all RxSwift-based reactive code.
Subjects
Subjects in RxSwift act as both Observables and Observers, making them useful for bridging non-reactive code into reactive streams. PublishSubject emits only new items to subscribers; BehaviorSubject replays the last value to new subscribers; and ReplaySubject replays a configurable number of past values. Subjects…
Operators
RxSwift operators are functions that process, transform, or combine observable sequences. They allow developers to manipulate data streams in powerful ways. Common operators include map (transform elements), filter (select elements based on criteria), flatMap (transform elements into new observables), merge…
Schedulers
Schedulers in RxSwift control on which thread or queue Observable work executes. MainScheduler runs work on the main thread for UI updates, while ConcurrentDispatchQueueScheduler and SerialDispatchQueueScheduler run work on background queues. The observeOn and subscribeOn operators specify which scheduler handles…
RxSwift with MVVM
RxSwift integrates seamlessly with the MVVM (Model-View-ViewModel) architecture in iOS development. In this combination, ViewModels expose Observable properties that Views can bind to, creating a reactive data flow. Models emit data changes through Observables, which ViewModels transform and expose to Views. This…
Stage 17: Callbacks
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.
Closures
Closures are self-contained blocks of code that can capture and store references to values from the surrounding context. In Swift, closures are first-class types that can be passed as arguments, stored in variables, and returned from functions. They are the basis for callbacks, higher-order functions like map and…
Understanding and using Closures
Understanding closures involves knowing their syntax, how they capture surrounding values, and how to use them as function parameters and return values. Swift offers shorthand argument names and trailing closure syntax to keep closure usage concise. Closures appear throughout the Swift standard library and iOS SDK…
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…
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…
Stage 18: Data Persistence
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.
Core Data
Core Data is Apple's framework for persisting complex object graphs and relational data on iOS. It provides an abstraction layer over SQLite with tools for defining data models, fetching, filtering, and observing changes. Core Data supports undo/redo, background data operations, and CloudKit integration for syncing…
User Defaults
User Defaults is a simple key-value store for persisting lightweight user preferences and settings across app launches. It stores basic types like strings, numbers, booleans, and dates in a plist file. User Defaults is not suitable for sensitive or large data and is intended only for small configuration values.
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…
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,…
SQLite
SQLite is a lightweight, serverless relational database engine embedded in iOS. Apps can use SQLite directly through its C API or through higher-level Swift wrappers like GRDB or SQLite.swift. SQLite provides structured, queryable storage and serves as the underlying engine for Core Data and other data frameworks.
Stage 19: Async / Await
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…
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…
Stage 20: JSON / XML
JSON / XML
JSON and XML are the two most common data interchange formats used when communicating with web services or storing structured data locally. iOS apps frequently parse JSON responses from REST APIs and serialize Swift models into JSON before sending them. XML is less common but still used in some legacy APIs and…
Parsing
Parsing JSON in Swift is done using Codable and JSONDecoder, which automatically decode JSON data into Swift structs and classes. XMLParser provides a SAX-style parser for processing XML documents event by event. Correct parsing handles optional fields, nested structures, and type mismatches cleanly.
Serializing
Serializing converts Swift data structures into JSON or XML format for storage or network transmission. JSONEncoder turns Codable types into Data. Proper serialization handles date formats, custom key naming strategies, and optional values to produce valid output that the server or storage layer can interpret…
Stage 21: Concurrency and Multithreading
Concurrency and Multithreading
Concurrency and multithreading allow iOS apps to perform multiple operations simultaneously without blocking the main UI thread. iOS provides Grand Central Dispatch (GCD) and Operation Queues as the two main systems for managing concurrent work. Swift's async/await, introduced in Swift 5.5, is now the preferred…
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…
Operation Queues
Operation Queues manage collections of NSOperation objects and execute them concurrently or serially. Operations support dependencies on each other, cancellation, and priority settings. Operation Queues provide a higher-level abstraction than GCD and are useful when tasks have complex interdependencies or need…
Stage 22: Networking
Networking
Networking in iOS covers how apps communicate with remote servers and APIs. The native foundation is URLSession for HTTP requests, and Alamofire is a popular third-party library that simplifies common networking tasks. iOS apps commonly consume REST APIs over HTTPS and, increasingly, GraphQL APIs.
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…
REST
REST (Representational State Transfer) is an architectural style for networked APIs that uses standard HTTP methods like GET, POST, PUT, PATCH, and DELETE. iOS apps consume REST APIs by making URLSession or Alamofire requests and decoding JSON responses using Codable. REST is the most common API style in iOS app…
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.
URLSession
URLSession is Apple's built-in networking API for making HTTP and HTTPS requests. It supports data tasks for simple requests, download and upload tasks for large transfers, and background sessions that continue after the app is suspended. URLSession integrates with async/await in Swift, allowing network calls to be…
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…
Stage 23: Dependency Manager
Dependency Manager
Dependency managers automate adding, updating, and removing third-party libraries in an iOS project. The three main options are Swift Package Manager, CocoaPods, and Carthage. Each has different trade-offs around integration complexity, build speed, and the breadth of available packages.
CocoaPods
CocoaPods is a dependency manager for Swift and Objective-C Cocoa projects. It has over 100 thousand libraries and is used in over 3 million apps. CocoaPods can help you scale your projects elegantly.
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…
Swift Package Manager
The Swift Package Manager (SwiftPM) is a tool for managing the distribution of Swift code. It’s integrated with the Swift build system to automate the process of downloading, compiling, and linking dependencies. The Package Manager is included in Swift 3.0 and above.
Stage 24: Frameworks & Library
Frameworks & Library
Frameworks and libraries are reusable packages of compiled code and resources that can be linked into iOS apps. Understanding the differences between XCFrameworks, static libraries, and dynamic libraries is important for packaging shared code, distributing SDKs, and managing binary dependencies.
XCFramework
An XCFramework is a distributable binary format that bundles frameworks for multiple platforms and architectures in a single package. It supports iOS devices, iOS Simulator, macOS, and other Apple platforms simultaneously. XCFrameworks are the recommended format for distributing precompiled iOS libraries and SDKs.
Static Library
A static library is a compiled archive of object code that is copied directly into the app binary at link time. Static libraries increase binary size but have no runtime loading overhead. They are distributed as .a files and are commonly used to share compiled code between targets within the same Xcode project.
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.
Stage 25: Accessibility
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…
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…
Voice Over
VoiceOver is iOS's built-in screen reader that allows users who are blind or have low vision to navigate and interact with apps using gestures and spoken audio feedback. Apps support VoiceOver by providing accessibility labels, traits, and hints on UI elements. Testing with VoiceOver enabled is essential for…
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…
Stage 26: Code Quality Tools
Code Quality Tools
Code quality tools for iOS enforce consistent style and detect potential issues in Swift code through static analysis. SwiftLint, Tailor, and SwiftFormat are the main tools available. Integrating them into the Xcode build process or CI pipeline ensures consistent code quality across the team.
SwiftLint
SwiftLint is an open-source tool developed by Realm, that facilitates maintaining standardized code development by enabling the definition and enforcement of project-specific conventions and guidelines. It ensures developers adhere to these standards, thereby promoting organized code practices.
Tailor
Tailor is a static analysis tool for Swift that checks code style and detects common issues. It is configurable and integrates with Xcode and CI pipelines. Tailor is an alternative to SwiftLint for teams that prefer a different rule set or configuration model.
SwiftFormat
SwiftFormat is a command-line tool that automatically reformats Swift source code to follow consistent style rules. Unlike SwiftLint, which reports violations, SwiftFormat directly edits source files. It handles formatting rules like indentation, blank lines, trailing commas, and bracket placement.
Stage 27: Debugging Techniques
Debugging Techniques
Debugging in iOS involves identifying and resolving issues in app behavior, performance, and memory. Xcode provides a built-in debugger with breakpoints and variable inspection, and Instruments provides deep profiling for CPU, memory, energy, and network usage.
Xcode Debugger
The Xcode debugger allows developers to pause execution at breakpoints, inspect variable values, evaluate expressions using LLDB commands in the console, and step through code line by line. The debug area displays the current thread, call stack, and local variable state during a paused session.
Profiling Instruments
Instruments is a performance analysis tool bundled with Xcode that provides templates for profiling CPU usage, memory allocations, energy impact, network activity, and more. The Time Profiler identifies which functions consume the most CPU time, while the Allocations instrument tracks memory usage and helps detect…
Stage 28: CI / CD
CI / CD
Continuous Integration and Continuous Delivery (CI/CD) for iOS automates building, testing, and distributing apps on every code change. CI/CD pipelines run on platforms like CircleCI, Jenkins, GitHub Actions, GitLab, and Azure DevOps. Automated pipelines catch regressions early, enforce code quality checks, and…
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…
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.
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.
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.
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…
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…
ARKit
ARKit is Apple's augmented reality framework for iOS. It uses the device's camera and motion sensors to track the physical world and overlay digital content on top of it. ARKit provides features like horizontal and vertical plane detection, image tracking, face tracking, and LiDAR scene reconstruction on supported…
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…
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.
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.
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.
Unit & UI Testing
iOS apps are tested at two levels: unit tests verify individual functions and classes in isolation, and UI tests verify app behavior from the user's perspective. XCTest is the framework for both. Unit tests run on the local machine and are fast; UI tests launch the full app on a device or simulator and simulate…
XCTest
XCTest is Apple's framework for writing unit tests in Swift and Objective-C. Tests are organized into subclasses of XCTestCase, and individual test methods begin with "test". XCTest integrates with Xcode's Test Navigator for running tests, viewing results, and measuring code coverage against the app's source.
XCUITest
XCUITest is the UI testing component of XCTest that automates user interactions with a running iOS app. Tests launch the app, query elements by accessibility identifier or type, perform actions like tap, swipe, and type, and assert on UI state. XCUITest runs on a simulator or physical device and is slower than unit…
Test Plan & Coverage
Test plans in Xcode define how tests are executed, including which test targets to include, environment variables, and configurations for multiple runs with different settings. Code coverage reports show which lines of code are exercised by tests, helping identify gaps. Test plans make it straightforward to run…
Stage 29: FastLane
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…
Stage 30: TestFlight
TestFlight
TestFlight is Apple's platform for distributing beta versions of iOS apps to testers before public release. Internal testers with access to the developer's App Store Connect account can be added directly, while external testers receive email invitations. TestFlight builds expire after 90 days and can be shared with…
Stage 31: App Store Distribution
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…
Stage 32: App Store Optimization (ASO)
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.
Stage 33: Keeping Updated with WWDC
Keeping Updated with WWDC
WWDC (Apple Worldwide Developers Conference) is Apple's annual developer event where new iOS, macOS, and framework announcements are made. Watching WWDC sessions, reading the associated documentation, and reviewing the release notes keeps iOS developers current with new APIs, deprecations, and best practices.
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…
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.
New Feature Announcements
Apple announces new platform features at WWDC each year that affect how iOS apps are built and what they can offer users. Recent examples include StoreKit 2, Live Activities, WidgetKit updates, and Vision framework additions. Staying aware of these announcements helps iOS developers evaluate which new capabilities…
Stage 34: More topics
Simple UI Building
Simple UI building in SwiftUI covers the fundamental skills for constructing working app screens. This includes composing layout containers, applying modifiers, connecting views to state, implementing navigation between screens, and adding animated transitions.
Questions about the iOS Roadmap
Is the iOS Roadmap free?
Yes. All 170 lessons in this roadmap are free to read on Bibha AI Learning Labs, with no account and no payment. Signing in is optional: it lets you mark lessons as done and keep your progress, and it opens the AI tutor, which runs on your own API key.
How long does the iOS Roadmap take?
There is no fixed duration. It has 170 lessons in 34 stages, and the time it takes depends on how many hours you give it each week. Nothing is locked, so you can skip what you already know, and your progress is saved once you sign in.
Where should I start the iOS Roadmap?
Start with stage 1, Objective-C, and work down in order. The stages are numbered in the order the roadmap suggests, but every lesson is open, so if you already know Objective-C you can go straight to Pick a Language or anything after it. Each lesson links to free resources for going deeper.
Can I learn iOS in Hindi?
The lessons are written in English. Once you sign in, you can ask the AI tutor on any lesson to explain it in Hindi or Hinglish. It answers from that lesson’s own text, so the explanation stays on the syllabus. The tutor runs on your own Google, OpenAI or Anthropic key.