Application Software Data: Cross-Store Metrics, Open-Source Infrastructure and Vendor Directories · Head-to-head
FFIEC Central Data Repository - Public Data Distribution (CDR PDD) vs F-Droid Open Source Android Apps
Which application software data: cross-store metrics, open-source infrastructure and vendor directories data fits your job: FFIEC Central Data Repository - Public Data Distribution, or F-Droid Open Source Android Apps. API, files, or your warehouse. Daily, weekly, or hourly.
FFIEC Central Data Repository - Public Data Distribution (CDR PDD)
F-Droid Open Source Android Apps
Coverage, side by side
| FFIEC Central Data Repository - Public Data Distribution | F-Droid Open Source Android Apps | |
|---|---|---|
| Geographic | United States only | Global FOSS Android ecosystem, localized entries in 70+ languages |
| Temporal | Quarterly filing periods; single-period or four-period calendar-year products | Rolling current-state index with per-app and per-APK timestamps; no removed-package archive in the main index |
What each contains
Pick by fit, not by loyalty.
| FFIEC Central Data Repository - Public Data Distribution | F-Droid Open Source Android Apps | |
|---|---|---|
| Publisher | FFIEC (Federal Financial Institutions Examination Council) | F-Droid |
| Subject lens | U.S. commercial bank Call Reports and Uniform Bank Performance Report statistics, filed under regulatory obligation | — |
| Population | Every U.S. commercial bank filing a Call Report - national banks, state member banks, insured state nonmember banks; thousands of filers per quarter | 4,247 apps in the main repository, each with one sub-record per published APK |
| Record grain | One row per institution per schedule line item; one row per institution per UBPR ratio, rank or percentile | One record per application plus one sub-record per APK version |
| Geography | United States only | Global FOSS Android ecosystem, localized entries in 70+ languages |
| Temporal shape | Quarterly filing periods; single-period or four-period calendar-year products | Rolling current-state index with per-app and per-APK timestamps; no removed-package archive in the main index |
| Field dictionary | Six core columns; column-level names inferred during research from files and taxonomies | 22 fields with definitions and examples; verified during research |
| Best for | Bank fundamentals, peer benchmarking, custody-bank fiduciary analysis | Ecosystem research, release monitoring, permission and anti-feature tracking |
What each does better
FFIEC CDR PDD
Complete regulated populations. Every U.S. commercial bank that files a Call Report appears: national banks, state member banks, insured state nonmember banks - thousands of institutions per quarter, with single-period populations running to hundreds of megabytes of schedule detail. Nothing is sampled; the panel is the filing universe itself.
Depth on performance, not just position. Six coordinated products pair raw Call Report schedules - balance sheet, income statement, past due - with Uniform Bank Performance Report derivatives that rank each institution inside its peer group and place it in percentiles. One quarter alone, or four quarters in a single cross-year pull.
A custody lens almost nowhere else sits. The fiduciary and custody-related schedules carry assets under custody and trust income for custodians such as BNY Mellon and State Street - the numbers behind custody-bank analysis, filed under regulatory penalty rather than self-reported marketing.
F-Droid Open Source Android Apps
A documented, verified dictionary. Twenty-two fields, each defined and exemplified during research - the cleanest field documentation in the pairing, and rarer than it sounds across the catalog.
Version-level granularity. One record per application becomes one sub-record per published APK: version string, monotonic version code, byte size, signing fingerprint, SDK floors and ceilings, ABI list, permission array. Release archaeology - when did the permission set grow, which architectures dropped out - falls straight out of the shape of the data.
Sample rows captured during research:
packageName: org.fdroid.fdroid authorName: F-Droid
categories: [App Store & Updater, System] suggestedVersionName: 1.23.2
packageName: com.github.ashutoshgngwr.tenbitclockwidget
summary: A beautiful BCD clock for your home screen
packageName: InfinityLoop1309.NewPipeEnhanced versionName: 5.2.5
minSdkVersion: 23 targetSdkVersion: 36 nativecode: [arm64-v8a]Where they're equivalent
Both are whole-population extracts rather than samples: every filing bank, every indexed app. Both resolve to one row per entity per unit of observation - per schedule line item or ratio on one side, per APK build on the other. Both carry stable keys that survive re-delivery, so a joined history builds cleanly. And both document their entities far beyond the number itself: a bank's legal name and reporting dates, an app's author, categories and multilingual descriptions. Where they stop agreeing is geography: one universe is chartered by U.S. regulators, the other is the global Android ecosystem with localization in 70-plus languages.
The verdict
Verdict: sample both, pick by fit - these two answer questions that never intersect, so the fit test decides everything.
Accept the frame: banks only, quarter-end grain, U.S. charters only.
Take F-Droid Open Source Android Apps if your question names software supply. Ecosystem sizing, permission creep, release cadence, architecture abandonment, vendor screening on anti-feature flags - anything answered from an app inventory. Accept the frame: current state only, Android only, no removed-package history.
Investors and quants reach for the bank filings on fundamentals screens and the app index when the thesis touches mobile distribution; developers and builders rarely need the reverse. Market researchers split the same way by client.
Sample both, pick by fit. See FFIEC Central Data Repository - Public Data Distribution · See F-Droid Open Source Android Apps
Or take both in one feed
Yes, as two legs of one technology-exposure story: bank technology spending and digital-channel strategy on the filings leg, mobile distribution reality on the app-index leg. Align keys before joining - certificate number plus schedule-item code plus quarter-end on one side, package name plus version code on the other - because nothing joins natively between a regulator's ledger and a software catalog.
Datadory ships either record alone or both merged onto one delivery calendar, aligned before it reaches you - delivered daily, weekly, or hourly, your call. Or take both in one feed.
API, files, or your warehouse. Daily, weekly, or hourly.
Fair questions
Is FFIEC CDR PDD better than F-Droid Open Source Android Apps?
Better at different jobs. FFIEC CDR PDD owns regulated U.S. bank fundamentals: every commercial bank filer's Call Report schedules plus Uniform Bank Performance Report ratios, ranks and percentiles, quarter after quarter. F-Droid owns the community-built Android software census: 4,247 apps with complete APK inventories, permission sets and 70-plus-language listings.
Do FFIEC CDR PDD and F-Droid Open Source Android Apps cover the same ground?
Only in structure, not substance. Both publish complete single-topic populations keyed by a stable identifier - FDIC certificate number versus Android package name - with one row per entity per measurement. But one records fiduciary assets and past-due loans for custodians such as State Street; the other records SDK levels, ABIs and anti-feature flags for apps. No overlap in subject matter.
Which dataset has the better-documented field dictionary?
F-Droid: 22 fields with definitions and worked examples, verified during research, from packageName down to signer fingerprints and minimum SDK levels. FFIEC CDR PDD's dictionary was reconstructed during research as inferred - the portal publishes the data and its XBRL taxonomies but never enumerates column headers on a documentation page, so schedules have to be read to be mapped.
How fresh is the information on each side?
Datadory re-delivers both records on your calendar - daily, weekly, or hourly, your call. On content: FFIEC CDR PDD holds quarterly filing periods, with single-period products covering one quarter-end and four-period products spanning a calendar year. F-Droid carries a rolling current-state index with added and lastUpdated timestamps per app and per APK, but no archive of removed packages.
Can I get both in one delivery?
Yes. Datadory ships either record alone or merged onto one delivery calendar, aligned before it reaches you. Bank rows join on certificate number, schedule-item code and quarter-end date; app rows join on package name and version code. Say the word and both arrive as one feed - Or take both in one feed.