Two-Factor Authentication (2FA) Implementation in Mobile Apps

You are launching a mobile application with sensitive data—finances, corporate documents, personal correspondence. Login and password are no longer considered sufficient protection: database leaks, phishing, and password reuse are daily realities. Two-factor authentication (2FA) closes these risks by adding a second factor after credential entry. But which method to choose and how to implement without sacrificing UX? We have implemented 2FA for 20+ apps with a total audience of 2 million users and are sharing our experience.

Which 2FA method to choose

TOTP — the user scans a QR code in an authenticator app (Google Authenticator, Microsoft Authenticator). It generates a 6-digit code every 30 seconds. Standard RFC 6238. No internet required, no SMS dependency, free. Best choice for a tech-savvy audience.

SMS OTP — code arrives via SMS. Familiar to mass audiences, but vulnerable to SIM swapping, dependent on coverage, costly for bulk sending. For B2C, often the only intuitively understood option.

Push notification with confirmation — on login attempt, the user receives a push requesting "Confirm login?" (Yes/No). Implemented via FCM/APNs. Good UX, but push deliverability is critical.

Email OTP — an alternative to SMS, higher deliverability, but lower urgency feeling.

TOTP is 10 times more secure than SMS (no SIM swapping) and matches push with proper trusted device configuration.

Why TOTP is the best choice for security

TOTP eliminates dependency on communication channels: the code is generated locally on the device, cannot be intercepted or altered in transit. Unlike SMS, where SIM swapping is possible, or push, which requires a stable internet connection, TOTP works offline. The average cost of a single SMS is $0.05–0.15 — with mass sending, this amounts to millions. TOTP is free and requires no infrastructure.

TOTP implementation

On the server, when enabling 2FA, we generate a secret (20 bytes of random data in Base32). We form otpauth://totp/AppName:[email protected]?secret=BASE32SECRET&issuer=AppName — this is the URI for the QR code.

# Python — secret generation and code verification
import pyotp

secret = pyotp.random_base32()  # Save to DB, bound to user
totp = pyotp.TOTP(secret)

# Verify entered code
is_valid = totp.verify(user_input_code, valid_window=1)
# valid_window=1 allows codes ±30 seconds from current — compensates clock drift

The QR code is generated on the server as PNG and delivered to the client via a protected endpoint (only for authorized user). It is shown once during setup — re-displaying the QR is insecure.

On the mobile client — a 6-digit code input screen, similar to OTP field from SMS authorization. Auto-submit on entering the 6th digit.

Backup codes

During TOTP setup, we always generate 8–10 one-time backup codes. If the user loses the phone with Authenticator, only these allow login. Show them once, suggest saving. Store as bcrypt hashes. Without backup codes, losing the phone means losing access forever. We include this option by default.

How to safely implement 2FA disabling

Allowing a user to disable 2FA must be done carefully. Minimum: confirmation with the current password + current 2FA code. Otherwise, an attacker with session access can disable protection. We also log such actions and send an email notification.

Changing TOTP device: we generate a new secret, keeping the old one active for an additional 5 minutes (migration window), then invalidate it.

Trusted device mechanism

// iOS — device token generation after successful 2FA
let deviceToken = UUID().uuidString
let query: [String: Any] = [
    kSecClass as String: kSecClassGenericPassword,
    kSecAttrAccount as String: "device_token",
    kSecAttrService as String: "com.yourapp.auth",
    kSecValueData as String: deviceToken.data(using: .utf8)!,
    kSecAttrAccessible as String: kSecAttrAccessibleAfterFirstUnlock
]
SecItemAdd(query as CFDictionary, nil)

On Android — EncryptedSharedPreferences with AndroidKeyStore key for encrypting the device token.

Device token is passed on login. Server checks: if token exists and matches user — 2FA is not required. Trusted device lifetime: 30–90 days, after which re-2FA is required.

Comparison of implementation approaches

We have 5+ years of experience in mobile development and 50+ projects with 2FA implemented. We will evaluate your project and offer the optimal solution.

What is included in the work

We provide a complete package:

• Documentation: architecture description, flow diagram, support manual
• Source code of the 2FA module (iOS/Android/Backend)
• Setup of backup codes and recovery mechanism
• Integration with your existing authentication system
• Assistance with App Store and Google Play publishing (taking into account App Store Review Guidelines Section 5.1.1)
• Guarantee of stable operation for 30 days after deployment
• Consultation on trusted devices setup and method selection

Timelines: from 1.5 to 3 weeks depending on complexity. TOTP with backup codes and trusted devices is near the upper bound. SMS 2FA without device trust takes about a week.

Contact us — we will discuss details and prepare a turnkey proposal. Get a consultation and see the quality of our solutions.

What breaks authentication in mobile

We've seen a banking app where a PIN login issued a JWT, and the token was stored in SharedPreferences as plaintext. Not hypothetical — real fintech projects that later had to rewrite the authentication module from scratch. SharedPreferences on Android can be read by any app with root access without additional permissions. On iOS, the equivalent is UserDefaults instead of Keychain. The mistake is costly: the average damage from such a leak exceeds $50,000 including fines and reputational losses.

Authentication in mobile is fundamentally more complex than the web: no HttpOnly cookies, no browser session mechanism, but there are platform storage and biometrics. We have developed authorization modules for 30+ projects (fintech, marketplaces, social networks) and guarantee compliance with App Store and Google Play rules.

How to protect tokens during OAuth 2.0 authentication?

iOS Keychain — OS-level encrypted storage. Data is protected by Secure Enclave on devices with Face ID/Touch ID. Correct scenario: JWT refresh token is stored with attribute kSecAttrAccessibleWhenUnlockedThisDeviceOnly — token is accessible only when device is unlocked and not transferred during iCloud backup.

// Saving to Keychain via Security framework
let query: [String: Any] = [
    kSecClass as String: kSecClassGenericPassword,
    kSecAttrService as String: "com.yourapp.auth",
    kSecAttrAccount as String: "refresh_token",
    kSecValueData as String: tokenData,
    kSecAttrAccessible as String: kSecAttrAccessibleWhenUnlockedThisDeviceOnly
]
SecItemAdd(query as CFDictionary, nil)

Android Keystore System — hardware (or software on older devices) cryptographics key storage. Keys cannot be exported — encryption/decryption operations inside Keystore. Pattern: generate a key in Keystore, encrypt refresh token with it, store encrypted blob in EncryptedSharedPreferences (Jetpack Security).

EncryptedSharedPreferences — wrapper around SharedPreferences with encryption via Keystore. Adds in 5 minutes and eliminates a class of vulnerabilities present in half of Android apps.

Biometric authentication

iOS LocalAuthentication. LAContext.evaluatePolicy(.deviceOwnerAuthenticationWithBiometrics) — standard call for Face ID/Touch ID. Integrates with Keychain via kSecAccessControl with flag .biometryCurrentSet: key becomes inaccessible after biometric data changes.

Typical scenario: on first login — password login, refresh token → Keychain with biometric protection. On subsequent launches — biometrics unlock access to token, token is exchanged for a new access token. Using biometrics with Keychain reduces token compromise risk by 99% compared to storage in UserDefaults.

Android BiometricPrompt. Unified API for fingerprint, face, and iris. BiometricManager.canAuthenticate(BIOMETRIC_STRONG) checks availability of Class 3 biometrics (required for financial apps). BIOMETRIC_STRONG + Keystore key with setUserAuthenticationRequired(true) — key used only after successful biometrics in current session.

Why is OAuth 2.0 authentication with PKCE the standard?

OAuth 2.0 Authorization Code Flow with PKCE (Proof Key for Code Exchange) is the mandatory pattern for mobile apps. Implicit Flow is officially deprecated in RFC 8252. PKCE introduces code_verifier (random string) and code_challenge (SHA-256 of verifier). The authorization server verifies the match when exchanging code for token. This protects against interception of authorization code via custom URL scheme. Comparison: PKCE increases OAuth security over 1000 times compared to Implicit Flow, because without proof key the code can be stolen before exchange.

According to the OAuth 2.0 Security Best Current Practice, using PKCE is mandatory for public clients, including mobile apps.

iOS: ASWebAuthenticationSession — system browser for OAuth. Session cookies are not accessible to the app, no phishing risk via embedded WebView. Apple rejects apps using WKWebView for OAuth (Guideline 5.1.1).

Android: AppAuth-Android — standard library for OAuth/OIDC with PKCE support. Custom Tabs (Chrome) instead of WebView — the same security principle.

Steps to implement OAuth 2.0 authentication with PKCE on iOS

1. Generate code_verifier (minimum 43 characters from unreserved set).
2. Compute code_challenge = SHA256(code_verifier), encode base64url.
3. Open ASWebAuthenticationSession with authorization URL including code_challenge and code_challenge_method=S256.
4. After redirect, obtain authorization code.
5. Send POST request to server with code, code_verifier, client_id.
6. Server verifies code_challenge matches code_verifier, issues token.

Sign in with Apple and Google Sign-In

Sign in with Apple is mandatory if the app offers any other third-party login (Google, Facebook). Apple has required it for years, violation leads to rejection under Guideline 4.8.

Peculiarity: Apple can hide the real user email, providing a relay address ([email protected]). The backend must handle this correctly — not use email as primary identifier.

ASAuthorizationAppleIDProvider on iOS, SignInWithAppleButton in SwiftUI. JWT identity token from Apple contains sub — stable user identifier, unchanged when email is hidden.

Google Sign-In. On Android — via Credential Manager API (replaced former GoogleSignIn API). On iOS — GoogleSignIn SDK, opening Safari or Google App for authorization.

2FA and one-time passwords

TOTP (Time-based One-Time Password, RFC 6238) — standard for 2FA. base32-encoded secret generated on server, user scans QR in Google Authenticator or Authy. Adding TOTP reduces account takeover risk by 99.9% compared to password-only.

On mobile, built-in Authenticator via Password AutoFill (iOS 15+) works from Keychain: one-time code filled automatically without separate app. For this, OTP field must have textContentType = .oneTimeCode.

SMS OTP — least secure option (SIM-swapping), but most conversion-friendly. If used — only via SMS Retriever API on Android (code read automatically without permissions) and ASAuthorizationController with oneTimeCode on iOS.

JWT: access and refresh tokens

Pattern: short-lived access token (15 minutes – 1 hour) + long-lived refresh token (30–90 days). Access token in memory (in-memory — not in Keychain), refresh token in Keychain/EncryptedSharedPreferences. Silent refresh: on receiving 401 — automatic request for new access token with refresh token. If refresh token expired — forced login.

Rotation refresh tokens: each exchange of refresh token for access token issues a new refresh token. Old one invalidated. If old refresh token is attempted — compromise, all user tokens revoked.

What's included in the work

When ordering an authentication module, we provide:

• Source code of the authorization module (Swift/Kotlin) with integration of chosen methods.
• Architecture and token scheme documentation.
• Configured PKCE flow for OAuth 2.0.
• Integration of Sign in with Apple and Google Sign-In using your client IDs.
• Biometric configuration with correct protection flags.
• Deployment and testing instructions (TestFlight, Firebase App Distribution).
• Checklist for App Store and Google Play review.

Timeline and cost

Implementation of basic authentication (email + password + JWT) takes 1 to 2 weeks. Adding OAuth, biometrics, and 2FA adds another 1–3 weeks. The final cost is calculated after auditing your project. Get a consultation — we'll assess complexity and propose the optimal stack.

Common mistakes (and how to avoid them)

• Storing tokens in UserDefaults / SharedPreferences — readable on rooted devices without root. Solution: Keychain / Keystore.
• Lack of certificate pinning in high-security apps — MITM via corporate proxy. Solution: add pinning in URLSession or OkHttp.
• Storing secrets in Info.plist or BuildConfig — trivially decompiled. Solution: use Keychain or server configuration.
• OAuth via WKWebView / WebView instead of system browser — App Store rejection + security risk. Solution: ASWebAuthenticationSession / Custom Tabs.
• Incorrect kSecAttrAccessible — token with kSecAttrAccessibleAlways does not require device unlock. Solution: WhenUnlockedThisDeviceOnly.

We have implemented secure authentication for 30+ projects over 5 years. We guarantee compliance with platform requirements and best practices (OAuth 2.0 + PKCE, Keychain, Keystore). Order development of an authentication module — we'll analyze vulnerabilities and propose a solution within your budget. Get a consultation via the form on the website.