Facebook now allows Android apps to request phone number for login and skip SMS verification if the number matches the one in the user's Facebook profile
Jordan Novet / VentureBeat :
Context & Ripple Effects
This move builds directly on Account Kit, which Facebook launched earlier in 2016 to let developers offer phone-number-only signup and login. What changes now is friction: an Android app can ask for the number and skip the SMS verification step entirely whenever it matches the one already on the user's Facebook profile.
The phone number had been becoming Facebook's cross-app identity key throughout 2016; the later coverage shows the company eventually hedging that bet, first letting users do [[a:929899|two-factor authentication with hardware keys or code-generating apps instead of a phone number]], then removing phone-number signup from Messenger altogether.
First-order effects
- Developers building on Account Kit get faster Android onboarding with no verification-code step, cutting both SMS delivery costs and signup drop-off at exactly the moment a user decides whether to complete registration.
- Users who keep their number current on their Facebook profile can log into participating Android apps with just the number, no code entry.
Second-order effects
- SMS aggregation and verification vendors lose volume on every Android login flow where profile-matching replaces a sent code, pressuring the economics of pay-per-message identity checks.
- Rival login SDKs face a lower-friction benchmark on Android, since Facebook is verifying against data it already holds rather than charging each app for its own verification loop.
Third-order effects
- Identity verification shifts from per-app proof-of-possession toward platform-attested data: whoever holds the authoritative profile becomes the trust layer for third-party apps. The later walk-backs — hardware-based 2FA and Messenger's return to Facebook-account-only signup — show how reversible that dependence on the phone number proved to be.
The trend: Consumer identity is consolidating around platform-held profile data as the verification layer, with each major login provider deciding how much of the phone number's role to absorb or shed.