Apple adds ‘face unlock’ to the iPhone Duo, but it’s not Face ID
- ID
- 47142
- Status
- summarized
- Published
- 17 Nov 2026, 3:26 AM
- Fetched
- 17 Nov 2026, 3:51 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/11/16/apple-adds-face-unlock-to-the-iphone-duo-but-its-not-face-id/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 2.0
- Created
- 17 Nov 2026, 3:51 AM
- Tags
- Audience
- developers
What happened
With the iOS 27.3 developer beta released Monday, Apple added a "face unlock" option to its foldable iPhone Duo, which shipped without Face ID because the thin foldable chassis has no room for the TrueDepth sensor array (flood illuminator plus dot projector casting 30,000+ infrared dots). The feature uses the front camera and only works when the phone is close and the user authenticated with Touch ID or passcode recently — Apple Pay and passwords still require Touch ID, and re-authentication is forced after 45 minutes of inactivity. Bloomberg reporting cited in the article says Apple is working on true Face ID for a future Duo, and the same update also fixes a complaint about a workaround early adopters used to force the phone to lock.
Why it matters
Almost nothing here changes what a working developer, founder, or AI builder should do this week — it is a consumer hardware convenience feature with no Malaysia or Southeast Asia angle and no pricing, availability, or platform implications stated. The one concrete thing: if you ship an iOS app, this is evidence that biometric capability on Apple devices is fragmenting (a device can now have face unlock that is explicitly not Face ID, with Apple Pay and password autofill still gated on Touch ID), so don't hard-assume Face ID when designing auth flows — check Apple's docs for how this is exposed, since the article doesn't say.
Discussion angle
The 45-minute inactivity re-auth window is the interesting design bit: a deliberate 'convenience unlock vs. security boundary' split where the fast path expires and falls back to the strong factor. Worth 5 minutes on whether that pattern — cheap unlock for low-risk actions, hard factor for payments and secrets — is something you already do in your own apps, or whether you've just been treating 'logged in' as one binary state.