Skip to main content
Week 04 • Track 04 • The Vision

The
Drop.

You've built it. You've debugged it. You've polished it. Now it's time for the world to hear it. Deploy to production and share your URL.

The Mental Model

The studio work is done.

Think of your app like an album. Every phase has led to this moment.

You've Recorded

Built the features. Wrote the code. Created the pages.

You've Mixed

Debugged the errors. Fixed the edge cases. Handled the failures.

You've Mastered

Polished the UI. QA'd the experience. Made it feel right.

Now Press "Release"

Let the world hear it.

The album is ready. Time to drop it.

deploy-status

$ npm run build

✓ Compiled successfully

✓ 16 pages generated

✓ Assets optimized

$ git push origin main

Deploying to production...

LIVE— yourapp.com

The Domain

🌐

Buying Your Domain

Your domain is your address on the internet. Namecheap, Google Domains, or Cloudflare are the most popular registrars. The process is simple.

1Search
2Purchase
3Point Nameservers
https://myapp.com
Available
🆓

Free Alternatives

Don't have a budget for a domain? These free subdomains are perfectly fine to start with.

yourapp.vercel.app
yourapp.netlify.app
username.github.io

Good enough to launch. Upgrade later.

Connecting the Dots

Your domain needs to know where to point. The registrar holds the name, the nameservers route traffic, and Vercel serves your app.

Domain RegistrarNameserversVercelYour App
DNS Configuration

$ dig myapp.com

myapp.com → ns1.vercel-dns.com

Status: Active

SSL: Auto-provisioned

The Production Env

↔️

Development vs Production

DevProd
URLlocalhost:3000myapp.com
Env Vars.env.localDashboard
DataTest dataReal data
ErrorsVerboseClean
🔐

Environment Variables

Environment VariablesProduction
NEXT_PUBLIC_SUPABASE_URL••••••••
NEXT_PUBLIC_SUPABASE_KEY••••••••
DATABASE_URL••••••••

Never commit .env files to git. Add .env.local to your .gitignore immediately.

The Publish Button

“Done is better than perfect.”

1

It doesn't have to be perfect

v1.0 is supposed to be rough. That's why it's called version one. Polish comes later.

2

Nobody is watching yet

Your first deploy gets 0 traffic. Relax. The pressure is entirely self-imposed.

3

You can always update

That's what v1.1 is for. And v1.2. And v2.0. Software is never finished—it's iterated.

The hardest part isn't the code. It's clicking publish.

Common Patterns

Stage Fright

"It's not ready yet"

It never will be. Ship it.

"I need more features first"

MVP means Minimum. Ship the minimum.

"What if people judge it?"

They won't. They're too busy with their own stuff.

"I'll deploy manually"

Automate it. Push to main = deploy.

The Drop

"Ship early, ship often"

Every deploy is practice. The more you ship, the less scary it gets.

"Share the URL immediately"

Accountability drives completion. Share it before you overthink it.

"Monitor after launch"

Check Vercel analytics for errors. Fix what breaks in production.

"Celebrate the milestone"

You built and shipped a real product. That puts you ahead of 99% of people who just talk about it.

The Final Exam

Graduate from Building and Bopping.

01

The Deploy

Ship It

  • Connect repo to Vercel
  • Push to main
  • Wait for build to finish
  • Visit your live URL
Goal: App is live on the internet
02

The Domain

Claim It

  • (Optional) Buy a domain
  • Add DNS records
  • Verify HTTPS works
Goal: Custom address secured
03

The Share

Announce It

  • Copy your live URL
  • Share on social media
  • Celebrate
Goal: The world knows

📋 Quick Reference

Deploy

git push origin main triggers auto-deploy on Vercel.

Domain

Add A record pointing to 76.76.21.21 (Vercel).