Can one person build a mobile app? Yes, and writing it is no longer the hard part.
Yes. One person can build a mobile app, get it onto the App Store and Google Play, and keep it running for years. Solo app development is normal now, and the tooling has made the writing faster again. The catch is the rest of the job. The code is one task out of about nine. The other eight arrive on other people's schedules. Two store accounts. An identity check. A closed test with twelve real humans in it. Review replies, a support address a stranger can use, tax details, and a rebuild every time the platforms move. Scope is the only lever fully under your control. That is why MVP app development matters more to a team of one than to a team of ten.
So the useful question is not whether one developer app is possible. It is which of those jobs you can defer, which a tool can take, and where one person stops being the cheapest way to run the app. The answer splits two ways, and both readers are named below before any verdict.
See where the week goesThe short version
Building it alone is realistic. Holding it up alone is the real question.
If you are making a narrow tool for people you already understand, one person is enough, and stays enough. Small scope, bounded support, no promise about uptime. Plenty of paid apps run that way for years with one name on the account.
If you are making a consumer app with accounts, money and strangers in it, one person gets version one live and then starts losing ground. Not to the code. To coverage. You cannot answer a support thread, chase a rejection and ship a crash fix in the same afternoon. An app like that needs all three in one afternoon more often than you expect.
What one person can genuinely build
Start with the honest version of the build. A single purpose app with local data, a real design, a handful of screens and both platforms is a solo job. It has been one for years, and AI tooling has shortened it again. Someone who can read code, or will learn to read it, can have a working app on their own phone in days, not months.
What stays hard is not screens. It is anything holding other people's data: accounts, sync between devices, offline edits that later conflict, moderation, live content, anything with a queue. Each of those brings a server, a schema, a migration path and an expectation that somebody is awake. One person can build them. One person maintains them at the cost of everything else on the list.
Team size questions get answered badly because they get answered in job titles. The useful version counts jobs per week, not the roles a normal company would hire. We work that count through in how many people to build an app. For a team of one the conclusion is blunt. Cut the app until the weekly job count fits the hours you actually have, then cut it once more for the week something goes wrong.
The store account is a legal identity, not a signup
The first wall in building an app alone is not technical. To publish on iOS you enroll in the Apple Developer Program, which Apple prices at 99 USD per membership year, with prices varying by region. You can enroll as an individual or as an organization, and that choice has a consequence people miss. Enroll as an individual and Apple confirms your personal legal name, then shows that name as the seller of your apps on the App Store. Enroll an organization and you need a legal entity that can contract with Apple, plus a D-U-N-S Number for it. Apple also says P.O. boxes are not accepted as an individual's address.
Google Play charges a one time registration fee of 25 US dollars, requires you to be at least 18, and verifies who you are. Its own help pages say you may be asked for a valid government ID and a credit card, both in your legal name. The registration fee is not refunded if that information turns out to be invalid. Then come the forms that have nothing to do with code. A privacy declaration covering every SDK you added. An age rating, export answers, tax and banking details before any money reaches you, and a support contact on the listing.
None of this is difficult. All of it is sequential, slow, tied to a real identity, and impossible to hand to the tool that wrote your app. Budget a day for the accounts and another for the metadata, and do both before the week you want to launch.
Apple, enrolling in the Apple Developer Program as an individual or an organization
The week after launch is the part nobody plans
Launch day is not the test. The following Tuesday is. A live app produces a small steady stream of work that arrives whether or not you are at your desk. A crash on a device you do not own. A one star review with a real bug inside it. A question that is really a refund request. A platform release note that changes something you relied on.
Review responses are a job with rules, not a nice extra. Apple lets you respond to any review of your app in App Store Connect, however old it is. When you respond, the reviewer is notified and can update their review, and you can edit your response later, with only the latest version shown. Apple's own guidance is to keep personal information and marketing language out of responses. If you cannot answer everything, prioritise the lowest ratings and the reviews reporting technical problems in the current version. Apple also tells you to make your support contact easy to find in the app and on the product page. That one sentence quietly creates a support inbox.
Ratings punish absence more than they punish bugs. Google says the rating users see is weighted towards recent ratings. New submissions are generally held for around 24 hours before they appear, and you can see and reply to them inside that window. Apple lets you reset a summary rating when you release a new version, though written reviews stay. An app with one person behind it is not scored on its launch. It is scored on the last few weeks of attention it got.
Put those hours in a column and the honest answer usually arrives before any argument about skill. It is also the point where a side project to startup decision stops being about ambition and becomes a calendar question.
Try it
What is left for the build
Tick the jobs that land on you once the app is live. The hours are rough weekly figures for a small live app, not measured data.
3 of 12 hours left for building
Under four hours a week, one small feature takes a month. Fine for a tool you own. Hard for a product with competitors.
Two walls that have nothing to do with your ability
The first is a store rule, and it surprises people who thought shipping alone was a private activity. Google Play requires personal developer accounts created after 13 November 2023 to run a closed test before an app can reach production. When you apply for production access, at least 12 testers must have been opted in continuously for the preceding 14 days. So a person building an app alone needs twelve other people and two weeks of their patience. Google's advice is to recruit from your own networks and from the communities your future users are already in. Internal testing does not count towards it, and the rule is written for personal accounts, so an organization account may sit outside it. Check your own console rather than planning around a page that can change.
The second wall is coverage. One person is one thread. What breaks a solo app is not the size of the work. It is two required jobs landing in the same hour. A crash in production, a rejection waiting on a reply, a customer waiting on an answer. You can survive that a few times. You cannot schedule it.
So the sane test for hiring or partnering is not revenue and it is not feature count. It is whether two required jobs keep colliding, and whether anyone is harmed when the second one waits. Once an app charges money or holds other people's data, waiting has a cost you can name. That transition, when one person stops being enough, needs its own walkthrough and is not a decision you make on launch week.
Google Play Console Help, app testing requirements for new personal developer accounts
Which kind of app can one person actually hold?
| What you are building | One person ships version one | One person holds it after launch | What breaks first | What a second person buys |
|---|---|---|---|---|
| A tool for a team you work in | Yes | Yes | nothing much, the users sit near you | very little |
| A paid utility for a niche you know | Yes | Yes | support volume in week one | faster replies |
| A client app you hand over | Yes | No | the maintenance promise | someone to hold the contract |
| A consumer app that needs growth | Yes | No | distribution, long before the code | reach, not more features |
| An app holding money or accounts | yes, once a backend exists | No | being the only person on call | cover at night and on holiday |
Building it alone without pretending the rest away
The build is the part that genuinely changed. One person can now describe an app, get a working project, run it on both platforms and hand a test build to friends inside a week. That used to be a quarter of work. Treat it as time bought, not work removed. Every hour the tooling returns goes straight into the list above, which is where solo projects actually die.
Newly is an AI app builder. You describe the app in plain English and it writes a real React Native and TypeScript project that belongs to you. It runs on cloud iOS and Android simulators while it builds. It uploads to App Store Connect and TestFlight, and publishes to Google Play internal testing from a chat message. The closed test that unlocks production is a separate track you set up in Play Console. It also builds a standalone production APK. It is $25 a month and there is no free plan. A new app starts local first, keeping its data on the phone with no accounts and no server. A backend is added only when the app needs sign in, shared data, syncing or payments. The code leaves as a ZIP from Settings, through the two way GitHub sync under Deploy, or with the CLI.
What no builder does is the part this page is about. It does not enroll you in a developer program. It does not press submit for review, find twelve testers for your closed test, or answer a one star review at eleven at night. Read every tool's claims with that split in mind. The code is the cheap half now. The paperwork and the people are the half that decides whether the app is still there next year.
Questions people ask before they start alone
Yes. Apple lets you enroll in the Apple Developer Program as an individual or sole proprietor, at 99 USD per membership year, and Google Play has a personal account type with a one time 25 US dollar registration fee. The trade is visibility and rules. Apple confirms your personal legal name and displays it as the seller of your apps, and Google Play asks personal accounts created after 13 November 2023 to complete a closed test before production. An organization account avoids the name question but needs a real legal entity and, at Apple, a D-U-N-S Number.
Decide the scope before you decide the team
Write down the jobs you will own after launch and the hours you actually have each week. Then build the smallest version of the app that survives both lists.
Start building