How to Make an iPhone App: Design, Build, Ship
How to make an iPhone app step by step: scope it, design iOS screens to Apple's rules, pick SwiftUI or cross-platform, test in TestFlight and pass App Review.

This guide is for founders, indie hackers and PMs who want to get an app onto iPhones without guessing at the order of operations. You will get the full path, from a one-page scope to an approved App Store listing, with the Apple-specific rules that trip up first-timers and the decisions you need to make at each step.
TL;DR: Scope one core job, design your screens to Apple's Human Interface Guidelines, then build in SwiftUI (or a cross-platform framework if you also need Android). Join the Apple Developer Program, test with TestFlight, prepare your listing assets and privacy answers, and submit for App Review. Most rejections come from crashes, missing account deletion, vague privacy disclosures and placeholder content.
What you need before you start
Making an iPhone app has a few hard requirements that are worth knowing on day one, because they affect budget and timeline.
| Requirement | Why it matters | Notes |
|---|---|---|
| A Mac | Xcode, Apple's build tool, only runs on macOS | Any recent Apple-silicon Mac is enough for most apps |
| Xcode | Compiles, signs and uploads your app | Free from the Mac App Store |
| Apple Developer Program membership | Required to distribute on the App Store and TestFlight | 99 USD per year for individuals and organizations; organizations need a D-U-N-S number |
| A real iPhone | Simulators miss performance, camera, push and haptics issues | Use the oldest device you plan to support |
| A privacy policy URL | Required for every App Store listing | Must describe what data you collect and why |
With a cross-platform tool such as React Native (with Expo) or Flutter, you can develop on Windows or Linux and use cloud builds to compile the iOS binary. You still need the developer account and a real iPhone.
Step 1: Define the one job your app does
Most first apps fail from scope, not code. Write one sentence: "This app helps [who] do [what] so that [outcome]." Then list the smallest set of screens that delivers that outcome once, end to end.
For a habit app, that might be: onboarding, create habit, today list, check-in, and a simple history view. Everything else, from social sharing to widgets, goes on a "later" list. If you have not tested demand yet, do that first; the process is covered in our guide to MVP app design.
Scope check: can a new user reach the core moment in under a minute, before creating an account?
Step 2: Map the flow before drawing screens
Sketch how a user moves through the app: entry, key decisions, success and error states. A flow diagram catches missing screens (password reset, empty lists, permission denied) before development. Our user flow diagram guide has templates you can copy.
Decide your navigation model now:
- •Tab bar for apps with 3 to 5 top-level sections that people switch between (Spotify, Instagram).
- •Single stack with a home screen for focused tools with one main task (a calculator, a timer).
- •Sheets and modals for self-contained tasks like composing, filtering or checkout.
Step 3: Design iPhone screens that feel native
iPhone users notice when an app ignores platform conventions. These specifics matter most.
Core iOS layout specs
| Element | Spec |
|---|---|
| Minimum tap target | 44 × 44 pt (Apple HIG) |
| Default body text | 17 pt SF Pro, supports Dynamic Type |
| Large navigation title | 34 pt bold |
| Standard navigation bar height | 44 pt, plus status bar |
| Tab bar | 49 pt, plus the home indicator inset on Face ID iPhones |
| Side margins | 16 pt is the common default; 20 pt on larger layouts |
| Safe areas | Keep content clear of the Dynamic Island, status bar and home indicator |
Design at a common base size such as 393 × 852 pt (iPhone 15 and 16 class), then check a small screen like the iPhone SE (375 × 667 pt) and a large Pro Max. Our device size reference lists current iPhone dimensions, and the notch and safe area simulator shows where the Dynamic Island will cut into your layout.
Patterns to follow
- •Use system components where possible. Navigation bars, tab bars, sheets, context menus, swipe actions and the share sheet are familiar and come with accessibility built in.
- •Support Dynamic Type. Test at the largest accessibility text sizes; layouts should reflow, not truncate.
- •Support dark mode. Use semantic colors rather than hard-coded hex values so both appearances work.
- •Respect the back-swipe. Do not block the edge swipe gesture with custom horizontal carousels near the left edge.
- •Ask for permissions in context. Request camera access when the user taps "Scan," not on first launch, and explain why in your own screen first.
For a full rundown of Apple's design rules, see our iOS typography guide and the mobile spacing system post. If you do not have a designer, you can generate a first draft of these iPhone screens in floow from a plain-English description and adjust them through chat before anyone writes code.
Step 4: Choose how to build it
There are four realistic routes. Pick based on whether you need Android, what skills you have and how native the app must feel.
| Approach | Best for | Trade-offs |
|---|---|---|
| Swift + SwiftUI | iPhone-first apps, deep iOS features (widgets, Live Activities, HealthKit) | iOS only; Android needs a separate build |
| React Native (often with Expo) | Teams with JavaScript/React skills who need iOS and Android | Some native modules need extra work; very custom animations can take effort |
| Flutter | One codebase for iOS and Android with consistent custom UI | Widgets mimic native controls rather than using them directly |
| No-code builders | Simple data-driven apps, internal tools, prototypes | Platform limits, vendor lock-in, harder to scale or customize |
For iPhone-first apps, SwiftUI is the most direct path, and Apple's free tutorials walk through a complete app. For iPhone and Android in one go, React Native or Flutter usually costs less. Our broader guide on how to build a mobile app compares these in more depth, and how to make an app without coding covers the no-code route.
Step 5: Set up your developer account and app record
- •Enroll in the Apple Developer Program. Enroll as an organization to show your company as the seller; verification takes longer.
- •Create a bundle identifier in Xcode, for example
com.yourcompany.habits. You cannot change it after release. - •Create the app record in App Store Connect with the same bundle ID, the app name and primary language. App names are unique across the store, so check availability early. Our app name generator helps if your first choice is taken.
- •Let Xcode manage signing so certificates and provisioning profiles are handled for you.
Step 6: Test on devices, then with TestFlight
Run the app on your own iPhone, then upload a build and use TestFlight:
- •Internal testers are members of your App Store Connect team and can test builds right away.
- •External testers can be invited by email or public link, up to 10,000 people, after a lighter beta review by Apple.
What to test before submission:
- •Fresh install, and a returning user with lots of data.
- •Every permission denied, then granted later in Settings.
- •Airplane mode, largest Dynamic Type size and dark mode.
- •Sign-up, sign-in, password reset and account deletion.
- •In-app purchase sandbox flows, including restore purchases.
Step 7: Prepare the App Store listing
You need:
- •App name (up to 30 characters) and subtitle (up to 30 characters).
- •Keywords field (100 characters, comma-separated, not visible to users).
- •Description and promotional text.
- •Screenshots for the required iPhone display size (currently the 6.9-inch size, with smaller sizes scaled from it), plus iPad if your app runs on iPad.
- •App icon at 1024 × 1024 px, no transparency.
- •Privacy "nutrition label" answers describing every data type you and your SDKs collect.
- •Age rating questionnaire, support URL and privacy policy URL.
Use the App Store screenshot sizes reference to get dimensions right and the iOS app icon sizes table for every icon export. For icon design itself, read our app icon design guide.
Step 8: Submit and pass App Review
Select your build in App Store Connect, answer the export compliance question (apps using only standard HTTPS usually qualify for the exemption) and submit. Apple says most submissions are reviewed within a day or two.
Pre-submission checklist
- • No crashes on launch or in core flows on the oldest supported iPhone
- • No placeholder text, "lorem ipsum," test data or broken links
- • Demo account credentials supplied in review notes if login is required
- • Account deletion available in the app if users can create an account
- • Sign in with Apple offered if you offer other third-party social logins (check current guideline 4.8 for exceptions)
- • Digital goods and subscriptions sold through in-app purchase where the guidelines require it
- • Privacy label matches what the app and its SDKs actually collect
- • Purpose strings explain every permission in plain language
- • Screenshots show the real app, not just marketing art
- • The app does something meaningful beyond a wrapped website
If rejected, the message cites the exact guideline. Fix it, reply with what changed and resubmit; rejections are routine.
Step 9: Launch and iterate
After approval you can release immediately, schedule a date or use phased release for updates. Add analytics and crash reporting before launch, watch where new users drop off, ship small fixes quickly and reply to reviews in App Store Connect.
FAQ
Can I make an iPhone app without a Mac?
You can design and write code on any computer if you use a cross-platform framework like React Native or Flutter, and cloud build services can compile and upload the iOS binary. For native Swift development you need a Mac, because Xcode only runs on macOS.
How much does it cost to put an app on the App Store?
The Apple Developer Program costs 99 USD per year, which covers TestFlight and App Store distribution. Apple also takes a commission on paid apps and in-app purchases; the standard rate is 30%, with a reduced rate for developers in the Small Business Program. Check Apple's current terms, as rules differ by region.
Is SwiftUI or UIKit better for a new app?
For a new iPhone app, SwiftUI is the default choice: it is Apple's modern framework, needs less code and gets new features first. UIKit is still useful for some complex custom views and older codebases, and the two can be mixed in one app.
Why do apps get rejected by App Review?
Common reasons include crashes and bugs, incomplete information or placeholder content, privacy disclosures that do not match behavior, missing account deletion and selling digital goods outside in-app purchase. Reading the App Review Guidelines once before you start building prevents most of these.
Design it with floow
Before you open Xcode, get the screens right. Describe your app in floow and it generates native-feeling iPhone screens you can refine in chat and export to SwiftUI, React Native or Figma. Try this prompt:
Design an iPhone habit tracker with 5 screens: onboarding, today list with check-off rows, add habit sheet, habit detail with a 30-day streak calendar, and settings. Use SF-style typography, a tab bar with Today, History and Settings, and support dark mode.
Design your mobile app with AI.
Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.
You might also like…
Insights17 November 2026Recipe App Design: Search, Cook Mode and ListsRecipe app design guide: the core screens, ingredient scaling, hands-free cook mode, smart shopping lists and search filters, with specs and copyable prompts.By floow.design
Insights17 November 2026Mobile Checkout Design: 11 Patterns That ConvertMobile checkout design patterns that reduce abandonment: guest checkout, wallet pay, smart forms, clear totals and error handling, with specs and a checklist.By floow.design
Guides16 November 2026User Flow Diagram: How to Make One, With App TemplatesHow to make a user flow diagram step by step: notation, happy and unhappy paths, tools, and copy-ready templates for sign-up, checkout and booking.By floow.design