People to interview (Report & Criteria)

People to Interview (Report & Criteria)

RnDAO DID SDK – July 2025

1 · Sections & topics to cover

Adoption journey & decision factors – why, when, and how teams choose an auth / identity SDK.

Pain moments – duplicate accounts, multi‑identifier mapping, cross‑app continuity.

Concept reaction – desirability of alias‑based payments (send to e‑mail / @handle).

Competitive toolkit experience – what works/fails in Auth0, Firebase Auth, Supabase, WalletConnect, Privy, Magic, ENS/UD, etc.

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)

Role – Dev / PM / Other

What do you care about when using SDKs?

Do you have any frustrations with it?

What have you struggled with using SDKs?

Is there a product person with whom you have build before and can we talk to them?

If yes, how can we contact you? Please lave your email, telegram, or preferred communication channel below

Drea’s version

Survey comments

What’s your role – Dev / PM / Other

What’s the last Login SDK you chose and implemented? (short answer)

Why did you pick that one? (short answer)

How would you rate it? (1-5 rating, not at all satisfied… very satisfied)

If there was one thing you could improve in Login SDK’s, what would it be?

Are you up for a conversation about this? If yes, how can we contact you? Please leave your email, telegram, or preferred communication channel below

5 · Outreach channels & hooks

Channel	Initial post / DM – SURVEY CTA	Follow-up after survey – INTERVIEW CTA	Why it works
Slack / Discord (#web3-dev, #Product-Led-Growth, #GameDev, Supabase, Auth0)	“🪄 Merge Google + Discord + Wallet into ONE account? Tell us what sucks → 3-min survey, <survey>. We’ll invite the best takes to a paid 1-hour call.” (pin message; reply to questions with emoji)	“Loved your duplicate-account war story 🤯. Wanna get a sanity-check a fix? We would love to hear you on a paid interview to understand more on it…Calendly: <link> (45 min).”	Community trust + public thread builds FOMO; DMs feel personal.
Farcaster / Lens + Twitter/X thread	Tweet 1: “5 login horrors destroying user funnels 👇” Tweet 2: “Help us nuke them. 3-min survey <survey> 💸” (Use polls/graphics; tag #buildinpublic #devrel)	ㅤ	High viral surface + public poll sparks discussion; direct replies convert the loudest voices.
LinkedIn filtered DM (Eng Lead OR PM AND “Auth0”/“Supabase”/“Magic.link”)	“<Name>, congrats on shipping <feature>! We’re mapping auth headaches for an open DID SDK. Would you answer 5 short questions Survey: <link>.	“Thanks for the survey—insightful! Could we book 45 min (X$) to review these common issues and learn how you choose auth SDKs? My calendar: <Calendly>.”	Hyper-personalised; appeals to professional pride; corporate devs like incentives framed as “consulting honorarium.”
Newsletter (RnDAO)	“Stop losing users at login. Take our 3-min survey → win early access to a cross-app DID SDK. <survey link>”	Automated e-mail to qualified respondents: fw/ Calendly invite.	One-to-many blast quickly tops up survey quota if social channels lag.

6 · Incentives

7 · Expected timeline (14‑day sprint)

Day 1‑2 – Launch screener in all channels.

Day 5 – First batch of surveys received.

Day 8 – Survey n≈50 closed; interim quotas review.

Day 10 – Interview scheduling.

Day 14 – Initial report on conversations

People to interview (Report & Criteria)

People to Interview (Report & Criteria)

RnDAO DID SDK – July 2025

1 · Sections & topics to cover

Adoption journey & decision factors – why, when, and how teams choose an auth / identity SDK.

Pain moments – duplicate accounts, multi‑identifier mapping, cross‑app continuity.

Concept reaction – desirability of alias‑based payments (send to e‑mail / @handle).

Competitive toolkit experience – what works/fails in Auth0, Firebase Auth, Supabase, WalletConnect, Privy, Magic, ENS/UD, etc.

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)

Role – Dev / PM / Other

What do you care about when using SDKs?

Do you have any frustrations with it?

What have you struggled with using SDKs?

Is there a product person with whom you have build before and can we talk to them?

If yes, how can we contact you? Please lave your email, telegram, or preferred communication channel below

Drea’s version

Survey comments

What’s your role – Dev / PM / Other

What’s the last Login SDK you chose and implemented? (short answer)

Why did you pick that one? (short answer)

How would you rate it? (1-5 rating, not at all satisfied… very satisfied)

If there was one thing you could improve in Login SDK’s, what would it be?

Are you up for a conversation about this? If yes, how can we contact you? Please leave your email, telegram, or preferred communication channel below

5 · Outreach channels & hooks

Channel	Initial post / DM – SURVEY CTA	Follow-up after survey – INTERVIEW CTA	Why it works
Slack / Discord (#web3-dev, #Product-Led-Growth, #GameDev, Supabase, Auth0)	“🪄 Merge Google + Discord + Wallet into ONE account? Tell us what sucks → 3-min survey, <survey>. We’ll invite the best takes to a paid 1-hour call.” (pin message; reply to questions with emoji)	“Loved your duplicate-account war story 🤯. Wanna get a sanity-check a fix? We would love to hear you on a paid interview to understand more on it…Calendly: <link> (45 min).”	Community trust + public thread builds FOMO; DMs feel personal.
Farcaster / Lens + Twitter/X thread	Tweet 1: “5 login horrors destroying user funnels 👇” Tweet 2: “Help us nuke them. 3-min survey <survey> 💸” (Use polls/graphics; tag #buildinpublic #devrel)	ㅤ	High viral surface + public poll sparks discussion; direct replies convert the loudest voices.
LinkedIn filtered DM (Eng Lead OR PM AND “Auth0”/“Supabase”/“Magic.link”)	“<Name>, congrats on shipping <feature>! We’re mapping auth headaches for an open DID SDK. Would you answer 5 short questions Survey: <link>.	“Thanks for the survey—insightful! Could we book 45 min (X$) to review these common issues and learn how you choose auth SDKs? My calendar: <Calendly>.”	Hyper-personalised; appeals to professional pride; corporate devs like incentives framed as “consulting honorarium.”
Newsletter (RnDAO)	“Stop losing users at login. Take our 3-min survey → win early access to a cross-app DID SDK. <survey link>”	Automated e-mail to qualified respondents: fw/ Calendly invite.	One-to-many blast quickly tops up survey quota if social channels lag.

6 · Incentives

7 · Expected timeline (14‑day sprint)

Day 1‑2 – Launch screener in all channels.

Day 5 – First batch of surveys received.

Day 8 – Survey n≈50 closed; interim quotas review.

Day 10 – Interview scheduling.

Day 14 – Initial report on conversations