Skip to content

Sell your app: store transfers, pricing and what buyers check

Indiemaker · Updated 17 November 2026

In short

To sell a mobile app you need store and revenue figures a buyer can check, source code that builds on someone else's machine, and a developer account in good standing so the app can be transferred. Apple and Google both have a formal transfer process that keeps the app's users, ratings and reviews. The code and the back end you hand over yourself.

An app is unusual among small online businesses because the most valuable part, the store listing with its users and reviews, sits inside an account you rent from Apple or Google. If you are thinking "I want to sell my app", the sale depends on that listing moving cleanly. Both stores allow it, each on its own terms.

What does an app buyer look at?

  • Downloads and active users, by month, from the store consoles. See monthly active users.
  • Revenue by type: subscriptions, one-off purchases, in-app purchases, adverts. Subscription income is read differently from advert income.
  • Retention. How many people still open the app a month after installing it.
  • Ratings and reviews, and how recent they are.
  • Where installs come from: store search, paid adverts, a feature, your own audience.
  • The code: framework, last update, whether it builds against current operating system versions.
  • Standing with the stores. Past rejections, warnings or removals.

The risk buyers weigh hardest is platform risk. The store can change its rules, its fees or its review decisions, and the app lives or dies by them. You cannot remove that risk. You can show a clean record.

What should you have ready before you list?

  1. Twelve months of store reports: installs, active users, revenue.
  2. Payout statements that match those reports.
  3. Source code in a repository, with build instructions tested on a clean machine.
  4. A list of every outside service the app calls: back end, database, push notifications, analytics, advert networks, subscription tools.
  5. Signing keys and certificates, stored safely and accounted for.
  6. Written confirmation that any contractor's code and any design assets are yours to sell.

What changes hands when you sell an app?

Item How it moves
Store listing Through the store's own app transfer process
Source code and build assets Handed over by you directly
Back end and database Accounts handed over or rebuilt under the buyer
Third-party services Each one moved or re-created
User data Only as your privacy policy and local law allow
Brand, icon, screenshots, text Assigned in the purchase agreement

On the App Store. Apple describes app transfer as the route to use when you have sold an app to another developer. The app can stay available during and after the transfer, it keeps its reviews and ratings, and users continue to receive updates. Your membership Account Holder starts the transfer and the receiving Account Holder accepts it. Apple states that you are responsible for exchanging the code and build assets with the recipient yourself. If the app offers auto-renewable subscriptions, it must use an app-specific shared secret, which you generate and share with the recipient before starting. Some things do not move, including the Apple Pay merchant ID and Game Center group membership. After the transfer you lose access to the app's analytics, so export what you need first.

On Google Play. Google says users, download statistics, ratings and reviews, subscriptions and store listing information move with the app. Earnings and payout reports do not, and orders made before the transfer stay in the original account, so download your reports beforehand. Both developer accounts must be registered and active, and if the app is paid or has in-app products the receiving account needs an active payments profile. Services linked to the app, such as analytics and cloud projects, have to be updated by hand.

Both stores set conditions an app must meet before it can transfer. Read the current pages listed under Sources before you agree a date with a buyer. There are step-by-step pages for the Apple transfer and the Google Play transfer.

What makes it hard: the store transfer is the easy part. The back end, the signing keys and the services stitched into the app are where time goes. An app that only you can build is not ready to sell.

How is the price of an app approached?

If the app earns money, on trailing annual profit. Add up twelve months of payouts after the store's cut, subtract the costs of running it, and add back your own pay.

Indiemaker's published guide range for mobile apps is 2.7 to 3.2 times trailing annual profit. It is a guide, not a valuation. Take an app that paid out $15,000 over twelve months with $3,000 of costs. Profit is $12,000, which gives a range of $32,400 to $38,400.

If the app has users but little or no revenue, a profit multiple does not work and no guide range applies. That case is covered in what to pay for a pre-revenue app, which is worth reading from the seller's side.

How do you sell an app on Indiemaker?

  • Listings are priced from $1,000 to $500,000.
  • Every published listing has been checked against our listing standards.
  • Revenue shows as Revenue Verified when you connect a payment provider. RevenueCat is one of them, alongside Stripe, Paddle, Lemon Squeezy and Polar. Figures you type in are owner-declared.
  • Buyers can open a limited number of listings a month for free, and message you and make an offer from an opened listing.
  • Payment and handover run through Escrow.com. The buyer's money is held until the transfer is done.
  • You pay a success fee out of the sale. The buyer pays no fee to Indiemaker. See pricing.

Indiemaker does not publish sold prices or time-to-sale figures.

When the reports match the payouts and the code builds for someone else, list your app.

Sources

Related: how-to-sell-a-mobile-app, how-much-do-apps-sell-for, transfer/apple-developer-app, transfer/google-play-app

List it when the numbers are ready.

One form, the same fields every buyer reads, from $1,000 to $500,000.