Mobile apps

Swift and SwiftUI for Business Apps: What iOS Development Involves

Swift and SwiftUI for Business Apps: What iOS Development Involves: MeraSEO article cover
Key takeaways
  • New iOS apps should be written in Swift. Objective-C is mainly relevant for maintaining older apps, and the two languages can live in one project.
  • SwiftUI is the default for new screens; UIKit still matters for older apps, minimum iOS versions and some advanced controls. Many real apps use both.
  • Budget time for the Apple Developer Program, App Store review, TestFlight testing and yearly updates after each new iOS release, not just for writing code.
  • Most rejections come from avoidable things: missing privacy details, broken demo logins, and digital purchases that skip Apple’s payment system.

If you are commissioning an iPhone app, the phrases “built in Swift”, “SwiftUI” and “submitted to the App Store” show up in every proposal, usually without explanation. This post explains what they mean, which choices are yours to make, and what work continues after launch.

It is written for business owners and product managers, not for developers. You should finish it able to question a vendor’s plan and spot gaps in it.

Swift and Objective-C: which one for your project

Apple introduced Swift in 2014 as the modern language for its platforms. Objective-C, the older language, is still in use inside apps that have been maintained for years. For you, the decision is mostly about whether your app is new or existing.

SituationWhat to do
New appWrite it in Swift. Apple’s newer frameworks and documentation are written around it.
Existing Objective-C app that worksKeep the stable parts. Write new features in Swift and migrate old files only when you are already changing them.
Existing app with many crashes or no one who knows the codeGet a code audit first. A rewrite may be justified, but it should be a decision based on evidence.
App relies on a large C or C++ libraryAsk the developer how it will be bridged. Swift can call C code, and C++ interoperability has improved, but it needs experience.

Swift can call Objective-C code and the reverse, so a mixed project is normal. A full rewrite of a working app delays features and adds new bugs, so avoid it unless there is a clear reason such as a dependency that can no longer be updated.

SwiftUI or UIKit

These are the two ways to build screens. UIKit is the older, mature toolkit. SwiftUI, introduced in 2019, describes screens in a shorter, declarative style, and Apple’s newer interface features are added there first. Some features need it outright: home screen widgets and Live Activities on the lock screen are built with SwiftUI even inside a UIKit app.

How to choose

  • New app with a recent minimum iOS version: SwiftUI for most screens.
  • Supporting old iOS versions: SwiftUI features depend on the iOS version, so the older you go, the more UIKit you will need.
  • Heavily customized screens or complex collection layouts: UIKit, or SwiftUI wrapping UIKit components. Mixing them is a supported approach.
  • Existing UIKit app: add SwiftUI screen by screen. There is no need to convert everything.

Ask your vendor which minimum iOS version they propose and why. Setting it lower than needed makes the code more complicated, and setting it too high excludes users with older phones. Check your own audience before you decide.

What you need before the first build

Apple Developer Program account

To publish, you need a paid membership in the Apple Developer Program. Enroll as an organization, using your company name and a D-U-N-S number, so the app appears under your business and not under a freelancer’s personal name. Check the official program page for the current fee and eligibility. Make sure the account is owned by your company, not your vendor.

Accounts, certificates and keys

The app is signed with certificates and identifiers tied to your account. Push notifications need their own key. Keep these on your side. If a vendor holds the only copy, moving to another team later becomes painful.

Testing with TestFlight

TestFlight is Apple’s tool for distributing pre-release builds. Builds are uploaded from Xcode, processed by Apple, and then installed through the TestFlight app by your team or invited testers. Two details catch people out: each build expires 90 days after upload, and the first build you send to external testers (people outside your App Store Connect team) goes through a short Beta App Review before they can install it.

A sensible beta routine:

  1. Internal round: your team and the vendor install each build and run through a written checklist.
  2. External round: 10 to 20 real users, such as friendly customers or staff, on different iPhone models and iOS versions.
  3. Collect crashes and feedback in TestFlight and fix the blockers.
  4. Freeze the build, then submit that exact build for review.

Test on at least one small-screen iPhone and one older iOS version you claim to support. Many layout bugs only appear there.

App Store review: what usually causes rejection

Every submission is checked against the App Store Review Guidelines. Read them once, as they are short enough to skim. These are the common stumbling blocks.

  • Login the reviewer cannot use: if your app needs an account, provide a working demo account in the review notes. This one mistake costs days.
  • Privacy details: you must declare what data the app collects, and you need a privacy policy link. The declaration has to match what your SDKs do, including analytics and ad tools. Apple also expects privacy manifests from commonly used third-party SDKs, so ask your developer to confirm each SDK version ships one.
  • Permission prompts without a reason: the text for camera, location or contacts access must say why you need it, and the app must still work sensibly if the user says no.
  • Digital purchases: content, subscriptions or features sold inside the app generally must use Apple’s in-app purchase. Physical goods and real-world services, like food delivery or a cab, can use gateways such as Razorpay.
  • Account deletion: if users can create an account in the app, they must be able to start deletion from inside the app.
  • A thin web wrapper: an app that is only a website in a frame risks rejection for minimum functionality.
  • Crashes and placeholder text: reviewers do try the app, so test the build you submit.

Plan on the first submission taking a few days, and leave buffer in the launch date for one rejection and resubmission. Passing review only gets the app listed; whether people find it depends on the title, screenshots and ratings, which our guide to app MVP planning and App Store Optimization covers.

After launch: maintenance is part of the job

Apple releases a major iOS version every year, usually previewed at Apple’s developer conference in June and released around September. Each release can change behavior: permission dialogs, background limits, interface details. Apps that are not updated gradually develop odd bugs, and Apple periodically raises the minimum Xcode and iOS SDK version required for new uploads, so an app left untouched for a couple of years may need tooling work before even a small fix can ship.

A yearly routine should include:

  • Building and testing against the new iOS beta between June and September.
  • Shipping a compatibility update when the new version is released.
  • Updating third-party SDKs and removing unused ones.
  • Watching crash reports and reviews monthly.

Our iOS app maintenance and support page describes how we handle this, and it is worth agreeing the scope before launch rather than after the first crash.

Questions to ask an iOS vendor

  1. Will the app be written in Swift, and which screens use SwiftUI?
  2. What minimum iOS version do you propose, and why?
  3. Whose name will the Apple Developer account and the source repository be in?
  4. How will you run beta testing, and on which devices?
  5. What happens when Apple releases a new iOS version?

If you are still deciding between native and a shared codebase, our guide to native, cross-platform or PWA helps you decide. Our iPhone app development page lists what we build for iPhone.

Frequently asked questions

Is Swift better than Objective-C for iOS development?

For new apps, yes. Swift is Apple’s current language, it catches many mistakes at compile time, and new frameworks target it first. Objective-C still runs in many older apps and can coexist with Swift, so you rarely need to rewrite a working app just to change language.

Should a new iOS app use SwiftUI or UIKit?

SwiftUI is the usual choice for new screens, provided your minimum iOS version supports the features you need. UIKit remains valuable for older iOS versions and highly customized interfaces. Many production apps mix both, which is a supported and common setup.

How long does App Store review take?

Many submissions are reviewed within a day or two, but timing varies and rejections add rounds. Do not tie a marketing launch to the first day you submit. Leave a buffer of at least a week, and choose manual release in App Store Connect so the app goes live when you are ready.

Do I need TestFlight before launching?

It is not mandatory, but skipping it is risky. TestFlight lets real people run the exact build you will submit, on their own iPhones, before the public sees it. It is the cheapest way to find device-specific crashes and confusing flows.

Planning an iPhone app?

Tell us what the app needs to do. We will outline the Swift and SwiftUI approach, the App Store steps and the maintenance plan.

Talk to our iOS team →

Related Post

Call Now Button