Is building an app a good side hustle? Usually not for the money, sometimes for everything else.
If you want a few hundred extra dollars a month within six months, no. Freelance work and small contract builds pay sooner, because a person is already asking for them. App side income arrives slowly, in a shape you do not control, and often not at all. The confusion comes from the fact that the same evenings produce two different things: a product nobody has heard of, and a skill that compounds. Building is now the cheap half. Getting found is the job. If the app is the proof rather than the product, a side project to startup path is a much better use of the same hours than a hopeful store listing.
Below is the arithmetic instead of the encouragement: what you pay before anyone pays you, what Apple and Google actually keep as of 1 October 2026, how many paying users your target needs, and the one condition that flips the answer to yes.
Work out what your target would takeThe short version
The answer depends on one thing: whether you can already reach the users.
Two people ask this question and they need opposite answers. The first wants income added to this month, and for them an app is a bad instrument: long lead time, no guaranteed demand, and a marketing job attached. The second wants an asset, a skill, or a cheap way to test a business idea, and for them evenings spent on an app are among the better options available.
The condition that separates them is distribution. A newsletter, a trade you work in, a forum where people know your name, a group of colleagues fighting the same spreadsheet. If your honest answer is nobody yet, you have not started an app business. You have started a marketing project with an app attached, and that project is the one that decides whether you get paid.
What it costs before anyone pays you anything
The fixed costs are small and knowable, which is the good news. Apple's enrolment page puts the Apple Developer Program at 99 USD per membership year. Google's account setup page puts a Play developer account at a one-time 25 USD registration fee. Both were read on 1 October 2026. Add whatever you build with, which for an AI builder is a monthly subscription rather than a single purchase. That is the entire bill for the right to publish on both stores.
The commission is where the folklore is wrong, and it is worth correcting before it talks you out of anything. The 30 percent figure quoted at every beginner is not the rate a beginner pays. Apple's App Store Small Business Program carries a reduced commission rate of 15 percent on paid apps and Apple in-app purchases, for developers who made up to 1 million USD in proceeds in the prior calendar year, and Apple says developers new to the App Store can qualify too. It is an enrolment, not a default, so you have to actually sign up.
So the honest cost picture is about 99 dollars a year, 25 dollars once, 15 percent of anything you sell, and an unbounded quantity of your own evenings. Only the last item is expensive. Anyone who tells you store fees are why app side hustles fail is pointing at the smallest number on the page.
Apple, App Store Small Business Program: 15 percent commission and eligibility
What each store keeps, with the numbers as they stand today
Google Play restructured its service fees during 2026 and the new shape favours small developers. For transactions with users in Australia, the European Economic Area, Japan, the United Kingdom and the United States, the first 1 million USD of annual earnings carries a 10 percent service fee plus a 5 percent billing fee. Google gives the regional rollout dates as 30 June 2026 for the EEA, the UK and the US, and 30 September 2026 for Australia and Japan. In the remaining markets, until the change rolls out globally, developers enrolled in the 15 percent service fee tier pay 15 percent on the first 1 million USD of annual revenue and 30 percent above that.
Above a million the rate steps up, and for non-subscription purchases from users who installed before the rollout date it reaches 25 percent plus the billing fee, or 20 percent if the purchase happens through an external web link. None of that is your problem in year one. Plan on keeping roughly 85 cents of every dollar on either store and your model will be close enough to make decisions with.
The same page carries a figure worth sitting with for a minute. Google says 97 percent of developers distribute their apps on Play at no charge, and that of the developers who do pay a service fee, 99 percent qualify for 15 percent or less. Read the first half again. Almost every app on the store pays no service fee at all, and a fee only applies when something actually sells through Google Play billing. The cut is cheap because for the overwhelming majority of apps there is nothing to cut.
Worth knowing too: the stores only take a share of what runs through their billing systems. Sell a service, a consulting hour, or a subscription bought on your own website, and neither store is in the transaction. That is why most honest accounts of vibe coding money end up being about selling to a specific person rather than listing a product and waiting, and it is the largest single lever on what you take home.
Google Play Console Help, Service fees: rates, rollout dates and the 97 percent figure
The arithmetic that answers the question
Pick the number you would be happy with and work backwards. Take a 4 dollar a month subscription with 15 percent to the store: you keep about 3.40. To clear 500 dollars a month you need roughly 147 people subscribed at the same time, every month, replaced as they leave. Not 147 downloads. 147 live subscriptions, after cancellations.
Now add conversion. If two installs in a hundred become payers, which is optimistic for an audience that has never heard of you, holding 147 subscribers sits on something like 7,350 installs, and more than that to grow rather than tread water. That calculation is what turns a vague hope into a plan you can check against reality, and it is why app ideas for a side hustle aimed at a narrow paying group beat ideas that need a million casual users.
The distribution of outcomes is the part people skip. Most apps earn nothing. That is not a pessimistic reading of a chart, it is the shape of any catalogue anyone can list in for 25 dollars, and the 97 percent figure above is the closest thing to an official confirmation you will get. We are deliberately not quoting you a median revenue per app, because the numbers circulating come from third party estimates rather than anything Apple or Google publish, and an invented median is worse than none. Plan as if your first app earns zero, then decide whether the evenings were still worth spending.
Work it out
What your target actually asks for
The paying users you have to hold at the same time, and the installs sitting behind them.
148 paying users at the same time
You keep about 3.40 USD of every 4 you charge, so 500 a month needs 148 live subscriptions, not 148 downloads. At 2 percent of installs paying, that is roughly 7,400 installs, and every month you replace the people who cancel. Apple's reduced rate, for under 1 million USD of proceeds in the prior calendar year.
The work that decides it, and it is not the code
Making money from an app comes down to two jobs that sit behind the build, and neither is fun. The first is being found, which is a standing job rather than a launch week task. An app with no audience behind it usually stays near zero however good it is, because nothing in either store hands attention to an unknown name. That is the distribution problem, and it earns a guide of its own rather than a paragraph here.
The second is maintenance, and it is what quietly ends most side hustle apps. Every year both platforms move: a new OS version, a raised target SDK requirement, a fresh privacy disclosure, a signing or account rule. An app you stop touching eventually stops being installable. So a project you have grown bored of is still a support inbox and an annual round of upgrades, and unlike a blog post it decays if you ignore it.
There is also a gate on the Android side that catches people out. Google's account setup steps say developers with personal accounts created after 13 November 2023 must meet specific testing requirements before they can make an app available on Google Play, and that new personal accounts must verify access to an Android device. Read the current rules in Play Console before you promise anyone a launch date.
Put those two jobs next to a freelance invoice and the comparison gets uncomfortable. Contract work pays on delivery and stops when you stop. An app pays later, maybe, and keeps asking for attention either way. That is the trade, stated plainly, and it is why the answer for most people is no.
Five ways to turn app work into money, and what each one asks of you
| Route | Cash out before cash in | When the first money lands | Needs strangers to find it | What you keep |
|---|---|---|---|---|
| A paid app or subscription in the stores | 99 USD a year, 25 USD once, plus build tools | after review, then after you find buyers | Yes | the app, the users and the revenue |
| Apps built for local businesses | almost nothing | on your first invoice, so weeks | No | a portfolio and referrals |
| A free app funded by ads | the same two store accounts | only at real traffic volumes | Yes | very little per user |
| A tool you sell to one team or employer | nothing | when the contract is signed | No | a contract, and no store listing |
| An app built to get the job or the raise | your evenings | at the next salary conversation | No | a skill, which does not churn |
What a cheap build changes, and what it leaves untouched
Cheap building did change one real thing: the cost of finding out you were wrong. Two evenings and a working app on a real phone beats two months and a prototype, so the sensible move is to put the smallest version in front of ten people you can name by name, before you think about a store listing at all. Ten honest reactions are worth more than any amount of planning, and they cost you nothing but the asking.
Newly is an AI app builder. You describe the app in plain English and it writes a real React Native and TypeScript project that you own. It runs the app on cloud iOS and Android simulators while it builds, uploads to TestFlight, publishes to Google Play internal testing and builds a standalone Android APK. It is $25 a month and there is no free plan. New apps start local-first, with data on the phone and no accounts or server, and a backend with sign in, an API, a Postgres database and file storage is added only when the app needs one. The code comes out as a ZIP from project Settings, through the two-way GitHub sync under Deploy, or with the CLI.
Two limits matter if the point is money, and both are the sort of thing people find out late. There are no built-in payments, so charging a subscription means wiring a purchase flow yourself, and that is the fiddliest part of any paid app. And App Store submission is your button: the build gets uploaded for you, then you press submit and you handle review. Neither is a reason not to start. Both are reasons not to budget one weekend for launch.
Questions people ask before they start
As a way to add income this quarter, no. Freelance and contract work pay sooner because demand already exists. As a way to build an asset, learn a skill or test a business idea cheaply, yes, and it is far cheaper than it used to be. The deciding factor is whether you can already reach the people who would use the app. If you cannot, the real project is marketing, not building.
Test the idea this week, not the business plan
Pick the smallest version of the app, name ten people who would use it, and build enough to show them. If none of the ten want it, you learned that for the price of two evenings instead of a year.
Start building