PokéPull - The 1 Hour Next.js Implementation

I sat down around 6:30 and decided to keep it stupid simple: build a tiny front end for the Pokémon API and ship it in one sitting.

By about 7:30 it was done and live. The app is dead simple on purpose. One button, one toggle (All vs. Original 151), one random Pokémon. Delivered via the public API. Polished with proper loading skeletons, a real error state with retry, and a small pull history so it doesn’t feel empty.

Under the hood it’s a Next.js app with a server-side proxy so the browser never touches the API directly. Hosting is AWS Amplify because I wanted this to be boring and stable, not “clever.”

One hour. One clean deploy. No fluff.