building-mobile-apps

Salesforce Mobile Route the user to the right SDK-family skill for building Salesforce-connected mobile apps. Do not implement features here; child skills own scenario detection and step-by-step instructions. Before routing Disambiguate on two dimensions: SDK family (Mobile SDK vs. Agentforce SDK) and platform (iOS vs. Android). They are not mutually exclusive — an app can use both SDKs. If the user's intent could plausibly map to either SDK, ask before routing. Guessing wrong wastes the user's time because the child skills are platform- and SDK-specific. Routing — which SDK family? User's situation SDK Authenticating end users to Salesforce, syncing records (MobileSync), storing data offline (SmartStore), biometric login, push notifications, REST integration Mobile SDK Embedding an Agentforce agent — chat UI, agent conversations, conversational features as the primary surface Agentforce SDK Both (data-driven app with an embedded agent) Mobile SDK first , then Agentforce SDK layered on top Tiebreakers when both seem to apply Show more Installs 485 Repository forcedotcom/sf-skills GitHub Stars 537 First Seen 10 days ago