| name | developer-signup-flow |
| description | Design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. Trigger phrases: developer signup, dev registration, OAuth flow, API k |
Developer Signup Flow
When to Use
Use this skill when you need design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. Trigger phrases: developer signup, dev registration, OAuth flow, API key onboarding, reduce signup friction, developer authentication, signup conversion,...
Create signup experiences that respect developers' time and get them to code as fast as possible.
Overview
Developer signup is your first chance to demonstrate that you understand developers. Every unnecessary form field, every extra click, every "verify your email before continuing" is a message that you don't value their time. The best developer signups feel like they barely exist—developers go from "I want to try this" to "I'm writing code" in under 60 seconds.
This skill covers OAuth integration, API key generation UX, progressive profiling, and measuring what actually matters in signup conversion.
Before You Start
Review the /devmarketing-skills/skills/developer-audience-context skill to understand your target developer segments. Signup optimization varies significantly based on whether you're targeting hobbyists exploring on weekends versus enterprise developers evaluating tools for their company.
OAuth Options That Work
The GitHub-First Approach
For developer tools, GitHub OAuth should be your primary option. Here's why:
- Identity verification built-in - Active GitHub accounts have commit history, repos, and social proof
- Scope familiarity - Developers understand GitHub's permission model
- Profile data - You get username, email, and can infer experience level from public activity
- Trust signal - GitHub is where developers already live
Good implementation (Vercel):
- Single "Continue with GitHub" button dominates the page
- Email option available but secondary
- No password creation required
- Immediate redirect to dashboard after OAuth
Bad implementation:
- GitHub, Google, Twitter, LinkedIn, Email, and "Sign up with phone" all given equal prominence
- Requires email verification even after GitHub OAuth
- Asks for additional profile information before showing dashboard
OAuth Option Hierarchy
Prioritize based on your audience:
| Audience | Primary | Secondary | Avoid |
|---|
| Open source developers | GitHub | Email | Google Workspace |
| Startup developers | GitHub | Google | Enterprise SSO |
| Enterprise developers | SSO/SAML | Google Workspace | Social logins |
| Data scientists | GitHub | Google | Twitter |
| Mobile developers | Google | GitHub | Facebook |
Google OAuth Considerations
Google OAuth works well when:
- Your tool integrates with Google Cloud services
- You're targeting Android developers
- Your audience includes non-technical stakeholders (product managers, designers)
Google OAuth fails when:
- Developers use personal Gmail but need to sign up with work identity
- Your tool has no Google ecosystem integration
- You require Google Workspace-specific scopes
Email Signup: When It Makes Sense
Email+password signup should exist but not dominate. It serves:
- Developers in enterprise environments that block OAuth
- Privacy-conscious developers who limit third-party access
- Situations where GitHub/Google accounts don't reflect professional identity
If you support email signup:
- Allow signup with just email—send magic link, don't require password creation
- Never require email verification before showing the dashboard
- Offer "Set password later" for developers who prefer magic links
Reducing Form Fields
The Zero-Field Ideal
The best signup has zero custom fields. Everything you need comes from OAuth:
- Name (from OAuth profile)
- Email (from OAuth profile)
- Username/handle (from GitHub username)
- Avatar (from OAuth profile)
When You Must Ask Questions
If you genuinely need information, defer it:
Bad: Blocking signup
Create Account
- Email
- Password
- Company Name (required)
- Role (required)
- Team Size (required)
- How did you hear about us? (required)
[Create Account]
Good: Progressive collection
Continue with GitHub
[Immediate dashboard access]
[Later, contextually in dashboard]
"To customize your experience, what are you building?"
[ ] API/Backend
[ ] Web app
[ ] Mobile app
[ ] Data pipeline
[Skip for now]
Field Elimination Checklist
For each field you want to add, answer:
- Can we infer this from OAuth profile data?
- Can we infer this from behavior after signup?
- Can we ask this later when context makes it relevant?
- What decision does this field enable that can't wait?
- What's the conversion cost of this field?
Research suggests each additional required field reduces conversion by 5-10%.
API Key Generation UX
Immediate Key Generation
Developers sign up to write code. Show them an API key immediately.
Good implementation (Stripe):
- OAuth compl
