The quietest feature is often the best one: How silent verification is changing the user login experience
There’s an old principle in product design, often attributed to Macintosh visionary Jef Raskin: the best interface is no interface. Users are not interested in interacting with a system for its own sake; they want to achieve an outcome as efficiently as possible. Every additional step, such as copying a code between apps, introduces friction.
I’ve been thinking about this lately, because much of my work at Nokia revolves around a question that sounds technical but is really about user experience: what should the network handle automatically, and what should users be required to do manually?
For two decades, the industry’s answer skewed heavily toward manual intervention. Users are asked to prove things the network already knows. Developers, in turn, have built layered verification flows on top of infrastructure that could otherwise provide answers directly. The SMS one-time passcode (OTP) is perhaps the most familiar example of this approach.
This is now beginning to change, particularly as the industry moves into the AI supercycle.
A small login, a significant shift
At MWC26 in Barcelona, we announced a landmark commercial deployment. Blocksport, a technology platform provider for sports clubs, leagues and venues, has integrated Nokia’s Number Verification API through our Network as Code platform. The first live deployment was for Telekom Baskets Bonn in Germany, with AS Monaco Basket in France following shortly thereafter.
In both cases, SMS OTPs were replaced with silent, network-based authentication. Users simply open the app, and they’re in, typically in under a second.
On the surface, this represents a modest improvement in user experience. Underneath, it’s a network capability being brought to a consumer-facing product, with a business model other developers can replicate. For telecommunication providers, this creates a new monetization pathway, advancing connectivity by exposing network intelligence through APIs that developers can directly build on.
Blocksport is also piloting Nokia’s Quality on Demand API to guarantee premium network performance during live events. The underlying idea is the same: the network can deliver capabilities on behalf of the user that previously required complex integration.
As Vladimir Liulka, CEO of Blocksport, noted:
“By integrating Number Verification, Blocksport is removing friction from the fan journey while creating commercial value for its customers.”
That second half matters. It’s easy to build a demo, but much harder to build something that scales.
From concept to production
In recent years, industry efforts to expose network capabilities to developers have made steady progress. Standards evolved, and frameworks began to mature. However, a key barrier remained: operator readiness to support these capabilities in live, commercial environments.
Over the past 12 months, this has shifted. Alignment across CAMARA, TMF and 3GPP has progressed, commercial models have stabilized and operators have increased their commitment to Network as Code. As a result, developers can increasingly think in terms of capabilities rather than underlying infrastructure.
And then there’s the moment you actually see it work. The real impact becomes clear when these capabilities are experienced in practice. With silent network authentication, the familiar login flow, entering a number, waiting for an SMS, inputting a code, is simply removed. Users expect the next step, but it never comes; access is granted instantly.
The reflex is so deeply wired that its absence registers, briefly, as something missing. That tells you how overdue this shift is.
At this point, the API itself becomes less significant than the applications it enables.
Building real commercial value
It is important to recognize that network APIs alone do not generate value automatically. Revenue is driven by real-world deployments and sustained adoption. Replacing SMS OTP with silent authentication offers clear commercial potential across operators, platforms, and developers, but it must be realized through practical implementation.
This is where I keep coming back to Amara’s Law: we tend to overestimate technology in the short run and underestimate it in the long run. As more developers incorporate network capabilities into their applications, the cumulative impact will become increasingly significant.
Authentication is only the starting point. Capabilities such as Quality on Demand are entering commercial use, while Device Location Verification is supporting fraud prevention. Nokia’s work at MWC26 with Google Cloud also points toward future models, including intent-based workflows where AI-driven systems can dynamically access network capabilities.
The portfolio keeps widening, and the most interesting use cases are the ones we haven’t built yet.
Looking ahead
As developers begin to treat network capabilities in the same way they use payment APIs or mapping services, new opportunities will emerge across industries. Early adoption is visible in fan engagement, but similar challenges (and opportunities) exist in sectors such as mobility, financial services, healthcare and gaming.
In these contexts, the network often has access to information that can significantly improve application performance and user experience. For example, silent authentication can allow a player to seamlessly reconnect after a dropped session, without login delays or user intervention.
With 85+ partners in our Network as Code ecosystem, and Nokia’s recent ranking by ABI Research as the overall leader in Network API Platforms for Internal Exposure, the foundation is already in place. Adoption on the demand side is now accelerating.
For end users, however, these changes will largely go unnoticed. That’s the point. The best interface is no interface. The quietest feature is often the best one.
To learn more about how Nokia is helping developers and enterprises unlock the full value of network capabilities through APIs, take a look at our Network as Code webpage.
