---
source_url: "https://docs.descope.com/mobile-sdk"
title: "Mobile SDK Component Reference | Descope Documentation"
mirrored_at: 2026-08-06T03:03:26.660Z
host: docs.descope.com
cited_in_42a: true
mirror_canonical: "https://index.42a.ai/docs.descope.com/mobile-sdk"
---

> **Original source:** https://docs.descope.com/mobile-sdk

SDKs

This guide is meant for developers that are NOT using Descope Flows to design login screens and authentication methods.

If you'd like to use Descope Flows, [Quick Start](https://docs.descope.com/getting-started) should be your starting point.

This is a list of all of the Mobile SDKs we currently support.

Descope enables you to add authentication to your mobile application. The authentication guides below contain step-by-step implementation of different authentication methods using Descope Mobile SDKs.

Each guide will direct you through the steps you need to follow irrespective of your chosen language and framework. The guides also contain sample code for all the languages and frameworks supported by Descope.

Authentication Method

Description

Guide

One Time Password (OTP)

A single-use code that grants a user access to your application. Descope supports OTP sent via SMS and email today.

[Guide](https://docs.descope.com/auth-methods/otp/with-sdks/mobile)

Magic Link

A single-use link sent to a user's email address or phone via sms that grants them access to your application.

[Guide](https://docs.descope.com/auth-methods/magic-link/with-sdks/mobile)

Enchanted Link

An enhanced version of magic link that enables a user to login by clicking a link on a different device.

[Guide](https://docs.descope.com/auth-methods/enchanted-link/with-sdks/mobile)

Social Login (OAuth)

Enable users to access your application by using identities they have created on other applications (Google, Twitter, LinkedIn, etc.).

[Guide](https://docs.descope.com/auth-methods/oauth/with-sdks/mobile)

Authenticator Apps

Enable users to access your application by using time-based numeric codes generated by apps like Google Authenticator and Authy.

[Guide](https://docs.descope.com/auth-methods/auth-apps/with-sdks/mobile)

Biometrics (WebAuthn)

Enable users to access your application by using passkeys built into their devices (fingerprint scanning, facial recognition, security keys).

[Guide](https://docs.descope.com/auth-methods/passkeys/with-sdks/mobile)

Single Sign On (SSO/SAML)

Enable users to access your B2B application using single sign-on with identity providers like Google, Microsoft, and Okta.

[Guide](https://docs.descope.com/auth-methods/sso/with-sdks/mobile)

You can reference the sample applications below to familiarize yourself with the different methods and quickly start your client-side implementation.

Language

GitHub Location

Swift

[Swift Sample App](https://github.com/descope-sample-apps/swift-sample-app)

Flutter (flows)

[Flutter Sample App (Flows)](https://github.com/descope-sample-apps/flutter-sample-app)

Flutter (without flows)

[Flutter Sample App (No Flows)](https://github.com/descope-sample-apps/flutter_sample_app_auth_func)

For diagnosing authentication, session, and flow issues during development, see [Logging](https://docs.descope.com/mobile-sdk/logging).