How to ship to App Store as a solo founder

Shipping to the App Store as a solo founder takes about two weeks of calendar time and $99 if you already have a working iOS build. The hard parts are not Apple's paperwork. They are the App Privacy manifest, the signing setup, and avoiding the four rejection patterns that account for most first-time bounces in 2026.

The mechanical sequence is well documented. What no one writes for solo founders is which steps you do at the kitchen table in an evening, and which steps need real iOS engineering attention. This is that playbook.

What "shipping solo" actually means in 2026

Solo means one person owns the spec, the storefront, and the call on what ships. It does not mean one person types every Swift file. Plenty of solo-founder apps in 2026 are built by the founder in Cursor or Claude Code, with a contractor wiring up the IAP and signing for the last 10% AI tools still get wrong.

Apple does not care whether you are one person or fifty. The advantage of being solo is decision speed. The disadvantage is that boring infrastructure (signing, privacy, IAP) sits on your plate too.

A realistic timeline once you have a working build:

Week 1: enroll in Apple Developer Program, set up App Store Connect, write the first cut of App Privacy declarations.
Week 2: configure Xcode signing, push to TestFlight internal beta.
Week 3: external TestFlight (24-48hr beta review), fix what real users break.
Week 4: submit for review. Sit through the 24-48hr median wait.

That is the floor. If you have not picked an entity, written privacy declarations before, or set up code signing, add a week.

LLC or sole-prop: the boring decision that matters later

Apple lets you enroll as an individual or as an organization. Both work. The choice has nothing to do with App Store mechanics and everything to do with what happens when something goes wrong.

Sole proprietor: enroll in your personal name, $99/year, set up in a day, but you are personally on the hook for refund disputes, IAP chargebacks, DMCA takedowns, and privacy lawsuits.

LLC (single-member, US example): file with your state ($50-500 plus registered agent), get an EIN (free, 10 minutes), get a D-U-N-S number for Apple's org enrollment (free, 5-30 days). Setup is 1-2 weeks. Liability is capped at the LLC's assets if you maintain the corporate veil.

If you are testing an idea and have not validated it, ship as a sole prop. Form the LLC when revenue, liability, or a co-founder makes it real. The transfer flow exists in App Store Connect, but it is friction. Most solo founders pick wrong by forming the LLC first and then never shipping.

The Apple Developer Program enrollment

Once the entity decision is behind you, enrollment is a 30-minute task you can do tonight. Apple ID with two-factor on, visit developer.apple.com/programs, pick Individual or Organization, pay the $99 USD annual fee. Individual enrollments are usually instant. Org enrollments take 24-72 hours while Apple verifies the D-U-N-S record.

After approval, head to App Store Connect (separate URL, same Apple ID) and accept the Paid Apps and Free Apps agreements. You cannot submit anything for review until those agreements are accepted and your tax forms (W-9 in the US, W-8BEN elsewhere) plus banking info are filled in. Most first-time founders forget this and discover it on submission day.

App Store Connect setup

App Store Connect is the storefront control panel. Set up the app record before you have a final build; metadata work runs in parallel with engineering.

Create the app record with a unique bundle ID matching your Xcode project, the app name (30 chars max), primary language, SKU, default territory, and pricing tier. Then fill in the App Information panel: subtitle (30 chars), category, age rating questionnaire, and a public privacy policy URL.

Then the part most founders underestimate: the App Privacy declarations. Apple requires you to declare what data your app and your SDKs collect across roughly 14 data categories (contact info, health, financial, location, user content, usage data, diagnostics, etc), the purpose for each, and whether the data is linked to user identity.

This is a legal artifact, not a checkbox. If your declarations do not match what your app actually does (and what Firebase, RevenueCat, Mixpanel, Sentry actually do), Apple's automated and manual review will catch the mismatch and reject under Guideline 5.1.1. The fix is tedious: read each SDK's privacy manifest and reconcile it against your declared use. For a solo founder who does not write iOS day-to-day, this is the most common place to either burn three days or to bring in someone who has done it before.

One late-stage trap: if you offer any third-party login (Google, Facebook, GitHub), you must also offer Sign in with Apple. Email/password only is fine; the rule kicks in the moment you add a "Continue with Google" button.

Xcode signing and provisioning without losing a weekend

Code signing is where solo founders quietly lose a weekend. The mental model:

An App ID is the bundle identifier registered with Apple.
A distribution certificate is your team's identity for App Store builds (one per team, 1-year validity).
A provisioning profile binds the App ID, the certificate, and the device list.

Modern Xcode handles most of this with "Automatically manage signing" if you sign in with your Apple ID and pick your team. For a solo founder shipping one app, automatic signing is fine. The errors you will see (and the fixes):

"Bundle identifier not available" → another developer registered it. Pick a unique one.
"No matching provisioning profile" → wrong team selected, or distribution certificate expired.
"Failed to register bundle identifier" → your Apple Developer Program agreement is not accepted yet.

If you ship multiple targets or collaborate with anyone, switch to Fastlane match. For a solo single-binary ship, automatic wins.

TestFlight: the internal-then-external loop

TestFlight is a free Apple service for distributing pre-release builds. It has two tiers and you should use both.

Tier	Limit	Apple review needed	Best for
Internal testing	100 testers (must be on your team)	No	Daily smoke-testing every build
External testing	10,000 testers (public link or invite)	Yes, 24-48hr beta review (first build only)	Real beta, stakeholder demos, paid users

Solo founder workflow: push every build to internal testing daily; promote stable builds to one external group (Apple beta-reviews the first build, subsequent ones in the same group typically skip review); send a public TestFlight link to design partners and investors. TestFlight builds expire 90 days after upload.

The hidden value: a TestFlight link is a stakeholder demo without an App Store review wait. If Apple's queue is spiking and you cannot get v1 approved in time for a partner meeting, TestFlight solves it.

Screenshots and ASO basics that move conversion

Screenshots and metadata drive install conversion more than rating count or description. Solo founders ship terrible screenshots because they treat them as a chore. They are the ad.

Required assets: 6.7-inch iPhone screenshots (up to 10), 6.5-inch (Apple auto-generates from 6.7 if you skip), iPad sizes if universal, and a 1024x1024 app icon (no transparency, no rounded corners).

Conversion rules that hold across categories:

Screenshot 1 carries roughly 80% of the install decision. Communicate the core value prop in a glance.
Use 3-5 screenshots, not 10. Most users swipe twice.
Caption with the value, not the feature ("Plan your week in 3 taps", not "Calendar view").
Title (30 chars) is your primary keyword field. Subtitle (30 chars) is the second. Promotional text (170 chars) updates without re-review.

If you have never designed App Store screenshots, hire a Fiverr designer for the asset pass. (For broader thinking on what to keep in-house versus book out, founder mode for technical product oversight walks through the decision frame.)

Submitting for review and the 2026 wait

Submission is mostly a button click. Upload your archive from Xcode (or via Transporter), wait for it to "process" in App Store Connect (10-30 minutes), attach it to the version record, click Submit for Review.

You will be asked for: a demo account if your app has a login wall (skipping this is the fastest path to rejection); reviewer notes (use them, link to a screen recording of the happy path); export compliance (most apps: no encryption beyond standard HTTPS); IDFA / advertising identifier declaration if you use AppTrackingTransparency.

Then you wait. The 2026 baseline:

Median first-review time is 24-48 hours.
Queue spikes happen multiple times a year. In March 2026, waits stretched to 7-30+ days for some apps. Beta-review queues spike with them.
"Waiting for review" is the queue. "In review" is a human reviewer actively looking. Most of your wait is the first state.

Coping strategy: do not promise a launch date until your first version is approved. Use TestFlight for any demo that needs to happen before then.

Common 2026 rejections and how to dodge each one

Most first-ship rejections cluster in four guidelines. Knowing them in advance saves a re-submit cycle (another 24-48hr at minimum).

Guideline 4.0 (Minimum Functionality). Apple rejects apps that are essentially a website in a wrapper. If your app is a thin Capacitor or WebView shell, expect a 4.0 rejection unless you add real native functionality (push notifications, offline mode, iOS API integration).

Guideline 5.1.1 (Data Collection and Storage). Your App Privacy declarations must match the data your app and SDKs actually collect. Apple's tooling reads SDK privacy manifests and compares them to your declarations. Mismatch equals rejection.

Guideline 4.3 (Spam / Clone Apps). Apple rejects duplicates and template-mass-produced apps, plus entries in saturated categories (fortune-telling, basic flashlights, generic dating clones) without unique value. If your app sounds like 50 others, lead with differentiated functionality in the screenshots.

Guideline 2.1 (App Completeness). Placeholder content, broken links, crashes on launch, missing demo credentials, "coming soon" features. Test on a real device, not just the simulator.

In-app purchases get their own review track. If your app sells digital goods (subscriptions, unlocks, currency), you must use Apple's IAP under Guideline 3.1.1. Routing payments through Stripe for digital goods is an instant rejection. Physical goods and real-world services are exempt; Stripe is fine for those.

When to do it yourself, when to book it out

The honest split for a solo founder who is not an iOS engineer day to day:

Path	Cost (first ship)	Time to App Store	When it wins	When it fails
DIY (you ship everything)	$99 Apple + your time	3-6 weeks	You want to learn the platform; revenue is far away	You burn nights on signing instead of talking to users
Hire an iOS freelancer (Upwork)	$2k-8k	4-8 weeks	Scope is tiny and well-defined	Sourcing and vetting are unpaid time you do not have
Book a senior on Cadence	$1,500/week, 48hr free trial	2-3 weeks of senior time	You want a vetted iOS engineer this week, not in 8 weeks	Scope is so small a freelancer is genuinely cheaper
Full-time iOS hire	$140k+/yr loaded	60-90 day hiring loop	You have a sustained iOS roadmap	You ship one app and need iteration help, not a salary

For most solo founders shipping their first iOS app in 2026:

You handle: entity choice, Apple Developer Program enrollment, App Store Connect setup, screenshots and ASO, demo account, reviewer notes.
You book out (or pair with someone who has done it): Xcode signing if new to it, the App Privacy manifest reconciliation, IAP wiring if you sell digital goods, the first TestFlight cycle.

Cadence is one option for the booking-out side. Every engineer on Cadence is AI-native by default (Cursor, Claude Code, Copilot fluency vetted in a voice interview before bookings unlock), matched against your spec in 2 minutes, with weekly billing and a 48-hour free trial. A senior at $1,500/week can typically own the iOS shipping chunk (signing, privacy, IAP, TestFlight) in 2-3 weeks. For a smaller scope, an Upwork freelancer is genuinely cheaper.

If you want a second opinion on whether to ship the iOS chunk yourself, the same logic that applies to building an MVP in 2 weeks with AI tools applies here on a per-feature basis.

Steps

Pick your entity. Sole prop for v1 unless you have a real liability reason to form the LLC now.
Enroll in the Apple Developer Program. $99/year. Individual is usually instant; org with D-U-N-S takes 24-72 hours.
Configure Xcode signing. Use automatic signing for a solo single-target app. Confirm bundle ID is unique and distribution certificate is valid.
Push your first build to TestFlight internal testing. Catch crashes on real devices before any external user sees the app.
Open external TestFlight to 5-20 design partners. Apple beta-reviews the first build (24-48hr); subsequent builds skip review.
Build out App Store Connect: screenshots (6.7-inch + 6.5-inch), title, subtitle, description, keywords, age rating, privacy policy URL.
Fill in App Privacy declarations. Match your declared data collection to every SDK's privacy manifest. This is the single highest-rejection-risk step.
Add demo account credentials and reviewer notes. Skipping this is a near-guaranteed Guideline 2.1 rejection.
Submit for review. Median wait in 2026 is 24-48 hours; queue spikes can stretch to a week or more.
On approval, schedule the release (manual or automatic). On rejection, read the Resolution Center note carefully, fix the cited guideline, and resubmit. There is no penalty for resubmits.

Founder mistakes that burn the most time

Building everything in Swift before validating the product. AI tools and React Native ship a v1 in days; native rewrites come after revenue.
Skipping TestFlight and going straight to App Store review. Same bugs, with a 48-hour penalty per cycle.
Treating App Privacy as a checkbox. The 5.1.1 rejection rate is high because most founders do not read SDK manifests.
Forming the LLC before the app ships. The entity does not protect a product that does not exist.
Underspending on screenshots. Conversion swings 2-3x on screenshot 1 alone.

If you are deciding whether to write the code yourself or hire your first technical helper as a non-technical founder, the iOS shipping chunk is a clean test case: bounded (2-4 weeks), clear deliverable, and the cost of a wrong hire is one bad TestFlight cycle, not a quarter of equity.

If the iOS shipping chunk is the thing standing between you and the App Store, book your first engineer on Cadence. Vetted iOS senior, weekly billing, 48-hour free trial. Replace the engineer any week with no notice.

FAQ

Do I need an LLC to publish on the App Store?

No. Apple lets you enroll as an individual. Most solo founders ship the first version as a sole proprietor and form an LLC later when revenue or liability merits it. Apple supports moving an app between teams later, so you are not locked in.

How long does App Store review take in 2026?

Median is 24-48 hours. Queue spikes have pushed waits to 7-30 days at points in 2026, so build a TestFlight buffer for any stakeholder demo with a fixed date. Beta review (the first external TestFlight build) is on the same queue and spikes with it.

Do I have to add Sign in with Apple?

Only if you offer any third-party login option (Google, Facebook, GitHub, etc). If your app uses email/password only, or only Sign in with Apple, you do not need to add anything else. The rule kicks in the moment you add a "Continue with Google" button.

What gets first-ship apps rejected the most?

Guideline 4.0 (minimum functionality, especially website wrappers), 5.1.1 (App Privacy declarations not matching actual SDK behavior), 4.3 (spam or clone apps in saturated categories), and 2.1 (broken builds, missing demo credentials, placeholder content). Read the Resolution Center note carefully; the cited guideline tells you exactly what to fix.

Can I ship to the App Store without writing Swift?

Yes. React Native, Flutter, Capacitor, and Expo all ship binaries that pass Apple review. Apple reviews the binary, not the source. The bottleneck for solo founders is rarely the language; it is the signing, IAP, and privacy work that surrounds it. Knowing what questions to ask a developer before hiring them matters more than which framework you pick.

All posts