pokelens mini-case study

November 7, 2026

pokelens

design diary & case study

I designed and developed a Pokédex web app with a Pokémon card camera scanner — built quickly to get hands-on with design engineering and shipping in Vercel.

role

designer & developer

timeline

june 2026

tools

Next.js, Tailwind CSS, PokéAPI

context

Pokelens is a Pokédex web app built with Next.js and the PokéAPI . It allows users to search and browse Pokémon by name, type, stats, and even playful community tags like emo, ugly, cute, and blue (these are my tags).

I built it as a quick, scoped project to get comfortable with design engineering . I went straight from ideation and wireframe sketches to building and shipping something real in Vercel, rather than a long design process. I was Inspired by the online community's mini AI assisted cretive projects on platforms like Figma Make and Lovable I started this project to practice my skills in design engineering It's still early: Phase 1 covers browsing, searching, and filtering, with a camera scanner (Phase 2) and the ability to save caught Pokémon (Phase 3) planned as next steps.

what it does

Pokelens is a Pokédex web app for browsing and exploring Pokémon — built with Next.js and the PokéAPI.

current functionality

detail pages

Tap into any Pokémon for a closer look at stats, type, and HP.

community tags

Beyond official stats, Pokémon are tagged with playful community labels — emo, ugly, cute, blue — for a more subjective, fun way to browse.

browse and search

Search Pokémon by name and browse the full list, pulled live from the PokéAPI

type filtering

Filter by type — fire, water, grass, electric, and more — to narrow the list down fast.

coming next: a camera scanner to identify Pokémon cards in real life (Phase 2), and the ability to save caught Pokémon (Phase 3).

process

Process

Pokelens was built as a design-engineering exercise — going straight from design decisions into code, rather than a long research-and-iterate cycle.

Stack
Next.js for the app, the PokéAPI for live Pokémon data, and Tailwind CSS for styling — a lightweight setup for moving fast between design and implementation.

Design in the browser
Instead of designing fully in Figma first, a lot of the layout and interaction decisions were made directly in code — adjusting spacing, filters, and card layouts in real time and deploying straight to Vercel to see it live.

What I was practicing
This project was less about solving a novel design problem and more about building the muscle of shipping — going from an idea to a working, deployed product quickly, without getting stuck in a long design phase first.

what i learned

reflection

Pokelens was small on purpose. I wanted to challenge myself to go straight from design decisions into code. I really pride myself in my design and systems thinking, but I also recognize that all skills need practic and in my case, with having had to learn to program like a designer- I wanted to try to design like a programmer! Working through this project gave me a clearer sense of gave me a clearer sense of what the camera scanner and saved Pokémon would take to build— which made the scope of a "quick project" a lot more honest by the end of it. Beyond that it was also just A FUN exercise in programming, such as working with CV and APIs.

made with love and some more fun stuff

©daisy fernandez-reyes 2026