The current iOS security model lacks a way to temporarily disable Face ID after locking the device, which could be useful in situations where immediate biometric access is undesirable. For example, when handing a phone to someone else or during potential law enforcement interactions where biometric coercion might occur. This gap means users can't selectively enforce passcode-only access during specific time windows, despite iOS offering other granular security controls.

A More Flexible Approach to Biometric Security

One approach could be adding a native setting that lets users configure a time delay during which Face ID or Touch ID would be disabled after locking. This might include:

• Adjustable timer options (e.g., 1 minute, 5 minutes, or "until next unlock")
• Separate toggles for different biometric methods
• Clear visual indicators when biometrics are temporarily disabled

This would build upon existing security features like the "Require Passcode" timing setting, but with finer control specifically for biometric authentication. The feature could appeal to privacy-conscious users, professionals in sensitive fields, and those who occasionally share devices but want to ensure the owner must use a passcode for subsequent unlocks.

Implementation Considerations

For a phased rollout, a simple version might start with a basic toggle in Settings, while more advanced versions could offer:

• Custom durations and method-specific controls
• Integration with Shortcuts for automated rules
• Status bar indicators when active

This would differ from Android's manual Lockdown Mode by offering automated timing options, and from existing jailbreak tweaks by maintaining iOS's security model. The main challenges would be UI clarity (to distinguish from similar settings) and preventing user confusion when the feature is active.

While primarily a user security enhancement, this could align with Apple's privacy-focused branding by giving users more nuanced control over when their biometric data can be used, without significantly impacting the convenience of normal use cases.