Mobile App Monetization Models That Work in the UAE

Most founders can tell you what their app does. Far fewer can tell you, in one sentence, how it will earn money. That gap is where promising apps run out of runway. This guide to mobile app monetization models in the UAE explains the main ways an app makes money, which models suit which kinds of business, what the numbers tend to look like, and how to combine them without annoying your users.

We build apps for UAE businesses across delivery, bookings, marketplaces, real estate and services, so the examples lean towards what we see in this region. We do not have a magic formula, and we will not pretend that one model always wins. We will show you how to think about it.

Start with the question, not the model

Before comparing models, answer four plain questions.

1. Who pays? The user, a business, or a third party?
2. What are they paying for? A product, a service, convenience, access, or attention?
3. How often? Once, occasionally, or every month?
4. What is the alternative? If a customer can get the same thing for free elsewhere, your model has to offer a reason to pay.

The answers usually narrow the field to two or three models. Choosing among those is much easier than starting from a list of seven.

1. Commission on transactions

In a marketplace or on-demand app, you take a percentage each time a transaction happens through the platform. Ride-hailing, food delivery, home services, property and many booking apps work this way. See our article on how Careem makes money for a well-known regional example.

How it works

The customer pays through the app; you keep a share and pass the rest to the provider. The commission rate depends on how much work you do (matching, payments, support, delivery) and how competitive the category is.

Strengths

• Your revenue rises with the value flowing through the platform.
• Providers pay only when they earn, which lowers the barrier to joining.
• It fits naturally with in-app payments and ratings.

Watch out for

• Disintermediation. Once a customer and provider have met, they may arrange the next job outside the app to avoid your fee. Good products make staying in the app worthwhile with payment protection, insurance, reviews, scheduling and repeat booking tools.
• Two audiences to win. You need both supply and demand, which makes launch harder and more expensive.
• Rate pressure. A competitor with a lower percentage can pull providers away.

Source: Arka Softwares guidance for maintenance after launch.

2. Subscriptions

Users pay a recurring fee for ongoing access to content, a service or a set of features. This works for fitness, learning, media, software tools and membership clubs.

When it fits

Choose a subscription when the value is delivered continuously and customers would feel the loss if it stopped. A learning app with a steady stream of lessons fits. An app people use twice a year does not.

Design decisions

• Free trial or freemium? A trial lets people try everything for a short time; freemium offers a limited free version forever. Trials usually convert a higher share of those who stay, while freemium builds a bigger audience.
• Monthly vs annual. Annual plans reduce churn and improve cash flow, so most apps offer a discount for them.
• Tiers. Two or three clear tiers are easier to understand than five.

Watch out for

• Churn. Monthly subscribers leave if they stop seeing value. Track how many cancel each month.
• Store fees. Digital subscriptions bought inside an iPhone or Android app generally go through Apple's or Google's billing, with a commission. Build that into your price.
• Content costs. If you must keep producing new content, the subscription needs to cover it.

3. Selling products directly

If you already sell physical goods, the app is a sales channel, not a business model of its own. Fashion, groceries, electronics and beauty fall here, as in our article on building an ecommerce app like Namshi.

Strengths

• Clear margins you already understand.
• Direct relationship with customers and their data.
• App-only offers can encourage downloads and repeat visits.

Watch out for

• Logistics. Delivery, returns and stock accuracy decide your reputation.
• Customer acquisition cost. Winning shoppers is expensive. Repeat purchases make or break the economics.
• Marketplace competition. Big platforms offer shoppers more choice, so you need a reason for people to come to you.

Physical goods and real-world services are generally outside the store commissions that apply to digital content, which is part of why they suit the payment methods your customers already use. Confirm the details against the current store policies for your case.

4. In-app purchases

Users buy digital items inside the app: extra features, virtual goods, premium content or one-off unlocks. Games are the best-known case, but productivity, photo and learning apps use it too.

Types

• Consumables are used up and bought again, such as credits or boosts.
• Non-consumables are bought once and kept, such as removing ads or unlocking a tool.
• Time-limited access sits close to subscriptions.

Watch out for

• Stores take a commission on digital purchases, and they require their own billing system for most digital goods.
• Rules around randomised rewards, children and spending limits are strict. Read the policies and your local regulations.
• If a small group of heavy spenders carries the revenue, you depend heavily on a few people.

5. Advertising

Show ads inside the app and earn from impressions, clicks or installs. It suits apps with large audiences and frequent use, such as news, games, entertainment and utilities.

The honest maths

Revenue per user from ads is usually small, so this model needs scale: a lot of active users, not just downloads. If you expect a few thousand users, ads will not fund a team.

Ways to run it

• Ad networks sell the space for you. They are quick to add but you control little.
• Direct sponsorships sell placement to local brands. They earn more per user, but need a sales effort.
• Promoted listings inside a marketplace let sellers pay for better visibility, a model that sits between advertising and commission.

Watch out for

• Too many ads drive users away, especially in a premium or professional product.
• Privacy rules on tracking and consent affect how well ad targeting works.
• Ad content in Arabic and English, and local advertising standards, need care.

6. Listing and lead fees

Businesses pay to list themselves or to receive enquiries. Property portals, job boards, car marketplaces and service directories do this. Our guide on building a property search app like Bayut shows how listings shape a product.

Variations

• Pay per listing or per month for a seller to be visible.
• Pay per lead when a buyer contacts the seller.
• Featured placement that costs extra for top positions.

Strengths and risks

Revenue does not depend on closing a transaction inside your app, which avoids the leakage issue. But you must prove that leads are real and valuable, otherwise advertisers stop paying. Quality and moderation matter.

7. Licensing and white label

You build a platform once and licence it to other businesses, sometimes under their own brand. It suits SaaS-style products: booking systems for salons, fleet tools, school apps, property management. It overlaps with software subscriptions, but the customer is a business.

Strengths

• Higher prices per customer than consumer apps.
• More predictable, recurring income.

Watch out for

• Sales cycles are longer, and support and onboarding take real effort.
• Each customer will want customisations, so protect your core product.

8. Hybrid and other models

Real products often mix models. A food delivery app may take commission from restaurants, charge a delivery fee, sell promoted placement and run a subscription for free delivery. A learning app might offer a free tier, a paid subscription and one-off course purchases.

Other models you may meet include:

• Data and insights sold in aggregate to partners (only with clear consent and careful legal advice).
• Sponsorship by a brand that wants to be associated with your audience.
• Donations and tips, rarely a main income source for a business app.
• Affiliate links that pay when a user buys through a partner.

Comparing the models at a glance

Model	Best for	Needs	Main risk
Commission	Marketplaces, on-demand	Supply and demand, in-app payments	Users move off-platform
Subscription	Continuous value	Regular content or service	Churn
Product sales	Retailers	Stock, delivery, returns	Acquisition cost
In-app purchases	Games, tools	Digital goods people want	Store fees, rules
Advertising	Large audiences	Scale and engagement	Low revenue per user
Listing and lead fees	Portals, directories	Trusted traffic	Lead quality
Licensing	Business software	Sales and support	Customisation demands

Match the model to your type of app

• Food and grocery delivery: commission from merchants, delivery fees, promoted listings.
• Home services (cleaning, handyman, car wash): commission or booking fee. See our breakdown of how car wash apps make money.
• Property: listing fees, featured placement, lead generation.
• Taxi, courier and logistics: commission plus surge or priority fees.
• Fitness, learning and media: subscription, sometimes with a free tier.
• Ecommerce and retail: product sales with loyalty tools.
• Fantasy sports and gaming: entry fees or in-app purchases, subject to strict local regulations. Our guide to fantasy sports app development in the UAE covers what to check.
• Business tools: licence or subscription per business.

Pricing in the UAE market

Local habits matter. A few observations that tend to shape pricing decisions here:

• Payment methods. Cards and wallets are widely used, but cash on delivery is still common in some categories. Plan for the methods your customers actually use. Our article on payment options for UAE apps covers the options.
• Price awareness. Shoppers compare quickly and respond to offers. Promotions are a standard part of retail and food apps.
• A mixed audience. The UAE has many nationalities and income levels. Segments may react very differently to the same price, so test.
• VAT. Show prices clearly, with VAT treated as the rules require for your category.
• Language. Pricing pages and checkout in Arabic and English reduce drop-off.

Unit economics: a simple way to check your model

Three numbers tell you if the model can work.

1. Customer acquisition cost (CAC): how much you spend on marketing and sales to win one paying customer.
2. Lifetime value (LTV): the profit you expect from that customer over their time with you.
3. Payback period: how many months until a customer has earned back their acquisition cost.

A common rule of thumb is that lifetime value should be a healthy multiple of acquisition cost, and payback should be short enough that your cash does not run out first. The exact numbers depend on your sector, so treat any benchmark with caution and calculate your own with real data after launch.

Here is a made-up example to show the arithmetic. Suppose it costs AED 40 in marketing to win a customer, the average order earns you AED 15 in commission, and a typical customer orders six times in their first year. Their first-year value is AED 90, more than twice the acquisition cost. If instead customers ordered only twice a year, the value would be AED 30 and you would be losing money on every new customer. The point is not the figures; it is that a small change in repeat behaviour decides everything.

Source: Arka Softwares delivery process.

A worked example: a home services marketplace

To make the ideas concrete, here is an illustrative case. The numbers are invented to show the arithmetic and are not a forecast.

Imagine an app where customers book home cleaning. The average booking is AED 200. The platform keeps a 20 percent commission, so AED 40 per booking, before costs. Payment processing takes roughly a few percent of the booking, support and refunds take a little more, and a share goes to marketing. After those costs, perhaps AED 20 to 25 of each booking is left as contribution.

Now add behaviour. If the average customer books four times in the first year, the contribution per customer is about AED 80 to 100. If winning that customer cost AED 60, the first year is profitable but not hugely. If they book eight times, it becomes comfortably so. The plan therefore has two jobs: reduce acquisition cost, and increase repeat bookings through reminders, saved preferences, packages and a good first experience.

Notice how the commission rate is only one lever. A one-point change in commission matters less than getting an extra booking per customer. That is why strong products invest in rebooking features, ratings, and trusted providers instead of obsessing over the percentage.

Launching a two-sided marketplace

Commission and listing models share a hard start: you need providers before customers will come, and customers before providers will stay. Founders usually solve this one side at a time.

• Start narrow. One city, one category, one neighbourhood cluster. Density beats breadth.
• Win supply first if supply is scarce (skilled technicians, drivers), or demand first if supply is plentiful (restaurants, shops). Ask which side is harder to find.
• Do some of the work by hand. Early on, your team can match requests manually. It is not glamorous, but it teaches you what to automate.
• Offer something to the scarce side. Low or zero commission for the first months can attract the first providers, as long as you plan the move to normal rates.
• Protect trust. Verification, ratings and responsive support matter more in a young marketplace than any feature.

The right monetization model is partly a function of this stage. Early on, you may charge nothing and focus on liquidity. Once transactions are flowing, introduce fees gradually and explain the value they pay for.

Subscriptions: the numbers that matter

If you choose a subscription, track a small set of metrics from day one.

• Trial-to-paid conversion: of people who start a trial, how many pay.
• Monthly churn: the share of subscribers who cancel each month. Small improvements compound.
• Average revenue per user (ARPU): total subscription revenue divided by paying users.
• Lifetime value: roughly ARPU multiplied by the average months a customer stays, minus the cost of serving them.
• Involuntary churn: payments that fail because a card expired. Simple retry and reminder flows recover a surprising share of these.

Simple actions often help more than new features: a good onboarding flow, reminders that bring people back, a pause option instead of cancel, and an honest cancellation process. Hiding the cancel button may save a few customers briefly and costs trust and store approvals in the end.

Promotions, loyalty and referrals

Discounts are a normal part of retail and food apps in the region, but they are a tool, not a model. Use them with purpose.

• First-order offers lower the barrier to trying you. Set a cap so heavy bargain hunters do not drain your budget.
• Loyalty points reward repeat behaviour and are easy to understand. Track the cost of redeemed points like any other discount.
• Referral rewards turn happy customers into a low-cost acquisition channel. Make the reward valuable to both sides and easy to claim.
• Limited-time offers create urgency, but overuse trains customers to wait for a deal.

Build the admin tools to create, schedule and limit promotions without developer help. It is one of the most useful features a business owner can have, and it is easy to overlook in the first scope.

Payments, payouts and refunds

Whichever model you choose, money has to move correctly. Plan these pieces:

• Collection: accepting cards, wallets and, where relevant, cash on delivery with reconciliation.
• Splitting: in a marketplace, calculating the provider's share and your commission on each order.
• Payouts: paying providers on a schedule, with statements they can understand.
• Refunds and disputes: clear rules, quick handling, and records for accounting.
• Invoices and VAT: producing documents that match the requirements for your business.
• Reporting: daily and monthly summaries for your finance team.

These back-office features cost real development time, and they are often missing from first quotes. Ask about them when you compare proposals. Our article on mobile app backend architecture explains where this logic lives.

Regulation and sensitive categories

Some categories need extra care. Handling money on behalf of others, running prize-based games, collecting health data or offering financial products can bring licensing and compliance duties in the UAE and other countries where you operate. Rules differ by emirate, free zone and sector, and they change. Get advice from a qualified local professional before you build revenue features in these areas, and write the requirements into your scope so your developers design for them from the start.

Four illustrative revenue mixes

These are examples of how a blend can look. They are not forecasts or client results.

Restaurant ordering app for one brand

Product sales through the app, a loyalty programme, and app-only offers. No commission, since the restaurant is the seller. The app's job is to lift repeat orders and reduce dependence on third-party delivery platforms.

Multi-vendor delivery marketplace

Commission from merchants, a delivery fee from customers, and paid promotion for merchants who want visibility. A subscription for free delivery can be added once customers order often.

Property search platform

Listing fees for agents, featured placements, and lead packages. Consumers use it for free, so the product must stay genuinely useful to them or the agents lose their audience.

Learning app

A free tier for a taste, a monthly or annual subscription for the full library, and occasional paid courses. Retention depends on regular, high-quality content.

Common questions

Should my first version include payments?

If payment is the core of the value, yes. If you are testing demand, you can sometimes start with manual invoicing or cash on delivery and add online payments once usage is proven. Weigh that against the trust and convenience that online payment brings.

How much commission is reasonable?

It depends on how much work you do and what alternatives exist. A platform that only introduces people can charge less than one that handles payments, delivery and support. Look at comparable apps in your category and test with early partners.

Can I change my model later?

Yes, but changes are easier before you have lots of users who expect something different. Announce changes clearly, give people time, and explain what they gain.

Is an ad-supported app realistic for a small business?

Rarely as the main income. Ads need big audiences. A better fit for a small business app is a direct model: sales, bookings or subscriptions.

Do I need a separate admin panel for revenue settings?

You almost always do. Rates, fees, promotions and payouts should be controlled by your team through an admin panel, not by asking developers for a new release.

How do I know if the model is working?

Watch repeat behaviour, net revenue per customer, and payback on acquisition cost. If these improve month by month, you are on the right track. If they stay flat, adjust the product or the price, not only the advertising.

Store rules and fees to check

Apple and Google publish policies on what you can sell in an app and how you must take payment. In broad terms, digital goods and subscriptions consumed inside the app generally go through the store's own billing and carry a commission, while physical goods and real-world services do not. Smaller developers may qualify for reduced rates. These rules change, so read the current App Store Review Guidelines and Google's Play Console policies before you finalise your pricing and checkout design. Our launch checklist includes a section on this.

Phasing: what to build first

Do not build every revenue feature in version one. A sensible order for many apps looks like this:

1. Launch with one clear model that you can explain in a sentence.
2. Measure conversion, repeat use and revenue per user for a few months.
3. Add a second stream that builds on existing behaviour, such as promoted listings after you have traffic, or a subscription after you have regulars.
4. Retire what does not work. Features that no one pays for are maintenance burden.

This phasing also keeps the first build affordable. For budget context, see our guide on app development costs in Dubai, and remember to include yearly maintenance in your plan.

Cheap ways to test your pricing before you build

You do not need a finished app to learn whether people will pay. Several low-cost tests give you real evidence.

1. Talk to ten potential customers. Ask what they pay now for the same job, what annoys them, and what price would feel fair. Listen for the problem, not for compliments.
2. Run a landing page test. Describe the product and the price, add a sign-up or pre-order button, and send a small amount of targeted traffic. The share who click tells you something real.
3. Do it manually first. Take bookings through WhatsApp and a spreadsheet for a few weeks. If customers pay and come back, you have found demand. If they do not, you saved a build.
4. Offer two price points to different small groups and compare conversion. Change one thing at a time.
5. Ask for a deposit. A small commitment is a stronger signal than a promise.

Record what you learn and share it with your development partner. The evidence helps you decide which revenue features belong in version one and which can wait, and it keeps the first scope focused. The same discipline applies when you write requirements; see our guide to the mobile app requirements document.

One last reminder. A monetization model is a living decision. Markets change, competitors copy you, and customers surprise you. Review the numbers every quarter, talk to your users, and be ready to adjust. The goal is not to find the perfect model on day one; it is to learn faster than your competitors do.

Mistakes to avoid

Choosing "free for now, we will figure it out later"

Free can be a strategy, but only with a clear plan for how the money arrives. Without one, users get used to not paying and a later change can be painful.

Stacking too many models

Subscriptions, ads, purchases and fees at once make the product confusing. Start simple.

Ignoring the costs behind the revenue

Payment processing, store commissions, delivery, support and refunds all eat into the headline figure. Model net income, not gross.

Setting prices without testing

A price chosen by guesswork is a hypothesis. Run simple experiments with small groups where possible.

Forgetting trust

People pay when they trust you. Clear pricing, no hidden charges, honest reviews and good support matter more than clever tricks.

Questions to ask your development partner

• Which payment and billing features does my model require, and what do they cost?
• Can the admin panel change commission rates, fees and promotions without a new release?
• How will you report revenue, refunds and payouts?
• What analytics will show me conversion and repeat use?
• How does your design handle the store rules for my type of product?

It is also worth deciding early whether the app is native, cross-platform or a PWA, because payment and store options differ between them.

Wrapping up

There is no best monetization model, only a best fit. Begin with how value moves in your business, choose a single primary model, check the store rules, and measure honestly. Add more only when the first one works. If you would like a second opinion on your plan, our team can review your idea and walk through the revenue features it needs. Start with our mobile app development service or the complete guide to mobile app development in the UAE.