How to Ship Your First App as a Beginner: Half-Built to Launched

The hardest part of your first app isn’t building it. It’s the last 10%: the part where you keep adding one more thing because launching feels scary.

You don’t need it to be perfect. You need it to work.

I once spent 3 days deciding on the UI of an app. Three hours on shipping beats 3 days on UI. I shipped each of my apps before I talked myself out of it.

This guide picks up where what to put in your first version ends. It’s the launch checklist: test, publish, submit, and get through Apple’s review. If you’d rather launch with guidance, here’s where I teach this.

When is your app ready to ship?

Your app is ready when a new user completes the one job it’s for, every time. Ugly is fine. Broken isn’t.

Freeze the scope now. Write the one job your app does on a sticky note and stop adding features. Every new feature this week pushes your launch back and gives you more to test.

Then fix the basics:

• Crashes and errors on the main path
• Broken links and buttons
• Placeholder text and test data
• Empty screens with no explanation

Ship ugly and fast, but useful. Ugly means visually basic. The useful part has to work.

How do you test an AI-built app before launch?

Give it to 3 to 5 real people and watch. The people you interviewed about the problem are the best testers, because they care whether it works.

Send each tester 3 specific tasks, not “let me know what you think”. Keep one short bug list, and fix only what stops someone finishing the main job.

For an iPhone app, use TestFlight. TestFlight takes up to 100 internal testers on your team and up to 10,000 external testers. External testing goes through a short Beta App Review the first time. Each build works for 90 days.

How do you launch a web app?

A web app launches when you publish it. On Lovable, Bolt or Replit, publishing gives you a link on their domain.

For your own domain, you need a paid plan on Lovable, or Bolt Pro. Lovable sets up the domain and the SSL certificate for you. Most domains go live within a few hours, and some DNS changes take up to 72.

Before you share the link, open it on your phone. Most of your first users will.

What does Apple need before you submit an iPhone app?

Apple needs 6 things from you before App Review:

1. An Apple Developer Program membership at $99 a year.
2. Screenshots: 1 to 10 per device size, in JPEG or PNG with no transparency. You need at least one set for iPhone, and iPad only if your app supports iPad. Apple’s screenshot specs list the exact sizes.
3. The privacy label. App Store Connect asks what data your app and its third-party tools collect, what it’s used for, and whether it’s linked to the user. Data sent off the device and kept counts as collected, even when it’s only used to run the app. Apple’s privacy details page explains each data type.
4. A privacy policy URL, public and linked in the app.
5. The age rating questionnaire. You answer questions about user-generated content, messaging, ads and mature themes, and Apple sets the rating. An unrated app isn’t published.
6. The encryption question. App Store Connect asks whether your app uses encryption. Check the right answer for your app before you submit.

If your app has a login, add a demo account in the App Review notes, and keep your back end switched on during review.

Why do apps get rejected, and how do you avoid it?

Most rejections come from an unfinished app. Apple says over 40% of unresolved issues relate to guideline 2.1, App Completeness.

The common reasons Apple lists:

• Crashes and bugs
• Broken links, including a missing support link or privacy policy link
• Placeholder content
• Missing demo credentials in the review notes
• Screenshots not matching the app
• An app offering no more than a repackaged website (guideline 4.2)
• Copies of other apps, or many near-identical apps

The 4.2 rule matters most for AI builders. Lovable builds web apps, and wrapping one as an iPhone app risks a 4.2 rejection. If your app needs the phone, build it as a native app with Replit or Bolt from the start.

Apple says it reviews half of all submissions in under 24 hours and 90% in under 48 hours. If you’re rejected, reply in App Store Connect, fix it and resubmit. For a critical bug fix after launch, ask Apple for an expedited review.

What does Google Play need before launch?

Google Play charges a one-time $25. New personal developer accounts also have to run a closed test with 12 testers for 14 days in a row before going live.

Recruit those 12 testers before your app is finished. Two weeks of waiting is easier when it overlaps your last fixes.

What do you do on launch day?

Tell the people who told you about the problem. Send each one the link and ask for one thing: use it once this week and reply with what confused them.

Then plan version 1.1 from what they say, not from your own feature list.

If you’re still stuck on starting, read how to start before you feel ready. For realistic timelines, see how long it takes to build an app. I also wrote about building and shipping an iPhone app in a 3-hour hackathon. And for the whole path from idea to first users, read how to build an app as a non-technical founder.

Apple’s and Google’s rules checked on their own developer pages on 24 October 2026.

I'm about to launch my first app. Check it against the most common reasons apps get rejected or fail on day one.

What the app does: [one sentence]
Where it's launching: [web / App Store / Google Play]
Has a login: [yes / no]
What I've tested: [list]

Ask me about each of these, one at a time: crashes and bugs, broken links, placeholder text, a support link, a privacy policy, a demo account for reviewers, screenshots matching the app, and whether the app does more than show a website.

Then give me a fix list, most urgent first. If you're not sure a rule applies to my app, say so.

Help me answer Apple's App Privacy questions in App Store Connect.

What my app collects: [for example: email for sign-in, analytics, payments]
Third-party services in the app: [for example: Supabase, Stripe, an analytics tool]

For each item, tell me which Apple data type it belongs to, what it's used for, and whether it's linked to the user or used for tracking. Flag anything I need to confirm with the service itself. Don't guess what a third-party service collects. Tell me to check its docs.

Write the App Review Information notes for my app submission.

What the app does: [one sentence]
How to reach the main feature: [steps]
Demo account: [username and password for reviewers]

Keep it short and plain. Tell the reviewer exactly where to tap to see the main feature. If anything needs setup on their side, explain it in one line.

Write a short message inviting 5 people to test my app before launch.

The app: [one sentence]
Who they are: [for example: people I interviewed about the problem]
How they get it: [link / TestFlight invite]

Give them 3 specific tasks to try and one easy way to report a problem. Under 120 words. Friendly, no hype.