SkillsAdd

forcedotcom/salesforcemobilesdk-templates · Archived

android-mobile-sdk

Add Salesforce Mobile SDK capabilities to Android Kotlin applications. Covers creating new apps with the SDK pre-integrated, or adding base SDK, SmartStore (encrypted database), MobileSync (cloud sync), and biometric authentication to existing applications.

First seen May 21, 2026

Installation

$ npx skills add forcedotcom/salesforcemobilesdk-templates --skill android-mobile-sdk
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

ios-mobile-sdk Same source · more installs
forcedotcom/salesforcemobilesdk-templates

Integrate Salesforce Mobile SDK into iOS Swift apps.

18 installs
update-ios-deployment-target Same source
forcedotcom/salesforcemobilesdk-templates

Update the minimum iOS deployment target across all iOS and React Native templates

1 installs
test-sdk-consumer-skills Same source
forcedotcom/salesforcemobilesdk-templates

End-to-end test harness for the consolidated SDK consumer skills. Creates 10 apps (5 iOS, 5 And…

1 installs
test-template Same source
forcedotcom/salesforcemobilesdk-templates

Test templates with test_template.sh script

1 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

firebase-data-connect Shared topics
firebase/agent-skills 142.2K installs
clerk-android Similar name
clerk/skills

Implement Clerk authentication for native Android apps using Kotlin and Jetpack Compose with cl…

11.7K installs
sentry-android-sdk Similar name
getsentry/sentry-for-ai

Full Sentry SDK setup for Android. Use when asked to "add Sentry to Android", "install sentry-a…

2.1K installs
mapbox-android-patterns Similar name
mapbox/mapbox-agent-skills

Official integration patterns for Mapbox Maps SDK on Android. Covers installation, adding marke…

1.1K installs
mobile-android-design Similar name
wshobson/agents 22K installs
argent-android-emulator-setup Similar name
software-mansion/argent

Set up and connect to an Android emulator using argent MCP tools. Use when starting a new sessi…

16K installs

Also in this package

Other skills from forcedotcom/salesforcemobilesdk-templates.

npx skills add forcedotcom/salesforcemobilesdk-templates
ios-mobile-sdk 18 update-ios-deployment-target 1 test-sdk-consumer-skills 1 test-template 1 remove-template 1

Browse all from forcedotcom/salesforcemobilesdk-templates

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 58
License LICENSE
Default branch dev
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,242 B
  • docs SUMMARY.md 283 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 9 installs

SKILL.md

Android Salesforce Mobile SDK Integration

This skill integrates the Salesforce Mobile SDK into Android Kotlin applications. It is consumed by autonomous coding agents — every reference file is self-contained and contains exact source-of-truth code, file paths, and CLI commands.

Scenarios

Pick the reference file that matches the task. Scenarios are layered: each later one assumes the previous is already wired up.

Scenario Reference Preconditions
Create a new Android Kotlin app from scratch [references/create-new-app.md](references/create-new-app.md) none
Add Mobile SDK authentication to an existing app [references/add-mobile-sdk.md](references/add-mobile-sdk.md) Gradle Android module exists
Add SmartStore (encrypted local DB) [references/add-smartstore.md](references/add-smartstore.md) SalesforceSDKManager.initNative(...) called and bootconfig.xml exists
Add MobileSync (sObject ⇄ soup sync) [references/add-mobilesync.md](references/add-mobilesync.md) SmartStoreSDKManager.initNative(...) called and userstore.json exists
Add Biometric Authentication (fingerprint / face / iris) [references/add-biometric-auth.md](references/add-biometric-auth.md) Mobile SDK is initialized in the Application subclass

Cross-cutting references:

Topic Reference
API class map (manager hierarchy, key types) [references/api-reference.md](references/api-reference.md)
Build / login / SmartStore / sync / biometric error symptoms [references/troubleshooting.md](references/troubleshooting.md)

Detection Rules

When the user request is ambiguous, run these checks against the working directory and pick the first scenario in the list below whose precondition is not met — even if the user asked for a later capability (e.g. a "sync" request lands on add-smartstore.md if userstore.json is not yet present, then chains forward):

  1. No settings.gradle.kts or build.gradle.kts at the repo root → create-new-app.md.
  2. Gradle module exists, but no import com.salesforce.androidsdk. (or any SDK class) anywhere in .kt → add-mobile-sdk.md.
  3. SDK initialized, but no app/src/main/res/raw/userstore.json → add-smartstore.md.
  4. userstore.json exists, but no usersyncs.json next to it → add-mobilesync.md.
  5. Biometric requested but no BiometricManager reference and no biometricAuthenticationManager call → add-biometric-auth.md.

Invariants Across All Scenarios

  • Manager class hierarchy (each subclasses the previous): SalesforceSDKManager ← SmartStoreSDKManager ← MobileSyncSDKManager. Each scenario's initNative(...) call uses the lowest manager that covers the modules in use. The base scenario uses SalesforceSDKManager; SmartStore swaps to SmartStoreSDKManager; MobileSync swaps to MobileSyncSDKManager. Each swap is additive — nothing is lost.
  • Maven artifact follows the manager. Base scenario: com.salesforce.mobilesdk:SalesforceSDK. SmartStore: com.salesforce.mobilesdk:SmartStore. MobileSync: com.salesforce.mobilesdk:MobileSync. Each artifact transitively pulls the lower ones — do not pre-emptively pull MobileSync for an app that only needs base auth.
  • Application subclass is mandatory: <Manager>.initNative(applicationContext, MainActivity::class.java) must run from Application.onCreate() before any SDK class is touched. Register the subclass with android:name=".MainApplication" in AndroidManifest.xml.
  • MainActivity extends SalesforceActivity: the SDK manages the OAuth/login lifecycle through this base class. Override onResume(client: RestClient?) from SalesforceActivityInterface for post-login logic — the SDK calls it once a RestClient is available (or with null when no user is currently authenticated).
  • Resource folders: userstore.json and usersyncs.json must live under app/src/main/res/raw/. The SDK resolves them by Android resource name.
  • Login host: configured via app/src/main/res/xml/servers.xml. https://login.salesforce.com is production; https://test.salesforce.com is sandboxes.
  • Do not recreate Gradle scaffolding for an existing app. When adding the SDK to an existing project, only modify app/build.gradle.kts, AndroidManifest.xml, and MainActivity.kt, and create the new files (MainApplication.kt, bootconfig.xml, servers.xml, strings.xml). Do not overwrite gradle.properties, settings.gradle.kts, root build.gradle.kts, or gradle-wrapper.properties — those belong to "Create New App" only.
  • Build target: ./gradlew assembleDebug from the project root unless the agent has reason to use a different variant.

Source of Truth

When the SDK API in this skill disagrees with reality, the upstream Kotlin/Java in <https://github.com/forcedotcom/SalesforceMobileSDK-Android>; wins.