Personal experiment · In progress

DevBrief

Watchlist → cached transcript → reviewable brief.

Open live product
DevBrief Daily Brief dashboard with completed summaries, key takeaways, and configuration readiness. Channel names are blurred.

What it is

For developers saving videos to revisit, DevBrief keeps the watchlist visible, fetches a transcript when asked, and turns it into a structured brief for review.

Decisions

  • Keep watchlist metadata visible before loading a transcript for the selected item.
  • Make transcript retrieval a manual, explicit action instead of hidden background work.
  • Structure briefs for review: summary, takeaways, risks, and source context beside regenerate actions.

What I cut

Skipped silent auto-summarization of the whole library; fetch and review stay explicit.

What I did

Built the Daily Brief, media library, and structured review flow around an explicit fetch step.

One decision

The difficult choice was silent auto-summarization versus an explicit transcript fetch. I chose a user-initiated fetch: watchlist metadata remains visible before retrieval, and the brief keeps summary, takeaways, risks, and source context together for review. The live flow exposes the fetch action and the case study keeps its personal-experiment limitation.

Screens

DevBrief media library grid with search, filters, and completed video briefs. Channel names and thumbnails are blurred.
Media library: search and filters over a card grid of briefed videos.
DevBrief brief modal with summary, key takeaways, and tags. The source thumbnail and creator name are blurred.
A reviewable brief: summary and takeaways stay on one screen with source context.

Honest boundary

A personal experiment: transcript availability depends on configured providers, and this case study does not claim production users or time saved.

NextCashLift