Mobile SDK Development Guide

Introduction to Mobile Development
Introduction to Salesforce Mobile SDK Development
What’s New in Mobile SDK 11.1
Getting Started With Mobile SDK 11.1 for iOS and Android
Updating Apps (5.0 and Later) Apps (5.0 and Later)
Native iOS Development
Native Android Development
HTML5 and Hybrid Development
Using Lightning Web Components in Hybrid Apps
React Native Development
Offline Management
Files and Networking
Push Notifications and
Authentication, Security, and Identity in Mobile Apps
OAuth Terminology
OAuth 2.0 Authentication Flow
Connected Apps
About PIN Security
Biometric Authentication
Portal Authentication Using OAuth 2.0 and Salesforce Sites
Using MDM with Mobile SDK Apps
Using Advanced Authentication
Upgrading Android Single Sign-On Apps to Google Login Requirements
Using OpenID Tokens to Access External Services
Secure Key Storage in iOS
Secure Key Storage in Android
Login Screen Customization
Identity Provider Apps
Using Key-Value Stores for Secure Data Storage
Dark Mode and Dark Theme Settings
Using Experience Cloud Sites With Mobile SDK Apps
Multi-User Support in Mobile SDK
Mobile SDK Tools for Developers
Logging and Analytics
Migrating from the Previous Release
Reference
iOS Current Deprecations
iOS APIs Removed in Mobile SDK 11.0
Android Current Deprecations
Android APIs Removed in Mobile SDK 11.0
Trademark Attributions
Removing UIWebView from iOS Hybrid Apps
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Connected Apps

A connected app integrates an application with Salesforce using APIs. Connected apps use standard SAML and OAuth protocols to authenticate, provide single sign-on, and provide tokens for use with Salesforce APIs. In addition to standard OAuth capabilities, connected apps allow Salesforce admins to set various security policies and have explicit control over who can use the corresponding apps.

Here’s a general list of information that you provide when you create a connected app.
  • Name, description, logo, and contact information
  • URL where Salesforce can locate the app for authorization or identification
  • Authorization protocol: OAuth, SAML, or both
  • IP ranges from where users can log in to connected app (optional)
  • Information about mobile policies that the connected app can enforce (optional)

On the most basic level, Salesforce Mobile SDK apps use connected apps to access Salesforce OAuth services, which enable access to Salesforce REST APIs.