← Portfolio

Web

Coming soon!

Browser-based products and experiments — documented here with the same rigor as mobile and AI work once they ship.

The web section of this portfolio is intentionally empty for now. I am reserving it for public-facing apps and tools that are far enough along to deserve screenshots, architecture notes, and honest retrospectives — not just landing pages or half-finished demos.

When the first project goes live, you will see the full stack story: routing and data boundaries, how auth and deployment are handled, performance trade-offs, and what I would redo on day one if I started again.

01CONTEXT

Problem

It is easy to clutter a portfolio with every spike and tutorial clone. I wanted the opposite: a single place where each web entry represents something I would still defend in a code review and still run myself in production.

That bar means some work stays private until it clears a higher threshold — especially anything that touches other people’s data or needs a support story I am not ready to own yet.

02PROCESS

Approach

Before anything appears under Web, it has to pass a small checklist: a clear primary user, a deploy path I trust, error states that do not blame the user, and documentation that would let someone else onboard without me in the room.

I also want each write-up to include the boring parts that usually get skipped: dependency choices, how I tested across browsers, and where technical debt was accepted on purpose so scope could ship.

03RESULT

Outcome

Until that first release hits the bar, this card stays a promise rather than a project. When it flips, it will be because there is a real URL, a real README, and a case study that reads like a build log — not a sales pitch.

If you are watching this space for collaboration or curiosity, the Mobile and AI sections already have concrete work you can dig into today.

04STACK
  • Next.js (planned)
  • React
  • TypeScript
  • Vercel or similar (TBD)