What we do
Tools
Industries
Department
How we workLet's talk →
Home/iOS Developer
iOS Development

Hiring an iOS Developer? Part of Your App Is Already Decided by Apple

Before anyone writes a line of Swift, Apple's App Review Guidelines have settled how the app may take payment, what it must offer at login, and whether it counts as an app at all. Most rejections we're asked to fix trace back to one of those decisions, made late or not at all. Settle them in the quote and the first submission has a far better chance.

Rejections that were baked in before the build started

Each of these is a design choice, not a bug. Fixing it after review means reworking screens that were already paid for.

Google or Facebook login, and nothing else

How you'll know: The sign-in screen offers social logins only, and review comes back citing guideline 4.8.

Fix: When a third-party login sets up the main account, Apple asks for an equivalent option that collects only name and email and lets people hide their email. Sign in with Apple meets that. Plan the button and the account matching behind it from the start.

People can sign up, but not delete their account

How you'll know: Account deletion is handled by emailing support, or by a link to the website.

Fix: Guideline 5.1.1(v) asks apps that create accounts to offer deletion inside the app. That's a backend job as much as a screen: what happens to the customer's orders, invoices and records in your other systems when they go.

The app is your website in a frame

How you'll know: A web view wraps the existing site, and review cites minimum functionality (4.2).

Fix: Apple wants features that go beyond a repackaged website. Give the app real jobs the site can't do as well: saved details, notifications, the camera, working offline. If none of those matter to your customers, a mobile-friendly web app may be the better buy.

Features unlocked by a code or a web purchase

How you'll know: Customers buy a plan on your website, then type a license key in the app to unlock it.

Fix: Guideline 3.1.1 rules out unlocking digital features with your own keys or codes. Which route is allowed depends on what you sell, so decide it with the table below before the paywall is designed.

The reviewer can't get past the login

How you'll know: Rejected under 2.1 because there was no demo account, or the test server was switched off.

Fix: Give App Review a working demo login with realistic data, and keep the backend running for the whole review window. Apps that only work against your live CRM or booking system need a safe test copy for this.

What the app sells decides how it may charge

This is the decision quotes most often skip. It changes the checkout, your margins and how the app talks to your billing system.

What people pay for How the app takes the money Worth knowing
Physical goods or real-world services (deliveries, appointments, repairs, tickets) Your own payment: card entry or Apple Pay through your processor Apple's guideline 3.1.3(e) says these must not go through in-app purchase, so no Apple commission. The work is connecting the payment to your order, booking or invoicing system.
Digital features or content used in the app (premium tiers, courses, subscriptions) Apple's in-app purchase Apple takes a commission. The Small Business Program cuts it to 15% for developers with up to $1 million in proceeds in the prior year. On the US storefront the app may now also link to buying on your website; in most other countries it still can't.
An app your company sells to other organizations for their staff Billing outside the app, under your contract with the customer Guideline 3.1.3(c) allows this when the app is sold directly to organizations, not to the public. If individuals can also sign up and pay, the in-app purchase rules come back.
Nothing is sold: an app for your own staff or existing customers No payment flow, and maybe no public listing A staff-only app can be published as a custom app through Apple Business Manager instead of the public App Store. Customers who log in with an account they already pay for elsewhere need the multiplatform rules in 3.1.3 checked line by line.
Let's talk

An iPhone app planned around App Review, not surprised by it

n-frames builds iOS apps for businesses whose app has to talk to a booking, billing or inventory system. The quote names the payment route Apple allows for what you sell, the login and account-deletion flow, and the demo setup review will need, before the first screen is designed.

Start my iOS app plan →

Questions people ask

Who owns the Apple Developer account if we hire an agency?

Your business. Enroll as an organization, which needs your company's D-U-N-S number, and add us as team members. Then the app, its listing and its reviews stay with you whoever builds the next version.

What happens when Apple rejects an update?

Apple cites the guideline it thinks the build breaks. We read the note, decide whether a change or a reply in App Store Connect is the right response, then fix and resubmit. A rejection can land on an update even when the earlier version passed, because each build is reviewed on its own.

Do you build Android too, or iOS only?

Both. If the app is mostly screens over your business data, one Flutter or React Native codebase can cover the iPhone and Android. If it leans on Apple-only features such as widgets, HealthKit or deep camera work, native Swift is usually worth it, with a separate Android build.

What exactly does the free quote cover for an iOS project?

What the app does and who it's for, which payment route applies, how people log in and delete their account, which of your systems it reads and writes, and how review will test it. Each is priced as its own line, plus a note on who holds the Apple Developer account.

Will the app keep passing review after each new iOS release?

Not on its own. Apple ships a major iOS release every year, and each one can retire APIs the app relies on, change how permissions behave or come with new review requirements. A build that passed last year is reviewed against today's rules when you send the next update. Testing against Apple's betas over the summer is how the app stays ready when the release lands, so the next update isn't held up.

How do we test the app before it goes public?

Through TestFlight. Your staff or a group of customers install test builds from an invite, and each build can be tested for up to 90 days. Builds for testers outside your team go through a lighter review first, so it's also an early warning for App Review problems.

What does someone need to start learning iOS development?

A Mac, because Xcode only runs on macOS. Then Swift and SwiftUI, and one small app taken all the way through TestFlight and App Review. Reading the App Review Guidelines once, end to end, saves a lot of rework later.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.