Posts

Part 4: Beyond Passwords - The Passkey Revolution

Image
 A Staff-level architecture guide to implementing phishing-resistant authentication using FIDO2, WebAuthn, and the Credential Manager API. In  Part 1 , we built the Stateless Blueprint. In  Part 2 , we secured tokens in the Hardware Vault. In  Part 3 , we mastered the Transport Layer. But even a bulletproof architecture is vulnerable if the user’s “front door” is left ajar by a weak password. Today, we eliminate the weakest link in the security chain:  The Password. ⚡  TL;DR Passwords  are “shared secrets” — inherently vulnerable to phishing and breaches. Passkeys  use asymmetric cryptography (FIDO2/WebAuthn) to provide  phishing-resistant  authentication. Credential Manager API  is the unified Android entry point for Passkeys (WebAuthn), Federated Sign-in, and legacy passwords. The Shift:  Authentication is moving from “what users know” to “what devices prove,” emerging as the dominant long-term path for high-scale application...

Part 3: The Interceptor Pattern - Mastering Transport & Concurrency

Image
 A Staff-level guide to high-concurrency Android networking: Implementing single-flight token refreshes with OkHttp and Kotlin Mutex. In  Part 1: The Stateless Blueprint  and  Part 2: The Android Vault , we designed and stored our secure tokens. Now comes the Staff-level operational challenge:  The Transport Layer. When scaling to 5 million users, your networking layer must handle high-concurrency environments without collapsing. If a token expires while 10 parallel requests are in flight, you face a “Refresh Storm.” Today, we build a  Networking Command Center  using OkHttp, Kotlin Mutex, and the  Single-flight refresh pattern . ⚡  TL;DR Stateless auth  scales better by removing session-stickiness on the backend. Store tokens  using hardware-backed Android Keystore to prevent extraction. Use OkHttp + Mutex  to prevent “Refresh Storms” and race conditions. Implement Single-flight refresh  to ensure only one network call up...