How I Coded ANOTHER Profitable App SOLO (step by step / from scratch / with AI)

Summary of technological/product content (and what the video teaches)

• App idea & purpose: Build a solo web tool that lets users download YouTube video transcripts in bulk from channels or playlists, converting “video-only” knowledge into text they can reuse.
• Use case for customers: The transcripts are meant to be fed into custom AI models and workflows such as:
  • writing better YouTube scripts
  • creating custom AI agents for startup tasks
• Problem being solved: Manual transcript extraction is described as slow and tedious, and the creator claims there aren’t many good bulk solutions.

Market research / competitor analysis

The creator checks competitors to decide how to position the product:

• YouTube transcript.io (mentioned as “YouTube transcript.io IO”)
  • Offers bulk downloading
  • Uses a subscription + credit system
  • Reported 350,000+ users (used as evidence of demand)
  • Creator’s opportunity: compete with a simpler pricing model
• Other sites (“Note GBT” and “Tactic” as auto-captured)
  • Only allow downloading one transcript at a time
  • Used to justify the creator’s focus on bulk + ease

Product planning approach (framework)

• Uses the SLC framework: Simple, Lovable, Complete
  • Simple: single straightforward path—bulk transcript extraction
  • Complete v1: users should sign up → pay → immediately download (deliver value from day one)
  • Avoids “MVP v0.1 complex” approaches; aims for a useful v1 rather than many half-built features.

Tech stack & implementation details

• Front end / API: React + Next.js
• Database & authentication: Supabase
• Payments: Stripe
• Time-saving tooling: uses Tempo to automate setup
  • Claims connecting DB/auth/payments and generating the initial project took under 10 minutes
  • Tempo generates project files and UI/landing page structure from prompts

Tempo UI workflow (tutorial/review-like details)

The video includes a practical tour of Tempo’s interface:

• Tempo has three tabs: Product, Design, Code

  1. Product tab
     • Write product requirements, features, and user flows
     • This context is fed to the AI to reduce hallucinations
  2. Design tab
     • Build UI via click/drag like Figma/Webflow
     • Generates React code
     • Can import custom Figma designs and ask AI to generate matching React code
  3. Code tab
     • Edit files like an editor (VS Code/Cursor-style)
     • GitHub integration for pushing to a repo and version control

• After Tempo-generated setup, the creator:

  • pushed code to GitHub
  • used Cursor to implement core app features

Launch strategy (analysis)

• Launch plan is lightweight:
  • posts to Product Hunt, Hacker News, and Twitter
• Creator’s “hot take”:
  • Product Hunt is generally better for founder-to-founder audiences (indie hackers)
  • Regular customers may not go there to solve niche tool problems
  • Still worth it for backlinks/SEO and potential traffic lift
• Main effort: outreach to ideal customers via niche subreddits and forums, focusing on relationship building instead of broad virality.

Results / early traction metrics

• No viral launch (explicitly discussed as discouraging initially)
• Post-launch outcomes:
  • 13 user signups
  • 6 converting to paying customers
  • £200+ revenue since launch
• Framed as validation that people will pay even early.

Ongoing plan

• The creator intends to iterate with improvements and continue documenting progress on the channel.

Main speakers/sources (end)

• Main speaker: The solo developer/creator of the app (narrator throughout)
• Sources referenced:
  • Competitors: YouTube transcript.io; also “Note GBT” and “Tactic”
  • Tools/services: Tempo, Cursor, GitHub, React/Next.js, Supabase, Stripe, Figma, Webflow