Upload as usual — Hub does the rest
Fylio Hub is a public catalogue of Android apps and mods assembled from files already uploaded to Fylio. Any APK in your storage can become a card with version history, a signature check and a download button. All it needs from you is a name.
How it works
Three steps, only one of them yours.
- 01
Upload a file
An APK, XAPK, APKM or APKS into the file manager — any folder, any upload mode, as usual.
- 02
The system reads the APK
Package name, version, architecture, signature and permissions come from the file; the store listing supplies the title, icon and screenshots. You get a ready card to confirm.
- 03
Confirm a name and a description
Once. From then on updates and new builds attach to the card by themselves — you get a notification and can roll back any release.
New cards always wait for your confirmation: nothing is published without you.
What a publisher gets
Hub is not a separate programme — it is one more place where your files are found.
Traffic
Hub pages are indexed by search engines and surface in the home-page blocks: Popular mods, New in Hub, Trending, Recently updated.
Earnings as usual
The Download button opens your regular download page. A Hub download is paid under the same PPD rules and rates as any other.
Ranked by real downloads
Valid downloads over 30 days, freshness of the latest release and quality signals. No paid placements among the cards.
Verified-author badge
Your own card icon, free-text feature chips, priority among equally popular cards and the badge on your profile.
Product ownership
Original developers get the Official kind: their builds show first on the product page, and the product can be locked against third-party cards.
What the system does
Everything below is read from the file — no fields to fill in.
Builds and ABIs: arm64-v8a, armeabi-v7a, x86_64 and universal in one release
XAPK, APKM and APKS with OBB and split APKs
Signature check: official, modified or not verified
Version history with rollback and rebuilds
Release notes plus automatically computed technical changes
Folder binding — uploads into it always land on the right card
Batches: files uploaded together are grouped and published in one click
Rules
Short and the same for everyone.
No links in titles, descriptions or release notes
Cards are moderated: misleading titles and other developers' branding lead to hidden cards and strikes
Reports are reviewed by moderators; after three reports from different networks a card is hidden until a decision
Publish only builds you have the right to distribute
Questions and answers
What publishers ask most often.
Check the badge next to the file. Only APK, XAPK, APKM and APKS are picked up; anything else says “not in Hub”. “Hub: processing…” means the file is still being analysed — a large XAPK can take a few minutes, and the batch panel appears only after the analysis finishes. If the badge says “in Hub: pending”, the suggestion is waiting in My Hub → Inbox.
Yes. A file is published only when you confirm its group, or when it is a confident update of a card you already have and automatic publication is on. “Do not publish” removes a suggestion; “Unpublish” takes a card down; “Unbind” a folder if you no longer want uploads to attach to a card.
One card. Upload every build of the version — arm64-v8a, armeabi-v7a, x86_64, universal — and they join one release; visitors pick the build on the card page. A build uploaded later is added to the existing release.
Yes. Hub analyses the base APK inside the XAPK; split APKs provide the architectures, languages and screen densities, and the OBB stays inside the package. Visitors download it as one file to install with an XAPK-capable installer. APKM and APKS bundles work the same way.
Hub compares the signing certificate of every build with the developer's reference. “Official signature” — the build is signed with the developer's key. “Modified signature” — it is signed with a different key or a public test key. “Signature not verified” — there is no reference for this app yet. For a mod a modified signature is expected and honest; nothing needs fixing.
No. Files, download links, monetisation level and rates stay exactly as they are. Hub does not host copies of your files; it links to the same download page with a source marker so you can tell Hub downloads apart in your statistics. Unpublishing a card does not touch the links either.
A badge the Fylio team grants to accounts with a consistent history of working builds and no upheld complaints. It unlocks your own card icons and free-text feature chips, ranks your cards higher among equally popular ones and shows the badge on your profile and cards. Ask support from the account that owns the cards.
Builds you have the right to distribute, under a title and description that say what the build really is. Misleading titles, hidden payment or messenger baits, prohibited content and other developers' branding on your icons lead to hidden cards, strikes and loss of trust badges. Links are not allowed in titles, descriptions or release notes.