How facebook/facebook-android-sdk works
Project type and purpose
• This is a multi-module Android SDK (Facebook Android SDK).
• Its purpose is to expose reusable Facebook features (Login, Share, Messenger, App Links, Analytics/Marketing, Gaming Services) as independent Gradle modules that app developers can pick and choose.
File structure
• Top-level modules (each with its own build.gradle.kts):
• facebook-core (base SDK functionality, Graph API, initialization, networking)
• facebook-common (shared UI/dialog utilities, custom tabs, login flows)
• facebook-login, facebook-share, facebook-messenger, facebook-applinks, facebook-gamingservices, facebook-marketing (feature modules that depend on core/common)
• facebook-bolts (asynchronous Task library used by multiple modules)
• facebook-testutil (utilities and mocks for testing within SDK modules)
• buildSrc directory managing shared dependency versions.
• Root build scripts: settings.gradle.kts, gradle.properties, jacoco.gradle.kts, maven.gradle (publishing), GitHub workflows under .github/workflows.
• “samples” directory containing standalone Android applications that consume the SDK modules.
README for additional insights
Facebook-android-sdk (umbrella)
├─ facebook-login, facebook-share, facebook-messenger, facebook-applinks
├─ facebook-common
└─ facebook-core
• Advises users to include only the modules they need, and warns that SDK init must run in the main process.
Main components
• Core (facebook-core)
• Common (facebook-common)
• Feature modules: Login, Share, Messenger, AppLinks, Marketing, GamingServices
• Bolts (facebook-bolts)
• Test utilities (facebook-testutil)
• Sample apps (FBLoginSample, HelloFacebookSample, KotlinSampleApp)
• CI/CD (GitHub Actions workflows, Maven Central publishing)
• Bolts → Core → Common → Feature modules
• Feature modules → Core (Graph API calls, token management)
• Feature modules → Common (UI flows, dialogs)
• Samples → selected Feature modules (they declare dependencies on specific feature modules in their Gradle configs)
• CI/CD → publishing pipeline → Maven Central
c. Architectural patterns and principles:
• Layered modular architecture: base (Core) → shared utilities (Common) → feature-specific modules
• Separation of concerns: each feature is its own Gradle project
• Dependency management via buildSrc (centralized versions)
• Testability: each module has its own unit tests and uses facebook-testutil for mocks
d. Technologies and frameworks:
• Kotlin & Java source → Android library modules
• Gradle Kotlin DSL for builds & publishing (build.gradle.kts, maven.gradle)
• GitHub Actions for CI (needs-attention.yml, stale.yml)
• ProGuard rules per module (proguard-rules.pro)
• Maven Central for distribution
Detailed focus points
• BuildSrc as the single source of truth for all dependency versions.
• That each module has its own ProGuard rules and tests.
• Publishing step: root maven.gradle → Maven Central badge (as shown in README)
• GitHub Actions workflows in the CI/CD component.