The Same Reading App Under Different Names

What this page claims, and what it does not

Reading apps that sell web novels by the chapter often turn up under several names: a second store listing in another language, a lookalike title, an app that is "the same" as the one a friend uses. Our question was narrow: can the public store listings show that two names belong to the same family? The claim rests on two kinds of evidence, and only these two:

• Publisher of record: the same legal-entity string printed on listings, as the App Store "Seller" line or the Google Play "About the developer" block;
• Backend: policies or terms hosted on one domain, the same URL path on different brand domains, or one website serving two brands.

We say "the same publisher of record" or "the same backend", never "owned by" or "run by one company". No source we read shows ownership of any family. We also did not compare catalogues. Whether two sibling apps carry the same books is a separate question that this page does not answer. For the two families that include apps we review, see our GoodNovel page and the Dreame review.

Seven names on our working list, and some of the evidence around them, fall outside this site's content rules. They are not named, not linked and not counted in the seven families. Where a withheld name would have added a member to a family, the family stands on the members shown. Two further families rest on a withheld name for their strongest link, so we do not show them: the evidence exists but is not shown.

The lead clue: a typo on two listings

Price points can coincide between unrelated apps, but a misspelling is harder to share by accident. On October 27, 2026 we opened the US App Store listings for GoodNovel (the listing) and BueNovela, a Spanish-language title (App Store id 1547565419, not linked). Each prints an in-app purchase called "WeekIy Membership" at $19.99. The third letter from the end is a capital I (the character U+0049), not a lower-case L, which looks identical in most fonts.

Both listings print the typo, and the two lists differ around it. GoodNovel's list also carries a correctly spelled "Weekly Membership" at $19.99, beside a "Weekly Subscription" at $9.99. BueNovela's list prints the typo version and the "Weekly Subscription" at $9.99, with no correctly spelled twin. A product-name typo that survives on two listings suggests the two lists were built from one product catalogue. It does not tell you who owns that catalogue.

Beside the typo sits a second trace. GoodNovel's privacy policy is at goodnovel.com/haiwai_other/static_file/privacy_policy.html (the page), and BueNovela's is at the same path on buenovela.com. Both return a page and both are the same template with the brand name swapped: GoodNovel's reads "Last update: December 12, 2023", BueNovela's "Last update: August 21, 2026". We checked that both addresses load on the day.

One thing to be exact about: both listings already name the same seller, SINGAPORE NEW READING TECHNOLOGY PTE. LTD., on the App Store and in Google Play's developer block, and BueNovela's Google Play developer name reads "GoodNovel". GoodNovel's own Terms name the same company, registered in Singapore. So the typo does not join two companies. It corroborates a shared catalogue between two listings that the seller line had already tied together.

The seven families

Each family below rests on one publisher of record or one backend, which anyone can check on the listings. Where a name is a sibling, not an app we review, we print the publisher string and the store id so you can find it, and we do not link it.

Changdu

Three strings appear: CHANGDU (HK) TECHNOLOGY LIMITED on Kifflire, CHANGDU TECHNOLOGY (USA) CO.,LTD. on ReadNow and Novella, and Changdu Technology (USA) Co Ltd in Google Play's developer block for WeRead, BestNovel and ReadNow. BestNovel's App Store seller is CHANGYI (HK) TECHNOLOGY LIMITED, which does not contain "Changdu", so its tie rests on the Google Play entity. Kifflire's and ReadNow's privacy pages and BestNovel's terms page sit on hosts under one domain, cdreader.com. Novella's policy is on a different host, manobook.net, so its link rests on the seller string alone. The Google Play package prefix com.changdu.* on WeRead and BestNovel is a hint, not a fact.

NovelFox

NovelCat and FoxNovel share an App Store seller, Beijing Shengyan Technology Co., Ltd. All three apps link terms and privacy pages on novelfox.net under the same /v1/main/ path, and those are the Developer Website and Privacy Policy links printed on each App Store listing. FantacyStory is tied to the other two by that host and path, not by seller: its App Store seller is HK Qingmo Technology limited and its Google Play entity is HK CHUANQI TECHNOLOGY LIMITED. The shared package prefix net.novelfox.* on NovelCat and FantacyStory is a hint.

Stary / Dreame

This is a publisher link only. Dreame and Starynovel list the same App Store seller, Stary Pte. Ltd., and all three Google Play listings in the family print the same entity in capitals and the developer name "Dreame Media". It is not a shared-backend family: Dreame's policy is on api.dreame.com and Starynovel's is on yugtofiction.com, and an earlier comparison, not re-run, found the two texts unlike. Dreame has a review on this site, so this is the family a reader may already use.

Bestread / TikNovel

HotNovel's App Store seller and the Google Play entity of Romance Novel Library and Romance Reads and Audiobooks are the same company, HONG KONG BESTREAD TECHNOLOGY LIMITED, and the two Play listings share the developer name "TikNovel". HotNovel's developer website, bestreadtech.com, and Romance Novel Library's site, tnovels.com, serve the same page template: fetched on October 27, 2026, the two home pages differed in about a dozen lines out of 903, the featured book in the title and tags and the Google Play package their download buttons point to. Two near-misses stay out of the claim. The Google Play app TopNovel has the developer name "Bestread" but a different legal entity, Helloreader LIMITED, and a near-empty site, and the App Store's TopNovel belongs to Mangatoon HK Limited. One shared title does not make a link. Separately, bestreadtech.com points its Android download buttons at a Google Play listing titled "HoneyNovel: Werewolf Romance" under a different developer; whether that is HotNovel's Android build is not confirmed.

iReader publisher

HK IReader Technology Limited is the App Store seller of all eight listings, and iReader's Google Play block names it too. Six listings (iReader, Storyroom, Storysome, Storyaholic, MyNovel and Novelmates) print a Developer Website and Privacy Policy link on an ireader.com or ireader.mobi host. Fatednovel's website link is the ireader.mobi root but its policy is on readnovle.com, and PopoVibe's site and policy are on dramapage.com, so for those two the evidence is the seller line.

One line about the evidence we do not use. The product pages on hk.ireader.mobi look like proof of a shared backend, but that host serves the same page for any path, including one that does not exist, so a product page there shows nothing. On October 27, 2026 three different paths, including a made-up one, returned the same 1,130-byte page. We rely on the links printed on the listings instead.

VitalTek

Readict, Readict Fiction and Fictify name VitalTek, Inc. on every listing (the Google Play block spells it "Vitaltek, Inc."). All three Google Play listings link readictnovel.com and keep their privacy pages on it.

How many independent sources are there?

Our working list held nineteen names: eleven reading apps, Dreame, and the seven names withheld above. After merging each app's App Store and Google Play variants, they carry eighteen publisher strings, because only HotNovel and Romance Novel Library print the same one. So nineteen names carry eighteen publisher strings, and on publisher and backend evidence there are at most eighteen independent sources. A shared legal template does not prove shared ownership, which is why we stop at that figure and do not shave it further on policy overlap.

Two cautions on the number. First, we count each app as one operator even where its App Store seller and its Google Play entity are written differently, which is an assumption: we recorded strings, not a legal finding. Second, the eighteen counts the working list, while the seven families above reach further, because each gathers sibling apps found by following the seller line and the policy links. That is why the table shows more names than the count does. No publisher or backend link joins two of the eighteen strings, which is why eighteen is the bound on this evidence.

A weaker observation: shared policy text

This section is labelled text reuse, not ownership, and its numbers never enter the count above. We compared privacy policies by splitting them into sentences of 60 characters or more, lower-casing them, stripping punctuation and replacing brand and company names with one placeholder. The percentage is the identical sentences divided by the sentence count of the shorter policy. Pages that need scripts were rendered read-only in a headless browser that clicks nothing.

Two pairs sit inside a family we already show (GoodNovel and BueNovela, NovelCat and FoxNovel). The more interesting rows are the ones that cross it. KissNovel (publisher Hong Kong RUIJIU Technology Limited) shares most of its policy sentences with GoodNovel's, from a different company on a different host. Fictio (Plotfun Inc.), NovelCat and Starynovel share most of one policy template across three publishers that no seller line or host joins. Shared policy text can come from one parent company or from one legal-template vendor, and the text alone cannot tell which. We therefore do not count it.

One more text-reuse observation, outside the claim: seven Android-only listings (Novelclub, LycanNovel, NovelVault, LycanFiction, WolfFiction, Romanfic and Bravonovel) share store-description sentences in two templates across five operators. Four of the seven listings name an individual rather than a company as publisher; we do not print the names. These listings were not checked against this site's content rules, and we say no more about them.

Coin ladders, for reference only

A coin ladder is not evidence of a link, and we do not count it. "100 coins per dollar" is common to unrelated apps, so it joins nothing, and the figures below are our own arithmetic (coins divided by price) from the US App Store lists, which print at most ten purchase items. We show them so that a reader comparing coin prices can see that a coin is not a fixed unit.

Three Changdu names (ReadNow, Novella, Kifflire) print packs numbered by dollar price, not coin counts, so no rate can be computed for them. The NovelFox and iReader ladders are distinctive, but we still treat them as reference. Our guide to how story app credits work and the glossary entry on credit-based reading explain why the rate matters less than the coin cost of a chapter, which none of these listings publish.

Listings that have not been updated

These are observations outside the claim, and the date is a fact about the listing, not a verdict on the app. FoxNovel's App Store listing was last updated on April 27, 2025, while NovelCat's is current. The Google Play listing of Romance Novel - Good Web Novel, in the Stary family, was last updated on May 27, 2025. Five of the iReader publisher's App Store listings (iReader, Storyroom, Storysome, Storyaholic and MyNovel) have not been updated since September 2024, while Novelmates, Fatednovel and PopoVibe are current. Bravonovel's Google Play listing dates from March 6, 2024.

What this does not show

• Ownership of any family. A and B evidence points to one operator or one software vendor; it does not say who owns it.
• That the libraries overlap. An earlier comparison of long story-blurb lines on the home pages of several sites found none shared, and we did not repeat it. The apps may share software and still carry different books.
• Whether coins or accounts carry across sibling apps. We did not look.
• Anything about prices on Google Play, which prints ranges only, or about App Store items beyond the ten a listing prints.
• Terms and content rules for most of the apps named here. We read the terms of the apps we review, not of the siblings.

How to check who publishes a reading app

1. Open the store listing. On the App Store, find the Seller line in the Information section. On Google Play, open "About the developer".
2. Compare the legal-entity string, not the app name or the developer display name, which can differ.
3. Look at the Developer Website and Privacy Policy links. Two apps whose policies sit on one domain, or at one path on two brand domains, share a backend.
4. Check the in-app purchase list for product names, including spelling.
5. Treat a shared template as a hint only. It can come from a shared parent or from a shared legal vendor.

Reading the rules of one app tells you about that app. Dreame and Starynovel, for instance, keep separate policies on separate hosts. If you use GoodNovel or Dreame, our guides to choosing an erotica app and to why erotica apps disappear from the app store cover what the stores allow, and the pricing pages on what GoodNovel costs and what Dreame costs cover the money. The apps section lists every review.