Build a Portfolio of Three Small Apps You Actually Use

A good vibe-coder portfolio isn't a gallery — it's three tiny apps you open every week. Here is the capstone plan to build yours.

45 min · Reviewed 2026

The Portfolio That Actually Gets Used

Most beginner portfolios are graveyards of half-finished demos. A better measure: three small apps that you open every week because they solve a real problem for you. That is a portfolio that hires itself.

A tracker — something you log daily (workouts, mood, reading, expenses)
A tool — something that replaces a Google Doc you hate (meal planner, trip brain, study flashcards)
A shareable — something other humans touch (a tiny site for a club, a gift, a friend's business)

Layer	Pick	Why
Builder	Lovable or v0 + Cursor	Covers everything vibe coders need
Database	Supabase	Free tier, auth + DB in one
Hosting	Vercel	One-click deploys, preview URLs
Domain	Namecheap or Porkbun	Eight dollars a year each

Capstone plan — 3 weekends, 3 apps.

Weekend 1 — Tracker
  Prompt: "Build me a [habit] tracker with daily logs and monthly charts."
  Deploy. Use it every day for two weeks.

Weekend 2 — Tool
  Prompt: "Build me a [tool] that replaces the Google Doc I keep copying."
  Deploy. Use it yourself first. Improve one thing per week.

Weekend 3 — Shareable
  Prompt: "Build a site for [club/gift/friend]."
  Deploy. Share the URL with three real humans. Listen.This is a real 3-weekend capstone. At the end you have shipped three working apps you and others actually touch.

Post a short write-up of each app on Twitter, LinkedIn, or a personal site
Add a link to each deployed app in your resume or bio
Pick the one with the most pull and go deeper — more features, real users
Teach a friend to vibe-code by cloning one of your repos

The big idea: a vibe-coder's best portfolio isn't polished screenshots, it's three tiny apps you can't stop using. Build those, share them honestly, and doors will open you didn't expect.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-vibecoder-portfolio-of-three

What is the defining characteristic of a strong vibe-coder portfolio according to this approach?
1. A collection of tutorial projects following coding courses
2. A single complex application with many features
3. Polished screenshots of impressive demos
4. Three tiny apps you open every week because they solve real problems
Which of these would qualify as the 'tool' category in the three-part portfolio framework?
1. A meal planner that replaces a Google Doc you hate
2. A website built for a friend's small business
3. A workout logging app used daily
4. A mood tracking journal
What does 'dogfooding' mean in the context of this portfolio approach?
1. Using your own app regularly to discover bugs and improvements
2. Building apps only for hypothetical users
3. Testing your app on users in a controlled environment
4. Selling your app to paying customers
Why is the 'shareable' app considered the most challenging category in this portfolio?
1. Watching a real human use your software creates the biggest skill jump
2. It requires the most complex technical architecture
3. It must generate revenue immediately
4. It needs to be free and open source
Which technology combination is recommended for the 'Builder' layer in the portfolio stack?
1. React and Node.js
2. Lovable or v0 plus Cursor
3. Figma and Webflow
4. WordPress and PHP
What advantage does Supabase offer for the portfolio apps?
1. It offers unlimited domains for free
2. It automatically handles all hosting and deployments
3. Its free tier includes both authentication and database in one service
4. It provides the best AI code generation
What benefit does Vercel provide as the recommended hosting solution?
1. It requires manual server configuration
2. It offers one-click deploys with preview URLs
3. It only hosts Python applications
4. It charges per user visit
After building your three portfolio apps, what should you do with the one that shows the most traction?
1. Only keep it as a backup
2. Abandon it and start something new
3. Delete it and start over
4. Go deeper with more features and real users
What is suggested as the final step in demonstrating your portfolio to others?
1. Teach a friend to vibe-code by cloning one of your repos
2. Submit your apps to app stores for review
3. Charge money for all three apps
4. Keep the code private and only show the live app
What does 'capstone' refer to in this curriculum context?
1. A specialized advanced course
2. A mandatory final exam
3. A technical documentation requirement
4. The three-app portfolio project that synthesizes all learned skills
Why does the lesson recommend posting write-ups on Twitter, LinkedIn, or a personal site?
1. To compete with professional marketing teams
2. To demonstrate your work and open unexpected opportunities
3. To get paid for your portfolio projects
4. Because the apps cannot be shared any other way
What is the primary reason the lesson gives for why apps built for hypothetical users tend to fail?
1. They require too many dependencies
2. They cost too much to maintain
3. They don't get real feedback from actual usage
4. They are technically too complex
What is the 'big idea' that the lesson emphasizes as the core message about vibe-coder portfolios?
1. A portfolio should showcase the most technically impressive projects
2. The best portfolio isn't polished screenshots but three tiny apps you can't stop using
3. You need at least ten projects to be hireable
4. Only complex machine learning projects impress employers
Which category would a flashcard study app fall under in the three-part portfolio framework?
1. Shareable
2. Tool
3. Tracker
4. None of these
What distinguishes a 'tracker' app in the portfolio framework from other categories?
1. It tracks user analytics for businesses
2. It tracks competitor products in the market
3. It involves daily logging of something personal like workouts, mood, or expenses
4. It requires GPS tracking capabilities

← Back to interactive lesson

Tendril · Creators · AI-Assisted Coding

Build a Portfolio of Three Small Apps You Actually Use

A good vibe-coder portfolio isn't a gallery — it's three tiny apps you open every week. Here is the capstone plan to build yours.

45 min · Reviewed 2026

The Portfolio That Actually Gets Used

A tracker — something you log daily (workouts, mood, reading, expenses)
A tool — something that replaces a Google Doc you hate (meal planner, trip brain, study flashcards)
A shareable — something other humans touch (a tiny site for a club, a gift, a friend's business)

Layer	Pick	Why
Builder	Lovable or v0 + Cursor	Covers everything vibe coders need
Database	Supabase	Free tier, auth + DB in one
Hosting	Vercel	One-click deploys, preview URLs
Domain	Namecheap or Porkbun	Eight dollars a year each

Capstone plan — 3 weekends, 3 apps.

Weekend 1 — Tracker
  Prompt: "Build me a [habit] tracker with daily logs and monthly charts."
  Deploy. Use it every day for two weeks.

Weekend 2 — Tool
  Prompt: "Build me a [tool] that replaces the Google Doc I keep copying."
  Deploy. Use it yourself first. Improve one thing per week.

Weekend 3 — Shareable
  Prompt: "Build a site for [club/gift/friend]."
  Deploy. Share the URL with three real humans. Listen.This is a real 3-weekend capstone. At the end you have shipped three working apps you and others actually touch.

Post a short write-up of each app on Twitter, LinkedIn, or a personal site
Add a link to each deployed app in your resume or bio
Pick the one with the most pull and go deeper — more features, real users
Teach a friend to vibe-code by cloning one of your repos

The big idea: a vibe-coder's best portfolio isn't polished screenshots, it's three tiny apps you can't stop using. Build those, share them honestly, and doors will open you didn't expect.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-vibecoder-portfolio-of-three

What is the defining characteristic of a strong vibe-coder portfolio according to this approach?
1. A collection of tutorial projects following coding courses
2. A single complex application with many features
3. Polished screenshots of impressive demos
4. Three tiny apps you open every week because they solve real problems
Which of these would qualify as the 'tool' category in the three-part portfolio framework?
1. A meal planner that replaces a Google Doc you hate
2. A website built for a friend's small business
3. A workout logging app used daily
4. A mood tracking journal
What does 'dogfooding' mean in the context of this portfolio approach?
1. Using your own app regularly to discover bugs and improvements
2. Building apps only for hypothetical users
3. Testing your app on users in a controlled environment
4. Selling your app to paying customers
Why is the 'shareable' app considered the most challenging category in this portfolio?
1. Watching a real human use your software creates the biggest skill jump
2. It requires the most complex technical architecture
3. It must generate revenue immediately
4. It needs to be free and open source
Which technology combination is recommended for the 'Builder' layer in the portfolio stack?
1. React and Node.js
2. Lovable or v0 plus Cursor
3. Figma and Webflow
4. WordPress and PHP
What advantage does Supabase offer for the portfolio apps?
1. It offers unlimited domains for free
2. It automatically handles all hosting and deployments
3. Its free tier includes both authentication and database in one service
4. It provides the best AI code generation
What benefit does Vercel provide as the recommended hosting solution?
1. It requires manual server configuration
2. It offers one-click deploys with preview URLs
3. It only hosts Python applications
4. It charges per user visit
After building your three portfolio apps, what should you do with the one that shows the most traction?
1. Only keep it as a backup
2. Abandon it and start something new
3. Delete it and start over
4. Go deeper with more features and real users
What is suggested as the final step in demonstrating your portfolio to others?
1. Teach a friend to vibe-code by cloning one of your repos
2. Submit your apps to app stores for review
3. Charge money for all three apps
4. Keep the code private and only show the live app
What does 'capstone' refer to in this curriculum context?
1. A specialized advanced course
2. A mandatory final exam
3. A technical documentation requirement
4. The three-app portfolio project that synthesizes all learned skills
Why does the lesson recommend posting write-ups on Twitter, LinkedIn, or a personal site?
1. To compete with professional marketing teams
2. To demonstrate your work and open unexpected opportunities
3. To get paid for your portfolio projects
4. Because the apps cannot be shared any other way
What is the primary reason the lesson gives for why apps built for hypothetical users tend to fail?
1. They require too many dependencies
2. They cost too much to maintain
3. They don't get real feedback from actual usage
4. They are technically too complex
What is the 'big idea' that the lesson emphasizes as the core message about vibe-coder portfolios?
1. A portfolio should showcase the most technically impressive projects
2. The best portfolio isn't polished screenshots but three tiny apps you can't stop using
3. You need at least ten projects to be hireable
4. Only complex machine learning projects impress employers
Which category would a flashcard study app fall under in the three-part portfolio framework?
1. Shareable
2. Tool
3. Tracker
4. None of these
What distinguishes a 'tracker' app in the portfolio framework from other categories?
1. It tracks user analytics for businesses
2. It tracks competitor products in the market
3. It involves daily logging of something personal like workouts, mood, or expenses
4. It requires GPS tracking capabilities

← Back to interactive lesson