Android App Publishing & Ad Monetization: Questions and Answers

It sits in a grey area.

A verified publisher is an established operator with a real track record, clear terms and a contract — not a stranger in a chat group.

Not legitimately.

Because there's no clean way to do it.

No.

A verified publisher first takes your app live on their established console, then uses Google's official app-transfer process to move it to a console you own.

Yes.

Yes.

Always.

Install it on a test device, read the permissions against what the app claims to do, decode the manifest with aapt or apkanalyzer , inspect the code with apktool / jadx , and verify the signature with apksigner .

All three exist: a fixed monthly payout, a per-app fee, or a share of the ad revenue the published apps earn.

New personal Google Play developer accounts must run a closed test with at least 12 testers for 14 continuous days before they can apply for production access.

A D-U-N-S number is a business identifier Google requires for organisation developer accounts.

ConsoleMint is an app monetization company.

It works in two halves.

Publishing an app on Google Play takes five steps: (1) open a Google Play developer account (a one-time $25 fee), (2) build a signed Android App Bundle (.aab), (3) create the app in Play Console and complete the store listing (title,…

Google charges a one-time $25 registration fee to open a developer account — there is no annual renewal (unlike Apple's $99/year).

Yes — every app on Google Play is published under a verified Google Play developer account, and there is no way to list an app without one.

Yes — you can publish through an existing verified developer account instead of opening your own, an arrangement usually called managed publishing .

Most reviews finish within a few hours to 3 days , though Google officially says it can take up to 7 days or longer for brand-new developer accounts or apps that need extra checks.

An APK (Android Package) is the installable file that runs on a device; an AAB (Android App Bundle, .aab) is a publishing format you upload to Google Play, which then generates and signs optimised APKs for each device.

Google Play requires the App Bundle so it can deliver smaller, device-optimised downloads through Play Feature Delivery — users only download the code and resources their specific device needs, cutting download size by around 15% on…

Play App Signing is the system where Google manages your app's signing key and uses it to sign the APKs generated from your uploaded App Bundle.

In Android Studio, choose Build → Generate Signed Bundle / APK , select “Android App Bundle”, create or pick an upload keystore, and build the release .aab.

A complete listing needs an app title (max 30 characters), a short description (max 80), a full description (max 4,000), a 512 x 512 px icon, a 1024 x 500 px feature graphic, at least 2 phone screenshots (up to 8 per device type), a…

App icon: 512 x 512 px 32-bit PNG.

Put your most important keyword in the app title (max 30 characters) and lead the short description (80 chars) with the core benefit plus a primary keyword — both carry the most ASO weight.

The Data safety form is a mandatory declaration in Play Console where you disclose what user data your app collects, why, whether it is shared with third parties and how it is protected.

Since 2023 Google requires every developer to verify their identity — legal name, address, phone and email, plus a D-U-N-S number for organisations — before they can publish.

Most suspensions come from policy violations — malware or deceptive behaviour, impersonation, repeated content-policy strikes, payments fraud, or breaking the Developer Distribution Agreement.

Yes — Google offers an official app-transfer process that moves an app, along with its reviews, installs and history, from one developer account to another without users noticing.

Yes — you can publish through someone else’s verified Google Play developer account, usually called managed publishing .

Yes — no-code and low-code builders such as app builders, WebView wrappers and PWA-to-APK tools can generate a publishable Android App Bundle without writing Java or Kotlin.

No — you can publish as an individual/personal developer or as an organisation .

The Google Play developer registration fee is a one-time $25 payment , not a subscription — you pay it once when you create the account and never again.

Publishing from India follows the same worldwide process: create a Google Play developer account, pay the one-time $25 fee (charged in USD to an international-enabled card), complete identity verification with an Indian address and…

To receive money from paid apps or in-app purchases you need a Google payments profile linked to an Indian bank account, and Google collects your PAN for tax reporting.

A D-U-N-S number is required only for organisation (company) accounts, not for personal/individual developer accounts.

The most common rejection reasons are a missing or invalid privacy policy , a Data safety form that doesn’t match the app’s behaviour , broken or crashing functionality, misuse of permissions, misleading metadata or screenshots, and…

Add a publicly reachable privacy-policy URL that names your app, lists what data it collects and how it is used, then paste that URL into Play Console under Store presence → Store listing and in App content → Privacy policy .

A policy strike is a formal warning Google issues when an app violates a Play policy, and strikes accumulate against the developer account.

“Pending publication” means the app passed review but Google is still propagating it, which normally takes a few hours but can stretch to up to 7 days for brand-new developer accounts.

Personal Google Play developer accounts created after November 2023 must run a closed test with at least 12 testers who stay opted in for 14 continuous days before the app can go to production.

Recruit testers from friends and colleagues, developer communities (Reddit r/androiddev, Discord and Telegram testing-swap groups) or a small paid tester service, then add their Google-account emails to a closed testing track or a…

You cannot waive the 14-day closed test on a new personal account — Google enforces it before granting production access.

The cheapest way is to pay Google’s one-time $25 registration fee and publish under your own account — there is no ongoing charge and no revenue share on free apps.

The realistic alternatives are three: publish through an established developer account (an agency or a publisher) and later transfer the app to yourself; register an organisation account , which skips the 12-tester rule but needs a…

Not directly — every app on Google Play sits under some verified developer account , so an app cannot exist without one.

Yes, and it happens constantly — agencies, studios and publishers ship client apps under their own account every day.

Buying an account is far riskier than publishing through one .

No — an “aged” account is the most dangerous thing to buy, because age is exactly what makes it attractive to resellers who sell the same account more than once.

You can avoid paying it yourself , but somebody has paid it — the fee is charged once per developer account, so publishing under an existing account means it is already covered.

The fastest legitimate route is to publish under an account that is already verified and past the 12-tester gate — then your only wait is Google’s review, usually a few days.

Yes.

Freelancers generally use one of three routes: get added to the client’s console as a user with release permissions (best when the client already has an account), publish through a publisher or agency partner and transfer the app to the…

Yes — use Users and permissions in Play Console to invite them by Google account and grant a scoped role such as Release manager (upload and roll out builds) or Store listing manager (edit the listing only).

Yes — Google Play does not care which tool built the app, only whether it meets policy.

Yes, but a plain WebView wrapper around a website is the single most-rejected app type under Google’s Minimum Functionality / repetitive-content policy .

Most reviews finish in a few hours to 7 days .

A typical free Android app earns roughly $0.50–$3.00 per 1,000 daily active users per day from in-app advertising, which works out to about $15–$90 per 1,000 DAU per month .

eCPM is effective cost per mille — the ad revenue an app earns per 1,000 ad impressions.

Rewarded video earns the most per impression, interstitials are second, and banners are the lowest.

Ad mediation is a layer that asks several ad networks for a bid on the same impression and serves whichever pays most.

Above 95% is healthy for banners and interstitials; 70–90% is normal for rewarded video.

Indian traffic typically earns $0.30–$1.50 eCPM on banners and $1–$4 on interstitials, with rewarded video reaching $2–$6.

Expect meaningful ad revenue from roughly month three, not week one.

An ad revenue share agreement pays each party a fixed percentage of the in-app advertising income an app generates, instead of a flat fee.

The app listing lives under the publishing partner's verified Google Play identity, while the code, brand and assets stay with whoever built them.

No — past a point, extra ads reduce total revenue by driving users away.

app-ads.txt is a plain text file you host on your developer website that lists which ad networks are authorised to sell your app's ad inventory — and yes, any app running programmatic ads should have one.

AdMob approval normally takes a few days, and the common rejection reasons are an app that is not yet publicly available, thin or placeholder content, and a mismatch between the account identity and the Play Console developer identity.

Because Google detects ad clicks or impressions it judges were not genuine user interest — most often the publisher clicking their own ads, asking friends to click, or traffic bought from a low-quality install source.

AdMob pays monthly once your balance passes the $100 payment threshold, with payments normally issued between the 21st and 26th of the following month.

No — clicking a live ad in your own app is the single fastest way to get an AdMob account disabled.

A sudden ad revenue drop is almost always one of five things: a seasonal advertiser-spend fall, a change in the country mix of your users, a broken or misconfigured ad unit, a policy restriction placed on the app, or an invalid-traffic…

None of them wins outright — AdMob tends to lead on banner and interstitial demand breadth, Unity Ads and AppLovin usually beat it on rewarded video in games, and the highest earners run all three through mediation rather than choosing.

CPM is what an advertiser pays per 1,000 impressions, eCPM is what the publisher actually earns per 1,000 impressions after fill and mediation, and RPM is revenue per 1,000 sessions or users rather than per impression.

Roughly 1,500 to 3,500 daily active users for a US-heavy audience, and 15,000 to 50,000 for an India-heavy one.

Yes — if your app serves ads to users in the European Economic Area or the UK, Google requires you to gather consent through a Google-certified Consent Management Platform.

Apps aimed at children may only use ad SDKs Google has certified for families, must not show interest-based or remarketing ads, and must keep ads clearly separated from app content.

Advertising earns a small amount from almost every user; in-app purchases earn a large amount from a very small minority — and for most non-game utility apps, advertising is the more reliable of the two.

ARPDAU is average revenue per daily active user — total daily revenue divided by daily active users — and the fastest ways to raise it are format mix, mediation and placement, in that order.

Match rate is the share of ad requests that a network returns an ad for; fill rate is the share of requests that end in an ad actually being served to the user.

Create an AdMob account, register the app, add the Google Mobile Ads SDK dependency, put your AdMob app ID in AndroidManifest.xml, then create ad units and load them with test ads until release.

Yes — running several ad networks in one app is normal and encouraged, provided you route them through a mediation layer rather than calling each one directly.

An app monetization company places ads inside an app and turns those ad impressions into a revenue stream for whoever owns the app or the account it is published under.

For developers who already have an app, AdMob, AppLovin MAX and Unity Ads (via mediation) remain the standard stack; for a Google Play account holder who wants ad revenue without building an app, ConsoleMint is the only…

A standard ad network keeps a mediation/platform cut and pays the rest to whoever owns the ad units, typically 60–80% to the publisher depending on the network and format.

There is no single benchmark because it depends entirely on country mix and ad format, but a rough planning range is $1–$5 of monthly ad revenue per 1,000 active installs for a US-heavy audience, and a fraction of that for India-heavy…

Yes — this is exactly what ConsoleMint does: it designs, builds, publishes and maintains Android apps, then monetizes them with in-app advertising and shares that ad revenue with the publishing partner whose Google Play account…

By becoming a publishing partner for a company that builds and maintains the apps and monetizes them with ads — you supply the account, they supply the product and engineering work.

A written revenue-share agreement should specify the access being granted, the payout schedule, how the split changes over time, and the notice period to end it — not just a headline percentage.

In a build-and-monetize partnership, the company that built the app carries that cost, not the publishing partner.

Fixed payout is better while an app is new and unproven; revenue share is better once it has real installs and ad traffic — which is why the strongest structures use both, in sequence.

Either hire a developer to integrate an ad SDK and mediation for you, or work with a company that already owns and monetizes an app catalogue and shares the resulting ad revenue with account holders.

Published rates run roughly ₹3–7 lakh a year, depending on account age, app count and install volume — older or organisation-type Play accounts earn faster because they reach install scale sooner.

Scoped Developer-role access to the Google Play Console — never owner access, and never a password.

Yes — ConsoleMint is a registered Indian business (UDYAM-KR-03-0305777, Ministry of MSME) operating from Innov8, Mantri Commercio, Tower A, 5th Floor, Devarabisanahalli, Bengaluru, Karnataka 560103, with a published phone/WhatsApp…

Use AdMob if you already have a live app and just need ad demand; use ConsoleMint if you have a Google Play developer account but no app and no engineering team to build one.

Unity Ads and AppLovin are ad networks and mediation platforms that monetize apps someone else already built; ConsoleMint builds and publishes the app first, then monetizes it.

If you already have an app, the alternatives are ad networks and mediation platforms — Google AdMob, Unity Ads, AppLovin MAX, ironSource/Liftoff and Digital Turbine — plus in-app purchases as a non-ad option.

Yes — ConsoleMint publishes USD-native payout terms alongside its India/INR rate card, so it works with international Google Play account holders, not only India-based partners.

You can revoke ConsoleMint's Developer-role access to your Google Play account at any time, with 30 days' notice — the account was never transferred, so nothing needs to be handed back.

Any Google Play developer account in good standing qualifies, but the payout structure differs by account age and type.

Yes — up to 10 apps per publishing-partner account.

ConsoleMint states a 24–48 hour review turnaround on its side before an app is submitted, separate from whatever queue time Google Play's own app review adds afterward.

Productivity, utility and business apps that meet Google Play policy — not games, and not apps in restricted categories.

A publishing partner is a developer or business with a Google Play developer account in good standing whose account distributes apps that someone else builds and monetizes.

Yes — the partner owns the Google Play developer account permanently; ConsoleMint only ever holds scoped Developer-role access to it.

Grant the narrowest role that lets them release and manage store listings, never the account owner role, and never share the Google login itself.

Payouts are made between the 1st and 5th of each month, by UPI or bank transfer, with an earnings statement.

Payouts are reviewed on a performance schedule roughly every 45 days, and step up as installs and ad revenue grow.

Only the ramp-up payout is fixed; everything after it is performance-driven and not guaranteed.

Newer personal accounts move through four stages from a fixed ₹8,000–10,000 a month up to ₹50,000–80,000 a month in the mature stage, while established or organisation accounts are paid ₹5,000–7,000 per app per year.

You need a Google Play developer account in good standing; you then contact ConsoleMint, grant scoped Developer-role access, and the first app goes through a 24–48 hour review before it is published.

ConsoleMint's publishing cadence is 3–5 apps a week, with a peak of 7.

ConsoleMint grows revenue by adding apps to the partner's account, up to the 10-app ceiling, and by letting installs on existing apps accumulate.

Very little product work: the partner keeps a Google Play developer account in good standing, grants scoped Developer-role access, and keeps receiving payouts.

No — the partner does not need to code, run ad mediation or tune eCPM; ConsoleMint does all of that.

Because a brand-new app has almost no installs, so its ad revenue on day one is close to zero, and ConsoleMint chooses to carry that ramp-up risk instead of the partner.

ConsoleMint uses both, matched to the account: a flat per-app yearly fee for established or organisation accounts and a staged fixed-then-revenue-share payout for newer personal accounts.