In App Advertising: Formats and User Experience Trade Offs

In app advertising earns money from users who will not pay, but every ad slot spends some of their patience. The format you choose, where it appears and how often matter more than the ad network behind it. The safest approach is to match each format to a natural pause in the app, check it against Apple and Google store rules, and measure its effect on retention before scaling it up.

In app ad formats at a glance

Most ad SDKs offer the same family of formats, although names vary. Google's AdMob documentation, for instance, lists app open, banner, interstitial, native, rewarded and rewarded interstitial formats. The table compares them on the trade off that matters most: how much they interrupt.

Weighing each format against retention

Banners: cheap attention, small returns

Banners rarely drive users away on their own, but they take screen space permanently and are easy to tap by accident when placed near buttons. Keep them away from navigation and primary actions, and avoid them on screens where users type, pay or read sensitive information.

Native ads: fit in, but stay honest

Native ads blend into a feed, which is why they tend to feel less intrusive. The risk is blending in too well. Both stores expect users to be able to tell an ad from content, so a clear label and a visible difference in treatment are essential. In a property or classifieds app, a native ad among listings works only if users never mistake it for a real listing.

Interstitials: only at real pauses

Full screen ads cause the most complaints when they appear while a user is mid task. A good test is to ask whether the user has just finished something. After a completed level, a saved entry or a finished video, an interstitial is tolerable. Before a checkout, a booking or a message, it is not.

App open ads: handle with care

Showing an ad the moment someone opens the app can make the whole product feel slower. If you use this format, limit how often it appears, never show it on a first launch, and skip it when the user arrives from a notification that promises specific content.

Rewarded ads: the user decides

Rewarded ads are usually the most accepted format because the user chooses to watch in exchange for something useful: extra lives, a premium filter for a day, or a bonus credit. They suit app monetisation in games and in utility apps with natural extras. The reward must be delivered reliably, and the core app must remain usable without watching.

Store policies that shape in app advertising

Store rules decide what is allowed and change regularly. The points below come from the official documents; confirm the latest wording before designing placements.

Google Play

The Google Play Ads policy covers disruptive ads in detail. Ads must stay inside the app that serves them, must not imitate app or system interfaces, and must not appear unexpectedly, for example at the start of gameplay or after a user taps a button but before the action happens. Full screen interstitials that cannot be closed after 15 seconds are not allowed, although opted in rewarded ads are treated differently. Apps aimed at children must also meet the separate Families requirements.

Apple App Store

Apple's App Review Guidelines limit display ads to the main app, not widgets, extensions or notifications. Interstitials must be clearly marked as ads, must not trick users into tapping, and need a visible close or skip button. Apps with ads must let users report inappropriate ones. Apps in the Kids Category should generally not include third party advertising, with narrow exceptions. Apple also allows apps to reward users for watching an ad, but not to force store actions such as ratings.

Privacy, consent and native ads

Ad SDKs collect data, so advertising is as much a privacy question as a design one.

• Tracking on iOS. Under App Tracking Transparency, apps must ask permission before tracking users across other companies' apps and websites or accessing the advertising identifier. Users cannot be gated or rewarded for accepting.
• Disclosure on Android. The Google Play Data safety form must reflect data collected or shared by third party code, including ad SDKs.
• UAE law. If you process personal data of people in the UAE, consider the Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, plus DIFC or ADGM rules where they apply. Ask counsel how consent and disclosures should work for your app.

Practically, this means auditing every SDK before it ships, keeping a record of what each one collects, and designing the app so it still earns something when users decline tracking, for example through contextual native ads.

A placement checklist before you ship

1. Map the user flow and mark natural pauses. Only these can host full screen formats.
2. Mark screens that must never carry ads: onboarding, payment, booking, account and support.
3. Set frequency caps per session and per day.
4. Keep tap targets for ads well away from navigation and buttons.
5. Check every placement against the current Google Play and Apple rules.
6. List SDKs, the data they collect and how this appears in store disclosures.
7. Test on slow networks so ads never block content from loading.
8. Run a controlled rollout and compare retention between users with and without the new placement.

Hypothetical example: a UAE fitness app adds an interstitial after each logged workout. Revenue per user rises in the first week, but returning users fall in the test group. The team swaps it for a rewarded ad that unlocks a weekly progress report, and returning users recover while ad revenue continues at a lower level. The test group showed the cost before the whole user base paid it.

When ads are the wrong model

Ads work best with large audiences and frequent sessions. For apps with smaller, high value audiences, such as banking, healthcare or B2B tools, ads can damage trust and add privacy risk for little return. Subscriptions, paid features or simply supporting a core business may suit better. The trade offs differ by sector, as covered in what AI changes in healthcare app development cost and features and cost drivers for property listing apps.

Planning an app with monetisation built in

Codeeo's mobile app development team designs and builds iOS, Android and cross platform apps, and its UI/UX design work covers where monetisation fits in the user flow. If you are still choosing a technology, compare Flutter and React Native by team and product or read about when iOS first makes sense. To talk through an app idea with a team that has delivered 200+ projects across the UAE and the US, get in touch.