Mobile app development, explained: what gets built, who builds it, and what it costs

If you are about to commission your first app, the hard part is not the code. It is knowing what you are buying: the screens are the visible part of the work, and the backend, the admin panel and the store submission sit behind them. This guide walks through what gets built, the first decision you have to make, who does the work, what it takes in time and money, and what you should own when it is done.

By Arjun Sareen, Head of Business Development

Reviewed by Kanika MathurPublished Sep 8, 2026Updated Sep 8, 202610 min read

Mobile

Key takeaways

The short version

An app is at least three products. The app on the phone, a backend that stores data and runs the rules, and an admin panel your team uses to operate it. A quote that only covers screens is not a quote for a working app.
Platform is the first real decision. Cross-platform (one codebase for iOS and Android) fits most first products; native fits apps that lean on device hardware or top-end performance; a web app fits when you do not need a store listing.
Six roles, not six people. Product lead, designer, mobile developer, backend developer, QA and release engineering. On a small team people double up, but every role should be named in the proposal.
Plan in ranges, then narrow. Published benchmarks put a simple app at 2 to 4 months and a mid-complexity app at 4 to 6 months, and the same scope can cost several times more with a US team than an offshore one, because pay differs that much by country.
Ownership is not automatic. Copyright in commissioned software stays with whoever wrote it unless a signed agreement says otherwise, and store accounts belong to whoever registered them. Fix both in the contract before you pay.

What building an app actually involves, and the parts you never see

The app on the phone is the part of the work you can see. Behind it sits a backend (the server that stores accounts, data and business rules), an admin panel your own staff use to run the product, and a store submission process that Apple and Google control, not you. When someone quotes you for "an app", ask which of those four parts the number includes.

The app itself. The screens, navigation, sign-up, push notifications, offline behavior and everything a user touches. This is what demos well and what most first-time buyers picture when they say "app". It is also the part with the least business logic in it.
The backend and API. Somewhere a server has to hold user accounts, store what people do, talk to payment and email providers, and send the notifications. That server is built separately, hosted on a cloud account (AWS, Google Cloud or Azure, typically) and billed monthly for as long as the app exists. Without it, the app is a brochure.
The admin panel. The web screens your team uses to look up a customer, refund an order, remove a bad listing, change a price or read the numbers without asking a developer. It is rarely in the pitch and always in the invoice, because you cannot operate a product without it.
Store accounts and review. Both stores review every submission against their own rules. Apple's guidelines say a submission should be a final version, tested on a device, with a working demo account if the app has a login, and every app must link to a privacy policy both in its listing and inside the app^[2]. Apple reports that, on average, 90% of submissions are reviewed in under 24 hours^[3], but a rejection restarts the clock, so plan a buffer of at least a week around your first launch on each store.

Then there is everything after launch: operating system updates that break something each year, crash reports, store policy changes, and the features users ask for in week two. The stages that lead up to that point are laid out in our guide to the app development process from idea to store.

Native, cross-platform or web app: how to make the first decision

You have three ways to build the thing users tap: native (a separate app for iPhone in Swift and for Android in Kotlin), cross-platform (one codebase in a framework such as Flutter or React Native, compiled for both), or a web app that runs in the browser and never goes through a store. The decision rule for a first product is simple: default to cross-platform, go native only if the app depends on deep device features or top-end graphics, and go web only if you do not need a store listing or the phone's hardware.

The three ways to build, and the decision rule for each
Option	What it is	Choose it when	Cost of that choice
Native	Two separate apps, built with Apple's and Google's own tools and languages	The app lives on camera, sensors, Bluetooth, AR or heavy graphics, or you need the best possible performance	Two codebases to build, test and maintain
Cross-platform	One codebase (Flutter, React Native) that ships to both stores	Most consumer and business apps: forms, feeds, lists, chat, payments, maps	Some device features need extra native work; you depend on the framework's release cycle
Web app or PWA	A website built to behave like an app, opened in the browser or saved to the home screen	You do not need a store listing or deep hardware access, and you want the fastest path to users	No store presence, weaker access to device features

Cross-platform is the default for most new consumer and business apps, not a compromise, and it leaves you with one codebase for a new team to pick up if the original one moves on. One caution on the web route: Apple's guidelines say an app that is a repackaged website does not belong on the App Store^[2], so if you start with a web app and later want a store listing, budget for real app features, not a wrapper. The trade-offs in more depth, including when native really earns its extra cost, are in our native versus hybrid versus cross-platform comparison.

Who is on an app team and what each person does

A first build needs six roles, not necessarily six people: a product lead, a designer, one or more mobile developers, a backend developer, a QA engineer and someone who owns releases and infrastructure. On a small team the product lead also runs the project and the backend developer also handles releases. What matters is that every role is covered and named, because the gaps are where projects fail.

The six roles on an app team
Role	What they actually do	When you will deal with them
Product lead or project manager	Turns your idea into a written scope, decides what is in the first version, runs the weekly cadence, reports progress and risk	Every week, start to finish
UX and UI designer	Maps the user journey, draws the screens, produces a clickable prototype you approve before code is written	Heavily in the first weeks, then for each new feature
Mobile developer	Builds the app users see, on one platform (native) or both (cross-platform)	Through the build, in demos every sprint
Backend developer	Builds the API, database, integrations (payments, email, maps) and usually the admin panel	Through the build; you rarely see the output directly
QA engineer	Writes test plans, tests on real devices, files and verifies bugs, signs off each release	From the first working build to launch, then every release
Release and DevOps	Sets up cloud hosting, build pipelines, store submissions, monitoring and backups	At setup, at launch, and when something breaks

Where those people sit is the largest single lever on the price. The US Bureau of Labor Statistics puts the median pay for a software developer at 135,980 dollars a year and for a software quality assurance analyst or tester at 104,300 dollars (May 2025)^[8]. The 2025 Stack Overflow Developer Survey reports a median of 170,000 dollars for a mobile developer in the United States and 10,462 dollars for one in India (a figure built on 55 responses)^[9]. That gap is why the same scope gets quoted at very different prices, and why most teams end up with a mix. Our notes on what app developers cost in the US and on choosing a US, offshore or hybrid team go through the trade-offs; Resourcifi runs its engineering teams in Noida, India, with headquarters in Wilmington, Delaware, which is the hybrid shape in practice.

How long it takes and what it costs, in ranges you can plan with

Business of Apps' review of published estimates puts a simple app at 2 to 4 months, a mid-complexity app at 4 to 6 months, and a complex app at nine months to a year; its price benchmarks run from 5,000 to 50,000 dollars for a simple app, 50,000 to 120,000 for medium complexity and 120,000 to 300,000 for a complex build^[7]. Those ranges are wide because two variables set the number: how much you put in the first version, and where the team is based.

2 to 4

Months for a simple app, rising to 4 to 6 for mid complexity and nine months to a year for a complex one.

Business of Apps, app development cost

99 and 25

The cost to publish: 99 dollars a year for the Apple Developer Program and a one-time 25 dollars for a Google Play developer account.

Apple Developer, Google Play Console

170k vs 10k

Median yearly pay in dollars for a mobile developer in the United States versus India, the reason team location moves the price so much (India median from 55 responses).

Stack Overflow 2025 Developer Survey

Treat the ranges as planning brackets, not quotes. The number that matters is the one attached to a written scope, and a good proposal shows its assumptions: which platforms, which features are in version one, how many people for how many weeks. Beyond the build, budget for the running costs: the Apple Developer Program is 99 dollars per membership year^[1], a Google Play developer account is a one-time 25 dollars^[4], and cloud hosting and third-party services (payments, messaging, maps) bill monthly for the life of the product. For the full breakdown by app type and feature, read our mobile app development cost guide; for what a realistic schedule looks like week by week, read how long an app takes to develop.

What you own at the end, and how to protect it

You should walk away owning three things: the source code and design files, the accounts the app lives in (store, cloud, domain, code repository), and the data. None of them is yours by default. Under US copyright law the person who writes the code owns the copyright unless the work qualifies as a work made for hire or the copyright is assigned to you in a signed written agreement^[5], and store and cloud accounts belong to whoever registered them.

Code and design. The US Copyright Office explains that a work made for hire arises in two ways: it was created by an employee within the scope of employment, or it was specially commissioned, falls into one of nine listed categories, and the parties signed a written agreement saying so^[5]. Software is not one of the nine categories, so for a contractor or agency the reliable route is a clause that assigns the copyright to you on payment. Ask for it, and have a lawyer check the wording; this is general information, not legal advice.
Store accounts. Register the Apple and Google developer accounts in your company's name, then give the agency access as team members. Apple requires a company to be a legal entity with a D-U-N-S Number (government bodies are exempt), the enrolling person must have authority to bind the company, and your company's name is what appears as the seller on the App Store^[1]. If an app was published under someone else's account, both stores allow a transfer: Apple keeps the app's reviews, ratings and bundle ID through the move^[6], and Google transfers users, statistics, ratings and subscriptions with it^[10]. Possible, but slower and riskier than starting in your own name.
Cloud, domain and repository. The hosting account should bill to your card, the domain should sit in your registrar, and the code repository should be in an organization you administer. If a supplier leaves, you revoke access; you should never have to ask for it.
Data and third-party terms. User data belongs with you and your privacy policy, not on a developer's test server. Ask for a list of every open-source library and paid service in the product, with its license, so nothing you depend on is licensed to someone else.

Questions to ask before you pay anyone

Put everything on this page into questions and ask them in writing before the first invoice. The answers tell you more than a portfolio does, because they show whether the supplier has thought about the parts you cannot see. A good team will have most of these answers ready; a weak one will say "it depends" without saying what it depends on.

What exactly is in the quote? Is the backend included? The admin panel? Store submission, with resubmissions if the first review fails? Hosting setup? If any of these are "phase two", ask what phase two costs.
Why this platform choice for my app? The answer should reference your features, not the team's preference. If they recommend native for an app that is mostly forms and lists, ask what the second codebase buys you.
Who, by name and role, is on my project? Ask for the six roles above, who fills each, where they sit, and how much of their week is yours.
What are the assumptions behind your estimate? Number of screens, integrations, platforms, weeks. An estimate without assumptions cannot be compared with another one.
What happens when the scope changes? It will. Ask how changes are priced and approved, and what the weekly or monthly reporting looks like.
What will I own, and when? Ask for the assignment clause, the account plan (whose name each account is in) and a handover list: code, design files, credentials, documentation.
What does the first three months after launch look like? Who fixes crashes, who handles an OS update that breaks a screen, and what that costs per month.

If you want a second opinion on a scope or a quote you already have, send it to our mobile app development team, and ask these questions of us before you ask them of anyone else.

Frequently asked

Mobile app development questions

What does mobile app development actually include?

A working app is at least three pieces of software: the app on the phone, a backend server that stores accounts and data and runs the business rules, and an admin panel your own team uses to operate the product. Around those sit the store accounts, the review process, cloud hosting and ongoing maintenance. When you get a quote, check which of those parts it covers, because the screens alone are the smallest piece of the work.

Should my first app be native, cross-platform or a web app?

For most first products, cross-platform is the sensible default: one codebase in Flutter or React Native ships to both stores. Choose native when the app depends on camera, sensors, Bluetooth, augmented reality or top-end graphics. Choose a web app when you do not need a store listing or the phone hardware and want the fastest path to users. Decide on your features, not on the preference of the team quoting you.

How many people does it take to build an app?

Plan for six roles: a product lead, a designer, a mobile developer, a backend developer, a QA engineer and someone who owns releases and hosting. On a small project people cover two roles each, so six roles can be covered by as few as three people, but every role should be named in the proposal. A team that has no tester or no one responsible for the backend is the usual reason a project overruns.

How long does it take to build an app?

Published benchmarks put a simple app at two to four months, a mid-complexity app at four to six months, and a complex product at nine months to a year. The two variables that move a project inside those ranges are how much you insist on for the first version and how quickly you make decisions. Add at least a week of buffer around your first store submission in case the review comes back with changes.

What does it cost to publish an app on the App Store and Google Play?

The store fees are small next to the build. Apple charges 99 dollars per membership year for the Apple Developer Program, and Google charges a one-time 25 dollars for a Google Play developer account. Both accounts should be registered in your company name, not the agency's, and Apple requires a company to be a legal entity with a D-U-N-S Number (government bodies are exempt). The larger ongoing costs are cloud hosting, third-party services and maintenance.

Do I automatically own the code an agency writes for me?

No. Under US copyright law the person who writes the code owns the copyright unless the work qualifies as a work made for hire or the copyright is assigned to you in a signed written agreement. Work made for hire covers employees, and for commissioned work it only applies to nine listed categories that do not include software. So for an agency or contractor you need a written clause that assigns the copyright to you on payment. Have a lawyer check the wording.

Arjun Sareen

Head of Business Development, Resourcifi

Arjun Sareen is Head of Business Development at Resourcifi. He scopes builds with founders and product leaders, matches each project with the right team model, and hears the same buying questions every week, which is what he writes about.

Resourcifi on LinkedIn →

Kanika Mathur

Reviewer. Head of Service Delivery, Resourcifi

Kanika Mathur is Head of Service Delivery at Resourcifi. She leads the engineering pods that scope, build and run client software, from mobile apps to AI systems, and she reviews the process and figures in our engineering guides for accuracy.

Resourcifi on LinkedIn →

Sources

Apple, Apple Developer Program enrollment (99 dollars per membership year; organization enrollment requires a legal entity, a D-U-N-S Number except for government entities, and an account holder with authority to bind the company; the organization name appears as the seller).
Apple, App Store Review Guidelines (2.1 app completeness and demo accounts, 4.2 minimum functionality, 5.1.1 privacy policy link requirement).
Apple, App Review (on average, 90% of submissions are reviewed in less than 24 hours).
Google, Register for a Google Play Developer account (the 25 dollars one-time registration fee).
US Copyright Office, Circular 30: Works Made for Hire (the two ways a work qualifies as made for hire, the nine categories for commissioned works, and who is treated as the author).
Apple, Overview of app transfer (an app can be transferred to another App Store Connect account and retains its reviews, ratings and bundle ID).
Business of Apps, App Development Cost (price benchmarks by complexity and the 2 to 4 month, 4 to 6 month and nine months to a year timelines drawn from published estimates).
US Bureau of Labor Statistics, Occupational Outlook Handbook: Software Developers, Quality Assurance Analysts, and Testers (May 2025 median pay of 135,980 dollars for software developers and 104,300 dollars for QA analysts and testers).
Stack Overflow, 2025 Developer Survey, Work (median yearly pay for a mobile developer of 170,000 dollars in the United States and 10,462 dollars in India; the India median rests on 55 responses in the chart data).
Google, Transfer apps to a different developer account (users, statistics, ratings and subscriptions transfer with the app).