Skip to main content
강홍재/ James
← Work
Archived2026 · Solo Builder· Started(First Commit date)

Easy Trend Explainer

Daily-refresh service that has AI break down today's trends into four categories.

  • Next.js
  • AI
  • Vercel KV
Screenshots
  • Home - today's trending keyword ranking plus a channel-based knowledge feed on one screen

  • Explorer - narrow the feed by topic chips, switch between knowledge, keyword, and date views

  • Search - popular keyword chips give the empty state a first move

  • My page - bookmarks, reading history, and settings in one place

  • Settings - font size, theme, and storage controls tuned for a tool people open daily

  • Login screen - the line "you can read freely without signing in" preserves the no-signup entry

Setup

Problem

Even when you see a trending keyword, "why is this trending?" is a separate search. For someone who wants the context quickly, a one-line summary isn't enough; a long article is too heavy.

Context

A lightweight curation experiment - auto-generated daily, with bookmarks and a read history.

Hypothesis

Break a keyword into four categories (overview, background, impact, related) and the "why is this trending?" lands within five minutes.

Build

What I did
  • Daily auto-collection of trends plus the AI generation pipeline for per-category explanations
  • Bookmark / read-history / per-card sharing UI
Product decisions
  • No-signup entry - matches the identity of a light tool you come back to every day
  • Uniform article length - consistency is what builds the habit of checking it daily
QA considerations
  • Daily auto-generation - guard the regression so one failure can't spread across several days (invisible piled-up regression)
  • Schema validation at each generation step on the four categories (overview, background, impact, related) so malformed output never reaches the reader
  • On a collect/generate pipeline failure, a fallback keeps at least the prior day's state
  • If the daily cron fails silently the content goes stale, so there's a way to detect and surface that failure
  • Uniform article length is actually enforced on every generation so the consistent "check it daily" rhythm doesn't break
  • The AI explanation renders "why is this trending?" for the keyword without drifting from fact (explanation accuracy)
  • The no-signup entry is preserved while bookmarks and read history stay consistent with user state even as content is swapped out daily

Outcome

Metrics

The deployment has been taken down. Traffic and return-visit numbers were never measured while it ran, and there is no reachable address for it now.

Tech stack
  • Next.js
  • Vercel
  • Vercel KV