Data source
Data from F-Droid, delivered clean.
1 dataset pulled from F-Droid's releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.
- 1 dataset
- 1 industry
- Real rows on request
What Datadory delivers from F-Droid
1F-Droid Open Source Android Apps
Pick a catch, see the rows.
Name any F-Droid dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.
Get a sampleAPI, files, or your warehouse. Daily, weekly, or hourly.
Straight answers about F-Droid data
How many apps are covered?
4,247 applications in the main repository, each delivered with its complete published-build inventory as version-level sub-records. Counts are re-verified at delivery time, so a sample reflects the live catalog rather than a stale snapshot.
Can I track one app's release history over time?
Per app you get suggestedVersionName and suggestedVersionCode plus one sub-record per published APK with its own version name, code, byte size, SHA-256 hash, signing fingerprint, SDK bounds and permission array. lastUpdated timestamps expose publishing cadence directly.
Is non-English metadata included?
Yes. Each app record contains a localized block per language with name, summary, description, whatsNew text and graphic references - 70+ locales observed across the catalog. Coverage is per-record because maintainers author translations, so it varies app by app rather than sitting in a uniform lookup table.
How current is the data?
It is a rolling current-state catalog - what exists now plus per-record added and lastUpdated timestamps - and Datadory delivers it daily, weekly, or hourly depending on what your pipeline needs. Your own recency filters run off those timestamps regardless of the cadence you pick.