Sell a Mobile App Online Without Waiting for an App Store

Most app revenue advice assumes one path: publish to Google Play or the App Store and hope. That path suits apps with a subscription and a marketing budget. It fits badly with the other kind of mobile product — a focused utility, a white-label template, an internal tool — where the buyer wants the build and the source, not an install from a store listing.

This page is about that second market. What a sellable mobile app listing contains, how pricing works when the buyer is an agency rather than a consumer, what to strip out of a build before you upload it, and how the economics compare with the Play Store’s fifteen to thirty percent commission and Gumroad’s ten percent plus payment fees.

The store here charges nothing to list and pays the seller seventy percent of each sale, with a fifty-dollar payout threshold by PayPal or USDT. That is a better share than the stores offer, and a smaller audience — so the honest framing is that this is where you sell a product to a specific buyer, not where you acquire a million users.

Three ways to sell an app, and who each one suits

Publishing to Google Play or the App Store puts your app in front of the largest audience in software, and takes fifteen to thirty percent of each transaction, a developer account fee, and a review process you do not control. It suits consumer apps with retention and a reason to return. It fits poorly with a template, a source-code product or an internal tool that a business wants to run privately.

Selling the build directly — on Gumroad, your own site, or a marketplace like this one — means the buyer gets a file, you keep most of the price, and nobody reviews your binary. It suits utilities, white-label apps, source-code products and anything where the buyer is a business or a developer rather than a phone user browsing a store.

The third path is selling the idea or the codebase to a single buyer: an acquisition rather than a product. That is a negotiation, not a listing, and it needs clean IP, a working build and a buyer who already wants the niche. It is worth knowing about, but it is not what the rest of this page covers.

What an app listing actually contains here

Five things: the build itself (an Android APK), the source archive, real screenshots of the shipped version, the version number and a description of what the app does and who it is for. The listing also carries the licence you are selling under and the price in dollars — the current catalogue runs from five to seventeen dollars, which tells you the shape of the market: small utilities at the bottom, complete tools with source at the top.

Screenshots are the conversion lever, and they have to be of the build being sold. A mockup of a design that never shipped is the fastest way to earn a refund request and a review you cannot recover from. Capture the real screens on a real device, at a consistent aspect ratio, and include one screen that shows the feature the buyer is paying for.

What to remove before you upload — the part nobody warns you about

An APK or source archive is not just code: it carries keys, endpoints and identifiers. Before a build leaves your machine, remove API keys and signing keystores, replace your own server URLs with placeholders, strip analytics identifiers and delete any test account credentials. A published build with a live key is somebody else’s free API quota, and in the worst case it is your bill.

The same applies to third-party assets: fonts, icons and stock images need licences that permit redistribution inside a sold product. If you cannot document the right to redistribute an asset, replace it with one you can — this is the single most common reason an app listing is rejected or taken down later.

Pricing an app when the buyer is a business

Consumer apps price at ninety-nine cents because the store audience is enormous and the decision is impulsive. A business buyer is solving a problem with a cost attached: a five-dollar utility that removes a manual step from a warehouse workflow is not expensive, it is trivially cheap. That is why app listings here sit between five and seventeen dollars rather than at the app-store floor.

Price by what the buyer replaces, not by lines of code. A white-label template that saves an agency a week of build time is worth far more than seventeen dollars to that agency — and pricing it at seventeen is how you get the first ten buyers and the reviews that let you raise it later. Start low, document the build, and raise the price when the reviews justify it.

The comparison: Play Store, Gumroad, and here

Google Play takes fifteen percent on the first million dollars a year and thirty percent after that, requires a developer account and a review, and gives you the store’s discovery engine in return. Gumroad takes ten percent plus payment processing, requires no review, and gives you a checkout link you have to bring traffic to yourself.

This marketplace takes thirty percent and pays seventy, requires a review of the listing, and puts the app in a catalogue alongside prompts and ebooks. It is not the cheapest per transaction — Gumroad is — but it is the only one of the three where a buyer browsing for a tool can find your app without you paying for the click.

Licensing: what the buyer is allowed to do

An app listing sells a licence, not the copyright. The standard position is that the buyer may install, use and modify the build for their own purposes, and may not resell the source as their own product. If you want to allow white-labelling — rebranding and reselling to their clients — say so explicitly in the listing and price it accordingly.

Write the licence in plain language in the description rather than linking to a legal page. “Personal and commercial use, one product, no resale of the source” is understood by every buyer. Ambiguity here is what turns a sale into a dispute three weeks later, and a dispute over a five-dollar product costs more in attention than the sale was worth.

Where the actual demand is

The buyers who purchase apps outside the stores are agencies needing a white-label base, small businesses that want a private tool without a subscription, developers buying a starting point, and resellers in markets the big stores serve badly — offline-first tools, right-to-left interfaces, low-end device performance. Those are the same gaps that make a focused utility worth building in the first place.

That is also the search strategy: describe the app by the job, not the technology. “Offline PDF and Word viewer for Android that never uploads your files” is a listing a procurement officer can find. “Kotlin document viewer” is a listing only another developer will ever read.

Step-by-step

1. Build the APK you intend to sell: Release build, correct version number, tested on a real device. The build is the product — a demo that crashes is a refund, not a listing.
2. Strip secrets and unlicensed assets: Remove API keys, keystores, personal endpoints and analytics IDs. Confirm every font, icon and image may be redistributed inside a sold product.
3. Capture real screenshots: Screens from the shipped build at one aspect ratio, including the screen that demonstrates the main feature. Never use a mockup of an unbuilt design.
4. Package the source archive: Zip the project with a short README: how to build it, which SDK version, what the placeholder configuration values mean. Buyers pay more for a build they can rebuild.
5. Write the licence in plain words: State what the buyer may do: install, use commercially, modify, and whether white-labelling is allowed. State what they may not do: resell the source as their own product.
6. Upload, price and publish: Use the app upload page, set the price between $5 and $17 to start, and submit for review. Keep the listing updated when the build changes, and re-shoot screenshots when the UI changes.

Frequently asked questions

Do I need a Google Play developer account to sell an app here?

No. This is a file marketplace: the buyer receives the APK and the source archive directly. A Play developer account is only needed if you also want to publish in the store.

Can I sell an app and also publish it on Play Store?

Yes, unless you have granted exclusivity — do not. Keep the Play listing for consumers and sell the APK plus source here to buyers who want the build or a white-label base.

What files does the buyer get?

The APK, the source archive with a README, and the screenshots and version details on the listing. The licence you write determines what they may do with the source.

How much of each sale do I keep?

Seventy percent. There is no listing fee and no developer account charge; payouts start at $50 and are made by PayPal or USDT (BEP20).

Is it safe to share my source code?

Only after you strip keys, credentials and personal endpoints, and only under a licence that forbids reselling the source. The risk is not the buyer reading your code — it is a leaked key or an unlicensed asset inside the archive.

Can I sell an app template or white-label build?

Yes, and it is the strongest category here. State explicitly that rebranding and client resale are allowed, price it accordingly, and document the placeholder configuration so a buyer can rebrand without support.

What price should a first app listing be?

Five to seventeen dollars covers the current catalogue. Start in the lower half, document the build well, and raise the price once you have reviews — a buyer who can rebuild the app from your README is worth more than a cheaper download.

How do I keep the listing current?

Ship the new build, update the version number and the screenshots in the same pass. A listing advertising the previous UI is the most common reason a good app stops converting.