Lorixen.
EN

One-Time Purchase or Subscription for a Small App?

Short answer: Choose a subscription when your app has costs that recur every month, such as servers, data feeds, messaging fees or ongoing support, and when customers keep getting new value. Choose a one-time price when the app is mostly finished, its running costs are small, and customers mainly want a tool they can keep. Many small apps end up with a hybrid: a one-time purchase for the core app, with a paid upgrade or an optional subscription for the features that carry real monthly cost. Work through the worksheet below with real numbers before you set the price in either store.

Start from your running costs

The price should cover what the app costs to keep working, plus a margin for the time you spend on it. Begin by listing every cost that recurs, in one column, and every promise you make to customers, in another.

Costs usually include:

  • Hosting for any backend, database or file storage
  • Push notification or messaging fees
  • Map, payment or data service charges that scale with usage
  • Developer account fees, which are paid each year on each store
  • Support time, bug fixes and platform updates

Promises usually include:

  • Updates for new operating system versions
  • Bug fixes within a stated time
  • Access to new features as they are released
  • Support by email or chat

A one-time purchase means you take on all of those promises forever, paid from a single sale. A subscription spreads the cost across the months a customer keeps the app, but it only works if the customer keeps getting value.

A worksheet with example numbers

The figures below are invented to show how the calculation works. Replace them with your own.

Item Example figure per year
Hosting and storage 240
Messaging and push fees 360
Store and developer account fees 150
Support and updates, 40 hours at an hourly rate of 50 2,000
Total running cost 2,750

Now look at the price. If the app sells for a one-time 20, you need 138 sales in the first year just to cover the running costs, before counting any income for yourself. If the app has 40 buyers in the first year, the one-time model cannot cover the cost of keeping them served. In that case a subscription at 4 per month, for example, brings in 160 per year from each subscriber who stays the full year, which is a more honest match for the workload.

These are only examples, but the method holds. Divide your yearly cost by the net amount you receive per customer, then ask whether the number of customers you expect can cover it.

Questions that decide it

Answer these five questions honestly:

  1. Does the app's value grow or refresh each month, such as new content, new data or new features?
  2. Does it rely on a server or a third-party service that charges by usage?
  3. Would your customers accept paying monthly for it, or do they expect a one-off tool?
  4. Could a competitor offer the same thing for a single price?
  5. Do you want to be responsible for supporting the app for the full life of the purchase?

If most answers point to recurring value and recurring cost, a subscription is the better fit. If most point to a finished tool with low running costs, choose a one-time purchase.

Hybrid options

Between the two sits a range of models that many small apps use successfully:

  • Core app free, paid upgrade once. Customers download the app for nothing and pay once to unlock the full feature set. This suits tools that are useful at first and grow with the customer.
  • One-time purchase plus an optional subscription. The app itself is a single purchase, while a separate subscription covers cloud sync, data feeds or messaging. Only the customers who need the recurring feature pay for it.
  • Lifetime tier. A higher one-time price that promises updates for a stated period. Be specific about what "lifetime" covers, because customers will hold you to it.

Each model needs a store setup that matches it. Non-consumable purchases, consumable purchases, auto-renewing subscriptions and free apps with in-app purchases are set up differently in each store. Read the current store documentation before you choose, because the categories and their rules are part of the store's terms.

Customer expectations

Customers judge pricing on the feeling of fairness. A one-off price can feel generous if the app is complete and reliable. It feels risky if the customer thinks the app will stop working in a year. A subscription feels reasonable when the customer can see the monthly service being delivered, such as new content or data, and it feels like a trap when the app does almost nothing new after the first month.

Make the promise visible on the store page. Explain what the price includes and what the customer will receive over the next twelve months. Short, specific wording does more than a long list of benefits.

Store rules to check

Both major app stores have rules for how subscriptions and purchases work, including how a customer cancels, how trials convert, and how refunds are handled. The rules also affect how much you keep after the store's commission. Check the current subscription and in-app purchase documentation in each console before you launch, since the terms and the fee arrangements change over time.

Steps to decide

  1. List recurring costs and recurring promises in two columns.
  2. Estimate the yearly running cost with real quotes where you have them.
  3. Calculate how many sales or subscribers you need to cover that cost.
  4. Compare that number with a realistic estimate of your first-year customers.
  5. Choose the model that covers the cost with a margin you can defend.
  6. Price a test version and review refunds, cancellations and feedback after the first month.

FAQ

Is a subscription always better for income?

No. A subscription produces steady income only if customers stay. A strong one-time purchase can earn more in the first year, especially for a tool that people use once a year or for a short project.

Can I change the model after launch?

Yes, but it is harder than starting with the right one. Existing customers will react to a change, so announce it in advance, explain what they keep, and avoid removing features they already paid for.

What if my app has almost no running costs?

A one-time purchase is often the best fit. Keep the price clear, state the promise of updates, and consider a paid upgrade for major new versions.

Should I offer a free trial?

A trial helps customers judge value, particularly for subscriptions. Make it clear when it ends and how to cancel, because confusion at that point drives refunds and poor reviews.

If you want a second opinion on your numbers before you set a price, tell us what the app does and what it costs to run, and we will work through the model with you: talk to us.

Sources

WhatsAppBook a call