iOS Tutorial: Learn Apple Development from Scratch (2026)
Building my first iOS app felt like learning to code all over again. The App Store review process, provisioning profiles, Xcode's idiosyncrasies, and the sheer number of ways to lay out a screen were overwhelming. But once I understood the Apple ecosystem's philosophy — human interface guidelines, sandboxed apps, and a focus on polish — I realized iOS development produces some of the most satisfying user experiences in tech. This guide covers UIKit, which remains the foundation of iOS development, and touches on SwiftUI where it matters.
Xcode, Swift, and Project Configuration
Xcode is the only IDE you need for iOS development. Download it from the Mac App Store — it includes the Swift compiler, Interface Builder, simulators, and Instruments for profiling. When you create a new project, choose iOS > App, pick Swift as the language, and UIKit for the interface. The project navigator organizes your code under AppName/, with AppDelegate.swift handling lifecycle events and SceneDelegate.swift managing the scene-based UI for iOS 13+. The Info.plist contains configuration keys like bundle identifier, version, and permissions. Always set your deployment target to the oldest iOS version you want to support — iOS 16 is a good baseline in 2026.
import UIKit
@main class AppDelegate: UIResponder, UIApplicationDelegate {
func application(_ app: UIApplication, didFinishLaunchingWithOptions opt: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { return true } }Views, View Controllers, and UIKit Hierarchy
The UIKit architecture follows MVC: Model-View-Controller. Views are instances of UIView or subclasses — labels, buttons, image views, text fields. Each screen is managed by a UIViewController that owns a view hierarchy. The view controller's viewDidLoad method is where you set up your UI programmatically or load it from a storyboard. Lifecycle methods — viewWillAppear, viewDidAppear, viewWillDisappear, viewDidDisappear — let you start and stop animations, observe notifications, and manage resources. Always call super in these methods to preserve UIKit's internal behavior.
class MainViewController: UIViewController {
override func viewDidLoad() {
super.viewDidLoad()
view.backgroundColor = .systemBackground
let label = UILabel(frame: view.bounds)
label.text = "Hello iOS"
view.addSubview(label)
} }Auto Layout and Interface Builder
Auto Layout is a constraint-based system for positioning UI elements relative to each other and the screen bounds. You can create constraints in Interface Builder by Ctrl-dragging between views, or programmatically using NSLayoutConstraint or the more readable Anchors API — view.topAnchor.constraint(equalTo: safeArea.topAnchor). Always set translatesAutoresizingMaskIntoConstraints = false on views you constrain programmatically. Safe area insets account for the notch, home indicator, and status bar. I learned to use stack views (UIStackView) for most layouts — they distribute content automatically and reduce constraint clutter.
let button = UIButton()
button.translatesAutoresizingMaskIntoConstraints = false
view.addSubview(button)
button.centerXAnchor.constraint(equalTo: view.centerXAnchor).isActive = trueNavigation: UINavigationController and Segues
The standard navigation paradigm in iOS is a navigation stack managed by UINavigationController. It provides a navigation bar with a back button and optional right bar buttons. You push view controllers onto the stack with pushViewController(_:animated:) and pop them off programmatically or when the user taps Back. In storyboards, segues define transitions between view controllers — show (push) and present (modal) are the most common. Pass data between controllers by overriding prepare(for:sender:) and setting properties on the destination controller before the segue executes.
let detailVC = DetailViewController()
detailVC.itemID = 42
navigationController?.pushViewController(detailVC, animated: true)Data Persistence: Core Data and UserDefaults
UserDefaults handles small amounts of key-value data like user preferences and login tokens. For relational data, Core Data is Apple's object graph and persistence framework. It manages a NSPersistentContainer with a SQLite backend, fetches objects with NSFetchRequest, and supports undo, validation, and iCloud sync. The learning curve for Core Data is steep — managed object contexts, persistent store coordinators, and faulting behavior confused me for weeks. I recommend using CloudKit for syncing across devices or just using SQLite with GRDB if Core Data feels too heavy for your use case.
let container = NSPersistentContainer(name: "Model")
container.loadPersistentStores { _, error in
if let error = error { fatalError(error.localizedDescription) } }App Store Submission and TestFlight
Before submitting to the App Store, you need an Apple Developer account ($99/year). Archive your app in Xcode by selecting Any iOS Device and pressing Cmd+B, then Product > Archive. The Organizer window lets you upload the build to App Store Connect. Use TestFlight for beta distribution — you can invite up to 10,000 testers via email or a public link. The App Store review guidelines are strict: no placeholder UI, no undocumented features, and you must provide a valid demo account if your app requires login. Plan for a 24-48 hour review window, though expedited reviews exist for critical updates.
// Archive in Xcode: Product > Archive
// Then distribute via TestFlight or App StoreFrequently Asked Questions
Do I need a Mac to develop iOS apps?
Yes, Xcode only runs on macOS. You can use a Mac Mini, MacBook, or rent Mac cloud instances from services like MacStadium. Cross-platform alternatives like Flutter and React Native let you build for iOS from Windows, but you still need a Mac for the final build and submission.
Should I learn UIKit or SwiftUI in 2026?
Both. UIKit is stable, has the largest ecosystem of third-party libraries, and is required for many production apps. SwiftUI is the future and great for new projects, but still lacks some advanced customization. Learn UIKit first, then add SwiftUI.
What is the difference between a strong and weak reference?
A strong reference increases the retain count of an object and prevents it from being deallocated. A weak reference does not. Use weak references for delegate and closure capture lists to avoid retain cycles and memory leaks.
How do I handle push notifications?
Enable Push Notifications in your App ID and Xcode capabilities. Register for remote notifications with UIApplication.shared.registerForRemoteNotifications(), implement didRegisterForRemoteNotificationsWithDeviceToken, and forward the token to your server.
Originally published on Ayodhyyya. Last updated June 1, 2026.