Notification Service Extension for iOS

Users complain that push notifications arrive without an image — the server sent it, but the device shows nothing. Or in an e2e messenger, "New message" appears instead of the text due to encryption. Standard push handling is not enough. The solution is a Notification Service Extension. We create this Extension end-to-end: from target setup to testing on real devices.

What problems does Notification Service Extension solve?

Media attachments. The server sends an image URL, and the Extension downloads it via URLSession, saves it to a temporary directory, creates a UNNotificationAttachment, and passes it through contentHandler. Without this, attachments won't work in push notifications — the user sees only text. Download time is limited to 30 seconds, so we configure the URLSession timeout to 20 seconds with a fallback: if not in time, we show the notification without an image, we don't fail the Extension.

End-to-end encryption. The payload arrives encrypted, the Extension decrypts it with a key from the Keychain and substitutes the readable text. In e2e messengers, this is the only way to show the notification content without exposing keys on the server. For key sharing, we use App Groups and Keychain Sharing with a common access group.

Delivery analytics. The Extension sends a fire-and-forget request to the backend upon receiving the notification — recording a delivered event. UIApplicationDelegate.userNotificationCenter(_:didReceive:) fires only on tap, while the Extension fires immediately on delivery. This gives accurate metrics.

How to implement end-to-end encryption in Notification Service Extension?

The decryption process consists of several steps:

1. Get the encrypted payload from request.content.userInfo.
2. Extract the key from the shared Keychain (configure Keychain Sharing with the main app).
3. Perform decryption (e.g., AES-GCM) and form the readable notification body.
4. Pass the modified content via contentHandler.

This approach is safer than server-side decryption: the key never leaves the device. We use this method in messengers with end-to-end encryption, where the server has no access to message content.

How we implement the Extension: an example with media attachment

Here is a typical code for handling:

override func didReceive(_ request: UNNotificationRequest,
                          withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void) {
    self.contentHandler = contentHandler
    bestAttemptContent = (request.content.mutableCopy() as? UNMutableNotificationContent)
    // download attachment, on error -> contentHandler(bestAttemptContent!)
}

override func serviceExtensionTimeWillExpire() {
    // called just before timeout — show what we have
    if let contentHandler, let content = bestAttemptContent {
        contentHandler(content)
    }
}

The Extension lives in a separate process and has no direct access to the main app's data. For exchange, we use App Groups: UserDefaults(suiteName: "group.com.example.app") and FileManager with the group container. Keychain Sharing is configured via kSecAttrAccessGroup with the same group identifier.

Why the Extension doesn't work in the simulator and what to do about it

APNs push notifications are not delivered to the simulator. For testing, use a real device or simulate local notifications via Xcode. We ensure correct operation on physical devices after configuring provisioning profiles and entitlements.

Scenario comparison: time and complexity table

Checklist of typical mistakes when setting up Notification Service Extension

Approach comparison: media attachment via Notification Service Extension vs. server-side generation

Notification Service Extension is better if you need to display large images or video — saves up to 40% traffic compared to server-side generation.

What's included in the work

• Creation and configuration of the Notification Service Extension target in Xcode
• Implementation of logic: attachment, decryption, or analytics
• Configuration of App Groups and Keychain Sharing for data exchange
• Testing on a real device (Extension doesn't work in simulator for APNs push)
• Preparation of entitlements and provisioning profiles for the Extension target

Timeline and cost

Timeline: from 1 day (single scenario) to 3–4 days (comprehensive solution). Cost is calculated individually — contact us for your project evaluation. Order the Extension implementation and get quality assurance: our engineers have extensive experience in iOS development and Apple certification. Write to us — we'll propose the optimal solution.

Apple Developer Documentation — UNNotificationServiceExtension contains the full API specification.

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.