People to Interview (Report & Criteria)

RnDAO DID SDK – July 2025

1 · Sections & topics to cover

  1. Adoption journey & decision factors – why, when, and how teams choose an auth / identity SDK.
  2. Pain moments – duplicate accounts, multi‑identifier mapping, cross‑app continuity.
  3. Concept reaction – desirability of alias‑based payments (send to e‑mail / @handle).
  4. Competitive toolkit experience – what works/fails in Auth0, Firebase Auth, Supabase, WalletConnect, Privy, Magic, ENS/UD, etc.
  5. Discovery & community hubs – Discord groups, communities, newsletters they trust for auth advice.

2 · Who to speak to ‑ vertical & role quotas

Vertical Survey target Interview target (TBD) Why important
DeFi / Payments 12 Highest pain for duplicate wallets & alias payments.
Productivity / Dev‑tooling 12 Tests cross‑app continuity in multi‑tool workflows.
Collaboration / DAO infra 13 Early adopters of composable identity across org tools.
Gaming / Social‑games 13 Fast‑signup loops expose auth friction quickly.
TOTAL 50 —

3 · Inclusion / exclusion checklist

Dimension Include if… Exclude if…
Primary role Software engineer, tech lead, or PM with experience owning or co‑owning auth/tooling decisions Students, hobbyists, roles with no say in SDK choice；non‑technical stakeholders only
App status Live, public beta, or launching ≤ 6 months Pure internal tooling；browser wallet extensions only
Auth stack Currently using or evaluating at least one of: Firebase Auth, Supabase, Auth0, Cognito, WalletConnect, Privy, Magic, Arcana, custom OAuth No user accounts / sign‑in flow
Identifier complexity Supports ≥ 2 identifiers or has faced duplicate accounts in last 6 months Single‑identifier flows only
Language Comfortable interviewing in English or Spanish —

Guideline not hard rule: a participant may not tick every cell, but the total pool should satisfy the quotas above

4 · Screener questions (Notion)

  1. Role – Dev / PM / Other
  2. What do you care about when using SDKs?
  3. Do you have any frustrations with it?
  4. What have you struggled with using SDKs?
  5. Is there a product person with whom you have build before and can we talk to them?