Feature request: nudge identities without a recovery method during app sign-in

Hi II team,

Apps where people hold value under their Internet Identity share a gap: many first-time users sign in once, often with Google or a single passkey, and never add a second way in. If they lose that one method, the funds go with it, and the app can’t help, because by design it can’t see how an identity is protected.

Today II nudges this on the management dashboard (the actions for a missing recovery phrase, recovery email or second access method). A newcomer who only meets II inside an app’s sign-in never sees that dashboard.

Options, in order of preference:

  1. A nudge in the sign-in flow. When an identity has no recovery method, or a single access method, II shows a short, skippable “protect your identity” step before returning to the app, at most every so often. The app learns nothing, and every app benefits.
  2. An app opt-in. An app that holds user value can ask for that step through an authorize parameter, so it appears where it matters most.
  3. An attribute an app could request with consent, e.g. “has a recovery method: yes/no”, so apps can tailor their own prompts. I’d rank it last, since it reveals something about how an identity is protected.

The legacy UI had an extra recovery nudge (#1248), and recovery email now makes this step much easier for non-technical users than a phrase alone, so it feels like the right time to surface it at sign-in.

Happy to share test notes or try a prototype.

+1 to this, and it’s not only apps holding funds. I run a leaderboard service for game devs, and the developer console supports II sign-in. A dev who signs up with one passkey and loses it would lose access to their games and API keys, and I couldn’t help, because all I see is a principal. I wouldn’t even know it had happened.

Option 1 would cover that without the app learning anything, so that gets my vote. Agree 3 should be last.

Chedz

What if when new user logs in to app, than has 2 option, first confirm that II seed has been saved (uses app normally), second would be to set up username and password from there every user action is executed by app backend.

Can this work?

@sea-snake @aterga a gentle bump, with one new reason.

With #4427 merged, Sign in with Apple will soon give a verified email too, so even more first-time users will arrive through a single Apple, Google or Microsoft sign-in and never add a second way in. The gap above grows with it.

Would the team consider the first option, a skippable “protect your identity” step in the sign-in flow, where the app learns nothing? If it’s on the roadmap, a rough sense of timing would help app builders plan. If not, I’m happy to open an issue or help with a PR.

@Henn91 thanks for the idea. A username and password run by the app’s backend would make the app the one holding the user’s access, which is what II is built to avoid, so I’d rather II prompt for the second way in itself.

Thanks @b3hr4d - we’ll discus this in the next team sync on Monday.

After discussing these ideas, we agree that reminding users of potential gaps in their II’s security posture (e.g., whether they have a recovery phrase) would make sense in the sign in flow. Conversely, we believe II-powered apps should not share this responsibility, nor should they be exposed to information regarding security settings of individual IIs. To allow for designing this feature holistically, we’re going to prioritize it after the upcoming II home page redesign, which we think is the most urgent improvement for II’s UX.

Thanks @aterga and team. That’s the outcome I hoped for: the reminder inside II’s sign-in, with apps learning nothing about an identity’s settings. Until it ships, apps can keep a generic pointer to II’s recovery settings after their key moment, which needs nothing from II. Happy to test the sign-in reminder when it’s ready.