Verified Credential flow requires II anchor

Is there a reason that the verified credential presentation flow requires the user to manually type their II anchor to issue a credential? This makes the feature unusable in my opinion. Users are no longer aware of their anchor number and are not shown it on a regular basis. If they have to figure out how to find their anchor and type it into the id.ai/vc-flow UI, then they are almost guaranteed to not go through with the action.

Is there any workaround to not require this or to somehow fill the field for the user?

bump

Any information on this or any plans for improvements for the flow UI?

cc @sea-snake

My words, like silent raindrops, fell and echoed in the wells of silence.

My desires, like quiet hummingbirds, flapping wings about the mute garden

cc @aterga

The VC flow has been designed quite a long time ago, for the old II product.

When II moved to the new product (id.ai), we’ve also observed the usability issues your report, and decided to keep the minimal backwards compatible version alive to avoid disruption, but to not iterate on it, since it became apparent that a holistic VC redesign would be necessary.

Since then, the team has been focusing on other priorities and did not yet prioritize the new VC flow, although it is on our longer terms backlog.

Thank you for your response. I appreciate the explanation of where the feature is at and I understand the constraints the team had to consider with the move to id.ai as well as the prioritization of resources in relation to the work you described vs other work the team considers more pressing.

I think the verified credential feature is a particularly interesting and useful feature (especially when taken with other aspects of II such as how it isolates user identities between applications). It was truly insightful for the team to implement such a feature and I think there are a number of capabilities an app could expose that would leverage the infrastructure. I’m happy to hear that an improved VC flow is on the team’s backlog. Until the user experience is more palatable, I think the feature (as I mentioned) cannot really be implemented by apps with any expectation of usage - IE users are simply unlikely to complete the flow. While prioritizing work is never simple, I hope the team will take this into account and consider investing in keeping this feature a viable option for IC apps to have in their toolkit.

Also - thank you @Lorimer for your help in getting the right sets of eyes on my questions.