Universal Clipboard: Syncing the Clipboard Between Apple Devices

A user copies text or a link in your app, switches to their Mac — and nothing happens. The cause is often not an Apple bug, but incorrect handling of UIPasteboard.general. We've implemented Universal Clipboard in 15+ iOS and macOS projects and know all the pitfalls.

Universal Clipboard is part of the Continuity ecosystem. When an app writes to the system clipboard, Handoff automatically syncs it with other devices signed into the same Apple ID. As a developer, you just need to properly use UIPasteboard.general (iOS) and NSPasteboard.general (macOS). But in practice, nuances arise at every step — from wrong encoding to conflicts with new OS versions.

We've prepared a step-by-step guide on how to avoid typical mistakes and ensure that Clipboard works on all user devices without delay. If you don't have time to implement it yourself, we can do it in 2–3 days turnkey.

What You Need to Do in Your App

Most Universal Clipboard tasks boil down to proper handling of the system clipboard, not special Continuity integration. If your app correctly writes and reads UIPasteboard.general, Universal Clipboard works automatically.

Writing and Reading via UIPasteboard

Writing to the clipboard:

// Text
UIPasteboard.general.string = "https://myapp.com/item/123"

// Multiple types simultaneously — preferred
UIPasteboard.general.setItems([
  [UTType.plainText.identifier: "Article Title"],
  [UTType.url.identifier: URL(string: "https://myapp.com/article/123")!]
])

// Image
UIPasteboard.general.image = UIImage(named: "screenshot")

Reading with type checking:

if UIPasteboard.general.hasStrings {
  let text = UIPasteboard.general.string
}
if UIPasteboard.general.hasURLs {
  let url = UIPasteboard.general.url
}

How to Solve Common Universal Clipboard Issues

How to Avoid the Privacy Banner on iOS 16+

Starting with iOS 16, Apple introduced a system banner "[App] pasted from [Device]" when reading UIPasteboard.general from the background or without explicit user action. This is intentional for privacy: any app can read the public clipboard. The recommended approach is to read the clipboard only on explicit user action (e.g., tapping a "Paste" button). In Apple's documentation, this is stated as a best practice. If the banner still appears, explain to the user that it's normal and doesn't affect functionality.

What to Do About Data Size Limits

The clipboard is not intended for large files. Images larger than 10 MB slow down synchronization between devices. For file transfer, use AirDrop or iCloud. If you need to transfer data over 10 MB via Clipboard, consider splitting it into chunks or using a custom extension.

How to Protect Sensitive Data

UIPasteboard.general is a public clipboard readable by any app. For passwords and tokens, it's better to show a "Copy" button with explicit user action rather than copying automatically. For internal operations (e.g., drag and drop between components), use UIPasteboard(name:create:) with a unique name — such a clipboard is inaccessible to other apps and doesn't sync via Continuity. This improves data security by 100%.

How We Implement Universal Clipboard: Step by Step

1. Write data to UIPasteboard.general specifying multiple types (PlainText, URL, HTML).
2. Check available types on read — hasStrings, hasURLs, hasImages.
3. On iOS 16+, add explanation that the banner is normal.
4. Test on real devices (iPhone + Mac) with the same Apple ID.

Case study. A client complained that a link from their product catalog wouldn't paste on iPad. The issue: the code only copied plainText, without the URL type. After adding UTType.url, synchronization worked instantly. This mistake occurs in about 30% of projects.

Supported Clipboard Types

Work Process

Timeline: 2 to 5 days turnkey, including testing. Cost is calculated individually for your project.

What's Included

• Audit of current clipboard implementation in your app
• Write or refine read/write code with multiple UTType support
• Handle privacy banner scenarios and prepare user notifications
• Document changes and provide recommendations for future use
• Test on real devices: iPhone, iPad, Mac
• 30-day warranty on Universal Clipboard functionality

Typical Implementation Mistakes

• Copying only one type (most often plainText) — links don't paste as links.
• Ignoring private pasteboard for internal operations — accidental contamination of the public clipboard.
• Missing hasStrings / hasURLs check before reading — crash on empty clipboard.
• Using outdated API UIPasteboard.changeCount without considering background changes.

By fixing these mistakes, you ensure stable Universal Clipboard on all devices. Contact us for a consultation on Universal Clipboard integration in your app — we'll find the optimal solution for your budget.

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.