0. the idea

I wanted a place to just look up a movie fast — rating, cast, runtime, a synopsis that isn't three paragraphs of marketing copy — without the ten seconds of cookie banners and autoplay trailers that come with most movie sites.

moviebuzzfeed is a small React app that does exactly that: search a title, get the essentials, move on.

1. stack

The whole thing is a React + TypeScript single-page app. I actually built the first prototype inside StackBlitz — spinning up a full Node environment right in the browser tab meant I could go from idea to a working search box in about ten minutes with zero local setup. I pulled it down to develop locally once the shape of the app was clear.

What's doing what:
  • React + TypeScript for the UI and type-safe API responses
  • A public movie metadata API for posters, ratings, cast, and synopses
  • Vercel for hosting and preview deploys on every push

2. features

What it does:
  • Live search-as-you-type with debounced requests
  • Poster, rating, runtime, and synopsis on one card — no extra clicks
  • A trending/popular rail on the home screen
  • Responsive layout that works as a quick lookup on mobile

3. a challenge — noisy search

Firing an API request on every keystroke is an easy way to get rate-limited and make the UI feel janky. The fix was a debounced search hook that waits for a short pause in typing before firing, plus caching identical queries so re-typing something you already searched is instant.

Debounce the request, not the input state — keep the input itself perfectly responsive and only delay the network call. Anything else feels laggy even if the network is fast.

4. the code

function useDebouncedSearch(query: string, delay = 350) {
  const [debounced, setDebounced] = useState(query);

  useEffect(() => {
    const id = setTimeout(() => setDebounced(query), delay);
    return () => clearTimeout(id);
  }, [query, delay]);

  return debounced;
}

5. what i learned

Typing the shape of an external API response in TypeScript up front saved me from a bunch of 'cannot read property of undefined' bugs later — movie APIs love to make fields optional in ways you don't notice until an obscure title breaks your card layout. And for a lookup tool like this, speed beats completeness every time.