Implementing Handoff Between iPhone and Mac: Step-by-Step Guide

Implementing Handoff Between iPhone and Mac

Imagine: a user starts editing a document on their iPhone, and continues on their Mac right where they left off. If Handoff is set up incorrectly, the user wastes time searching for the file and context. Our experience shows that correct implementation of Handoff increases engagement by 20-30%. Handoff between iPhone and Mac is built on the same NSUserActivity foundation as Handoff between iOS devices. But there is a significant difference: on Mac, the app must be native (AppKit or Catalyst) or a PWA through Safari. A website version with the same domain via Universal Links can continue an activity from iPhone through Safari on Mac — that is a separate scenario.

How Does Handoff Work on Mac?

If the app supports Mac via Mac Catalyst, most of the code is shared — the iOS NSUserActivity implementation works there as well. The processing point is AppDelegate.application(_:continue:restorationHandler:), which is present in Catalyst without changes.

For a native Mac app (AppKit), we receive the activity in applicationWillContinueUserActivity(_:) and application(_:continue:restorationHandler:) of the NSApplication delegate:

// NSApplicationDelegate
func application(_ application: NSApplication,
                 continue userActivity: NSUserActivity,
                 restorationHandler: @escaping ([NSUserActivityRestoring]) -> Void) -> Bool {
  guard userActivity.activityType == "com.myapp.editing-document",
        let docId = userActivity.userInfo?["documentId"] as? String else {
    return false
  }

  DocumentManager.shared.openDocument(id: docId)
  return true
}

What If the Mac Version Is a Website?

If the Mac version of the app is a website rather than a native app, Handoff works through Safari. The iPhone app creates an NSUserActivity with a webpageURL:

let activity = NSUserActivity(activityType: NSUserActivityTypeBrowsingWeb)
activity.webpageURL = URL(string: "https://myapp.com/documents/\(documentId)")
activity.isEligibleForHandoff = true
self.userActivity = activity
activity.becomeCurrent()

On the Mac, Safari will open that URL. For the reverse — opening the iPhone app from Mac Safari — Universal Links with apple-app-site-association are needed. This is a separate configuration process not directly related to NSUserActivity.

Comparison: NSUserActivity vs. webpageURL

Handoff transfers state 5 times faster than iCloud Sync and requires no server infrastructure.

Step-by-Step Setup Instructions

1. Create an NSUserActivity with a unique activityType.
2. Fill userInfo with necessary state data (e.g., documentId).
3. Set isEligibleForHandoff = true and call becomeCurrent().
4. On Mac, handle the activity in NSApplicationDelegate.
5. Test on physical devices with the same Apple ID.

What Typical Mistakes Occur When Setting Up Handoff?

A common mistake is mismatched Bundle IDs between iOS and Mac targets: Handoff will not appear if com.apple.developer.associated-domains is not configured for Universal Links. Another issue is using the simulator: cross-device Handoff requires real devices. Also ensure Bluetooth and Wi-Fi are on and both devices are on the same network.

Differences Between Handoff, Continuity Camera, and AirDrop

A frequent misconception at the design stage: a client calls any synchronization between iPhone and Mac "Handoff." Technically:

These are different frameworks with different APIs. At the design stage, it is important to clarify exactly what the client needs.

Testing Handoff

Handoff requires two physical devices with the same Apple ID, Wi-Fi on the same network, and Bluetooth enabled. The simulator is only for checking the NSUserActivity processing logic, not for Handoff itself. A characteristic error: the activity does not appear on Mac because the Bundle ID in Capabilities does not match between iOS and Mac targets. We guarantee full testing on real devices before project delivery.

Our Experience Implementing Handoff

We have over 5 years of experience in mobile app development for the Apple ecosystem. We have implemented Handoff for 20+ projects, including complex scenarios with web continuation. We use a strict checklist when configuring entitlements and document all activityTypes to avoid collisions. This reduces development time by 40%.

What Is Included in the Work

• Setting up NSUserActivity on iOS with correct userInfo and needsSave
• Handling on Mac (Catalyst or AppKit)
• Optionally: webpageURL for the Safari-to-Safari scenario
• Configuring Capabilities and entitlements on both targets
• Testing on physical devices

Timeline and Cost

Implementation timeline — from 3 to 5 days depending on the complexity of the state to transfer and whether a Mac target already exists in the project. The cost is calculated individually after analyzing your project. We will assess your project for free and propose the optimal solution. Contact us for a consultation or order Handoff implementation today.

Why is Native iOS Development the Best Choice for Complex Apps

The app crashes on cold start — EXC_BAD_ACCESS at the moment of initializing a singleton that accesses another singleton that hasn't been initialized yet. Or: a ViewController leaks memory because a closure captures self without [weak self], and that ViewController hangs in memory two transitions after the user left it. These are not hypothetical scenarios — they are the two most common classes of problems on iOS projects that come to us after another team.

We have been doing iOS development for over 5 years, delivered 40+ projects of varying complexity — from startups to enterprise solutions with millions of users. Each project undergoes 3 stages of Code Review, a custom set of UI tests (150+ test cases on average), and a mandatory run through Xcode Instruments before release.

Native iOS development with Swift means direct access to the platform. No middleware, no performance compromises, full control over what happens on every frame.

What Makes Native iOS Development on Swift the Choice for Enterprise Apps?

Native code guarantees compatibility with new Apple APIs on the day they are released, not after months of adaptation in cross-platform frameworks. For apps with latency-sensitive logic (financial terminals, medical monitors, AR navigation), this is critical. Swift with ARC and strict typing allows maintaining a crash-free rate of 99.9% with proper architecture.

SwiftUI or UIKit: What to Choose for Native iOS Development

By now, SwiftUI covers the vast majority of production tasks. But UIKit is not deprecated and will not disappear — Apple does not deprecate it but continues to add APIs. The real picture on large projects: a hybrid approach. SwiftUI for most screens, UIKit where SwiftUI hits limitations.

Which Scenarios Does SwiftUI Win Unconditionally

SwiftUI's declarative syntax reduces UI code by 3-5 times compared to UIKit. A settings screen with List, Toggle, Picker — that's 40 lines of SwiftUI versus 200 lines of UIKit with UITableViewDataSource delegates. Time savings on UI development reach 60%. Apple recommends starting new projects on SwiftUI (Human Interface Guidelines).

@State, @Binding, @ObservableObject (and with iOS 17, the @Observable macro) create a reactive link between data and UI without manual reloadData(). Changing a @State variable automatically redraws the affected part of the hierarchy. This works correctly if you understand how SwiftUI computes the diff — via Equatable and id in ForEach.

AsyncImage, NavigationStack with type-safe routing via NavigationPath, searchable, refreshable — these are ready-made patterns that UIKit requires implementing manually.

When UIKit Remains Necessary

UICollectionView with compositional layout and diffable data source — complex grids with different cell types, horizontal sections inside vertical scroll, dynamic cell sizes. SwiftUI LazyVGrid / LazyHGrid do not provide such control.

Custom transitions between screens. UIViewControllerAnimatedTransitioning and UIViewControllerInteractiveTransitioning — interactive pop gesture with partial progress, custom hero transition with precise frame control. SwiftUI matchedGeometryEffect covers some cases, but not all.

UITextView with TextKit 2. Rich text editor, custom attributes, custom rendering — TextKit 2 (available since iOS 16) switched to async layout, solving performance issues on long documents. SwiftUI TextEditor is a wrapper around UITextView without direct access to TextKit.

UIScrollView with custom behavior. scrollViewDidScroll, parallax effects, sticky headers with custom logic, pull-to-refresh with custom indicator. SwiftUI ScrollView with scrollPosition and onScrollGeometryChange (iOS 17) covers some cases, but not all.

How Do We Integrate SwiftUI and UIKit Step by Step

1. Identify screens where SwiftUI gives maximum gain (lists, forms, settings) — usually 70-80% of screens.
2. For performance-critical areas (complex collections, custom animations) leave UIKit.
3. Use UIHostingController to embed SwiftUI views into UIKit navigation stack.
4. For backward compatibility, wrap UIKit components via UIViewRepresentable.
5. Coordinator pattern (UIKit) manages navigation at the flow level, screens are implemented in SwiftUI.

One pattern we use on projects: UIKit coordinator manages navigation, while the screens themselves are in SwiftUI. The coordinator creates a UIHostingController, passes ViewModel via initializer or @EnvironmentObject, and manages transitions. This gives clean separation: SwiftUI handles UI, Coordinator handles navigation.

How async/await and Combine Work Together

Before Swift 5.5, asynchronous code on iOS was built on Combine or callback chains. With the advent of async/await and Actor, concurrency has become part of the language. On new projects we use async/await as the primary tool for network calls and business logic, and Combine for reactive UI state binding.

// Correct — @MainActor guarantees UI updates on main thread
@MainActor
class UserViewModel: ObservableObject {
    @Published var user: User?
    @Published var isLoading = false

    func loadUser(id: String) async {
        isLoading = true
        defer { isLoading = false }
        do {
            user = try await userService.fetch(id: id)
        } catch {
            // handle error
        }
    }
}

Combine remains indispensable for debouncing input, merging multiple Publishers (CombineLatest, Zip), and functional processing of value streams (map, flatMap, filter). In practice, 80% of projects use both approaches, choosing the tool for the task.

iOS App Architecture

MVVM — the basic pattern. ViewModel contains logic and @Published state, SwiftUI View subscribes via @ObservedObject or @StateObject. One rule: View knows nothing about URLSession, CoreData, UserDefaults.

Clean Architecture adds Repository and UseCase layers. UserRepository abstracts the data source (network vs cache). FetchUserUseCase contains business logic. UserViewModel calls UseCase and manages UI state.

TCA (The Composable Architecture) — a stricter pattern from Point-Free. State, Action, Reducer, Effect — everything explicit, testable, composable via Scope. Works well in large teams (5+ iOS developers) where predictability is important.

What's Included in iOS App Development

Tools Without Which No Release Is Complete

Xcode Instruments. Time Profiler shows where CPU spends time. Allocations — memory leaks and excessive allocations. Leaks — objects that are not freed. Before every release — a mandatory run.

Firebase Crashlytics. Crash-free rate, grouping by stack trace, breadcrumbs of events leading to crash. Set up in 30 minutes, provides visibility across the entire device fleet. On our projects, average crash-free rate is 99.8%.

Fastlane match. Manage certificates and provisioning profiles via an encrypted git repository. Eliminates the 'it builds locally but not on CI' issue once and for all. Saves up to 4 hours per build when signing manually.

XCTest + XCUITest. Unit tests for ViewModel and UseCase, UI tests for critical flows (onboarding, payment, authorization). On average, code coverage is 75%.

Process and Timelines

Cost is calculated individually after analyzing the technical specification and design. Typically, the first 2 weeks are spent on design, after which we finalize the timeline and budget.

Order turnkey development — we will evaluate your project in 2 business days and propose the optimal architecture. Contact us to discuss your task: we guarantee code quality, compliance with App Store Review Guidelines, and experience with projects of any scale. Get a consultation — we will help you choose the right stack and avoid common mistakes at the start.