Question 1

SwiftUI or UIKit for a new iOS app, which should we use?

Accepted Answer

SwiftUI is the default for new iOS apps now. The framework has matured through several iOS versions, ships with everything most apps need (lists, navigation, animation, gestures, charts, maps), and pairs naturally with Swift concurrency and the Observation framework. UIKit remains the right answer for apps targeting iOS versions older than iOS 16, for the few cases where SwiftUI does not yet expose the specific UI control you need, or for apps integrating heavily with a legacy UIKit codebase. Most production apps now mix both, with SwiftUI driving new screens and UIKit handling the small set of cases where it still wins.

Question 2

What gets iOS apps rejected from the App Store, and how do you prevent it?

Accepted Answer

The top rejection categories are unclear sign-in or account flows, in-app purchases routed through non-Apple payment systems where prohibited, missing privacy descriptions in Info.plist, and crashes that Apple reviewers hit on launch or in core flows. We design sign-in, payment, and privacy strings against the current App Store Review Guidelines before code is written, test on the latest iOS beta on real devices before submission, and include a short reviewer note for any feature that needs context. First-submission approval is the rule for the apps we ship, not the exception.

Question 3

What can we actually build with Apple's on-device ML stack (Core ML, Apple Intelligence)?

Accepted Answer

Three classes of features. On-device inference for vision, language, and audio models that need to run without sending data off the phone, using Core ML to convert a model trained in PyTorch or TensorFlow and run it on the Neural Engine. Apple Intelligence integrations through the App Intents framework, which surface your app actions to Siri, Spotlight, and the system-wide writing tools. Custom Foundation Model usage on newer devices for tasks like summarization and classification that previously needed a cloud round-trip. Performance is excellent on devices with the Neural Engine, and the privacy story (nothing leaves the device) is a meaningful sales point in regulated industries.

Question 4

How do you handle apps that need to work across iPhone, iPad, Apple Watch, and Mac?

Accepted Answer

We pick the right tool per device class. SwiftUI shares 80 percent or more of the UI code across iPhone, iPad, Mac (via Mac Catalyst or native macOS), and Apple Watch, with size-class-adaptive layouts that adjust without forking. Apple Watch usually needs a dedicated watchOS app for anything beyond basic notifications, since the platform constraints are different enough to justify it. For genuinely cross-platform business logic we share a Swift package across every target, which keeps networking, models, and core services in one place while letting each platform present them natively.

Question 5

What's the situation with App Store fees and alternative app stores after the DMA?

Accepted Answer

The default flow remains the same: App Store distribution, 15 percent commission on year-one subscriptions and small-business revenue, 30 percent above that and on first-year non-subscription IAP. In the EU under the Digital Markets Act, developers can now distribute through alternative app marketplaces and use third-party payment processors, with different fee structures that can be cheaper at scale but add operational overhead. For most apps the App Store remains the right channel, but the choice now genuinely depends on business model and geography. We review the trade-offs against your distribution strategy during scoping.

iOS

iOS Capabilities

Swift and SwiftUI

ARKit and RealityKit

Core ML and Vision Framework

Apple Secure Enclave

HealthKit and HealthKitUI

Widgets, Extensions and App Clips

Your Native iOS Questions, Answered.

When does native iOS development fit better than cross-platform alternatives?

What We Ship With iOS

HealthKit and HIPAA iOS Apps

iOS Banking and Investment Apps

AR Commerce and Shopping Apps

iPad Enterprise and Field Apps

What You Get From Us

App Store Submission and Review

SwiftUI Design System

TestFlight Beta Program

Instruments Performance Audit

iOS Strengths

Tools & Libraries We Use

Why Teams Choose Software Pro for iOS

iOS Development FAQs

Ready to Build Your iOS App?