If you’ve been tracking the rumor mill surrounding the upcoming Pixel 11, you’ve likely been waiting for the moment Google finally closes the gap on one of the most persistent hardware disparities between Mountain View and Cupertino. For years, Pixel enthusiasts have watched Apple’s Face ID set the gold standard for biometric authentication—a seamless, infrared-driven experience that just works, regardless of whether you’re sitting in a sun-drenched cafe or fumbling for your phone in a pitch-black bedroom. The whispers were loud: Google was finally ready to answer back with an internal initiative codenamed “Project Toscana.” But, as is often the case in the high-stakes world of smartphone engineering, the reality of physics and integration has proven more stubborn than the marketing roadmaps.
The news breaking this week is a tough pill for the hardware-obsessed to swallow: Project Toscana will not be making its debut in the Pixel 11 series. Despite the aggressive development cycles Google has maintained with its Tensor-led hardware strategy, sources indicate that the infrared-based face unlock system is simply not ready for the rigors of a flagship launch. While it’s tempting to label this as a failure, it’s more accurately a reflection of the immense difficulty involved in moving from software-defined recognition to dedicated, high-fidelity hardware.
The Technical Hurdle: Beyond Machine Learning
To understand why this delay matters, we have to look at how the current Pixel authentication actually functions. Since the Pixel 8 Pro, Google has made massive strides in elevating its camera-based face unlock to a “Class 3” biometric standard, allowing it to be used for banking apps and secure logins. However, this system relies heavily on machine learning and visible light. It’s a software triumph, certainly, but it hits a wall the moment the ambient light drops. When you’re relying on a standard CMOS sensor to capture facial geometry, shadows and low-light noise are your enemies. It’s clever engineering, but it’s not the same as having a dedicated depth-mapping system.
Project Toscana was designed to change that equation entirely. By utilizing hybrid near-infrared (NIR) sensors, the system was intended to function independently of ambient light. This isn’t just about convenience; it’s about reliability. In the industry, we often talk about “sensor fusion,” and Toscana was Google’s attempt to marry its advanced AI processing with a robust, hardware-level depth map. The goal was to achieve parity with Apple’s Face ID, providing a level of speed and security that isn’t dependent on the camera’s ability to “see” your face in the traditional sense. The fact that this technology reached the prototype stage—and reportedly performed well in UX testing—suggests that Google isn’t abandoning the vision, but rather acknowledging that the integration isn’t quite ready for the mass-market scrutiny of a flagship rollout.
The Quest for Invisible Hardware
What makes the Project Toscana delay particularly interesting is the ambition behind its implementation. Google isn’t just looking to slap a notch on the screen and call it a day. The engineering team has been exploring the feasibility of under-display infrared hardware. The dream here is a completely clean aesthetic: a front-facing sensor suite that remains invisible to the user until it’s needed, firing through the display stack without compromising the screen’s brightness or color accuracy. Achieving this requires a delicate balance of sensor sensitivity and display transparency, a feat that has tripped up many manufacturers attempting to hide cameras and sensors beneath pixels.
We’ve been here before, haven’t we? Long-time Google fans will remember the Pixel 4, which featured a dedicated infrared array and even Soli radar for gesture control. That hardware was ahead of its time, but it also came with a bulky top bezel that felt antiquated even the day it launched. Project Toscana represents the next evolution of that philosophy—trying to bring back the security and low-light prowess of the Pixel 4’s dedicated hardware, but wrapping it in the sleek, bezel-less design language of the modern era. The delay, while frustrating, highlights the sheer complexity of shrinking these components and calibrating them to function through a modern, high-refresh-rate OLED panel. It’s the classic battle between form and function, and for the Pixel 11, it appears that engineering constraints have forced a tactical retreat.
…dard camera sensor, the system is essentially playing a game of catch-up with physics. It attempts to compensate for poor lighting with aggressive image processing and noise reduction algorithms, but it can never truly replicate the reliability of a dedicated Infrared (IR) flood illuminator and dot projector. While the software team at Google deserves credit for pushing Class 3 security through a standard lens, it remains a reactive solution rather than a proactive one.
The Trade-off: Integration vs. Aesthetic Purity
The core challenge behind “Project Toscana” isn’t just getting the sensors to work; it’s getting them to work invisibly. Unlike competitors who have historically opted for a “notch” or a “dynamic island” to house the necessary hardware, Google has been aggressively pursuing a clean, all-screen aesthetic. Integrating high-fidelity IR sensors beneath an OLED panel introduces significant hurdles regarding light transmission and signal interference.
When you place an infrared array under a display, you are effectively asking the light to pass through a matrix of pixels, metal traces, and layers of glass without losing the structural integrity of the biometric map. The following table outlines the fundamental differences between the current software-reliant approach and the hardware-intensive path Google is attempting to master:
| Feature | Current Pixel (Camera-Based) | Project Toscana (IR Hardware) |
|---|---|---|
| Lighting Dependency | Requires ambient light | Self-illuminating (works in pitch black) |
| Processing Load | Heavy reliance on Tensor NPU | Hardware-level verification |
| Form Factor | Minimal footprint | Requires under-display sensor array |
| Security Class | Class 3 (Software-verified) | Class 3 (Hardware-verified) |
The delay of Project Toscana suggests that Google is unwilling to compromise on its design language. They aren’t interested in adding a bulky sensor housing back to the flagship aesthetic, even if it means waiting another cycle to perfect the under-display integration. It is a classic “Google” play: prioritizing the clean, modern look of the device over the immediate implementation of a feature that would require a visible hardware footprint.
Infrastructure and the Future of Biometrics
We must also consider the broader ecosystem. Google’s commitment to Android BiometricPrompt and the underlying security architecture is robust, but it is built to be hardware-agnostic. By continuing to iterate on software-based recognition, Google is actually strengthening the security capabilities of the entire Android ecosystem, not just the Pixel line. While Apple’s hardware approach is monolithic and proprietary, Google’s strategy is to lift the floor for all manufacturers.
However, for the power user, this doesn’t soften the blow. The absence of Toscana in the Pixel 11 means we will likely see another year of “good enough” in low-light environments. We are essentially watching Google try to solve a hardware problem with a software hammer. While the hammer gets better every year—thanks to the Tensor Processing Unit (TPU)—it is never going to be the same as having a dedicated laser-based depth map of your face. For more on this topic, see: Lockin’s New Smart Locks Never .
For those interested in the technical standards that define these security classes, you can find more information on the official Android developer documentation:
- Android BiometricPrompt API Documentation
- Android Security: Biometric Authentication
- W3C Web Authentication (WebAuthn) Standards
Perspective: The Cost of Perfectionism
From where I sit, the cancellation of Project Toscana for the Pixel 11 is a calculated risk. Google is clearly betting that a perfect, under-display implementation is better than a compromised, “notched” implementation. In the smartphone market, where iterative updates are the norm, this level of patience is rare. It suggests that Google is looking at the Pixel 12 or 13 as the true maturation point for their next-generation hardware stack. For more on this topic, see: What a Simple Elevator Change . For more on this topic, see: What the Galaxy S26 Ultra’s .
We are currently in a period where software is attempting to outpace physical limitations. While I’m disappointed that we won’t see the hardware jump this year, I respect the decision to hold back rather than ship a sub-par experience. The Pixel 11 will undoubtedly be a powerhouse of AI-driven features, but until the hardware catches up to the vision, the “Face ID” gap will remain the most visible asterisk on Google’s spec sheet. As enthusiasts, we have to decide: do we want the phone to look like the future today, or do we want the hardware to function like the future today? For now, Google is betting on the former, hoping the software can keep us satisfied in the interim.
