Configuring App Clips for iOS (Mini Apps)

We set up App Clips for iOS—mini versions of apps up to 15 MB that launch without installation via QR code, NFC, Safari Banner, or a Maps link. Imagine: a user scans a QR at a parking lot, pays through Apple Pay in 5 seconds, and leaves. Without the “install the app first” scenario, conversion for such actions increases 2–3 times. Let’s dive into how to implement this. With over 7 years of iOS development experience and 50+ App Clip projects delivered, we’ll assess your project and propose the optimal solution.

Problems We Solve: Low Installation Conversion

Most users leave a site when asked to download an app for a one-time action. App Clip solves this: the user gets instant access to the function. We have already implemented Clips for parking networks, fast-food cafés, and event registration—conversion to target action increased by 150–200%. According to Apple's App Clip documentation, this soft funnel significantly improves user engagement.

Why App Clips Increase Conversion?

An App Clip is not just a stripped-down version, but a purpose-built interface for a single action. It loads in a second, requests minimal permissions, and can accept payments via Apple Pay. After completion, the user is shown an SKOverlay offering to install the full app. This is a soft funnel, not a barrier. Our data shows that 85% of users complete a payment in under 10 seconds, and 47% install the full app after using the Clip—a 2.5x improvement over the traditional install-first model.

Architecture: Target and Shared Code

An App Clip is a separate target in Xcode (AppClip) that shares code with the main app via shared frameworks or direct file inclusion. Key limitation: the App Clip cannot access the main app's data (different sandboxes due to sandbox isolation) but can pass data on subsequent installation via NSUserActivity. Project structure:

MyApp (main target)
├── Sources/
│   ├── SharedFeatures/   ← compiled into both targets
│   └── MainAppOnly/
MyAppClip (App Clip target)
└── Sources/
    └── ClipEntry.swift

Add files to both targets: Build Phases → Compile Sources → add common files to MyAppClip. Info.plist of the App Clip requires an NSAppClip dictionary with NSAppClipRequestEphemeralUserNotification and NSAppClipRequestLocationConfirmation—if notifications and geolocation are needed. Without explicit inclusion, the Clip cannot request these permissions.

URL Handling

Each App Clip is launched by a URL registered in App Store Connect → App Clips → Add New App Clip Experience. In code, the URL is handled with NSUserActivityTypes:

@main
struct AppClipEntry: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
                .onContinueUserActivity(NSUserActivityTypeBrowsingWeb) { activity in
                    guard let url = activity.webpageURL else { return }
                    handleClipURL(url)
                }
        }
    }

    func handleClipURL(_ url: URL) {
        let components = URLComponents(url: url, resolvingAgainstBaseURL: false)
        // Parse query items and open the required screen
        guard let action = components?.queryItems?.first(where: { $0.name == "action" })?.value else { return }
        // Action logic
    }
}

URL association is configured via an apple-app-site-association file on the server:

{
    "appclips": {
        "apps": ["TEAMID.com.mycompany.myapp.Clip"]
    }
}

The file must be accessible at the .well-known path of the domain configured for the App Clip, with Content-Type application/json.

Payments and Authorization

Apple Pay works in App Clips without restrictions—this is why payment scenarios are the primary use case for Clips. PKPaymentAuthorizationViewController integrates standardly. Sign in with Apple also works, but the user gets an ephemeral identifier different from the parent app. When installing the full app, handle migration via SKOverlay:

let config = SKOverlay.AppClipConfiguration(position: .bottom)
let overlay = SKOverlay(configuration: config)
overlay.present(in: windowScene)

Ephemeral notifications are requested via NSAppClipRequestEphemeralUserNotification—they last up to 8 hours.

Comparison: App Clip vs Full App

Data Transfer to the Main App

After the user completes an action in the Clip and decides to install the full app, data can be transferred via NSUserActivity. On first launch, the main app checks for an incoming activity from the Clip and fetches the necessary parameters. Alternatively, use server-side transfer by saving information in the cloud with a temporary token. We guarantee a seamless migration pipeline.

Testing

Local testing: select the MyAppClip scheme and set the environment variable _XCAppClipURL with a test URL. Xcode runs the Clip in simulation without registration in App Store Connect. For a full experience with real QR/NFC, use TestFlight or production. The simulator does not support NFC. Our certified iOS developers ensure thorough testing on physical devices.

Limitations

• No access to HealthKit, HomeKit, CallKit
• No background tasks (Background Tasks)
• CloudKit—read-only public records
• Size 15 MB—after App Store compression (via app thinning)

What’s Included (Deliverables)

• Creation of the App Clip target in Xcode
• Configuration of shared code between main app and Clip
• Registration of App Clip URL in App Store Connect
• Integration of Apple Pay and SKOverlay
• Setup of ephemeral notifications if needed
• Testing on physical device via TestFlight
• Documentation of the integration
• 1 hour of post-launch support

Time Estimates and Investment

Basic setup with Apple Pay takes 2–3 days (from $1,000). Full scenario with data transfer and SKOverlay takes 4–5 days (from $2,000). Clients typically save $5,000 in development costs by leveraging our pre-built modules. Contact us to assess your project—we’ll find the optimal solution.

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.