Skip to content
§
§ · ios app development

iOS app development, five rings deep.

A Swift-6 + SwiftUI-first iOS practice for DTC, SaaS, fintech, and health brands shipping native iPhone, iPad, and visionOS apps with Live Activities, Widgets, App Clips, and the Apple platform surface done right.

2,000+
brands shipped
55+
countries served
5
platform rings, mapped
48 h
scoped quote
§ 01 · five platform rings

Shipping on iOS is always about finding the right depth in Apple's stack.

Every iOS app sits on a five-ring stack. The outermost ring is App Store submission and signing. Inside that lives SwiftUI, plus the platform affordances only SwiftUI exposes: WidgetKit, Live Activities, App Clips, visionOS volumes. The next ring is UIKit, for the edge cases SwiftUI hasn't reached.

Deeper still sit Foundation and the specialized frameworks: HealthKit, StoreKit 2, CoreML, CloudKit. At the core is your app's logic in Swift 6. Knowing which ring a feature lives in tells you how much of Apple's platform you are actually using.

in short
  • SwiftUI first, UIKit where SwiftUI is not yet proven (UICollectionView edge cases, deeply custom transitions).
  • Five platform rings: App Store + signing → SwiftUI → UIKit bridge → Foundation + HealthKit / StoreKit 2 / CoreML → Swift 6 domain.
  • Native depth: WidgetKit, Live Activities, App Clips, Shortcuts, Sign in with Apple, Apple Pay, HealthKit, StoreKit 2.
  • Test stack: XCTest + Swift Testing for unit, TestFlight for real-user beta + crash signal.
  • Four engagement shapes: 2-week audit (refundable), greenfield build, UIKit→SwiftUI migration, retainer. Client owns App Store + signing certs.
ring 01 · app store

Review queue, signing, provisioning, privacy labels, TestFlight. Every shipped iOS app passes this ring.

ring 02 · swiftui

Declarative UI, Widgets, Live Activities, App Clips, focus filters, visionOS volumes. Default for new builds.

ring 03 · uikit bridge

Still needed for complex collection views, legacy interop, some framework edges. Clean SwiftUI interop.

ring 04 · frameworks

HealthKit, StoreKit 2, CoreML, CoreLocation, CloudKit. Where Apple-platform apps earn their feel.

ring 05 · swift 6

Your domain. Strict concurrency, actors, async/await. Non-negotiable for 2026 builds.

the depth test

Count how many rings your app uses. Apps that use only rings 1-2 could be React Native. Apps using 3-5 are genuinely native.

§ 02 · swiftui vs uikit

SwiftUI first, UIKit where proven.

SwiftUI is production-ready now. Every Apple platform feature shipped since 2020 (Widgets, Live Activities, App Clips, visionOS, focus filters) is SwiftUI-first or SwiftUI-only. UIKit still bridges edge cases cleanly via UIViewRepresentable and UIHostingController. The table shows when to use each.

needSwiftUI (default)UIKit (where)
navigationNavigationStack, NavigationSplitViewlegacy UINavigationController integration
lists + collectionsList, LazyVGrid, LazyVStackUICollectionViewCompositionalLayout edge cases
widgets + live activitiesSwiftUI onlynot applicable
app clipsSwiftUI onlynot applicable
visionOSSwiftUI + RealityKitnot applicable
complex video or ARSwiftUI + UIViewRepresentable wrappingAVKit, ARKit bridged
§ 03 · the platform rings, in motion

Five rings down. One app.

The animation below traces the five-ring stack from the outer App Store layer down to your Swift 6 domain core. Knowing which ring each feature sits in is the central architectural conversation every iOS engagement opens with.

Fig. 1 · platform rings · five rings, one app
§ 04 · the apple platform surface

The features that make iOS apps feel native.

Every iOS app has an icon and screens. What makes an app feel native, not ported, is the Apple platform surface it uses. That means Live Activities on the Lock Screen. Widgets on Home Screen and Today View. App Clips that launch without install. HealthKit for health data your app genuinely owns. Below is the platform surface we ship when your use case warrants it.

Editorial Apple platform framework map an iOS app developer plans against: concentric rings radiate outward from a central amber your-app core through Foundation and CoreData, SwiftUI and UIKit, HealthKit, StoreKit, CoreML, CloudKit, WidgetKit, ActivityKit, and an outermost App Store Review ring.
Fig. 2 · the concentric framework surface · Apple's platform, drawn
live activities

Ongoing real-time updates on Lock Screen + Dynamic Island. Orders, rides, matches, workouts.

widgets

Home Screen + Today View + StandBy + Lock Screen widgets via WidgetKit and ControlWidget.

app clips

Launch-without-install flows for point-of-sale, parking, menus, one-tap use cases.

healthkit

Read + write health data with user permission. Workouts, heart rate, mindfulness, sleep.

coreml

On-device ML: image classification, text recognition, sound classification, custom models.

storekit 2

In-app purchases and subscriptions. Swift-native API, signed transaction receipts, family sharing.

cloudkit

iCloud-backed sync across user devices. Public and private databases, no server needed.

visionos

Spatial volumes, RealityKit content, Look-to-Dwell. When the brand fits spatial computing.

§ 05 · testing + testflight

XCTest + Swift Testing. TestFlight for real users.

Three layers of testing build confidence. Swift Testing handles unit tests on logic, view models, and async code. XCUITest covers critical user flows. TestFlight distributes to real beta testers (up to 10,000 external users), collects crashes, and gathers feedback per version. Every build runs through CI (Xcode Cloud or GitHub Actions) first.

§ 06 · performance SLA

Launch time and 120 Hz scroll.

We ship with performance budgets. Cold launch under 1.5s on iPhone 12+. 120 FPS scroll on ProMotion. Apps under 35 MB thinned. 99.8%+ crash-free over 30 days. All verified on real hardware, not simulators, because the App Store ranks on real-world signals.

metrictargetnote
cold launch< 1.5siPhone 12 + newer
warm launch< 400msin-process resume
scroll fps120 fpsProMotion-capable devices
binary size< 35 MBthinned IPA
crash-free> 99.8%30-day rolling

Two archetypes. One health, one fintech.

Two industry archetypes based on real patterns we see. The health tracker uses HealthKit, WidgetKit, and Live Activities. The fintech app uses Apple Pay, Secure Enclave, and biometric auth. Both represent the kind of native-depth iOS work we typically ship.

archetype 01 · health tracker

Native iOS with HealthKit + widgets.

Health and fitness tracker with HealthKit integration for workouts, heart rate, sleep. WidgetKit for Home Screen and Lock Screen. Live Activities for in-progress workouts. SwiftUI + Swift 6. 16 weeks.

rating
4.9
App Store
DAU
68K
12mo post
launch
1.2s
cold iPhone 14
archetype 02 · fintech consumer

iOS-first fintech with Live Activities.

Consumer fintech app, iOS launched first. Live Activities for transfers in progress. Apple Pay integration, Sign in with Apple, biometric auth via LocalAuthentication, Secure Enclave. 18 weeks.

rating
4.8
App Store
MAU
210K
year 1
crash-free
99.91%
30d
§ 08 · engagement + fit

Four shapes. Audit names the right one.

We start by scoping the right shape for your app. A 2-week readiness audit. A greenfield SwiftUI build. A UIKit-to-SwiftUI migration. A retainer with senior engineers. The right fit emerges before any contract.

shape 01

Readiness audit.

2 weeks. Platform surface, Swift 6 path, review pre-check. Refundable.

shape 02

iOS MVP.

10-16 weeks. SwiftUI + Swift 6 + store submit.

shape 03

Full build.

14-22 weeks. Live Activities, Widgets, Clips, HealthKit, IAP.

shape 04

Universal + visionOS.

16-26 weeks. iPhone + iPad + visionOS one codebase.

right fit
  • You use 3+ of the five platform rings (SwiftUI, frameworks, custom Swift)
  • Apple-specific affordances matter (Live Activities, Widgets, HealthKit)
  • iOS is the primary platform for year one
  • Premium user feel and App Store polish are differentiators
wrong fit
  • ×Need Android at the same time with shared codebase; see React Native
  • ×Mostly web content wrapped as app; a PWA is cheaper
  • ×No Apple Developer budget; $99/year membership is required

Eight answers.

Questions iOS teams ask before booking: SwiftUI vs UIKit. When to go iOS-first. App Store timelines. App Store Connect ownership. TestFlight scale. And exit terms.

Should we build native iOS or use React Native / Flutter?

Three signals favor native. First, you need Apple-platform features (Live Activities, Widgets, App Clips, HealthKit, CoreML, visionOS) where cross-platform frameworks don't or barely support them. Second, native feel and pixel-perfection matter more than sharing code across platforms. Third, you're iOS-only this year but plan multi-platform later; native buys validation time before cross-platform costs hit. Otherwise, React Native or Flutter with native modules handles 80% of use cases. We build all three. The choice depends on your app, not our preference.

How much does a native iOS app cost in 2026?

Senior iOS engineers run $160 to $220/hour in the US and UK, $100 to $150/hour in India. A Swift 6 MVP with 15 to 25 screens, auth, and push takes 10 to 16 weeks. A full production app with Live Activities, Widgets, Clips, HealthKit, in-app purchases, and CloudKit runs 14 to 22 weeks. An iPhone + iPad + visionOS build from one codebase runs 16 to 26 weeks. A 2-week readiness audit is refundable. Scoped quote in 48 hours.

SwiftUI or UIKit in 2026?

SwiftUI for new builds, always. SwiftUI is production-ready now. It handles navigation, scaled lists, collection layouts, animations, custom shapes, and platform surfaces (Widgets, Live Activities, visionOS) that UIKit doesn't touch. UIKit still wins in a few edge cases: very complex collection views needing fine-grained reuse, legacy UIKit codebases where mixing costs more than it saves, and some framework integrations not yet updated. For new builds: SwiftUI first, UIKit only where proven necessary.

What's required for App Store submission in 2026?

You'll need Apple Developer Program membership ($99/year) under your legal entity. App Store Connect app record. Provisioning profiles and signing certificates (we handle these). App icons in every required size. Screenshots for every device you claim to support (iPhone 15 Pro Max, iPhone SE, iPad Pro 12.9, iPad Pro 11).

App Privacy label, Data Safety disclosure, privacy policy URL, support URL, and a Review contact are required too. First submissions take 1 to 3 days. Rejection rates have climbed since 2024's stricter guidelines. We run a pre-check before submit to catch common failures: account deletion flow, subscription disclosures, privacy manifest.

How do you handle StoreKit 2 and in-app purchases?

StoreKit 2 is the default for any new iOS build. It's Swift-first, async/await-native, and uses JWS-signed receipts verified directly, so no third-party validation service needed. We implement subscriptions, one-time and consumable purchases, intro and promotional offers, and family sharing. Backend validation uses Apple's App Store Server Notifications V2 for real-time events. For brands shipping across platforms (Apple, Google Play, web), we abstract the purchase layer so subscription logic works everywhere.

Do you support visionOS and iPad adaptations?

Yes. For universal apps (iPhone + iPad + visionOS), SwiftUI lets us share most code with platform-specific adaptations via conditional modifiers. iPad gets split view, slide over, sidebar navigation, pointer interactions, and keyboard shortcuts. visionOS adds 3D volumes, spatial audio, and Look-to-Dwell. We scope visionOS as an add-on when your use case fits spatial computing.

How do you handle Swift 6 strict concurrency?

Swift 6 strict concurrency is non-negotiable for new builds. We enable complete concurrency checking from day one, use @Sendable and @MainActor correctly, and design data layers around actors. Async/await is the default for all I/O.

The first two weeks include a concurrency architecture pass where we decide which actors own which state. Teams new to Swift 6 may find this slower at first, but the payoff is zero data races and a codebase that compiles cleanly on every future Swift version.

Who owns the Apple Developer account, signing, and codebase?

You do. Apple Developer Program membership under your legal entity. Signing certificates and provisioning profiles stay in your developer account; we're added team members, removable anytime. GitHub repository under your organization from day one. TestFlight and App Store Connect access under your control. On exit: credentials rotated, repo transferred, CI documented, and 30 days of support. No lock-in.

Start with a readiness audit.

Two weeks of deep review. Platform surface. Swift 6 migration path. App Store guidelines pre-check. Refundable. Quote in 48 hours.

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply