Same title, same description, twenty-plus accounts: how a Vietnamese PDF reader got onto a UK utilities chart

PDF Viewer - PDF Reader was published in Aug 13 and got only 3,851 installs in its first two months. In Oct 8 it shipped an update, and three weeks later it reached 217k installs. In Oct 29 it hit #5 on the Australia Google Play utilities free chart and #6 in the UK and Sweden. It is word-for-word identical to an app with the same name and description, behind which sits a whole PDF template that gets relaunched under a new account. Below we explain where its installs came from, how the money comes back, and why you shouldn't build the twentieth-plus PDF app.

A review: without the update, you can't use YouTube

In Oct 25, a user named Douglas Wright left a comment on its store page:

"It interferes with YouTube. Unless you update this program, you can't use YouTube."

37 people marked it helpful, putting it at the top of the reviews. In Nov 4 another came in: "PDF update notifications bombard me day and night, I'm sick of it, leave us alone."

A PDF reader that can stop you from using YouTube means it's showing overlays over other apps and pushing notifications urging "upgrade." That's not a bug; it's how apps like this make money.

What it is

Features are the usual PDF toolkit: open PDF, Word, Excel and PPT files, highlight and annotate, scan documents with the camera into PDFs, convert Word / Excel to PDF, merge and split, and file management. The store page is labeled "Contains ads, in-app purchases." Before Nov 3, in-app purchases ran $19.99 to $29.99; afterward a cheaper $3.29 tier appeared (Google Play store page, 11-06), which looks like a test of subscription pricing.

The developer is named AstraMobi. The "About the developer" section lists an individual in Kim Long town, Khanh Hoa province, Vietnam; the support address is a personal gmail; the "website" is a free subdomain on app-ads-txt.com, which only hosts the app-ads.txt file for ad networks and isn't a real site; the privacy policy is on Google Sites. The same account also publishes find-my-phone, photo recovery and file cleaner apps, the standard combination of small utility ad apps.

How fast it grew

(Before Oct 29, the figures are third-party AppstoreSpy estimates; after that, they're Google Play page numbers.)

The chart tells the same story. Oct 29 was the peak: #5 in Australia's utilities free chart, #6 in the UK, #6 in Sweden, #9 in Canada, #19 in the Netherlands, and #81 on the UK overall chart. By Nov 6 it was down to #53 in the UK, #56 in Sweden and #98 in Australia, and it had dropped out of Canada.

One more number tells the story: installs grew from 76k to 217k, an increase of 140k, while ratings only went from 237 to 282, an increase of 45, averaging two to ten a day regardless of how installs moved. The rating count is only 0.13% of installs; a tool app people actually use typically has one order of magnitude more. Most people who came in installed it and forgot about it.

Where users come from

Ad buys, on and off (inferred). It had almost no growth for two months after launch. Within two weeks of the update, daily installs jumped from a few hundred to 40k a day, then fell back to a few thousand within another week. That's the shape of "turn on budget, climb the charts, turn off budget." Installs concentrated in the UK, Australia, Sweden, Canada and the Netherlands, the highest-CPM markets, not in India, Indonesia and Brazil, where PDF tool demand is naturally largest. Meta's ad library has no record of it, so the most likely channel is Google App Campaigns, which is how most Vietnamese tool apps buy (not verified).

The title is the search term. "PDF Viewer - PDF Reader" are the two most-searched terms in this category, and the package name also stuffs in pdfeditor and pdfreader. Once it breaks into the top 10 of the tool charts, people browsing the charts and searching "pdf" will pick it up along the way.

One template, lots of accounts. This is the part worth looking at. On Google Play there are at least twenty-some PDF apps with package names like com.<brand>.pdfeditor.pdfreader, or the reverse, whose websites are all free app-ads-txt.com subdomains. They went live one after another from April 2025 to October 2026. Spot-checking 7 of them, every developer is a Vietnamese individual with a gmail address. The BitCraft one has the same title, "PDF Viewer - PDF Reader," and an identical description, word for word.

Each account is bought against separately and judged separately on payback. The ones that work get more budget (PDF ProX already has over 30 million installs); the ones that don't get swapped for the next one. Spreading across many individual accounts means one ban doesn't drag the others down. AstraMobi is only mid-to-low in this setup; several of the same-template accounts are 5 to 10 times bigger.

Where the money comes from

Banner, interstitial and native ads, plus subscriptions, plus those "upgrade" notifications. Every popup is either an ad impression or a chance to pull the user back into the app. The reason to buy installs in the UK, Australia and Sweden is that one ad impression pays more there. As long as the ad and subscription revenue a user brings in before they delete the app exceeds the cost of acquiring them, the math works. Its real revenue has no public data, and it doesn't appear on the top-grossing charts.

Who it's competing with

PDF readers are among the most crowded tool categories on Google Play. There are 547 apps with PDF in the title, 219 of which launched after May 2026. Together they added 41.2M installs in a single week (Google Play, 11-06).

It has no real differentiation. Next to Adobe or WPS it's lighter but has more ads; next to its sibling accounts it even has the same name. Newstar, iKame and Begamob, all Vietnamese companies, are also doing the same thing.

Can I copy it?

Copying this product exactly won't work. You'd be the twentieth-something same-template account, with rivals dozens of times bigger in front of you, who know their budgets and account-swapping better than you do. This one went from charting to falling off in two weeks; an account's lifespan is typically a few weeks to a few months. On top of that, reviews complain about popups disrupting other apps and spammy upgrade reminders. These practices break Google Play's ads policy, so getting banned is part of the cost, not a surprise.

What you can take is the playbook itself: one generic codebase, reskinned with different package names and published across multiple accounts; buy installs only in countries where ad CPMs are high; use the category's two biggest search terms in the title; filter accounts by payback, give winners more budget, and drop the losers. PDF is already saturated with this, but the same pipeline applied to a needs-based tool category that hasn't been flooded with reskinned packages works the same way.

There's one smaller gap too: the negative reviews show plenty of people got annoyed and left. A document viewer with fewer ads and a one-time payment to remove them could catch some of those users. But it would still have to compete with the system's built-in viewers and Adobe for the users who actively search, and that alone makes it hard to scale.

If it were you

In short: Don't build this PDF reader. It's one part of a Vietnamese tool-app pipeline, and the product itself has nothing to copy. What's worth learning is the pipeline.

Who it's for: small teams that already run Google App Campaigns, understand ad monetization, have a few developer accounts, and can afford to lose a few weeks of budget. They want to move the "template + multiple accounts + paid installs in high-CPM countries" approach to other tool categories.

Who it's not for: indie developers with no paid-acquisition experience who hope a single PDF reader will grow organically. In this category, organic search is held by Adobe, WPS and the system apps, and paid acquisition is held by dozens of same-template accounts.

How to do it: First choose a category: a tool people open repeatedly, that can serve as a default handler, where the built-in options are weak and Play doesn't yet have dozens of fresh same-template accounts. Build one generic base, ship two or three packages across separate accounts, and use the category's top two search terms in each title. Test each package with a small budget in one high-CPM country for a few days, measuring the cost per install and ad revenue over the first 7 days. For the ones that pay back, concentrate spend for a few days to push into the category chart.

How to get users: Mainly Google App Campaigns. Once you reach the category chart, you'll pick up organic traffic from chart placement and search. Skip tactics like popups that disrupt other apps or fake upgrade prompts. They bring bad reviews and mass takedowns.

When to move: There's no window left for PDF; it's too late. If you're switching categories, the sooner the better. When new accounts with the same package-name format and the same description start appearing in a category, it means the pipeline has already moved there.

What would show this read is wrong: ① AstraMobi doesn't change accounts or names and still holds the top 20 of the UK Tools chart in February 2027, with ratings rising alongside installs, which would mean it actually retains users and isn't just one-off paid acquisition; ② if a same-template account gets mass-removed by Google, it means the pipeline is more fragile than it looks, and the value of copying the playbook drops accordingly.

---

Data and sources: Google Play store pages (US and UK storefronts, read on 2026-11-06, including developer info, in-app purchase ranges and reviews); Google Play charts and daily installs/ratings (10-29 to 11-06); installs before October 29 are third-party AppstoreSpy estimates; store pages for each same-template app; a comparison page for BitCraft and AstraMobi on chrome-stats; Meta Ad Library searches by name and package returned nothing. Review text is originally in English, and the translations here are ours. The US page shows 3.7 stars and the UK page shows 4.7; both list the same reviews, and the reason for the difference is unverified.