Can AI replace VidNotes?

KINDA · weekend project

price $9.99/moyou'd save $119.88/yrbuild time weekendcategory 🎬 audio & videoreplaced by 0 peoplebuild unverified

The narrow DIY loop is achievable in a weekend: import a file or YouTube URL, transcribe it, generate notes, and save the result locally. VidNotes as a product is broader than that prototype. It maintains ingestion across changing video sites, runs long jobs reliably, ships iOS, Android, web, and a Chrome extension, keeps account state consistent, and exposes the workflow to agents through an API, CLI, and MCP server. Rebuilding all of that is a multi-day integration project with an ongoing operations burden.

the prompt

Build me a local video transcription and study-notes app to replace VidNotes. Requirements:

- A Python 3.12 app using FastAPI, Jinja templates, HTMX, and SQLite FTS5,
  served only on localhost:8787.
- The home screen accepts one YouTube URL or an MP4, MOV, M4A, or MP3 upload;
  use yt-dlp for the URL and ffmpeg to extract mono audio.
- Use the OpenAI Python SDK for timestamped speech-to-text and the Responses API;
  keep the API key in .env and split large audio into chunks with preserved offsets.
- Show queued, extracting, transcribing, generating, complete, and failed states. The
  result page has a player plus a searchable transcript with clickable timestamps.
- Generate a 5-bullet summary, key points, 10 flashcards, and a 5-question quiz
  from the completed transcript, with a button to regenerate each section.
- Store metadata and generated text in SQLite, media under ./data/projects/<uuid>/,
  and export the transcript and notes as Markdown, TXT, SRT, and JSON.
- No accounts and no telemetry. Everything stays local except yt-dlp downloads and
  OpenAI API calls, and each project keeps its original source URL.
- Out of scope: native apps, hosted web, cross-device sync, the Chrome extension,
  Instagram or TikTok extraction, and a public API, CLI, or MCP server.
- Include a README with setup, ffmpeg and yt-dlp installation, .env.example, data
  location, deletion steps, and a warning that source-site changes can break imports.

$ open in your agent (prompt prefilled, you press enter) or copy it raw

why people still pay

People pay for the maintained system around transcription: source adapters that keep working, long-job processing and retries, consistent results across native apps, web, and the extension, synced account state, and stable API, CLI, and MCP access for agents. The recurring value is avoiding integration breakage and operations work, not just getting speech-to-text.

what you lose

xnative iOS and Android apps, a Chrome extension, and cross-device Premium state

xmanaged extraction for TikTok, Instagram, Vimeo, and changing source sites

xbackground processing, queue reliability, and long-video handling

x30+ language polish and prebuilt flashcards, quizzes, and chat

xhosted web, API, CLI, and MCP access for agents

prior art · use these instead of building, if you'd ratherwhisper.cppLocal speech-to-text engine that can replace the hosted transcription step.↗yt-dlpOpen-source media downloader that covers the DIY URL import step.↗