# Build brief — a focused alternative to VidNotes

> **Verdict:** Partly, if you narrow it · **Buildability:** 49/100 · **Category:** Audio Video
> **Source:** https://www.canitbevibecoded.com/vidnotes
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from VidNotes. Verify current pricing and capabilities before acting.

## Context

**VidNotes** — Turn videos into searchable transcripts and study tools across apps, web, and agent workflows. It currently costs $9.99/mo.

The narrow DIY loop is achievable at small scale: 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 substantial integration project with an ongoing operations burden.

This brief describes a focused, single-operator replacement for the part of VidNotes that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Import a video file or YouTube URL, extract and transcribe its audio, generate structured study notes, search the timestamped transcript, and export the result.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Python 3.12.
- Ffmpeg.
- Yt-dlp.
- Local disk.

### Data and integrations

- OpenAI API key.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

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.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Native iOS and Android apps, a Chrome extension, and cross-device Premium state.
- Managed extraction for TikTok, Instagram, Vimeo, and changing source sites.
- Background processing, queue reliability, and long-video handling.
- 30+ language polish and prebuilt flashcards, quizzes, and chat.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- Reliability at the vendor's scale is an operations problem, not a prompt.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [whisper.cpp](https://github.com/ggml-org/whisper.cpp) — Local speech-to-text engine that can replace the hosted transcription step
- [yt-dlp](https://github.com/yt-dlp/yt-dlp) — Open-source media downloader that covers the DIY URL import step

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/vidnotes