W3C home > Mailing lists > Public > public-credentials@w3.org > November 2022

Re: Google Browser/FedCM team exploring native APIs for CHAPI

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 27 Nov 2022 17:52:35 -0500
Message-ID: <CAMBN2CSJweptz1SXDPQv4vVC-_s5w0rQbyffzGVprpR6g7oGpw@mail.gmail.com>
To: public-credentials@w3.org
On Tue, Nov 22, 2022 at 3:34 PM David Chadwick wrote:
> Just to note that OpenID4VCI has always enabled individuals to choose their wallet in the cross device flow because the Issuer shows a QR code to the user, who chooses which wallet app to scan it into.

Sure, but that's missing the point. What CHAPI does is enable open
wallet selection no matter if you're using a native app or a web app,
no 2nd device necessary.

The "wallet selection handwave" that was being referred to was this
insistence that to have open wallet selection, and get rid of NASCAR
screens, you need a second device. Except for MFA flows, many of us
don't regularly swap between transferring an interaction from our
laptop, to our mobile, and back. Even MFA flows are fairly annoying if
you have to do them regularly.

What CHAPI enables is open wallet selection, web and native, without
needing to pick up a 2nd device... thus keeping you in the flow of
whatever website you're on. That there is now interest in making it
native in the browser could open up a variety of other possibilities
like seamless flows between web-to-native-and-back.

That's what people are getting excited about; it's a better experience.

-- manu

Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
News: Digital Bazaar Announces New Case Studies (2021)
Received on Sunday, 27 November 2022 22:53:24 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 27 November 2022 22:53:25 UTC