To make an app, you go through seven steps: check that people search for what your app does, choose the platform (iPhone, Android or both), build it with the platform’s free tools, test it with real people, open a developer account, prepare the store page, and send it for review. For an iPhone app, Apple’s tool is Xcode, which runs on macOS, and its language is Swift; for an Android app, Google’s tool is Android Studio, which runs on Windows, macOS, Linux and ChromeOS, and you write in Kotlin. Both tools now include AI coding agents. Publishing costs 99 US dollars a year on the App Store and 25 US dollars once on Google Play, and a new personal Google Play account must first test its app with 12 people for 14 days.
This guide walks through each step with what Apple and Google say in their own pages, as read on 2 November 2026, and links to our longer guides where a step deserves one.
1. Check that people want it, before you build
Most apps are never found: they answer a need nobody searches for, or a search that dozens of large apps already own. Before writing code, check two things on the store itself:
- Demand: do people type the words that describe your app? The App Store’s search box suggests the searches people make, and how early it suggests a phrase says how often it is searched.
- Competition: how established are the apps that already show up? The ratings of the first 10 results are a fair measure: a search whose first apps have a few hundred ratings is open; one whose first apps have hundreds of thousands is taken.
Our list of app ideas for 2026 applies exactly that test to 585 searches on the US App Store, and ASO keyword research shows how to do it for your own idea in a few minutes.
2. Choose iPhone, Android, or both
The platform decides the tools, the language and the store:
- iPhone and iPad: you build with Xcode, Apple’s free tool, which runs on macOS only (on a Windows PC, see Xcode for Windows for what you can do). Apple’s language is Swift, and its framework for interfaces is SwiftUI.
- Android: you build with Android Studio, Google’s free tool. You write in Kotlin (or Java), and Google’s framework for interfaces is Compose. Our guide to Android app development goes step by step.
- Both: you can write the app twice, or use a framework that builds both from one codebase. Android Studio supports Kotlin Multiplatform, and other frameworks exist outside Apple and Google.
A practical rule: start where your future users are, and with the computer you have. Android Studio runs on more systems:
Android Studio can be installed on Microsoft® Windows®, MacOS®, Linux, and ChromeOS.
3. Build it with the platform’s tools
Apple describes Xcode as the whole workshop:
Xcode offers the tools you need to develop, test, and distribute apps for Apple platforms
It includes simulators for Apple devices, previews that redraw your screens as you type, and testing tools. SwiftUI is meant to keep the code short:
SwiftUI helps you build great-looking apps across all Apple platforms with the power of Swift — and surprisingly little code.
On Android, Google’s starting point is to “create your first app” with Compose, then adapt it to phones, tablets, foldables and more.
Both companies now build AI coding agents into these tools. Apple writes: “Bring your ideas to life faster using coding agents in Xcode, powered by the model of your choice.” Google’s Android site offers to “turn prompts into real Android experiences using your favorite agents.” Building an app by describing it to an AI has a name, and the stores’ rules still apply to what comes out: see our guide to vibe coding.
4. Test it with real people
Both stores have their own testing service.
On the App Store, TestFlight. You upload a beta build to App Store Connect and invite testers, who install it with the TestFlight app:
- Internal testers: up to 100 members of your team, with builds sent to them automatically if you choose.
- External testers: up to 10,000 people, invited by email or through a public link. The first build you share with them must be approved by App Review for TestFlight.
- Each tester can install your betas on up to 30 devices, and you can share up to 100 builds.
On Google Play, testing tracks. An internal test reaches up to 100 testers within minutes. For a new personal developer account, a closed test is not optional:
Developers with personal accounts created after November 13, 2023, must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days.
Start finding those 12 testers while you build, not when you are ready to publish: the 14 days only count once they have all joined. Our guide to Google Play Console has the whole procedure.
5. Open a developer account
Apple Developer Program: “99 USD per membership year”, with prices in local currency in some regions. As an individual, you need an Apple Account with two-factor authentication, to be of legal age in your region, and your legal name, which the App Store shows as the seller of your apps. An organization needs a D-U-N-S number, a public website on its own domain, and someone with the authority to sign for it. Nonprofits, accredited schools and government entities can ask for a fee waiver. Our guide to the Apple Developer account has every step.
Google Play Console: a one-time fee of 25 US dollars, an age of 18 or more, and an ID and a card in your legal name if Google asks. Organizations also need a D-U-N-S number, which Dun & Bradstreet issues for free.
6. Prepare the store page
The store page decides whether people find your app and whether they download it. Apple lists what it must contain:
- The product page: your app’s name, icon, description, screenshots, app previews and keywords, plus a subtitle and promotional text. Every screenshot size Apple asks for is in App Store screenshot sizes.
- The age rating questionnaire, in App Store Connect.
- Your app’s privacy details, including the practices of third-party code you include, which become the Privacy Nutrition Label on your page.
On Google Play, the store listing has a name of 30 characters, a short description of 80 and a full description of 4,000, an icon, a feature graphic and screenshots, plus the App content declarations: a privacy policy, ads, a content rating and the target audience.
The words in these fields are what search reads. On the App Store, the name, the subtitle and the keyword field carry most of it: see the keyword field and the name and subtitle. On Google Play, there is no keyword field, and search reads your title and descriptions.
7. Send it for review, and publish
Both stores review apps before they appear. Apple says why:
Apple reviews submissions to confirm they’re safe, secure, and reliable.
A few rules catch first apps most often:
- Finish it. Apple asks for final versions, with “placeholder text, empty websites, and other temporary content” removed, tested on a device, with a demo account for the reviewer if the app needs a login.
- Make it more than a website. Apple’s rule 4.2: “Your app should include features, content, and UI that elevate it beyond a repackaged website.”
- Don’t clone. Apple’s rule 4.3 turns away apps “indistinguishable from what’s already widely available”, and Google doesn’t allow apps “that only have limited functionality and content.”
- Link a privacy policy, in the store’s metadata and in the app, on both stores.
Apple also sets technical minimums: starting April 2027, iPhone and iPad apps uploaded to App Store Connect must be built with the iOS & iPadOS 27 SDK or later and target iOS 15 or later. On Google Play, a new personal account applies for production access after its closed test, and Google says the review of that application “usually takes seven days or less”.
Once approved, the App Store reaches 175 storefronts in 50 languages, by Apple’s count.
8. After launch: get found, then measure
A new app starts with no ratings and no history, and search is where most downloads begin: Apple says “almost 65% of downloads happen directly after a search” on the App Store. Watch three things:
- Your rank for each search that matters, in each country, over several days: one reading means little, because ranks move with the country, the language and the hour. Our guide to checking a keyword ranking explains how.
- Your ratings. On both stores, ratings, reviews and downloads count among the signals of search, as our guides to App Store search and Google Play search show.
- Each change to your page: compare the weeks before and after, then decide whether it worked.
What to do
- Check demand and competition on the store before you build.
- Pick one platform to start, the one your users and your computer favour.
- Build with Xcode and SwiftUI, or Android Studio and Compose, with or without an AI agent.
- Test early: TestFlight on the App Store; on Google Play, line up 12 testers for a 14-day closed test.
- Open the developer account in your legal name: 99 USD a year at Apple, 25 USD once at Google.
- Write the store page for search: name, subtitle and keywords on the App Store; title and descriptions on Google Play.
- Read the review rules before you submit: finished, more than a website, not a clone, with a privacy policy.
- After launch, measure your ranks per country, and judge each change over weeks.
Sources
- Apple, Apple Developer, Xcode: what Xcode does, coding agents.
- Apple, Apple Developer, SwiftUI: Swift and SwiftUI.
- Apple, Apple Developer, TestFlight: internal and external testers, builds, devices.
- Apple, Apple Developer, Enroll: requirements for individuals and organizations, the 99 USD membership.
- Apple, Apple Developer, Membership Details: fee waivers.
- Apple, Apple Developer, Submitting: the product page, age rating, privacy details, review, SDK minimums, 175 storefronts.
- Apple, Apple Developer, App Review Guidelines: rules 2.1, 4.2, 4.3 and 5.1.1.
- Apple, Apple Ads, Ads on the App Store: downloads after a search.
- Google, Android Developers, Android Studio: the systems it installs on, Kotlin.
- Google, Android Developers, Build your first app: Compose, agents.
- Google, Play Console Help, Get started with Play Console: the US$25 fee, age, identity.
- Google, Play Console Help, App testing requirements for new personal developer accounts: 12 testers for 14 days, the review of production access.
- Google, Play Console Help, Create and set up your app: the store listing’s limits.
- Google, Play Console Help, Minimum functionality: apps with limited functionality and content.
Checked on 2 November 2026.