70k installs push a PDF reader into Thailand's tools chart at #8: an Australian company whose tax number has been cancelled, and an app built to be thrown away

Lumora PDF launched on Google Play on Oct 14. It drew only 807 installs in its first two weeks, then gained 70k in the following week and climbed to #8 on Thailand's free Tools chart. The product is no different from the hundred-plus PDF readers launched around the same time. The developer account is registered to an Australian company whose tax number has already been cancelled, and an earlier VPN from the same account has already been delisted. What it shows is not that PDF readers still have room, but that some charts are cheap enough that 70k installs is enough.

A 2-character review, 73 people tapped "helpful"

On Oct 31, a Thai user left a review on Lumora PDF's store page reading "สุดยอดครับ" ("Awesome"), and 73 people marked it helpful. The next day another Thai user wrote "ดี" ("Good"), and 49 people marked it helpful. On Nov 2, someone wrote "ไม่ชอบ" ("Don't like it") and got 10 likes. On the US store, an Oct 30 review, "hopeful that is great service for the future," sits at the top, and on Nov 5 a review that just says "trash" appeared (Google Play store page, 11-06).

Across the whole store page there are 161 ratings, and none of the visible reviews mention a specific feature: no one says a file wouldn't open, that merging works well, or that there are too many ads. A three-week-old utility collecting 73 likes on a two-word review does not look like genuine users voting on their own (inference). The same app shows a 4.6-star rating on the Thai store page and a 3.5-star rating on the US page.

What it is

A document tool for Android: open PDF, Word, Excel, and PPT files, turn JPG / PNG images from your phone or photos of paper documents into PDFs, merge and split PDFs, and read documents aloud (reading continues when you switch apps or lock the screen). It also has a local file list, recently opened files, and favorites. It's free, labeled "contains ads," with no in-app purchases. The version number has stayed at 1.0.0.

This feature set is standard for the category. The only thing that qualifies as a differentiator is background read-aloud. The title "Lumora PDF - Reader & Tools" follows the same template as PDF Pilot - Reader & Tools and PDF Reader Viewer - Tools, which launched around the same time.

How the volume came in: two quiet weeks, then a jump in steps

(Public Google Play install count, 11-06; the increase between the first few days is the difference between two observations.)

自然长起来的 App 曲线是平的、慢慢弯上去的;这条是上架后放了两周,然后一档一档地跳。地区也是一批一批开的:10-29 先出现在香港、日本、台湾的工具榜 100–180 名,10-31 扩到意大利、波兰、泰国、土耳其(Google Play 各区榜单)。这是分批投放预算的样子,最像 Google 自己的应用推广(推断;在公开渠道没查到它的广告记录,也找不到任何自然讨论:TikTok 搜「Lumora PDF」出来的全是同名的珠宝、出版社,X 上 30 天 0 条,没有媒体写过它)。

The ratings back this up too. The US store star distribution 11-06 is: 1 stars 34, 2 stars 0, 3 stars 17, 4 stars 17, 5 stars 86. The 2-star count stayed around 0,4 until 11-04 to 11-05, then jumped from 0 to 13. Of the 155 ratings, only 4 came with written reviews (Google Play, 11-06). Paid installs are mostly people who tapped an ad inside another app, and they rarely leave reviews. There's no way to prove that the sudden block of five-star ratings was prompted, though.

Why Thailand: this chart is cheap

Top 15 on Thailand Tools Top Free chart (Google Play) for 11-06:

Of the top 15, 6 are PDF readers, and several are new packages that launched in the second half of this year. Lumora's 70k installs in a week (global figures; only part of that lands in Thailand) put it at #8. The competitors ahead of it take about 200–300k a week. That suggests the bar to reach the top 10 of Thailand's Tools chart is roughly several thousand installs a day. From 11-03 it also landed on the overall Thailand apps chart, climbing from #160 to #66. Other countries were not as cheap: on the same day it ranked #75 on Turkey's Tools chart, #81 in Japan, #86 in Taiwan, and #169 in Hong Kong. It has never charted on any top-grossing chart.

The reasoning for choosing places like Thailand and Turkey is straightforward: installs are cheap there, and PDF readers are apps people reopen repeatedly, so each open can show an interstitial or app-open ad. As long as ad revenue covers the cost of acquisition, the spending can continue (inference; its revenue and retention are not visible).

Who's behind it: an account that gets thrown away once used

The developer is listed as L & V CO PTY LTD, a private company in New South Wales. Checking Australian business registration, its ABN (Australian tax number) was cancelled in Jul 2026 14, and ASIC has published a proposed deregistration notice (ABN Lookup, ASIC notices). The contact email is a personal Gmail account. The privacy policy was built from a Google Sites template. The website pdftoolfilescan.com went live on the same day as the app, and when opened, 11-06 still shows an empty 404 storage bucket.

The same account previously published a VPN (Lonng VPN) and an "answer book"-style app called AnswerArchon. Both have been removed from Google Play (AppBrain and APKPure records).

This closely resembles the bulk-bought or rented overseas developer accounts common in the going-global tools scene: one account tests one tool, and when it gets delisted or stops performing, the operator switches to the next account and the next package name (inference; the team behind it was not identified). The Lumora brand name has no other presence online. It was never meant to become a brand.

Who it's competing with

This street is already crowded. Since July 2026, 174 apps with PDF or document in the name or package name have launched first on Google Play, with 78.2M cumulative installs and 8.52M in the last 7 days combined. Lumora's 7-day new installs rank roughly #38 among them (public Google Play data, 11-06).

Among these new packages, Lumora sits in the middle to lower tier. It is not leading this wave, just one of many in it.

If it were you

In one line: Don't copy this app, and don't build the 175th PDF reader. The one useful takeaway it offers is that some countries' category charts are cheap enough that a few thousand installs a day can reach the top 10. Chart rank is not the same as product quality.

Who it suits: Teams already running Google app promotion, with a "tool template + ad monetization" pipeline, can use the approach of picking low-bar country category charts to climb rankings and then capturing organic traffic from the chart.

Who it doesn't suit: Solo indie developers, people who haven't run paid ads, and anyone hoping to break through with a better product. Users here can't tell the 6th PDF reader from the 1st and won't pay. And the overseas company accounts and bulk-swapped packages that drive its volume are a tactic that can be removed at any time.

How to do it: If you already build tool apps, use Lumora as a benchmark: before launch, check how many weekly new installs the #10 spot on the target country's category chart gets. Thailand's Tools chart is currently about tens of thousands of installs a week, far cheaper than Europe or the US. Spending paid acquisition on charts like this is more useful than ranking #100 on the US chart. And pick a category that isn't yet crowded with 174 packages.

How to get users: Follow this order: Google App Campaigns, first test small in Hong Kong, Taiwan and Japan, then concentrate budget on low-cost, low-bar markets like Thailand and Turkey. Once it cracks the top 10 of a category chart, pick up some organic installs from chart placement and store search.

When is the window: No deadline. Someone has always built in this category. But the built-in PDF viewers on Android keep getting better, so the plain "open a file" need will only shrink.

What would mean I read it wrong: If Lumora is still in the top 20 of the Thai utilities chart a month after paid acquisition stops, with installs still climbing by thousands a day, then these users stick and organic reach is bigger than I think, so the category isn't played out. Conversely, if it drops off the chart within a week or two, or the whole package gets pulled, that is what this playbook looks like when it runs its course.