For architecture and construction teams, WhatsApp’s passkey rollout is less a lesson in building technology than in coordinating a user-facing change across multiple technical layers. WhatsApp committed to adopting passkeys in 2023, aiming for a fast, phishing-resistant sign-in option that reduces friction and helps protect against account takeovers and credential theft.
A change that crosses system boundaries
Passkeys use public-private key cryptography and authenticate users through biometric or screen-lock authentication. On the server side, WhatsApp’s backend is written in Erlang and calls the Rust webauthn-rs library through a native interface; that library handles signature verification and credential parsing. The implementation therefore spans both the sign-in experience and the services that process authentication.
For AEC software and BIM workflows, the transferable point is the integration pattern, not the specific technology choice. When a project team introduces a new access method or platform capability, it can affect interfaces, backend services and the path users take when something goes wrong. WhatsApp’s reported approach makes those connections visible without suggesting that passkeys or the same software stack are suitable for every project.
Design the prompt—and the recovery path
WhatsApp developed its passkey-creation prompts through extensive A/B testing. It also built an error-handling layer that allows traditional authentication to remain available if a passkey flow cannot complete. Together, these details show attention to both the route a user is encouraged to take and the route available when that process fails.
That is a practical consideration for project-delivery teams evaluating digital tools: adoption depends not only on the planned workflow but also on how clearly it is presented and what happens when it cannot be completed. WhatsApp’s testing and fallback are specific reported choices; applying the same principle in AEC would mean evaluating prompts and recovery options against the needs of the relevant project users.
Scale makes small workflow changes consequential
Mayank Manuja, identified as an Android Engineer on WhatsApp’s Registration and Access team, led the design and implementation of passkey-based authentication. He said that even a small improvement to WhatsApp touches billions of users worldwide. For AEC, the scale is different, but the underlying delivery question remains useful: how will a change behave across the full set of people, systems and handoffs that depend on it?
The integration also involved collaboration between WhatsApp and Google teams to address challenges encountered while implementing passkeys. That offers a restrained but relevant project-delivery takeaway: changes that cross platform boundaries may call for coordination between the teams responsible for different parts of the workflow.
