demo-apps

No client brief. Just me, learning by building.

Small, self-directed projects outside of client work — mostly how I'm picking up Next.js, TypeScript, and full-stack patterns like auth and databases. Each one below is planned or in progress.

4 apps planned
in progress
Food Tracker
Why: Postgres schema design, server-side data modeling

Multi-user food logging app backed by Neon Postgres — daily macro targets, meal logging, and a searchable food database.

  • Neon Postgres relational schema
  • Server Actions for all data mutations
  • Dummy multi-user login — no real accounts, no real risk
  • Per-user limits to keep the demo database small
Next.jsNeonServer Actions
in progress
Pokémon Playground
Why: Custom game-loop architecture, collision systems, full-stack persistence

A top-down exploration game built entirely in Next.js — walk a hand-built map, trigger zone-based events, and catch Pokémon using data sourced from PokéAPI and persisted to a Neon database.

  • Custom movement + animation engine (no game library)
  • Zone-based collision & trigger detection
  • PokéAPI-sourced encounter data
  • Neon Postgres persistence for caught Pokémon
Next.jsPokéAPINeon
planned
Movie Diary
Why: Auth flows, relational data modeling with Neon

A personal movie-watching log — auth, ratings, and notes per film, backed by a relational schema in Neon Postgres.

  • NextAuth-based authentication
  • Relational schema — users, films, ratings
  • Per-film notes & star ratings
Next.jsNeonNextAuth
planned
Component Sandbox
Why: A sandbox for testing UI patterns before using them live

A running library of reusable React components — filter bars, cards, form patterns — built and tested here before landing in client or personal projects.

  • Reusable UI pattern library
  • Built with shadcn/ui + Tailwind
  • Staging ground before components land in client work
ReactTailwindshadcn/ui