Summary of "How I Built ANOTHER Profitable App From Scratch SOLO (full journey)"

Overview

Goal: Turn a simple tutorial translation app into a sellable browser extension that produces better, reliable translations/subtitles for foreign YouTube videos.
Result: A Chrome extension injected into the YouTube player that produces translated subtitles via a custom AI pipeline. Chrome Web Store approval in under 24 hours. Early marketing produced ~5 paying customers and roughly $100 MRR after about $100 in ad spend.

Idea validation and product positioning

The project started from a “Polyglot” tutorial and evolved into a painkiller product addressing the creator’s own need: accurate English subtitles for foreign YouTube videos.

Key validation steps:

Researched complaints about YouTube’s auto-translate and found clear demand.
Named the product “Fluently.”
Used a simple idea-evaluation framework:
- Classify ideas as painkiller / vitamin / candy.
- Check search volume and forum complaints.
- See whether people already pay for similar solutions.
- Ensure the app can be explained in one sentence.

Tech stack and development workflow

Heavy use of AI coding agents (referenced as Claude / Claude Code) and agent teams.
Terminal-first workflow and editor-based iteration (mentions of Ghosty terminal and cursor edits).
Frontend & hosting: Next.js for landing page and API, deployed on Vercel.
Extension framework: a browser extension framework (transcript shows an unclear name like “WXT”).
UI: component presets (transcript shows “SHN/CHTN” — likely a UI system such as shadcn).
Backend: Supabase for authentication and database.
Emphasis: AI tools amplify developer productivity but do not replace strong programming fundamentals.

MVP scoping & product design (SLC framework)

SLC = Simple, Lovable, Complete

Simple: A single translate button embedded in the YouTube player that starts translation immediately.
Lovable: Captions must be noticeably better than YouTube’s auto-translate.
Complete: Include reliable translations, authentication, payments, and support.

Landing page best practices:

Focus on copy (clear headline/subheadline), design, and social proof.
Keep sections minimal for early launch: hero + demo, how-it-works, pricing, FAQ.

Pricing model:

Free tier
$9.99/month (casual)
$24.99/month (power users)

Core technical implementation

The extension injects a content script into the YouTube player to render a translate button and start the translation pipeline on click.
Major technical challenge: YouTube rate limits and blocks bots/scrapers.
- Solution: a custom pipeline that extracts raw audio from videos and uses dedicated AI models to transcribe and translate into subtitle formats. Implementation details are intentionally not disclosed.
UI consistency is maintained via component presets shared between the web app and the extension.

Marketing and go-to-market

Assets created:

Chrome Web Store listing visuals
Product demo

Channels tried and results:

X (Twitter): modest results
Product Hunt: ~85 upvotes, ranked #13
LinkedIn: low impact
Reddit: high potential but restrictive for self-promotion

Paid ads experiment:

Spent ≈ $100 → ~150k impressions → ~400 clicks → 26 registrations → 5 paid customers → ≈ $100 MRR
Creator’s takeaway: paid ads are not recommended for most early-stage, low-budget apps — used here to learn the process.

Automations and community tactics:

Built an autonomous “skill/agent” (with Chrome browser access) to search Reddit, find threads, and generate pre-written responses for outreach. This automation is available to Startup Club members.

Recommended long-term strategy:

Focus on organic, short-form content (Reels / Shorts / TikTok) targeted to niche audiences (anime, K-drama, and other heavy foreign-content consumers) to drive low-cost, high-intent traffic and to improve storytelling/hooks.

Lessons, recommendations & tactics

Use the SLC framework to scope an MVP that delivers real value quickly.
Landing page fundamentals matter: crystal-clear headline + demo; address common objections in FAQ; keep design simple.
AI tooling is a force multiplier — not a substitute for coding fundamentals.
Prefer organic content and community channels over paid ads for early traction unless you have budget and experience.
Turn tutorial projects into product ideas by asking what real problem they could solve — you may already have a viable product.

Guides, tutorials, and resources mentioned

SLC framework (Simple, Lovable, Complete) — MVP scoping guide.
Landing page checklist: headline, subheadline, demo, how-it-works, pricing, FAQ; focus on copy, design, social proof.
Extension implementation tips: content-script injection into video player; use UI component presets for consistent styling.
Marketing tips: Reddit/community outreach, Product Hunt launch prep, paid ads basics (use with caution), focus on short-form organic content.
Learning resource: “Scriber” (transcript shows “Scribbler/Scriber”) — interactive, project-based coding courses covering front end, full-stack, backend, cybersecurity, and AI engineering (OpenAI API, LangChain). The creator offers a 20% discount link in the video description.
Community: Startup Club — a private community providing skills (e.g., Reddit marketing skill) and indie-hacking guides.

Notes about transcript uncertainties

Some tool names may be mis-transcribed (examples: “Vel” likely Vercel; “SHN/CHTN” likely a UI component system such as shadcn; “WXT” may refer to the webextension framework). The summary interprets these in context but retains the original intent:

Next.js frontend
Vercel hosting
A browser-extension framework
UI component presets
Supabase backend

Main speakers / sources

Video creator / narrator: primary source, solo founder, developer, and marketer of Fluently.
Claude: friend and/or AI assistant referenced for brainstorming and coding help.
Scriber: recommended learning platform.
Startup Club: creator’s private community.
Platforms/tools mentioned: Next.js, Vercel, Supabase, Chrome Web Store, Product Hunt, Reddit, X (Twitter), LinkedIn, and various AI agent tools.